Talk:Dojo Toolkit

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Internet (Rated B-class, Mid-importance)
WikiProject icon This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
B-Class article B  This article has been rated as B-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.

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 —Preceding unsigned comment added by (talk) 14:58, 29 December 2008 (UTC)

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.


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)


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?[edit]

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[edit]

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)


I added information on Dijit and I merged Dijit.Editor into the article. -id1337x —Preceding unsigned comment added by Id1337x (talkcontribs) 19:56, 24 December 2008 (UTC)

New Feature Section: "Widget Development"[edit]

Dojo doesn't just provide the "Dijit" widgets - it provides an entire system for building your own widgets; either by inheriting base mixin classes (i.e. "_Widget" and "_Templated") or extending the higher level widget classes such as Accordion or Dialog. The system includes the ability to easily create one-off in-page widgets right up to templated, configurable widgets with as much complexity as any of the Dijits. These can all be created within the Dijit namespace, or a custom application-specific one. I'd like to add a section on this, and am just looking for feedback. PeteOtaqui (talk) 14:55, 19 January 2009 (UTC)

What you wrote seems a bit advertisement-ish, clean it up and I'm sure nobody will have a problem with adding it. Psychcf (talk) 03:16, 20 January 2009 (UTC)

I'd suggest removing the words before the first dash and replace the "it" after the dash with either "Dojo" or "Dijit". Then it reads fine to me. Martin Packer (talk) 09:21, 20 January 2009 (UTC)

Feedback: This section could have good value but not unless it begins with a definition of all of the terms used. Wikipedia is the place people go -- or hopes to be, does it not? -- if you don't know anything about he subject. At least, this seems the case with Dojo -- or I'd be reading the Wiki for the Toolkit. To me, the "system for building your own widgets" exists within JavaScript's object hierarchy and (object) model. At this point, I do not know what are "_Widget" and "_Templated". Whether or not something is "easy" is relative and subjective. What is "one-off", "in-page". A template is something you can make but it isn't something you can do so I do not understand "templated", either -- unless it is the same thing as a word I use, which is "templatized" and means a thing has been converted into a template from which other things can be made. These thoughts should not sound nitpicky; I really am confused. :-) —Preceding unsigned comment added by Kernel.package (talkcontribs) 15:11, 20 January 2009 (UTC)

Content in "List of Web Application Frameworks"[edit]

An example of a language is PHP. Fusebox is not a language. The entry of Fusebox under "Other languages" should be removed. As a framework it should be added to the PHP entry.

If Drupal is a framework for PHP and not an application, the so are Wordpress, Mambo, and Joomla, aren't they? Kernel.package (talk) 15:23, 20 January 2009 (UTC)

Content in "List of Web Application Frameworks"[edit]

An example of a language is PHP. Fusebox is not a language. The entry of Fusebox under "Other languages" should be removed. As a framework it should be added to the PHP entry.

If Drupal is a framework for PHP and not an application, then so are Wordpress, Mambo, and Joomla, aren't they? Kernel.package (talk) 15:23, 20 January 2009 (UTC)

Sun Microsystems[edit]

Sun Microsystems is listed as a sponsor/member of the Dojo Foundation. Since Sun is now Oracle America, should this be updated? I'm not sufficiently trademark savvy to know what the proper entry should be here. Skinrider (talk) 13:37, 15 June 2012 (UTC)