[mapguide-internals] Viewers and the Future of Web Layout

Haris Kurtagic haris at sl-king.com
Tue Feb 27 05:23:10 EST 2007


I think that having multiple viewers is not a bad thing as a matter of
fact I believe that we need different types of viewers.
Right now I can't imagine having one viewer for all types of
applications and requirements.

I don't know how Fusion works also we have recently started developing
AJAX apps so I am talking mostly based on my "feeling".

There were two main reason for choosing GWT:
1. we need simple and efficient remote procedure call
2. scalable, large client application - we can't do it coding in
As project progress we are more and more satisfied with result and

Few months ago we have looked at WebStudio and we very impressed about
it. It has changed my view on web applications.
We discussed how to add functionality for connecting to FDO data
But then I realized that writing JavaScript code is not a way we won't
to go.
I could be subjective and inexperienced about this, I would like to hear
other opinions.



-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Robert
Sent: 26. februar 2007 23:01
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?
> Jason
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list