<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Oh, I get it. If I render something that doesn't return anything, of course there would be nothing to render.<br>
<br>
If I have a class with #renderContentOn: then that would called as part
of the render loop when it is loaded into the document. Is this correct
or am I going crazy? Actually, I just tried that and it doesn't work...<br>
<br>
Thanks,<br>
RS<br><br><hr id="stopSpelling">From: watchlala@hotmail.com<br>To: seaside@lists.squeakfoundation.org<br>Subject: RE: [Seaside] jQuery html rendering<br>Date: Sun, 12 Jul 2009 12:18:49 -0600<br><br>
<style>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</style>
Thanks, Julian. I am a bit confused, though.<br><br> html anchor<br> onClick: ((html jQuery: '#contentArea') html: [:r | r render: (RPSSCreator new)]);<br> with: 'Create a new survey'.<br><br>I have been using code like this in a few areas, and it works just fine. The object just needs to persist until it does its job, then I can move along in whatever process.<br><br>I can't seem to get some of my components to render in this way... I get: 'MessageNotUnderstood: RPSSSurveyItemComponent>>nil'. As far as I can tell, there is nothing different about it (than the others), and I am not sending any messages to it except #new. WACounter, etc. work fine in its place.<br><br>As far as #children goes, I havn't been including everything there because the page is remaining relatively static. 'RPSSSurveyItemComponent' is a WAComponent subclass, but I'm just using it to generate survey components, so for each new survey item I will need a new instance.<br><br>Is lazy initializing good enough for creating these objects in advance when it comes to jQuery?<br><br>Thanks,<br>RS<br><br>> Date: Sun, 12 Jul 2009 08:22:03 +0100<br>> Subject: Re: [Seaside] jQuery html rendering<br>> From: jfitzell@gmail.com<br>> To: seaside@lists.squeakfoundation.org<br>> <br>> Components are persistent objects. You can't create them on the fly as<br>> throw-aways (in particular they need to be returned from your<br>> #children method). See the recent discussion about components,<br>> painters, and renderable objects on this list.<br>> <br>> You either need to create the component earlier and store it somewhere<br>> or not use a component here (if you don't need the object to persist,<br>> you don't need a component).<br>> <br>> Julian<br>> <br>> On Sun, Jul 12, 2009 at 12:25 AM, Robert Sirois<watchlala@hotmail.com> wrote:<br>> > clickFunctionNew: html<br>> > ^((html jQuery: '#newArea') html: [:r | r render:<br>> > ((RPSSSurveyItemComponent new) newInputOn: self inputType; yourself)]).<br>> ><br>> > Could someone please explain to me why this does not work? If I replace the<br>> > class 'RPSSSurveyItemComponent' with some like a string 'blah', it runs<br>> > fine. Am I to understand that I cannot render components (the aforementioned<br>> > class is a WAComponent subclass with the proper 'renderContentOn:' method)<br>> > like a can do with standard Seaside callbacks?<br>> ><br>> > Thanks!<br>> ><br>> > RS<br>> ><br>> > ________________________________<br>> > Windows Live™: Keep your life in sync. Check it out.<br>> > _______________________________________________<br>> > seaside mailing list<br>> > seaside@lists.squeakfoundation.org<br>> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br>> ><br>> ><br>> _______________________________________________<br>> seaside mailing list<br>> seaside@lists.squeakfoundation.org<br>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br><br><hr>Lauren found her dream laptop. <a href="http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290">Find the PC that’s right for you.</a><br /><hr />Lauren found her dream laptop. <a href='http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290' target='_new'>Find the PC that’s right for you.</a></body>
</html>