Bart - [EMAIL PROTECTED] wrote: > If you are changing interfaces/APIs, should it not really be Mapbuilder 2.0 > instead of 1.5? >
I suspect the reason you are asking is because one of the products you use frequently (OpenLayers) has a very strict policy to not change the API between minor releases. It is good to have such a policy, but this is not necessarily applicable for an application building framework like Mapbuilder. Even general-purpose JavaScript frameworks like Dojo and ExtJS have API changes in some components between minor releases. Mapbuilder has a very small core, which is still unchanged. The power of Mapbuilder lies in its widgets, and AOIBoxDHTML is a widget that has already been deprecated since 1.5alpha2. So strictly speaking, this is not an API change, but just a deprecated widget that is no longer part of the framework. I agree, however, that things like that need to be documented. But as you know, this is a different story and seems to be a general problem in some OpenSource projects. The Mapbuilder community is well aware of that, but there are simply not enough resources to get that job done better. On the other hand, most user questions on the mailing lists get answered within a day or so, so nobody who decides to use Mapbuilder has to re-invent the wheel. Regards, Andreas. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Mapbuilder-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-users
