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

[Philippe Marschall]

2010/6/24 Julian Fitzell <jfitzell at gmail.com>:
> On Wed, Jun 23, 2010 at 5:39 PM, Julian Fitzell <jfitzell at gmail.com> wrote:
>> On Wed, Jun 23, 2010 at 1:02 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
>>> 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?).
>
> Another comment... is Widgets needed in there by something? I'd kind
> of prefer people depend on that if they use it instead of pulling it
> in for everyone (those components are badly aging and not really
> *core* functionality but samples of usage).

Aye, I'd switch Widgets with Flow (if available).

Cheers
Philippe