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

[Dale Henrichs]

Julian Fitzell wrote:
> On Thu, Jun 24, 2010 at 12:11 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
>> Philippe Marschall wrote:
>>> 2010/6/24 Julian Fitzell <jfitzell at gmail.com>:
>>>> On Thu, Jun 24, 2010 at 11:09 AM, Dale Henrichs <dhenrich at vmware.com>
>>>> wrote:
>>>>> Julian Fitzell wrote:
>>>>>> It appears that Tests-Functional, Tools-Web, and Welcome depend on
>>>>>> Widgets. This means it will get loaded in Base anyway, so it's not the
>>>>>> end of the world, though I wonder if we should change those
>>>>>> dependencies to make them more explicit. I'm inclined to say yes...
>>>>>> others?
>>>>>>
>>>>>> Julian
>>>>>>
>>>>>> On Thu, Jun 24, 2010 at 1:29 AM, Dale Henrichs <dhenrich at vmware.com>
>>>>>> wrote:
>>>>>>> Julian,
>>>>>>>
>>>>>>> Widgets is included because it is listed as an Environment dependency
>>>>>>> in
>>>>>>> the GRPackage definition, so I don't know whether there is an actual
>>>>>>> dependency or an artificial one...
>>>>>>>
>>>>>>> Dale
>>>>> Julian,
>>>>>
>>>>> Are you saying that you want Welcome to be made part of the Base? I
>>>>> thought
>>>>> the point of the Base group was to provide a minimal set of packages
>>>>> that
>>>>> would be the starting point for anyone that was building a Seaside app.
>>>>> That
>>>>> meant to me that extra things not really needed (like Welcome and
>>>>> Tools-Web
>>>>> and Widgets) would be excluded ... If someone is loading Pier, I
>>>>> wouldn't
>>>>> think that the SeasideWelcome would show up as the default application,
>>>>> or
>>>>> even be loaded unless explicitly asked for ...
>>>>>
>>>>> That's why I'm using Magritte-Seaside as my use case right now and
>>>>> trying to
>>>>> think of the folks building applications no top of Seaside ...
>>>>>
>>>>> I think the explicit dependencies are already in place, but I can take a
>>>>> look...
>>>> No, I thought Tools-Web was included in Base and thus that Widgets
>>>> would be loaded. Welcome doesn't want to be in Base, I agree.
>>> I'd like Welcome to be in something like "One-Click" that would also
>>> include Development, Kom and OB. Basically the stuff we want first
>>> time users and people coming form 2.8 to have. That should feel more
>>> or less like 2.8 used to feel.
>>>
>>> Cheers
>>> Philippe
>>> _______________________________________________
>>> seaside-dev mailing list
>>> seaside-dev at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>> Philippe/Julian,
>>
>> Are there any tests that you'd like included in the One-Click (or were
>> planned to be in the One-Click) ... I could wait for Julian to ship the
>> One-Click image itself and then model the One-Click group, but I would
>> imagine that it wouldn't be too hard to specify the sets of tests to be
>> included (if at all)...
> 
> The one-click has traditionally included more or less everything. :)
> You can look at the image at
> http://hudson.lukas-renggli.ch/job/Seaside%203.0/219/ . The one-click
> I'm building is more or less the same, just without Lukas' preference
> modifications (we felt it was confusing to new users if our pharo
> behaves differently than standard pharo).
> 
> Or take a look at the build scripts here:
> http://github.com/renggli/builder/tree/master/scripts
> 
> Julian
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

If what you ship with the one-click is different than 'ALL', then I'll 
include a one-click group otherwise I won't:)