Talk:Dojo Toolkit: Difference between revisions
m Signing comment by Id1337x - "" |
No edit summary |
||
| Line 13: | Line 13: | ||
|| This article was nominated for [[Wikipedia:Deletion policy|deletion]] on [[2006-03-07]]. The result of [[Wikipedia:Articles for deletion/{{{votepage|{{PAGENAME}}}}}|the discussion]] was {{{result|'''keep'''}}}. |
|| This article was nominated for [[Wikipedia:Deletion policy|deletion]] on [[2006-03-07]]. The result of [[Wikipedia:Articles for deletion/{{{votepage|{{PAGENAME}}}}}|the discussion]] was {{{result|'''keep'''}}}. |
||
|} |
|} |
||
The section "[http://en.wikipedia.org/wiki/Dojo_Toolkit#Developing_Dojo Developing Dojo]" is misleading. Dojo is just javascript; development can occur in any text editor or IDE (ie Notepad, Gedit, TextMate, Eclipse, Dreamweaver, etc etc etc). --Matt Kantor 29 December 2008 |
|||
I think this article should be deleted and an external link to DoJo wiki pages should be provided, so that community could seek the latest updated information. |
I think this article should be deleted and an external link to DoJo wiki pages should be provided, so that community could seek the latest updated information. |
||
Revision as of 14:58, 29 December 2008
 | The article Dijit Editor was nominated for deletion. The discussion was closed on 08 December 2008 with a consensus to merge the content into Dojo Toolkit. If you find that such action has not been taken promptly, please consider assisting in the merger instead of re-nominating the article for deletion. To discuss the merger, please use this talk page. Do not remove this template after completing the merger. A bot will replace it with {{afd-merged-from}}. |
 | Internet B‑class High‑importance  | ||||||||||||
| |||||||||||||
|
This article was nominated for deletion on 2006-03-07. The result of the discussion was keep. |
The section "Developing Dojo" is misleading. Dojo is just javascript; development can occur in any text editor or IDE (ie Notepad, Gedit, TextMate, Eclipse, Dreamweaver, etc etc etc). --Matt Kantor 29 December 2008
I think this article should be deleted and an external link to DoJo wiki pages should be provided, so that community could seek the latest updated information.
Adding and maintaining information to this page will be redundant.
-saM
- Except for the dojo wiki is not NPOV and ISN'T wikipedia. The purpose of this page is not to provide advertising or help with using for dojo. It is to provide information about dojo.--Grimboy 21:16, 31 January 2007 (UTC)
The following text has been deleted, feel free to put it back once it has been adapted to be less annoying and advertisingish.
""" Dojo allows you to easily build dynamic capabilities into web pages and any other environment that supports JavaScript sanely. You can use the components that Dojo provides to make your web sites more useable, responsive, and functional. With Dojo you can build degradeable user interfaces more easily, prototype interactive widgets quickly, and animate transitions. You can use the lower-level APIs and compatibility layers from Dojo to write portable JavaScript and simplify complex scripts. Dojo's event system, I/O APIs, and generic language enhancement form the basis of a powerful programming environment. You can use the Dojo build tools to write command-line unit-tests for your JavaScript code. You can use the Dojo package system to make your code easier to maintain and less platform dependent. The Dojo build process helps you optimize your JavaScript for deployment by grouping sets of files together and reuse those groups through "profiles".
Dojo does all of these things by layering capabilities onto a very small core which provides the package system and little else. When you write scripts with Dojo, you can include as little or as much of the available APIs as you need to suit your needs. Dojo provides MultiplePointsOfEntry, InterpreterIndependence, ForwardLookingAPIs, and focuses on ReducingBarriersToAdoption.
Dojo is being built around a single markup language that will provide application authors with a (more) simple way of declaring and using responsive DHTML interface components. Renderings may be made available in several rendering contexts (such as SVG, or perhaps even the desktop or Flash), but the markup language (DojoML) and scripting language (JavaScript) will not change. Better yet, the DojoML parser accepts extended HTML and SVG as valid input, and can be used to easily create DegradeableResponsiveApplications.
The adoption of the Dojo Toolkit is being promoted by the Dojo Foundation. """ --Grimboy 14:42, 1 July 2006 (UTC)
I've tried to improve this page and have stubbed it out with some topics which can be expanded.--Grimboy 23:34, 2 July 2006 (UTC)
Cleanup
I've taken a first stab at cleaning up the article to be more suitable for Wikipedia; let's see how things go for a little while, then see about removing the cleanup tag.
Things that would be nice to add:
- A little history of Dojo, and its relationship with Jot.
- More information on development, and the contributions from Sun and IBM.
Ubernostrum 07:43, 14 July 2006 (UTC)
More info on the structure of dojo?
I would like to see some more info on how dojo is laid out, perhaps cover the different namespaces and what type of things you can find in each. Also, I think it would be beneficial if the article covered how dojo works in many different environments, such as adobe AIR, aptana jaxer, etc. Psychcf (talk) 00:55, 15 April 2008 (UTC)
Adobe AIR
I added a brief section on AIR support. Anyone care to expand on it a bit? It's worthwhile as it stands but probably could use more info. Martin Packer (talk) 08:17, 12 July 2008 (UTC)
- I just added in a short description of Dojo Toolbox, an AIR app that Sitepen made using Dojo. The section still needs more info though. Psychcf (talk) 17:58, 21 September 2008 (UTC)
Dijit
I added information on Dijit and I merged Dijit.Editor into the article. -id1337x —Preceding unsigned comment added by Id1337x (talk • contribs) 19:56, 24 December 2008 (UTC)