Le 2010-03-04 18:51, Tim Schaub a écrit : > Hey- > > At a recent sprint, I put together a JavaScript build service hosted on > App Engine. Using this service, we can put up a client page for > configuring a custom build of GeoExt. Here's an example: > > http://dev.opengeo.org/~tschaub/gxbuild/ > Really nice ! Are you sort of building a .cfg file on the fly that you shove to jsbuild hosted on AppEngine ?
We're running your jsbuild engine with MapFish's build scripts and we often have requests of people wanting a lighter OL + MF + GeoExt bundle so I was thinking of building .cfg files with a client web app like the one you did and then shove that file to whatever jsbuild instance, AppEngine or not. Is there something like a dependency tree for the whole stack, let's say GeoExt and it's dependencies, that is ExtJS and OpenLayers, that I could use to build minimal Ext and OL versions as a function of what I want from GeoExt ? I think I understand dependencies in GeoExt are determined from @require and @include code directives. Does that hold true for parts further down the stack ? Or maybe those sofware parts have other directives or ways of determining dependencies ? Cheers, Yves > This form knows about dependencies (@require and @include) declared in > the code. When you select a component with dependencies, those > components get selected as well. You can explicitly uncheck > dependencies that are not strictly required. > > Clicking "download" should give you a minified version of just the > portion of the library you need in your application. > > I still need to do a bit of testing to make sure everything is working > properly, but I'd like to include this in the GeoExt website if others > agree it has value. > > If nobody objects, I'll update the website to include a "build your own" > page (one for each release). > > Tim > > _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
