<div class="gmail_quote">On Wed, Dec 31, 2008 at 2:13 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="Ih2E3d">> It would be far more useful to have Sake/Packages definitions from the<br>
> outset. Why not have a new class PackagesSeaside, or even just Seaside.<br>
> Why not do it the other way around, define the dependencies in<br>
> Sake/Packages and build the builder on top of that. It will even sort<br>
> the load order for you.<br>
<br>
</div>I've added an experimental export option for Sake/Packages. I tried to<br>
add as much meta-data as possible and it seems to work.<br>
<br>
I don't know how useful this is though. Seems to be less intuitive<br>
than the other two options and is takes a very long time to load even<br>
a small code base. Maybe there is something wrong with the<br>
Sake/Packages definition?<br></blockquote><div><br></div><div>Hi Lukas, the two options that you have provided works great because it allows me to tailor it to my needs. Furthermore, it's very fast to load. I don't know if this experimental stuff is really necessary because when I select a check box, the associated dependencies are checked in regards to the core library. Maybe, this can be </div>
<div>extended to the other items outside of the core library on the site.</div><div><br></div><div>-Conrad</div><div><br></div></div>