Hi, in my short experience, it's well suited for both traditional and dynamic content. For example, when developing in raw XHTML sites, I have noticed a lot of duplication. How does one easily reuse chunks of<div>XHTML across an entire site without using server side includes? Seaside allows one to isolate these chunks </div>
<div>into neat components that can easily be used across their site(s). Next, I have always looked at a framework as a whole before determining its weakness. Just because Seaside doesn't have X feature that exists in framework Y doesn't necessary count this as a weakness in Seaside. Why? This may be a feature that's not needed at all within Seaside because it does other things very well and/or there exists a better or another way to do it. Finally, I don't want to see the Seaside framework cluttered with stuff that it really doesn't need when their exists better ways of solving the problem with the existing functionality.</div>
<div><br></div><div>-Conrad </div><div><br><div class="gmail_quote">On Sun, Mar 30, 2008 at 5:23 AM, cdrick <<a href="mailto:cdrick65@gmail.com">cdrick65@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2008/3/30, Philippe Marschall <<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>>:<br>
<div class="Ih2E3d">> 2008/3/30, Conrad Taylor <<a href="mailto:conradwt@gmail.com">conradwt@gmail.com</a>>:<br>
><br>
> > Hi, is there any particular reason for comparing Seaside with another<br>
> > framework in a Seaside mailing list?<br>
><br>
><br>
> Yes, I truly believe so. To better understand for which tasks Seaside<br>
> isn't suite, what problems people have with Seaside and of course what<br>
> strengths and advantages Seaside has over other frameworks.<br>
><br>
<br>
</div>same... I feel seaside attracts lots of people and most of the time,<br>
they want just want to realize "classic web content" even if dynamic<br>
too. So Seaside is not particularly well suited. Especially since Pier<br>
can be the way to do such tasks in seaside...Precisions on strenghts<br>
of frameworks will really help whether seaside or whatever else.<br>
<br>
I think Sophie and Ramon picked up the framework really quickly for<br>
good reasons (even if apparently they had two different background<br>
with in common a good OO understanding ; Ramon was already a web dev<br>
and Sophie was new to web apps). Maybe they can help here. Colin<br>
explains it well too.<br>
<br>
My 2 cents about differences after my little investigations...<br>
I think the main visible difference between aida and seaside is the<br>
back button story (aiders correct me if I'm wrong) which allow<br>
different kind of apps.<br>
<br>
Seaside allows natively to track or not track state (variables and<br>
objets interaction), to isolate some flow too... But this is an extra<br>
job too.<br>
Aida back button will bring you "back, your page will be refreshed and<br>
you'll have a new, not old state of that object. A valid one, always"<br>
(quoted from Janko). Also, I notice removing cookies support in your<br>
broser enable different sessions in the same browser. But when hitting<br>
button in aida, there seems to be no registration in the browser<br>
history (so no back possibility) and this is not done in ajax.<br>
<br>
Both are ok to me. We just need to know. So what I call Desktop like<br>
app is total control on entries whereas classical web forms may not<br>
need this complexity. Note I don't say that Aida can't do that but it<br>
seems to me natively supported by seaside.<br>
<br>
Cheers,<br>
<br>
Cédrick<br>
<br>
ps: As a side note, discussion started on both lists (aida + seaside),<br>
but when answering I think we lost one and they it became two separate<br>
posts on both lists. So I add this mail to aida.<br>
<br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br></div>