On Sun, Jan 31, 2010 at 9:15 PM, stephane ducasse stephane.ducasse@free.fr wrote:

Far less than we could expect when you consider the amount of time and energy we spent on it and its quality. We are at 34....

You haven't talked about it outside the mailing lists and 1 or 2 blogs. What about news websites (linuxfr for example).

Far less than we could expect when you consider the amount of time and energy we spent on it and its quality. We are at 34....

35 :-)

Thanks for a great book!

Regards,

Ole.

Hello Tony,

On Sun, Jan 31, 2010 at 4:52 PM, Tony Giaccone tgiaccone@gmail.com wrote:

Well I purchased a copy. And now I've reached a point where I'm very frustrated.. Great progress, but now reached a limit and I feel like I'm not understanding the basic ways the framework should be used.

Have patience....

Here's my dilemma. Imagine a page with an editor and a browser. The browser lists the entries of a particular type. The editor allows you to create a new entry or edit one which exists already.

The page as a whole is initialized like this:

initialize super initialize. person := Person new initialize. editor := (person asComponent addValidatedForm). browser := PersonBrowser new initialize.

The renderContentOn method looks like this:

   html text: 'Hello'; break.
   html div class: 'personInfo'; with: [
           editor isNil ifFalse: [html render: editor].
           browser isNil ifFalse: [html render: browser].
   ]

What I can't figure out how to do is to connect into the method that gets called when the user presses save on the editor. At that point I want to persist the person, and do some other things. I see this lovely line from the book:

This is clearly the place to hook a database commit for example.

Could you point us to where in the book you find this lovely line?

If I'm not mistaken, you need to add an onAnswer: block to the editor := line of code: editor := person asComponent addValidatedForm; onAnswer: [ :p | "do something with p" ]; yourself.

To explore further put a self halt in the block to see when it gets called.

Also, I don't think you need to send initialize after you send new. And be sure person and browser are returned in an array in the children method.

Yes, it clearly is.. what's not clear is how the heck you do it. LOL

Tony

PS I have this feeling, coming from a Java background that I'm totally am not doing things in the tao of smalltalk. It's extremely frustrating.

Look at the bright side: You aren't in Java anymore =)

Regards

On Sun, Jan 31, 2010 at 1:29 PM, Squeaker squeakman@gmail.com wrote:

...

Lukas Renggli wrote:

...

The PDF version of the book "Dynamic Web Development with Seaside" is available for download now:

 http://book.seaside.st/book/introduction/pdf-book

Any chance of getting some stats on how well it is selling. It would be nice to gauge community support.

BTW - I purchased the pdf book.

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

John,

Thanks for your assistance. I really appreciate the quick response.

One thing I really hate. Is struggling with understanding a new framework. Reaching a blockage point, fighting with it for a few days. Then asking for help, only to find the answer myself, shortly after posting a message that say "Hey I can't figure out how to do this". I hate that.

My problem of course is that I'm not reading the book sequentially from start to finish. That would make too much sense, be to logical and take too long (that should all be read with a note of irony). Instead I'm jumping around reading a bit here and a bit there.. So I jumped to chapter 24. Where I read about Magritte and found my quote:

This is clearly the place to hook a database commit for example.

I went back scanned through the book again and found the whole section 12.6.2 Behavioral Decorations. Shortly there after I had my code using SandstoneDB and saving records to the filesystem.

On Jan 31, 2010, at 7:17 PM, John McKeon wrote:

Hello Tony,

This is clearly the place to hook a database commit for example.

Could you point us to where in the book you find this lovely line?

page 364, second paragraph from the end.

If I'm not mistaken, you need to add an onAnswer: block to the editor := line of code: editor := person asComponent addValidatedForm; onAnswer: [ :p | "do something with p" ]; yourself.

I actually do it on two different lines:

editor := (person asComponent addValidatedForm).

editor onAnswer: [ :answer | answer isNil ifFalse: [answer doSave]].

I call my own save method here, rather then call the Sandstone save method so I can do any thing else that might be required before I save to the db.

To explore further put a self halt in the block to see when it gets called.

Also, I don't think you need to send initialize after you send new. And be sure person and browser are returned in an array in the children method.

Yes, it clearly is.. what's not clear is how the heck you do it. LOL

Tony

PS I have this feeling, coming from a Java background that I'm totally am not doing things in the tao of smalltalk. It's extremely frustrating.

Look at the bright side: You aren't in Java anymore =)

Oh, where that only true. My full time day job is still java development. I'm just sneaking in a quick attempt to try and do a prototype proof of concept with smalltalk/seaside, with out anyone being the wiser and on my own time. Yes, I have to say I'm enjoying this a great deal more than Java dev.

Tony

Regards

I do not really know :) did you asked lukas ?

Stef

Is there any way to change the quantity of books you want to order?

Cheers Philippe _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside