[Seaside-dev] WAPackage dependencies

[Lukas Renggli]

> This concept has got a bit muddied though: I was just talking about it
> again with Lukas the other day and he had forgotten we were talking
> about doing that and so was not combining the static dependency info
> into the load order. But I think he was going to try doing that now...

Yes, this is important.

I merged the functional dependencies with the static ones for building
load scripts. It works extremely well. I reported the delta as an
issue, so that we can check if there are any obvious mistakes in the
functional dependencies:
<http://code.google.com/p/seaside/issues/detail>

Merging the two sources gives (as far as I could test) a very good
dependency model. I published an automatically built load script
(actually this is the first load script without manual tweaking) that
loads all the sources according to this model, but got no feedback so
far. The web application that allows one to select a set of desired
packages and produces a load script is also ready for testing. I need
to fix some quirks and make it ready for deployment on the website
though. Would be time for a Seaside 2.9a2?

Cheers,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch