[Mapserver-users] JavaScript vs MapScript for interface devel opment...

[Tom.Kralidis at CCRS.NRCan.gc.ca]

Scripting client side gives a more interactive experience to the user, and
can create some neat apps, as shown in the MapServer user's gallery.  This
also creates less load on the server.

However, by scripting client side, you are taking on the burden of coding
against multiple web browser clients, especially for advanced DHTML type
features.

I'm sure others on this list can talk to this better, but these are my
general experiences.

..Tom

=================================
Tom Kralidis
Systems Scientist
Canada Centre for Remote Sensing
Tel: (613) 947-1828
http://www.cgdi.ca/
=================================



> -----Original Message-----
> From: AMC Story [mailto:s9646183 at sms.ed.ac.uk]
> Sent: Thursday, June 26, 2003 11:47 AM
> To: mapserver list
> Subject: [Mapserver-users] JavaScript vs MapScript for interface
> development...
> 
> 
> Dear all,
> 
> At the moment, I've set up a basic MapServer application 
> which is now running 
> fine.  However, I'm not too happy with the interface, which 
> follows the model 
> set out in the demo and the tutorial examples.  I don't find 
> it all that user-
> friendly or intuitive, so I'm looking to develop the 
> interface so as to allow 
> users to use familiar tools like zoomin and zoomout buttons, 
> pan arrows and 
> checkboxes for turning layers on and off.
> 
> It seems that this functionality can be implemented, and that 
> I have a choice 
> between either using MapScript or JavaScript.  Does anyone 
> have any comments to 
> make as to the relative merits of each approach?  I've had a 
> look through the 
> archives but haven't come across anything on this subject.
> 
> Any input gratefully recieved!
> 
> Many thanks,
> Ali
> _______________________________________________
> Mapserver-users mailing list
> Mapserver-users at lists.gis.umn.edu
> http://lists.gis.umn.edu/mailman/listinfo/mapserver-users
>