<div class="gmail_quote">On Sat, May 16, 2009 at 3:30 AM, Lukas Renggli <span dir="ltr"><<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> Yes, this sounds doable to me because I really don't want to be loading<br>
> un-needing components. Seaside provide a mechanism to automatically<br>
> generate the API when these components are included in the head tag?<br>
> For example, if a new stable release is published with a new and/or<br>
> modified API, would these new additions be added to Seaside's interface<br>
> for this component?<br>
<br>
</div>What are you referring to as "Component"? The Javascript classes found<br>
in Prototype and <a href="http://script.aculo.us" target="_blank">script.aculo.us</a> libraries? If so, then yes.<br>
<br>
As soon as new versions of these libraries are released I usually<br>
update the Smalltalk bindings within a few days. This is not an<br>
automated process though, I have to work through the changes and<br>
update the bindings manually. For the JQuery packages I have a script<br>
that downloads and parses the documentation and automatically<br>
generates the required code. I don't know if Prototype and<br>
<a href="http://script.aculo.us" target="_blank">script.aculo.us</a> are still maintained these days, there were no big<br>
releases for a very long time.<br>
<div class="im"></div></blockquote><div><br></div><div>Lukas, it seems that there's some life within the Prototype community:</div><div><br></div><div><a href="http://www.prototypejs.org/2009/3/27/prototype-1-6-1-rc2-ie8-compatibility-element-storage-and-bug-fixes">http://www.prototypejs.org/2009/3/27/prototype-1-6-1-rc2-ie8-compatibility-element-storage-and-bug-fixes</a></div>
<div><br></div><div>However, you're correct in regards to not knowing if the <a href="http://script.aculo.us">script.aculo.us</a> project is being maintained</div><div>because there haven't been a release since November 18, 2008. However, there seems to be activity</div>
<div>in the Google group:</div><div><br></div><div><a href="http://groups.google.com/group/prototype-scriptaculous">http://groups.google.com/group/prototype-scriptaculous</a></div><div><br></div><div>In regards to Javascript, I started to learn jQuery after taking a tutorial session at Railsconf 2009 which</div>
<div>emphasizes the use of unobtrusive Javascript technique (i.e. separating Javascript from HTML structure). </div><div>Thus, I feel creating an API for a Javascript may be overkill in this regard when one would simply include</div>
<div>the required librar( y | ies) within the <head> tag and include the required Javascript within the <script> tag.</div><div>Also, I use a similar rule for CSS by eliminating all styling from the HTML structure. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
> It would be great if I can click a Seaside component and select update<br>
> without<br>
> destroying the image. At time time, I was informed that I would need to use<br>
> an<br>
> image that doesn't have Seaside in it. It's like creating a new document<br>
> each time<br>
> you add a new paragraph to it. Will this be resolved in the future?<br>
<br>
</div>This is not really a problem of Seaside, but rather of Smalltalk and<br>
the way how code is loaded and packaged. While Seaside is still in<br>
alpha phase we rename packages and move classes around. Loading such<br>
changes in the right order is very hard, without that you end up with<br>
many obsolete classes and broken objects.<br></blockquote><div><br></div><div>Yes, I'm sorry because I did mean Smalltalk and thanks for correcting me.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
As Seaside 2.9 becomes more stable, updating should become easier.<br>
There are also at least two projects that try to solve with the issues<br>
of loading, updating and uninstalling code in a running system.<br>
<br>
I think that generally it is a good practice if you package code so<br>
that it can be cleanly loaded into a new image. This also makes the<br>
deployment much easier. Some people even advocate to create a new and<br>
clean image every day, while this certainly has its advantages it is<br>
also sort of a lame excuse that it is not possible to easily update<br>
that have many dependencies ;-)</blockquote><div><br></div><div>I'm have my fingers crossed that someday this will happen for Smalltalk.</div><div><br></div><div>-Conrad</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
Cheers,<br>
<div><div></div><div class="h5">Lukas<br>
<br>
--<br>
Lukas Renggli<br>
<a href="http://www.lukas-renggli.ch" target="_blank">http://www.lukas-renggli.ch</a><br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br>