[Seaside] [Fwd: Re: [Moose-dev] Re: why Glamour configuration
is loading Refactoring and all the rest?]
dhenrich at vmware.com
Fri May 28 23:32:06 UTC 2010
Julian Fitzell wrote:
> Hi Dale,
> That was bad quoting on someone's part as that question was not from
> me but from Mariano. :)
> As you say, Slime depends on the refactoring engine, not the UI. But
> that doesn't change my point, nor Doru's question. I still don't think
> that loading Grease should require you to load the refactoring engine.
> I'm pretty sure Slime should be in its own Metacello package
> ("package"? yes?).
Sorry for the miscommunication ... But I thought that you _already had_
answered Doru's question:)
To directly answer your question...I agree, loading Grease should not
load Slime by default and yes, Slime can certainly be in it's own
Metacello configuration (not package:).
I would like to tackle the whole Seaside/Grease configuration structure,
but I don't want to do it on my own.
We can start by you telling me the structure that you'd like or I can
propose an initial structure.
Either way I'd expect some iteration before settling on a final answer.
So if I add Slime to the list, then here are the projects that are
currently embedded in the Grease and Seaside30 configurations that
should be broken out into their own configurations:
If that makes sense to you I can start building up the configurations (I
can do the work without interfering with current users) for your
It probably makes sense to do the configurations first and if/when we
get the projects broken up satisfactorily, then we can look at the need
More information about the seaside