[mapguide-internals] Viewers and the Future of Web Layout
trevor.wekel at autodesk.com
Mon Feb 26 17:22:35 EST 2007
I agree with Bob. If we can stick to a flexible, common, client
framework then moving from one programming environment to another is
much easier. Enhancements and custom packages can be written for a
single common environment instead of writing them 3 times.
There is a risk of "lowest common denominator" technology hampering what
can be achieved with the client framework. However, there is a large
body of web technology out there today. I would be surprised if we
couldn't find something that would be a good fit for PHP, .Net, and
Java. We also have SWIG available to add common API "helper" classes if
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Robert
Sent: Monday, February 26, 2007 3:01 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Viewers and the Future of Web Layout
Change Subject, was: foss4g workshops
Now I am worried. I was hoping that Fusion would lead to a next
generation web layout and we could continue a write once run anywhere
type of viewer strategy. Sounds like we really need to get together and
decide on a strategy for moving forward. Deciding to split is not a
bad thing, but I want to make sure it is a conscience decision as
opposed to the project randomly growing appendages.
From my perspective the pro for keeping it all together is that we can
all take advantage of one another's work. Once we have a flexible
client framework then folks can focus on developing new widgets to plug
into it. The only potential pro for splitting is to take advantage of
best of breed technology from different vendors, but I am not totally
convinced this cannot be achieved with the first approach.
What does everyone else think? Paul?
Jason Birch wrote:
> Bob wrote:
>> Hows that RFC for Fusion support coming along anyway :)
> I'm a little worried about direction with the AJAX viewers. While the
current viewer meets a large proportion of the users' needs, it's not
very flexible and the map surround elements aren't very AJAX.
> DMSG has been working on Fusion as an alternative, and it looks like
SL-King is looking at building a similar framework for Java based on
GWT. I could see something coming for .Net that leverages "atlas" in
the same way.
> Do we need to talk about this to ensure that these apps are developed
in a particular way (if they're going to be merged into the MapGuide
project)? Are we OK with different viewers having different APIs, etc?
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals