Hi all, this is kind of a noob question, sorry. I'm using Damian
Cassou's Web dev image and for some reason creating a new WAComponent subclass doesn't seem to result in that subclass becoming available in the new app config's "Root Component" dropdown in Seaside. In the images I was using earlier, just creating a subclass (in its own top-level category) would result in the subclass becoming available as a root component, and yet I didn't end up with an overwhelming number of root components in the dropdown. What am I missing? Sorry for the basic-ness of the question. -- Giles Bowkett Blog: http://gilesbowkett.blogspot.com Portfolio: http://www.gilesgoatboy.org _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> Hi all, this is kind of a noob question, sorry. I'm using
> Damian Cassou's Web dev image and for some reason creating a > new WAComponent subclass doesn't seem to result in that > subclass becoming available in the new app config's "Root > Component" dropdown in Seaside. In the images I was using > earlier, just creating a subclass (in its own top-level > category) would result in the subclass becoming available as > a root component, and yet I didn't end up with an > overwhelming number of root components in the dropdown. What > am I missing? Sorry for the basic-ness of the question. > > -- > Giles Bowkett On the class side of your component, add canBeRoot ^true Ramon Leon http://onsmalltalk.com _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> On the class side of your component, add
> > canBeRoot > ^true Thanks Ramon. Managed to track that down, but first I kind of chased a red herring, registerAsApplication. -- Giles Bowkett Blog: http://gilesbowkett.blogspot.com Portfolio: http://www.gilesgoatboy.org _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Wed, 23 May 2007 20:28:59 -0700, Giles Bowkett <[hidden email]> wrote:
>> On the class side of your component, add >> >> canBeRoot >> ^true > > Thanks Ramon. Managed to track that down, but first I kind of chased a > red herring, registerAsApplication. > Hey, I did that, too. I still haven't figured out what the deal is with that. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Giles Bowkett
2007/5/24, Giles Bowkett <[hidden email]>:
> > On the class side of your component, add > > > > canBeRoot > > ^true > > Thanks Ramon. Managed to track that down, but first I kind of chased a > red herring, registerAsApplication. #registerAsApplication: can be used to manually register a component (or task) as an application. In this case it doesn't matter what #canBeRoot returns, that's just for the UI. #registerAsApplication: is very convenient if you have just created a new component and want to register is as an application and don't want to go through the whole /config application. You can just type self registerAsApplication: 'foobar' somewhere in the class (self is bound to the class in the code browser) and you're done. Cheers Philippe > -- > Giles Bowkett > > Blog: http://gilesbowkett.blogspot.com > Portfolio: http://www.gilesgoatboy.org > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |