Hi GeoExt, A few years later and faced with updating my apps to support ExtJS 4, these questions still remain unresolved for me :( I still struggle with understanding how to setup a project that magically pulls in needed components from the base libraries in order to build a minified custom build.
Perhaps a simpler question: Does anybody have an example app (which uses Geoext, openlayers, and extjs 4) and has a build process to generate a customized build of these support libs? I have had some luck hacking GeoExt into the Openlayers build process, but it was from trial + error, not with automagic dependency resolution. But then I could not get ExtJS into that process. thanks daryl On Thu, Mar 3, 2011 at 12:01 PM, daryl herzmann <akrh...@iastate.edu> wrote: > Greetings GeoExt Community, > > I've been happily hacking away on a javascript application that utilizes > the following libraries: > > - JQuery > - Strophe > - Google Maps API > - SoundManager2 > - Sencha ExtJS > - GeoExt > - OpenLayers > > The application is basically a BOSH Jabber client with geo-spatial > chatrooms. Anyway, I am really struggling with the following concepts and > was hoping folks could provide guidance or weblinks for me to read up on. > > 1) How to layout a directory to develop this application? Do you use > sym links, how should the folders be organized? What all gets > managed by subversion? > > 2) What options are there for minified builders? Currently, I pull in > the full release libraries of the above into my app. Yes, I realize > this is a terrible thing to do, thus my questions here. :) I have > been messing around with Google Closure Compiler and am building my > code just fine with it, but am not sure how best to proceed with > custom building geoext/openlayers/extjs . > > 3) Are there established practices for keeping track of dependencies for > the build process? Or is it all manually configured in some simple > build script? > > And just for some feedback on GeoExt (probably showing my ignorance > again), I wish: > > - one could provide an array of styles to unique styling rules, instead > of only one per lookup value. > > - The same radio button logic of baselayers could more easily be applied > to overlay groups. I figured it out eventually. > > - There was a tighter way to tie one layeropacityslider to a treenode of > layers. > > - Having static WMS legends (non WMS GetLegend images) appear in a map > friendly location. > > I suspect all the above are 'easy to do', but I struggle with doing it! > I'm also the least sharp tool in the toolbox :) > > thanks for your time! > daryl >
_______________________________________________ Users mailing list Users@geoext.org http://www.geoext.org/cgi-bin/mailman/listinfo/users
