I understand your frustration, but I don't think that DMSG or the Fusion project (it's independent now, and has as many MapServer users as MapGuide) should take any blame for what version of their project was bundled with MapGuide 2.0.2. This was entirely decided by the MapGuide PSC in order to reduce the risk to existing MapGuide installations. This is part of retaining the trust of MapGuide users that rely on point releases being bug-fix only and not requiring new development... there are strong and valid reasons for this policy. In this case, the amount of re-development required to implement Fusion 1.1 on top of MapGuide 2.0.2 is relatively low, and the benefits are solid. I would certainly encourage developers who are willing to take on the work of porting their custom templates to Fusion 1.1 to download it either from SVN, or to wait for the Fusion 1.1 release which should be forthcoming shortly. Jason ________________________________
From: [EMAIL PROTECTED] on behalf of Rock Beans Sent: Thu 2008-09-25 6:45 AM To: MapGuide Users Mail List Subject: Re: [mapguide-users] Fusion on Firefox 3 and new MapGuide Release This means developers who tried to get on board now have to either create custom viewers from the scraps or the standard AJAX viewer now. I understand open source and I also understand trying to get consulting time (DM) but if you want to receive full trust from the community you have to step it up. Was Fusion just a pet project? Is DM trying to get Autodesk to buy the idea or something before it becomes released in every version? Is there anywhere I can get big picture plans so I don't make the same mistake twice? Thanks for the information everyone! This sadly makes me look bad for supporting Fusion for the last year and forces us to change directions... again. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
