[Seaside-dev] ConfigurationOfSeaside30 3.0.0-alpha5.15 ready for a bit of review

[Julian Fitzell]

On Wed, Jun 23, 2010 at 1:02 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
> I would like to release 3.0.0-alpha5.15 for the GLASS users relatively soon,
> but I thought I'd get some feedback on what's included before releasing
> it...

If you hold off briefly I'll get the bloody RC release done and you
can call the version that. :) Naughty me, I've already changed the
version in the code so it will be a bit confusing to have releases
described as alpha describing themselves as RC's (that was bad
planning on my part given the delay in releasing it).

> Looking at a load of the 'Base' group these are the packages that are
> loaded:
>
> linear load :
>        linear load : 3.0.0-alpha5.15 [ConfigurationOfSeaside30]
>                load : ConfigurationOfGrease
>        linear load : 3.0.0-alpha5.15 [ConfigurationOfSeaside30]
>                linear load : 1.0-alpha9.3 [ConfigurationOfGrease]
>                        load : Grease-Core-pmm.42
>                        load : Grease-Pharo-Core-pmm.23
>                load : Seaside-Core-pmm.648
>                load : Seaside-Pharo-Core-pmm.9
>                load : Seaside-Component-lr.82
>                load : Seaside-Canvas-pmm.95
>                load : Seaside-Session-jf.132
>                load : Seaside-RenderLoop-lr.72
>                load : Seaside-Tools-Core-lr.17
>                load : Seaside-Widgets-obi.18
>                load : Seaside-Environment-lr.69
>                load : Seaside-Pharo-Canvas-lr.3
>                load : Seaside-Pharo-Environment-lr.6
>
> this matches the list that Julian (or was it me?) proposed, so I think we
> are in good shape:)

Looks about right, though I wonder why Pharo-Canvas isn't loaded after
Canvas (I guess because nothing else actually depends on Canvas?).

> I have not added a 'Development' group, because I'm not sure what would need
> to be included beyond Seaside-Development (and it's dependents). If there
> another couple of packages that you would consider development packages
> (like including Slime?) then a 'Development' group would be called for.

I think Slime (at least on platforms where it works) is a good
candidate for inclusion. Maybe worth having "Development" there then
on all platforms, even if on some it only currently includes
Seaside-Development?

> As for other groups I can imagine a 'Flow' group would be useful if a
> package beyond Seaside-Flow (and it's dependents) would be required...

Would Flow not be just conditionally loaded in Base depending on the platform?

> Finally, when you load the Seaside-Welcome page using this expression:
>
>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>    load: #('Base' 'Seaside-Adaptors-Comanche' 'Seaside-Welcome' ).
>
> quite a bit gets loaded, because of the inclusion of the Task example
> (WAFlowConvenienceFunctionalTest in Seaside-Tests-Flow)... here's the list
> of mcz files:

Welcome depends on Environment so I expect a lot to get loaded but the
fact that it pulls in a bunch of unit test packages, Development
tools, and possibly Flow is a bit unfortunate. Still, we kind of do
want to demonstrate Flow... suggestions? (btw, I have uncommitted
changes to the Welcome package - I'll try to get those pushed in now).

> linear load :
>        linear load : 3.0.0-alpha5.15 [ConfigurationOfSeaside30]
>                load : ConfigurationOfKomHttpServer
>        linear load : 3.0.0-alpha5.15 [ConfigurationOfSeaside30]
>                load : ConfigurationOfGrease
>        linear load : 3.0.0-alpha5.15 [ConfigurationOfSeaside30]
>                load : ConfigurationOfGrease
>        linear load : 3.0.0-alpha5.15 [ConfigurationOfSeaside30]
>                linear load : 1.0-alpha9.3 [ConfigurationOfGrease]
>                        load : Grease-Core-pmm.42
>                        load : Grease-Pharo-Core-pmm.23
>                linear load : 1.0-alpha9.3 [ConfigurationOfGrease]
>                        load : Grease-Tests-Core-DaleHenrichs.58
>                        load : Grease-Tests-Pharo-Core-jok.7
>                load : Seaside-Core-pmm.648
...
>                load : Seaside-Environment-lr.69
...
>                load : Seaside-Welcome-obi.12
...
>                load : Seaside-Pharo-Environment-lr.6
>                load : Seaside-Tests-Pharo-Functional-lr.12
>                load : Seaside-Pharo-Tools-Web-lr.21
>                load : Seaside-Pharo-Continuation-lr.5
>                load : Seaside-Tests-Pharo-Continuation-lr.7
>                load : Seaside-Pharo-Flow-lr.5
>                load : Seaside-Pharo-Development-lr.42
>                load : Seaside-Adaptors-Comanche-pmm.59
>
> Let me know if you'd like to see changes ... I can always release another
> version if you want to add groups or make other tweaks...

Why do all those Pharo packages get loaded at the end? My expectation
is that Pharo-Environment is loaded right after Environment, for
example. This could be important for initialization. I thought
Metacello's requires/includes distinction handled that?

Julian