Mapbuilder doesn't only uses the standard functionality from IE 6.0 and 
Firefox. So no additional functionality is required to be downloaded.

I'm not familiar with MSXML and assume it is an extra extension to IE? 
In that case, Mapbuilder doesn't need it.

Vish Uma wrote:
> Hi Cameron,
>
> Does the client side XML transformation add a dependency to MSXML 
> versions?
>
> Thank You,
> Vish
>
>
>
> On Nov 26, 2007 8:57 PM, Cameron Shorter < [EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     Most Mapbuilder widgets transform a Context document - Web Map
>     Context
>     (WMC) or OWS Context. A context is an XML representation of a
>     LayerList, AreaOfInterest and some metadata.
>
>     Other widgets transform:
>     * GML - Eg to produce a list of feature attributes
>     * A Context Collection,
>     * A Capabilities document
>     * A response from a Catalog query
>
>     And anything else that you care to transform from a server.
>
>     On Nov 27, 2007 12:43 PM, Vish Uma < [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
>     > Hi Cameron,
>     >
>     > I appreciate your efforts in taking the time to answer my
>     question. I
>     > do really appreciate it and has really saved me a lot of time and
>     > trouble. Your answers did clear away a lot of questions and
>     concerns.
>     > Your answer about the WFS and the POST restrictions makes a lot of
>     > sense, I am surprised that OpenLayers doesn't mention it anywhere in
>     > their documentation. I was wondering if you wouldn't mind answering
>     > one final question. I am not exactly sure what XML data is
>     transformed
>     > using the XSLT on the clinet-side? Is it just the config XML data?
>     > This again will go to answer my questions about the following
>     you had
>     > mentioned.
>     >
>     > "If you want to design new widgets, with data sources from a
>     number of
>     > sources, especially if they would be easier to write in XSL,
>     > Mapbuilder may be better."
>     >
>     > Is the data source represented in XSL, is so how?
>     >
>     > The answers to the above questions might be lengthy. I was just
>     hoping
>     > that you might atleast steer me in the right direction. Again, I
>     > really appreciate your answer to my inquiries.
>     >
>     > Thank You,
>     > Vish
>     >
>     >
>     >
>     >
>     >
>     > On Nov 26, 2007 5:32 PM, Cameron Shorter <
>     [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
>     > > Vish, I hope you don't mind me CCing my response to other
>     mapbuilder
>     > > developers as this is of common interest.
>     > >
>     > > Vish Uma wrote:
>     > > > Hi Cameron,
>     > > >
>     > > > I got your email from your blog when I was doing some
>     research online
>     > > > on whether I should select OpenLayers or MapBuilder for one
>     of my
>     > > > projects. I was hoping that you might be able to help me by
>     passing
>     > > > along your comments. I was wondering if you let me know what
>     you think
>     > > > about the below questions.
>     > > >
>     > > > 1) Is MapBuilder completely Client-side like OpenLayers? I
>     am reading
>     > > > that it tries to server independent but sometimes relies on
>     the apache
>     > > > - php stack. I am struggling to understand what features
>     relies on the
>     > > > server side?
>     > > >
>     > > There is one security limitation using HTML faced by both
>     Mapbuilder and
>     > > Openlayers.
>     > > You can only POST a request to the server that the HTML comes
>     from. This
>     > > is an issue when trying to access a service like a WFS from
>     another server.
>     > > Both Mapbuilder and Openlayers have a server side proxy to
>     address this.
>     > > All the rest of Mapbuilder and Openlayers code is client side.
>     > >
>     > > > 2) MapBuilder states that it is integrated with OpenLayers.
>     But I
>     > > > can't understand why and how OpenLayers is used interally.
>     > > >
>     > > Openlayers is used to render our MapPane.
>     > > > 3) Does the client-side XSLT transformations slow things down?
>     > > >
>     > > No, it speeds it up. (Passing XML using Javascript is slower).
>     > > The downside is that some older browsers don't support XSL.
>     > > > 4) I found that the documentation and help for OpenLayers
>     were bad. I
>     > > > was not happy with it at all. MapBuilder seems to have better
>     > > > documentation than OpenLayers. Is the MapBuilder community
>     active
>     > > > enough to expect help with issues that I may come across.
>     > > >
>     > > Both Mapbuilder and Openlayers have an active community.
>     > > In particular, Openlayers' IRC channel is regularly used and
>     usually has
>     > > someone responding on it. Mapbuilder's communication is mainly
>     via email.
>     > > > I can understand that the above questions might be a whole
>     lot to
>     > > > answer. But I would really appreciate your input for those
>     question
>     > > > and it will go a long way in helping choose a solution.
>     > > >
>     > > If you just want a map and a few common widgets on the display,
>     > > Openlayers might be for you.
>     > > If you want to design new widgets, with data sources from a
>     number of
>     > > sources, especially if they would be easier to write in XSL,
>     Mapbuilder
>     > > may be better.
>     > > You will find that Mapbuilder does a better job implementing the
>     > > Model/View/Controller design pattern.
>     > > > Thank You,
>     > > > Vish
>     > > >
>     > > >
>     > >
>     > >
>     > > --
>     > > Cameron Shorter
>     > > Geospatial Systems Architect
>     > > Tel: +61 (0)2 8570 5050
>     > > Mob: +61 (0)419 142 254
>     > >
>     > > Think Globally, Fix Locally
>     > > Commercial Support for Geospatial Open Source Solutions
>     > > http://www.lisasoft.com/LISAsoft/SupportedProducts.html
>     > >
>     > >
>     > >
>     >
>
>
>
>     --
>     Cameron Shorter
>     Geospatial Systems Architect
>     Tel: +61 (0)2 8570 5050
>     Mob: +61 (0)419 142 254
>
>     Think Globally, Fix Locally
>     Commercial Support for Geospatial Open Source Solutions
>     http://www.lisasoft.com/LISAsoft/SupportedProducts.html
>
>


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Mapbuilder-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-users

Reply via email to