seaside November 2004

seaside@lists.squeakfoundation.org

35 participants
43 discussions

Nested form tags
by Bany, Michel 04 Nov '05

04 Nov '05

I came accross some weird situation when using a component that is a composition of other components. A subcomponent may in turn be a composition of some more components. To make things even more complex, some deeply nested subcomponents may call some other component. Some of the subcomponents may contain some input html tag and as such will require to be contained in a form html tag. In such a complex construct it may be difficult to decide exactly what component should have the responsibility to generate the form tag. Also, it happened frequently to me that form tags become nested especially when a subcomponent calls another component that happens to be a dialog. Therefore I am making the following suggestion : Seaside should prevent form tags from being nested. It should discard any form tag that occurs within a previously opened form tag. With this in place, I can design a component that needs a form with a form construct knowing that if my component happens to be used inside a form, then my form construct will be discarded. Otherwise my form construct will be preserved. If my component calls a dialog component, the form generated by the dialog component will be discarded if my component happens to be used from inside a form. Michel.

6 6

Magic Date by Simon Willison
by Yar Hwee Boon 01 Jan '05

01 Jan '05

I've implemented Magic Date input by Simon Willison (http://simon.incutio.com/archive/2003/10/06/betterDateInput) and a similar variant for entering time. Feel free to use it or change it. Comments are welcome, thanks. -- Regards HweeBoon MotionObj

2 6

Unused instance variable?
by Samuel Tardieu 12 Dec '04

12 Dec '04

It looks like the "session" variable of "WAMain" is unused. Sam -- Samuel Tardieu -- sam(a)rfc1149.net -- http://www.rfc1149.net/sam

5 9

RE: Updated SmallBlog?
by Bob Houston 01 Dec '04

01 Dec '04

Thanks for the quick response. However, I'm going to need a little more assistance with SmallBlog. I've loaded SmallBlog-cwp.10.mcz from SqueakSource, but I'm unable to get it to run. As soon as I point my browser to http://localhost:9090/seaside/blog/admin to get the following walkback: MessageNotUnderstood: WARenderLoop>>start: WARenderLoop(Object)>>doesNotUnderstand: #start: SLBlogMain>>configureBlog: ... Please let me know if you can tell me what I'm doing wrong. TIA, Bob > On Fri, 26 Nov 2004 00:37:19 -0500, Bob Houston <bobh at agents.com> > wrote: > > > Could someone point me to the current version of SmallBlog? I'm > aware > > of the link below, but suspect that a later version is available. > This > > version requires squeak 3.6. I'd prefer running SmallBlog in a > squeak > > 3.7 image with a seaside 2.5 beta? > > Try SqueakSource http://kilana.unibe.ch:8888 > > > -- > Regards > HweeBoon > MotionObj

3 6

Some thoughts and cs to improve Seaside
by stephane ducasse 30 Nov '04

30 Nov '04

Hi all I started to really program with seaside and I bumped in the following problems: no class comments, limited examples...and I was in the train. And I did all the mistakes one after the other (no children, direct invocation of renderContentOn:...). So instead of complaining I would like to know what we can do to improve the situation. So here is a list of questions and simple cs to improve simply what can be done. - How can I get the WAAllTests running? I added a initialize method so that we can get AllTests up and running in the browser. I guess like that so may be this should be in the distribution... - What is the process to add comments to seaside? Should we send something to this list and avi will review it and include it? Even if this comment is copied an paste from the web site at least if it would have been there I would not make all my mistakes. - There are a lot of widgets but I could not find example (may be this is in WAAllTests)? Is there a simple process to have examples of the widgets. - Is there an FAQ? Is there a Wiki that we can add some examples? - Is there a process to collect and document other widgets? - Is there a database of widgets? - I saw a demoes of seaside written in seaside and some other pieces of code. How can I find all the projects available developed in seaside that I can use as examples? Would he make sense to have www.seasideSource.com (a SqueakSource containing only seaside examples?) Now some more technical questions: ------------------------------------------------------------------------ ------------------ What is the difference between a task and a component? ------------------------------------------------------------------------ ------------------ What is the difference between renderOn: and renderContentOn:? I tried to explain it here. ------------------------------------------------------------------------ ------------------ In WAStoreFillCart>>displayItems: aCollection | list | aCollection size = 1 ifTrue: [^ self displayItem: aCollection first]. list := WABatchSelection items: aCollection link: #title text: #subtitle. [self displayItem: (main call: list)] repeat I do not understand the repeat. ------------------------------------------------------------------------ ------------------ I used a batchSelection as follow: renderContentOn: html html divNamed: 'bdList' with:[. html text: 'BDs'. html break. batch := WABatchSelection items: items link: #title text: #title. batch renderContentOn: html] my domain objects have accents in its string representation and I do not know how from the model object I can specify that the text should be encoded. ------------------------------------------------------------------------ ------------------ In a batchSelection I wanted to have my own element displayer. Because I would like to have more information. Is it possible? So if you really like seaside (like me for example) I can't imagine that you can only use it without willing to help making it better. So I'm sure that if we take each us some times to comment a bit the classes we know and the key methods in no time we will get a much better version. I think that this is our responsibility as a community to help seaside inventors to make it better. Stef

3 4

Another question before going to sleep :)
by stephane ducasse 29 Nov '04

29 Nov '04

I have another problem with the following example WASimpleNavigation class>>example ^ self new add: WACounter new label: 'yet another counter'; add: WAPath example label: 'a cool path'; yourself When I press the ++ or -- of the counter I get an error Error: Components not found while processing callbacks: #(a WACounter) So I tried to add WASimpleNavigation>>children ^ Array with: self objects WASimpleNavigation>>objects ^ components collect: [:ea | ea value] but it did not fix the bug and I do not know what to do. What is my mistake? Thanks 28 November 2004 10:28:29 pm VM: Mac OS - a SmalltalkImage Image: Squeak3.7 [latest update: #5988] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir OSX:Users:ducasse:Workspace:ThirdCircle:SW2 Trusted Dir OSX:Users:ducasse:Workspace:ThirdCircle:SW2 Untrusted Dir OSX:Users:ducasse:Library:Preferences:Squeak:Internet:My Squeak WARenderLoop(Object)>>error: Receiver: a WARenderLoop Arguments and temporary variables: aString: 'Components not found while processing callbacks: #(a WACounter)' Receiver's instance variables: root: a WAToolFrame WARenderLoop>>unprocessedCallbacks: Receiver: a WARenderLoop Arguments and temporary variables: aCollection: #(a WAActionCallback) owners: #(a WACounter) ea: a WAActionCallback Receiver's instance variables: root: a WAToolFrame WARenderLoop>>processCallbacks: Receiver: a WARenderLoop Arguments and temporary variables: aCallbackStream: a WACallbackStream lastPosition: 0 ea: a WAToolFrame Receiver's instance variables: root: a WAToolFrame WARenderLoop>>render Receiver: a WARenderLoop Arguments and temporary variables: request: a WARequest context: a WARenderingContext document: nil docRoot: nil url: nil response: nil ea: nil Receiver's instance variables: root: a WAToolFrame --- The full stack --- WARenderLoop(Object)>>error: WARenderLoop>>unprocessedCallbacks: WARenderLoop>>processCallbacks: WARenderLoop>>render - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [] in WARenderLoop>>run {[self render]} BlockContext>>on:do: WARenderLoop>>withRenderNowHandler: [] in WARenderLoop>>run {[notification := self withRenderNowHandler: [self render]. notification...]} BlockContext>>on:do: WARenderLoop>>withPageExpiredHandler: [] in WARenderLoop>>run {[self withPageExpiredHandler: [notification := self withRenderNowHan...]} BlockContext>>repeat WARenderLoop>>run WARenderLoopMain>>start: WASession>>start: [] in WASession>>performRequest: {[^ self start: aRequest]} Dictionary>>at:ifAbsent: WASession>>performRequest: [] in WASession>>responseForRequest: {[self performRequest: aRequest]} BlockContext>>on:do: [] in WASession>>withErrorHandler: {[aBlock on: Error do: [:e | self errorHandler handleError: e. WAP...]} BlockContext>>on:do: WASession>>withErrorHandler: [] in WASession>>responseForRequest: {[self withErrorHandler: [self performRequest: aRequest]]} BlockContext>>on:do: WACurrentSession class(WADynamicVariable class)>>use:during: [] in WASession>>responseForRequest: {[WACurrentSession use: self during: [self withErrorHandler: [self pe...]} [] in WASession>>withEscapeContinuation: {[:cc | escapeContinuation := cc. aBlock value. self pageIntentionallyLeft...]} Continuation class>>currentDo: WASession>>withEscapeContinuation: WASession>>responseForRequest: [] in WASession>>incomingRequest: {[self responseForRequest: aRequest]} BlockContext>>on:do: [] in WAProcessMonitor>>critical:ifError: {[value := aBlock on: Error do: errorBlock]} BlockContext>>ensure: [] in WAProcessMonitor>>critical:ifError: {[[value := aBlock on: Error do: errorBlock] ensure: [responseSem signal]]} [] in BlockContext>>newProcess {[self value. Processor terminateActive]}

4 3

About selecting the first element of a WASimpleNavigation
by stephane ducasse 29 Nov '04

29 Nov '04

hi WASimpleNavigation class>>example | counter | counter := WACounter new . ^ self new add: counter label: 'yet another counter'; add: WAPath example label: 'a cool path'; select: counter; yourself While trying to understand how the simple (and quite raw) widgets of seaside work, I tried to create the previous example class methods on WASimpleNavigation. Now when I start the WAExampleBrowser I get two tabs with the correct labels but I do not get the contents of the first one active ie I can't see the counter for example. I tried to used select: to select the first "object" but nothing changes. What am I doing wrong? Stef

2 1

[BUG]? WASimpleNavigation
by stephane ducasse 29 Nov '04

29 Nov '04

controllers is not defined.... May be this method is obsolete. selectedController ^ (controllers detect: [:ea | ea key = self selection] ifNone: [^ nil]) value Stef

2 1

about method category
by stephane ducasse 28 Nov '04

28 Nov '04

I started to rename some of the as yet unclassified category in seaside to ease navigation but I would like to know if mc will keep the category changes and if I'm not losing my time... Stef

2 1

Re: [Seaside] Some thoughts and cs to improve Seaside
by stephane ducasse 28 Nov '04

28 Nov '04

hi avi Thanks for your anwsers. I like the new logo :)) >> - How can I get the WAAllTests running? >> I added a initialize method so that we can get AllTests up and running >> in the browser. > > The other way would be through the /seaside/config app: > - add a new application named "tests" > - choose WAAllTests as the root component Ok I remember now I could not figure it out when I tried. I tried for WAExampleBrowser But I could not understand where I can choose WAExampleBrowser. Then in addition in Path I typed /seaside/Examples and then I got /seaside/seaside/Examples so may be you should provide a default text "name of your application (without seaside in front)" Should I change main class in the configuration pane? I got lost.Really lost. I even tried to look at counter but could not find WAcounter in the config interface to remove counter and add it again to see where WACounter should be entered >> I guess like that so may be this should be in the distribution... > > AllTests is really meant more as a (non-automated) regression test > suite than as a set of examples. Ideally we would have a > better/prettier set of components that were meant purely as examples. But better than nothing :) I took me a while to understand that path could be a tab :) >> - What is the process to add comments to seaside? Should we send >> something to this list and avi will review it and include it? > > Yes, preferably as a .mcz. If you have a bunch of comments to submit, > it's probably best to just send one version that has all of them > added. Ok >> - There are a lot of widgets but I could not find example (may be this >> is in WAAllTests)? >> Is there a simple process to have examples of the widgets. > > Actually, yes, although it's little known and little used (but please, > let's change that). Just add class-side creation methods to > subclasses of WAComponent, with selectors that start with #example. > These will then automatically show up in WAExampleBrowser. When I do http://localhost:9090/seaside.....I get an error So how do I get the configuration so that I can add WAExampleBrowser to see the demoes... Ok I see http://localhost:9090/seaside/config ! Now how can I reset the password :) I saw that there is WAauthMain createRoot but I do not know how I can reset it. So now I redefined verify to ^true (a bit radical but works quite well :)) So can I also deduce when canBeRoot ^ true this means that the component can be manually regsitered using the config panel. ifTrue: we should add it in the method comments. >> - Is there an FAQ? Is there a Wiki that we can add some examples? >> - Is there a process to collect and document other widgets? >> - Is there a database of widgets? > > Not yet. These are definitly things we need to do. Does anybody want > to volunteer to organize this? Please someone do it Seaside and avi deserve it >> Would he make sense to have >> www.seasideSource.com (a SqueakSource containing only seaside >> examples?) > > That would certainly be one way to organize the above... if someone > sets that up, I'll be happy to move the development of the Seaside > package itself to it as well. Ok bernish seasiders can we do that (besides rebooting kilana since the roots changed the file system but did reboot kilana :(. >> What is the difference between a task and a component? > > This is a FAQ. Both of them are reusable, embeddable, callable pieces > of user interface. A component has state (instance variables), > behavior (it may change its state, and it may also choose to display > other components with #call:), and appearance (it renders HTML). A > Task has only the first two - it doesn't render any HTML directly, but > only through the components it calls. This is useful when what you > want to encapsulate/embed/call is purely a process (show this > component, then this one, then this one). > > The key method for WATask is #go - as soon as a task is displayed, > this method will get invoked, and will presumably #call: other > components. > Excellent I added that into the new class comment of task joined with all the rest as a mcz file of course :) >> What is the difference between renderOn: and renderContentOn:? > > #renderOn: is the low level method that gets sent to any object > encountered by the HtmlRenderer (for example, if you do "html bold: > 'foo'", then String>>renderOn: will get called). > > Components need to do various special things when they are rendered > (for example, they need to render any Decoration objects that have > been applied to them). So subclasses are expected to override > #renderContentOn: instead (this is the Template Method pattern, I > guess). By the way just for the record: I guess that what you call decorator are chains of responsibilities since the interface of the decorated objects does not grow but it just give the power to other guys to talk and act. I may be wrong but this was always confusing me when I learned that you used decorators. >> In >> WAStoreFillCart>>displayItems: aCollection >> | list | >> aCollection size = 1 ifTrue: [^ self displayItem: aCollection >> first]. >> list := WABatchSelection >> items: aCollection >> link: #title >> text: #subtitle. >> [self displayItem: (main call: list)] repeat >> >> I do not understand the repeat. > > Yeah, that's a little subtle. Why don't you try removing it and see > what happens? Ok I will. So many stuff were not breaking that I did a divide and conquire onmy problems :) Now I'm getting over a lot of them. It was smelling fishy to me ;) > "self displayItem: (main call: list)" is letting the user pick and > examine a single item from the collection. But usually when you're > looking at a list of search results, you want to browse through many > items. So all this is doing is letting you pick another one (by > showing you the list again) when you're done with the first one. I like the trick >> my domain objects have accents in its string representation >> and I do not know how from the model object I can specify that the >> text should be encoded. > > It's best to have your domain objects encoded in UTF-8; then you > shouldn't need to do any conversion. Ok I will try to understand how I can do that. >> In a batchSelection I wanted to have my own element displayer. Because >> I would like >> to have more information. Is it possible? > > Yes, if you look at WABatchSelection you'll see that the list of page > numbers is in fact another, smaller component called WABatchedList. yes I saw that guy since originally I started to use it. > You can use WABatchedList with your own way of displaying the list. > You give it the full collection with #items:, and retrieve and display > just the current batch with #batch. Ok I was wondering if there was a pluggableItemSlectionBatchedList :) >> So if you really like seaside (like me for example) I can't imagine >> that you can only use it without willing to help making it better. So >> I'm sure that if we >> take each us some times to comment a bit the classes we know and the >> key methods in >> no time we will get a much better version. I think that this is our >> responsibility as a community >> to help seaside inventors to make it better. > > I certainly won't argue with that :). So community, avi explicitly says that he would appreciate our support :) So let us make him having more time to invent his and our future. Stef

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside November 2004