seaside June 2002

seaside@lists.squeakfoundation.org

19 participants
43 discussions

Squeak IDE written in Seaside
by Derek Brans 30 Jun '02

30 Jun '02

Hi all, I just finished tutorials 1 and 2. Very well written and easy to follow, even for a Smalltalk beginner. I'm looking forward to developing some real applications. This may have already been mentioned, but would it be interesting to have a Seaside version of all the Squeak IDE components, just like morphic or mvc? I will go on just in case: The user would create a new "seaside world" which would use a browser like scamper to render the world. You would be using browser to edit your code. Of course, that world could then just be an app on the Seaside server. You would only need to point your browser at that app and voila: you have a programming IDE. Regards, Derek Phasecraft: Smarter Web Development. Experts in web design, databases, flash design, multi-lingual sites, branding, marketing and web hosting. phone: 604-874-6463 mailto:info@phasecraft.com http://www.phasecraft.com

2 1

element <body>
by Jim Benson 30 Jun '02

30 Jun '02

The code generator seems pretty content spitting out <body> in IAPage>>printContentsTo: That is, it ignores the body tag attributes when generating code. However, I need to be able to say such silly things as: <body bgcolor='000000'> and such. Right, really I need to be able to put a 'class=' statement in there, but for sake of example... I don't see any way to do that currently. When I generate html ^ '<html> <heading> </heading> <body bgcolor=''000000''> </body> </html>' The HTML generated does not show the bgcolor tag. Is there a way around this? Jim

3 4

Dynamic HTML
by Lukas Renggli 28 Jun '02

28 Jun '02

Hi Reading some solder entries of the mailing-list, I learned that the templates are somehow static in Seaside. I think for most applications that is not a problem: but what, if there are foreign web-pages (downloaded form the internet) that I want to display as a component inside my web-application? I solved the problem in quite an ulgy manner and it works quite well. But now as 0.94 has been released I hesitate. I had to change the source-code of Seaside to make this work: IAPage>>printContentsTo: context context print: '<html>'. context print: '<head>'. self printHeadTo: context. context print: '</head>'. context print: '<body>'. self printBodyTo: context. self dynamicBody: context. " This is what I added " session printToolbar. context print: '</body>'. context print: '</html>'. IAPage>>dynamicBody " This is what I added " ^ '' So now I can override the message 'dynamicBody' in any component and return HTML-Code that has been downloaded (and even modified) form the internet. So my question is: What do you think about this? Are there any better ways to solve this problem? Thanks a lot in advance! Seaside is really great! Cheers Lukas

2 2

dynamic subcomponents proposal
by Avi Bryant 28 Jun '02

28 Jun '02

Actually this affects subcomponents pretty generally, but it's motivated by Tim's (and others) request for subcomponents with dynamic class. What I'm currently thinking about doing is this: - rather than configuring subcomponents in an #addHandlers (or #addBindingsTo:) method, each subcomponent will have a creation method in its parent. These will follow some sort of naming convention, ie, the subcomponent named 'questionPane' would be created by #subcomponentQuestionPane. The responsibility of this method is to create, configure, and return a subcomponent. For example, it might look like subcomponentQuestionPane ^ QuestionComponent new message: 'Answer the following question:' onDisplay: [:q | q question: self question] onUpdate: [:q | answer := q answer] - if the creation method takes 0 arguments, it is called only once in a component's lifetime - if the creation method takes 1 argument, it is called for every display of the subcomponent, and is passed the current instance of that subcomponent. The method can choose to return either the existing subcomponent or a new one. For example, subcomponentQuestionPane: current ^ current class = self question componentClass ifTrue: [current] ifFalse: [self question componentClass new ...] Comments: - are those rules too implicit? Is there a better way to do it (split it into two methods, one to decide whether to create and one to create)? - this draws a very strong line between simple template elements (ie, checkboxes) and full subcomponents. I used to think that was a bad idea, but it's bothering me less these days. What do y'all think? Avi

4 6

0.94 release
by Avi Bryant 27 Jun '02

27 Jun '02

So I've fixed a couple of nagging problems in 0.94 and patched up the existing documentation so it's not too inconsistent. Let's call this a release ;-). Seaside 0.94 is now available from http://beta4.com/seaside . This release significantly changes the way bindings are handled. A brief overview of what's required to migrate from 0.93 to 0.94: - all implementations of #addBindingsTo: will have to be changed to #addHandlers ('template' is now an instance variable of IAComponent and can be accessed directly). - The #bind:... and #set:... forms are now deprecated. #bind:toPath: and #set:toPath: will still function as before for subcomponents, but they are no longer supported for template elements. #bind:toNumber: and similar methods are replaced with #inputConversion: and #outputConversion; for example, this: addBindingsTo: template (template elementNamed: 'amount') bind: #value toNumber: 'amount' becomes this: addHandlers (template elementNamed: 'amount') inputConversion: #asNumber For subcomponents as well as template elements, it is recommended that the #onDisplay:/#onUpdate: methods be used rather than bindings. These are explained at http://beta4.com/seaside/design.html . All of the example applications have been updated to 0.94; it may be useful and informative to examine them. Please post any bugs, concerns, or problems you have when updating your applications. Cheers, Avi

1 0

backwards compatibility vs. progress
by Avi Bryant 27 Jun '02

27 Jun '02

Just a general philosophical question (maintainer angst, if you will). I'm struggling with the mythical 0.94 release, trying to shoehorn various agendas into it: my desire to separate the template system from the rest of the core and make programmatic html generation feasible, the need to simplify the bindings system, features that have been requested like dynamic/polymorphic subcomponents, and so on. Since each of these changes tends to break existing code anyway, the temptation is becoming stronger to just "burn the diskpacks" and start fresh on a new implementation of Seaside that takes what I've learned and reshapes it to better accomodate these and other features. What I don't know is how this would affect everyone else: some of you are deploying applications, some of you are working on ports to other dialects, etc. How important is a smooth migration from version to version, versus a clean, fresh design? Obviously the first step is to just release 0.94; the question is where to go after that. All comments much appreciated. Cheers, Avi

5 7

[ANN] Dolphin Seaside port
by Steve Waring 27 Jun '02

27 Jun '02

A Dolphin 5 port of the development version of Seaside is available at: http://www.chartexplorer.com/seaside/index.html Seaside is a Web Application framework by Avi Byrant and Julian Fitzell, more information can be found at: http://www.beta4.com/seaside Seaside is being actively developed, this is a port of the development version of Seaside, and therefore the tutorials and documentation on the Seaside pages will not fully match the code. The intended audience of this version is developers who wish to experiment with Seaside or help with the Seaside port to Dolphin. Please see the included notes for more information. Thanks to Avi Byrant for his work on Seaside. Thanks to Blair at Object-Arts for supplying the modified VM and Continuations package, that make a Dolphin port of Seaside possible (and the Dolphin version of "browser"!). Thanks to Jeffrey Odell and Jerry Bell for their support to see Seaside running in Dolphin. Steve Waring swaring(a)ozemail.com.au http://www.dolphinharbor.org

1 0

Iterators in 0.94
by Jim Benson 26 Jun '02

26 Jun '02

Back in the good old 0.93 days, I had a sketch for a little calendar app. I include it here for old times sake. OK, I go to convert it into 0.94. The way the calendar is supposed to work is that each day on the calendar has a color attached to it. You basically draw the days with the code in the RVCalendar>>html template with in 0.93 : ( tr repeat: '@week/weeks' ( td repeat: '@aDay/week' ( div align: center (font size: '+1' ( a sea:id: dayJump '[aDay.dayOfMonth]' ))) ) ) assign the color of the day with the binding: addBindingsTo: template (template elementNamed: 'aDay/week') set: #bgcolor toPath: 'dayBackground'. where RVCalendar>>dayBackground figures out which day it is by subjectDay := locals at: #aDay Fair enough. I start my 0.94 conversion. I know that I have to create an addHandler method for the IARepeatIterator. I thought it would be something along the lines of: (template elementNamed: '@aDay/week') onDisplay: [:r | r list: #week; iterator: #aDay; attributeAt: #bgcolor put: self dayBackground]. but when I get into >>dayBackground, there is nothing in the locals to indicate that there is anything associated with #aDay. Also, I a DNU barks at me when it gets to the aDay.dayOfMonth line, saying that it 'Could not find value for key "dayOfMonth"'. What am I missing? I assume that I'm messed up in the addHandler method. Jim

2 3

labelling radio buttons in a table
by Tim Rowledge 26 Jun '02

26 Jun '02

I'm making a table successfully from my potential multiple choice answers -looks pretty good so far. However, I'd really like to find a nice way to stick A -B-C etc next to the button, just like I do for the non-table questions. I haven't been able to find any hint of a way to do this from the W3C website. I have some vague ideas about other approaches but they all seem pretty likely to be ugly. My current html method looks like this:- html ^'[questionID]. [description] <if sea:id="needsTable=true"> <form sea:id="chooseAnswer" > <table border=1> <tr> <th> </th><th sea:id="hdr/tableHeaders">[hdr]</th> </tr> <tr sea:id="row/answerList"> <td><input type="radio" sea:id="tableAnswersGroup"></td><td sea:id="col/row"> [col] </td> </tr </table> <input type="submit" value="Answer"> </form </if> <if sea:id="needsTable=false"> <form sea:id="chooseAnswer" > <ol type="A" > <li sea:id="each/answerList"><input type="radio" sea:id="answersGroup"> [each] </ol> <input type="submit" value="Answer"> </form> </if> <br> <hr> Choose the answer you think is correct and then press the <b>Answer</b> button ' ======================= The least ugly thing I can come up right now is to make the #answerList method add the $A(etc) to the beginning of each element and then use COLSPAN=2 in the table defn to sort of fudge the letter onto the button. Yucky. Can anyone thing of a better trick? tim -- tim(a)sumeru.stanford.edu

2 7

Link to "a String as file"
by marbusse＠t-online.de 25 Jun '02

25 Jun '02

It's me again... What would be the simpliest way to send the contents of a stream a file to the client/ set a download link? One way, I thought, would be a link that creates the file and then points to a point of my apache. Is there a better way? Any pointers? I'll need this for an export-feature of my little WebBookmarks :-) Thank you, Markus

2 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside June 2002