tag:blogger.com,1999:blog-2677774430457039310.post346748460667370996..comments2023-11-02T12:05:41.418+01:00Comments on MapFish: Studio: Beta for the MapFile ManagerCédric Moullethttp://www.blogger.com/profile/06947117799577904122noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2677774430457039310.post-18962241324553936602009-03-28T03:24:00.000+01:002009-03-28T03:24:00.000+01:00Nice work guys! Cool to see this coming together....Nice work guys! Cool to see this coming together. I see that at least the <A HREF="http://dev.mapfish.org/studio/demo/js/fromGeoServer/MultiSlider.js" REL="nofollow">MultiSlider</A> widget <A HREF="http://projects.opengeo.org/styler/browser/trunk/lib/Styler/widgets/MultiSlider.js" REL="nofollow">comes from</A> our Styler app. Guess we should put a license on that huh?<BR/><BR/>Hope we find more places where we can share code.Tim Schaubhttp://opengeo.orgnoreply@blogger.comtag:blogger.com,1999:blog-2677774430457039310.post-31281385046618836552009-03-25T14:41:00.000+01:002009-03-25T14:41:00.000+01:00If studio can load an existing -- usually not work...If studio can load an existing -- usually not working ;-) -- mapfile and fill in the boxes, that would be a nice debugging help. Of course, starting a mapfile with the studio should avoid someone forgetting to set a symbol or something and wondering why the map doesn't show up. The trickiest part for me has always been the syntax of mapfile objects as a function of MapServer version (I saw 2 querymap syntaxes just recently while googling). <BR/><BR/>Studio may fill what I consider an important integrator gap in the "C/Python" FOSS4G world: easy data configuration. Thanx for this great effort !Anonymousnoreply@blogger.com