Smalltalk › Pharo › Pharo Smalltalk Users

Saving Seaside components to Monticello

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

spearson

Saving Seaside components to Monticello

Hello,
I created a Monticello repository on Smalltalkhub. When I commit my package, my Object subclasses all get saved to the repository. However, only my WAComponent subclass class definition gets saved (instance/class variables). The renderContentOn: and updateRoot: methods are not getting saved to the repository. Is this because they are overridden methods and not new methods?

How can I save my renderContentOn: and updateRoot: methods to the repository?

philippeback

Re: Saving Seaside components to Monticello

Le 4 juin 2014 21:17, "spearson" <[hidden email]> a écrit :
>
> Hello,
> I created a Monticello repository on Smalltalkhub. When I commit my
> package, my Object subclasses all get saved to the repository. However,
> only my WAComponent subclass class definition gets saved (instance/class
> variables). The renderContentOn: and updateRoot: methods are not getting
> saved to the repository. Is this because they are overridden methods and
> not new methods?
>
> How can I save my renderContentOn: and updateRoot: methods to the
> repository?
>
>

Strange. Never had this issue with Seaside.

Phil
>
> --
> View this message in context: http://forum.world.st/Saving-Seaside-components-to-Monticello-tp4761679.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>

Sven Van Caekenberghe-2

Re: Saving Seaside components to Monticello

On 04 Jun 2014, at 21:47, [hidden email] wrote:

>
> Le 4 juin 2014 21:17, "spearson" <[hidden email]> a écrit :
> >
> > Hello,
> > I created a Monticello repository on Smalltalkhub. When I commit my
> > package, my Object subclasses all get saved to the repository. However,
> > only my WAComponent subclass class definition gets saved (instance/class
> > variables). The renderContentOn: and updateRoot: methods are not getting
> > saved to the repository. Is this because they are overridden methods and
> > not new methods?
> >
> > How can I save my renderContentOn: and updateRoot: methods to the
> > repository?
> >
> >
>
> Strange. Never had this issue with Seaside.

I don't think this is a Seaside problem.

Did you follow any tutorial concerning the practical use of Monticello ?

In any case, we need more details, maybe a screenshot or two.

> Phil
> >
> > --
> > View this message in context: http://forum.world.st/Saving-Seaside-components-to-Monticello-tp4761679.html
> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> >
> >