Re: [Pharo-users] Saving Seaside components to Monticello
Le 4 juin 2014 21:17, "spearson" <sam@xofz.com> 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.
On 04 Jun 2014, at 21:47, phil@highoctane.be wrote:
Le 4 juin 2014 21:17, "spearson" <sam@xofz.com> 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.
participants (2)
-
phil＠highoctane.be -
Sven Van Caekenberghe