<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3086" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2>Hi Johnny,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2>I agree with Julien, in that Chameleon is complete enough
to be used as-is, without necessarilily needing much changes. There are also no
real bugs left that you would run into in normal situations. But I'm sure that
will change if core-changes are made.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2>We have a web-mapping system that has chameleon at its
core, and use it as out-of-the-box functionality (and have been doing so for a
few years), so I don't think you need to be concerned about committing to a
long-forgotten package.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2>Regarding future challenges: Chameleon supports
panning/zooming without submitting the whole page, which is AJAX-like behaviour.
But either way, I normally go with a solution that addresses the current needs
as best as possible, rather than optimising for a scenario that doesn't exist
yet and never may,or a past scenario that doesn't hold anymore, like
compatability with ancient browsers at the expense of current functionality.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2>Hope this answers some of your
questions,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=600083723-17052007><FONT face=Arial
color=#0000ff size=2>Jacob</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> chameleon-bounces@lists.maptools.org
[mailto:chameleon-bounces@lists.maptools.org] <B>On Behalf Of </B>dream
police<BR><B>Sent:</B> 18 May 2007 00:28<BR><B>To:</B>
chameleon@lists.maptools.org<BR><B>Subject:</B> [Chameleon] general
question<BR></FONT><BR></DIV>
<DIV></DIV>Hi List,<BR><BR>This is a question of general order addressed at
all present and past users of chameleon. I would like to learn more about Web
Gis and had a few questions, the answers of which are not easily findable by
simple web search. Chameleon looks great to me but I am looking for a long
term solution and so would appreciate sound advice from Web Gis specialists.
<BR><BR>My questions: <BR><BR>1) Is chameleon obsolete for the functionality
it proposes to fulfill? (its mailing list is somewhat inactive compared to
those of other web gis development environments: kamap, cartoweb, mapbender)
<BR>2) If yes, why?<BR>3) If yes, what alternatives could you propose to
accomplish the same goals?<BR>4) For what reasons?<BR>5) What is the solution
that confronts best the future challenges of Web Gis?<BR><BR>Thanks in advance
for all replys! <BR><BR>Johnny<BR></BLOCKQUOTE></BODY></HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000>This email and any attachments are intended solely for the named recipient and are confidential. The copying or distribution of them or any information they contain by anyone other than the named recipient is prohibited. If you have received this document in error, please notify the sender and delete all copies from your computer system and destroy all hard copies. It is the recipient's responsibility to check this email and any attachments to this email for viruses before use.<br>
</font></td></tr></table>