27 Apr
2011
27 Apr
'11
11:04 a.m.
On Apr 27, 2011, at 1:38 AM, Tudor Girba wrote:
Hi,
On 27 Apr 2011, at 03:23, Dale Henrichs wrote:
The challenging aspects of the wizard involve allowing a user to select from a list of
repositories (for the repository information), from a (filtered) list of packages and a
list of projects when building the basic specs to be included in a baseline.
At the next level of complexity, one must be allowed to define dependencies (required:)
between packages and put the specs in different for:do: blocks ... Within the Metacello,
there is an API and a model for managing these, but I a m sure that the API/model can be
improved when we get to this point.
So I suppose that the initial wizard could be done in Magritte...
Dale
On Apr 26, 2011, at 5:27 PM, Tudor Girba wrote:
I re-read the original mail, and indeed there is enough information :). I will try to
give it a try. What I saw is that there is basically no dependency between steps. Is that
correct? If yes, then all steps would fit in a simple Magritte form. Hi Dale,
On 27 Apr 2011, at 02:22, Dale Henrichs wrote:
okay? On 04/26/2011 05:01 PM, Tudor Girba wrote:
> Hi Dale,
>
> Glamour is independent from the rendering, just like Omnibrowser is. Here is a short
description:
> http://www.themoosebook.org/book/internals/glamour/rendering
>
> We already have a working Seaside rendering code for the basic widgets of Glamour.
For an example, take the following steps:
>
> 1. download
>
http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/lastSucces…
>
> 2. run:
> WAKom startOn: 8081
>
> 3. go to:
> http://localhost:8081/moose/metaBrowser
>
> Cheers,
> Doru
I'll hold off exploring the scope of the Glamour port until I see if Glamour can be
used to construct the configuration wizard:)
I'm not skeptical as much as I am very busy...
Did I provide you with enough info for the use case?
Not really :).