Comments on: Terse Guide to Seaside http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/ thoughts on Smalltalk and programming in general... Thu, 20 Nov 2008 09:13:23 +0000 http://wordpress.org/?v=2.5.1 By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-14734 Ramon Leon Sun, 12 Oct 2008 15:10:39 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-14734 Yea, you're right, I had a similar clean up phase a few months ago when I figured this out as well. I think it was a code critic rule and it certainly cleaned up a bunch of unnecessary calls to #render:. Unfortunately, the code critic isn't hooked up to all the old articles on my blog, lol. Yea, you’re right, I had a similar clean up phase a few months ago when I figured this out as well. I think it was a code critic rule and it certainly cleaned up a bunch of unnecessary calls to #render:. Unfortunately, the code critic isn’t hooked up to all the old articles on my blog, lol.

]]> By: Randal L. Schwartz http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-14733 Randal L. Schwartz Sat, 11 Oct 2008 21:16:07 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-14733 I think you can more easily write html div id: #header; with: [html render: header]. as html div id: #header; with: header. since "header" there is a "renderable" object. This cleaned up a lot of my code once I figured that out. Same thing with a collection of renderables... you can just hand the collection to "with:". Browse the implementors of #renderOn:... quite a cool list. I think you can more easily write

html div id: #header; with: [html render: header].

as

html div id: #header; with: header.

since “header” there is a “renderable” object. This cleaned up a lot of my code once I figured that out. Same thing with a collection of renderables… you can just hand the collection to “with:”. Browse the implementors of #renderOn:… quite a cool list.

]]> By: Documentación sobre Seaside : The command line http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-5890 Documentación sobre Seaside : The command line Fri, 21 Sep 2007 01:57:16 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-5890 [...] http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/ Muy claro en la presentación general de la arquitectura y uso de las clases principales de Seaside [...] [...] http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/ Muy claro en la presentación general de la arquitectura y uso de las clases principales de Seaside [...]

]]> By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-3202 Ramon Leon Thu, 05 Jul 2007 05:57:09 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-3202 Ha, good catch, it's totally unnecessary. I actually know that now, but at the time I wrote this I didn't. I think I was thinking that a task "must" render a UI component not realizing that if it didn't it'd just re-run itself. Ha, good catch, it’s totally unnecessary. I actually know that now, but at the time I wrote this I didn’t. I think I was thinking that a task “must” render a UI component not realizing that if it didn’t it’d just re-run itself.

]]> By: Eric Hochmeister http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-3201 Eric Hochmeister Thu, 05 Jul 2007 05:49:11 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-3201 Why do you need the repeat block in the #go method? I tried out of curiousity to see what would happen if I removed it and it behaved exactly the same. Or am I missing something? I don't exactly understand what is happening, other than it seems to be re-running the WATask from the start. I put an #inform at the end, and it seems to progress on to that #inform, but once it hits the end of the #go method it just starts from the beginning again. go | user | user := self call: LoginTestLogin new. user ifNil: [self inform: 'Unknown user or password, please try again!'] ifNotNil: [self inform: 'Congratulations, you are in!'. self session redirectTo: 'http://onsmalltalk.com'] self inform:'Booya'. Why do you need the repeat block in the #go method? I tried out of curiousity to see what would happen if I removed it and it behaved exactly the same. Or am I missing something? I don’t exactly understand what is happening, other than it seems to be re-running the WATask from the start. I put an #inform at the end, and it seems to progress on to that #inform, but once it hits the end of the #go method it just starts from the beginning again.

go
| user |
user := self call: LoginTestLogin new.
user ifNil: [self inform: 'Unknown user or password, please try again!']
ifNotNil:
[self inform: 'Congratulations, you are in!'.
self session redirectTo: 'http://onsmalltalk.com']
self inform:’Booya’.

]]> By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-978 Ramon Leon Wed, 17 Jan 2007 18:36:18 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-978 Marc, see my post <a href="http://onsmalltalk.com/programming/smalltalk/running-seaside-apache-and-iis-on-windowsxp/" rel="nofollow">Running Seaside Apache and IIS on WindowsXP</a> where I explain how to configure Apache to do this. Marc, see my post Running Seaside Apache and IIS on WindowsXP where I explain how to configure Apache to do this.

]]> By: Marc http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-977 Marc Wed, 17 Jan 2007 18:08:06 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-977 "Seaside is great for the complex application parts of a site, but you can blend it into an existing site by mapping only those areas to Seaside while keeping the static content served up by Apache or some other framework you’re running." Hi Ramon, I would like to know how you can blend classic pages and seaside code. I didn't find much information about it. I read Seaside Parasol can host this type of solution, but I don't see how it works. For the moment I just upload my squeak image to seasidehosting.st. That works but I would prefer to use Seaside for only a part of the website, like in dabbledb. If you can help me, thanks a lot in advance! Marc “Seaside is great for the complex application parts of a site, but you can blend it into an existing site by mapping only those areas to Seaside while keeping the static content served up by Apache or some other framework you’re running.”

Hi Ramon,
I would like to know how you can blend classic pages and seaside code. I didn’t find much information about it. I read Seaside Parasol can host this type of solution, but I don’t see how it works. For the moment I just upload my squeak image to seasidehosting.st. That works but I would prefer to use Seaside for only a part of the website, like in dabbledb.
If you can help me, thanks a lot in advance!
Marc

]]> By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-145 Ramon Leon Thu, 09 Nov 2006 15:45:55 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-145 I'm not familiar with many, I know <a href="http://www.loop.aero/" rel="nofollow">Loop Aero</a> uses it, <a href="http://www.dabbledb.com" rel="nofollow">DabbleDb</a> uses it (for their application, I think the dabble site itself is done with Wordpress), and I'll be using it at my company shortly for a site that does about 30,000 uniques a day scaled across a 3 server farm. I think it's as scalable as any other session based web server, it's a matter of how much hardware you have for it, how much memory the sessions use, and how long the session timeout is. Seaside is great for the complex application parts of a site, but you can blend it into an existing site by mapping only those areas to Seaside while keeping the static content served up by Apache or some other framework you're running. I’m not familiar with many, I know Loop Aero uses it, DabbleDb uses it (for their application, I think the dabble site itself is done with Wordpress), and I’ll be using it at my company shortly for a site that does about 30,000 uniques a day scaled across a 3 server farm. I think it’s as scalable as any other session based web server, it’s a matter of how much hardware you have for it, how much memory the sessions use, and how long the session timeout is.

Seaside is great for the complex application parts of a site, but you can blend it into an existing site by mapping only those areas to Seaside while keeping the static content served up by Apache or some other framework you’re running.

]]> By: Alan Meier http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-144 Alan Meier Thu, 09 Nov 2006 00:41:11 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-144 Hi there, I would be interested in knowing whether there are any commercial websites using seaside as a framework. I searched teh net but could not find a single one. I am interested in doing something with seaside but am reticent that it may not be scalable enough. regards Alan Hi there,

I would be interested in knowing whether there are any commercial websites using seaside as a framework. I searched teh net but could not find a single one.

I am interested in doing something with seaside but am reticent that it may not be scalable enough.

regards
Alan

]]> By: links for 2006-10-23 at He’s Just Had Coffee http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-52 links for 2006-10-23 at He’s Just Had Coffee Mon, 23 Oct 2006 22:21:49 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-52 [...] Terse Guide to Seaside | OnSmalltalk: A Squeak, Smalltalk, Seaside, Web Development Blog Ramon serves up the core of Seaside with a few notes. (tags: howto seaside smalltalk tutorial) [...] [...] Terse Guide to Seaside | OnSmalltalk: A Squeak, Smalltalk, Seaside, Web Development Blog Ramon serves up the core of Seaside with a few notes. (tags: howto seaside smalltalk tutorial) [...]

]]> By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-46 Ramon Leon Tue, 17 Oct 2006 14:49:23 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-46 Coming soon... Coming soon…

]]> By: Carl Gundel http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-44 Carl Gundel Tue, 17 Oct 2006 14:39:42 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-44 This is great, thanks! Do you have any experience with styles? Everything I do with CSS and Seaside ends up being a hack. I can't seem to properly set styles for individual subcomponents of my Seaside app. Everything ends up in the root class. This is great, thanks! Do you have any experience with styles? Everything I do with CSS and Seaside ends up being a hack. I can’t seem to properly set styles for individual subcomponents of my Seaside app. Everything ends up in the root class.

]]> By: Lidell http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-41 Lidell Tue, 17 Oct 2006 07:07:12 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-41 Much obliged, Ramon! That's a great demo of how Seaside truly rocks! Much obliged, Ramon! That’s a great demo of how Seaside truly rocks!

]]> By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-40 Ramon Leon Tue, 17 Oct 2006 04:09:02 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-40 There you go... There you go…

]]> By: Lidell http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-39 Lidell Tue, 17 Oct 2006 02:50:54 +0000 http://onsmalltalk.com/programming/smalltalk/terse-guide-to-seaside/#comment-39 Great explanations Ramon! This helps clear up a few murky notions I've had about Seaside. It's really great when somebody can explain things so clearly and succinctly. At the risk of imposing, can you illustrate these concepts with a few working examples? There's nothing like working code to nail a point home. Here's a simple Seaside application: present a login page that asks the user to enter a name and a password to authenticate. If the password is correct, the application presents a page that reads: 'Congratulations, you are in'. If the password is incorrect, the application displays a page that reads: 'Unknown user or password. Please try again.' A typical web app solution would have the programmer design several web pages each with wired-in logic to conform to the control flow of logging in correctly or trying again. Would the Seaside solution look like a subroutine call? I think this example can really illustrate Seaside's strong suit. Great explanations Ramon! This helps clear up a few murky notions I’ve had about Seaside. It’s really great when somebody can explain things so clearly and succinctly. At the risk of imposing, can you illustrate these concepts with a few working examples? There’s nothing like working code to nail a point home.

Here’s a simple Seaside application: present a login page that asks the user to enter a name and a password to authenticate. If the password is correct, the application presents a page that reads: ‘Congratulations, you are in’. If the password is incorrect, the application displays a page that reads: ‘Unknown user or password. Please try again.’

A typical web app solution would have the programmer design several web pages each with wired-in logic to conform to the control flow of logging in correctly or trying again. Would the Seaside solution look like a subroutine call? I think this example can really illustrate Seaside’s strong suit.

]]>