[Seaside] SushiStore removed from Seaside
ssastre at seaswork.com
Thu Nov 22 09:52:51 UTC 2007
ideas like features and framework practices can be learned from code
examples. If you recall, it was told here that the Sushi example uses some
deprecated techniques so it simply has no sense to have in the core package
potentially replicating deprecated practices. That way is simply too easy to
inadvertedly be teaching what is wrong. I'm sure you may know how expensive
is to un-teach what is teached wrong. So applying for this case the criteria
of "when in doubt refrain yourself" seems intelligent decision to me.
I imagine you want tools for teaching and is nothing wrong with
that. In fact is great you are using this for teaching so note that you can
use it anyway if you still find it useful and you filter the wrong part for
your students but have in mind that may be that is not the same intention
the Seaside team is having (due to be unable to filter the same you will for
every independent newcomer non one of your students among other things).
If what you want is a zero config situation for your students, why
don't you just load it in a fresh image to distribute among your students?
You can put other convenient examples for the way you plan to teach too and
also your own ones.
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Robert Hawley
> Enviado el: Jueves, 22 de Noviembre de 2007 00:16
> Para: seaside at lists.squeakfoundation.org
> Asunto: [Seaside] SushiStore removed from Seaside
> Hi Ramon
> Your point is reasonable and makes sense - but I don't know
> if that was what was being argued.
> However, I would counter your (reasonable) point. It makes
> also good sense to put a good example of the use of Seaside
> within the core for the benefit of learners. There are demo
> examples in the current image, but these do not provide a
> good template for learners to work from.
> However irritating the Sushi example was to the gurus, it did
> provide a common base for discussion. Even more importantly,
> its 'go' method demonstrated the simple elegance of Seaside
> very well. Take that away and you've taken away my sales-pitch!
> Not everyone is a guru. Learners stand the best chance of
> taking to Seaside if there is helpful code close at hand.
> Phillippe is right, examples might be nice, but they have no
> place in the core framework. The examples are, and should be
> maintained as separate loadable applications.
> Ramon Leon
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside