[ng-dhtml] putting the build tool thing to bed

Alex Russell alex at dojotoolkit.org
Tue Sep 28 00:23:43 CDT 2004

Hash: SHA1

On Monday 27 September 2004 9:54 pm, Tom Trenka wrote:
> > Martin Cooper wrote:
> > |> Whoa. I can see the docs now: "To build Dojo yourself from
> > |> source, first install Subversion, Java, Ant, Python, Docutils
> > |> and Rhino. Then, on the following week, ...". ;-)
> >
> > Well, there's a difference between different user types:
> >

[ snip ]

> Exactly why is it we need a build tool for an interpreted API
> again?

Because users also want things like:

	* documentation
	* regression tests (for those pesky multi-billion dollar companies)
	* speed (the ability to pull down as little as is required to run)
	* environment-specific customizations

I also cringe at the multi-language, multi-tool hell we're slowly 
winding up in, which is why I'm hacking on Rhino to give us doc 
output and compression without using another language. I would 
really, really like to keep our tools in one language if it can be 
done, and I hesitate to use Java because it gets in the way so much. 
OTOH, it's everywhere and a lot of stuff we need is mostly done in 
Java. Regardless, our functional goals come first: full documentation 
and test coverage, customization for various environments, etc.

So in conclusion, I do feel your pain. I am working to par down our 
dependencies to at most a single language if it can be done, but we 
have other needs as well. I've often considered a putting togeather a 
"fetch everything I need" shell script for the various platforms you 
might be on, or at the very least make sure they're available out of 


- -- 
Alex Russell
alex at dojotoolkit.org
alex at netWindows.org F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46
Version: GnuPG v1.2.4 (Darwin)


More information about the NG-DHTML mailing list