seaside July 2004

seaside@lists.squeakfoundation.org

16 participants
33 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

request termination
by Avi Bryant 10 Aug '04

10 Aug '04

Here's something I'd like an opinion on: if the browser times out when waiting for a response, or the user hits the stop button, and the connection is dropped, Seaside still keeps chugging away on the request. Should we terminate the process instead? And if so, how do we get a notification from the webserver about the dropped connection in a portable way? At least in Squeak, terminating the process does make sure to run all the #ensure: blocks, and I expect/hope the same would be true in other dialects as well. So as long as people are careful, it shouldn't do *too* much damage to kill the process. It's also unlikely that the callback processing is what would take too long and timeout (barring an inifinite loop) - usually it would be the render phase getting terminated, which should be pretty harmless. A

3 3

2.5b2
by Avi Bryant 04 Aug '04

04 Aug '04

Hi folks, Just released Seaside 2.5b2. The changes from b1, mostly thanks to Adrian Lienhard and Michel Bany, are: - added #orderedList: and #orderedList:do: to AbstractHtmlBuilder - fixed Application>>name to allow an empty basePath - fixed #findStyles to include the request in the context - fixed #valueInputOfType:value:callback: to use the raw string instead of throwing an error when it is expecting a number in the callback but doesn't find one - added a 'Cache-Control: No-cache' header to rendered pages by default I've also been experimenting some with Javascript's XMLHttpRequest support, and have included a preview of this work. You can read more in this blog post, and see an example in WALiveRequestTest: http://www.cincomsmalltalk.com/userblogs/avi/blogView? showComments=true&entry=3268075684 Like the Canvas work, this is *not* a supported part of Seaside 2.5, but since it's independent of the rest of the code I don't mind keeping the previews in the release. Avi

4 7

Changes in GOODS not showing in browser
by LK 04 Aug '04

04 Aug '04

Thanks for all the support. You guys are the greatest! I now have an app that will add and delete records from a GOODS database. My problem now is they added records are not showing in the PMLogsView when I refresh my browser. The user must close and re-open the browser to see the changes. Is there a way to fix this? -Larry Relevent code is below: PMLogsTask>>renderContentOn: html |db | html cssId: 'banner'. html table: [ html tableRowWith: [ html divNamed: 'title' with: self title. html divNamed: 'subtitle' with: self subtitle. ] ]. html render: pmLogsView. html text: 'testing'. ----- PMLogsView>>renderContentOn: html | | html table: [ html tableRow: [html tableHeading: 'View all Log Entries'; space; space; space.]]. html anchorWithAction: [self call: PMLogAddItem new] text: 'Add'. html attributeAt: 'cellspacing' put: 0; attributeAt: 'cellpadding' put: 5; attributeAt: 'border' put: 2. html table: [ allRecords do: [:i | html tableRow: [ html tableData: [html anchorWithAction: [self delete: i from: db] text: 'Del']. html tableData: i type. html tableData: i entryDate. html tableData: i startTime. html tableData: i entryText. html tableData: i endTime. ]. ]. html tableRow: [] ] ----------- PMLogAddItem>>renderContentOn: html " show add new log form" item := PMLogItem new. item initialize. html form: [ html table: [ html tableRow: [html tableHeading: 'New Log Entry']. html tableRow: [html tableData: 'Date'. html tableData: item entryDate]. html tableRow: [html tableData: 'Time'. html tableData: item startTime]. html tableRow: [html tableData: 'Type'. html tableData: [html selectFromList: #('DRE' 'SA' 'DBA' 'TEST') selected: (item type) callback: [:i | item type: i]]]. html tableRow: [html tableData: 'Entry Text'. html tableData: [ html textAreaWithValue: 'log entry' callback: [:i| item entryText: i]]]. ]. html submitButtonWithAction: [self add: item] text: 'Save'. ] --------- PMLogAddItem>>add: aRecord db _ PMDatabase new connect. self table: (db root at: 'logs'). table add: aRecord. db commit. db flush. db logout. self answer. -----

3 5

Subcomponent not returning to called component
by LK 29 Jul '04

29 Jul '04

How do I get a component to return to whoever called it, when it finishes? For example, I have a PMLogsView class that displays a list of records. It also contains a link to PMLogAddItem class. PMLogAddItem displays a form. When it is submitted, it adds a record to the database and redisplays itself so that another record can be added. I would rather it returned instead to the calling class. ( PMLogsView). PMLogsView>>RenderContentOn: html " . . ." html anchorWithAction: [self call: PMLogAddItem new] text: 'Add'. " . . ." ------------------------- -Larry

2 1

Add button not showing it's page
by s002 28 Jul '04

28 Jul '04

I have an object that shows a record from a GOODS database. I created a link to 'add' a new record. When I click on the link, the screen flashes and stays at the recordlist page. Can someone help me. PMLogsView>>renderContentOn: html | | html table: [ html tableRow: [html tableHeading: 'View all Log Entries'; space; space; space. html tableData: [html anchorWithAction: [self renderAddOn: html] text: 'Add']]]. html attributeAt: 'cellspacing' put: 0; attributeAt: 'cellpadding' put: 5; attributeAt: 'border' put: 2. html table: [ allRecords do: [:i | html tableRow: [ html tableData: [html anchorWithAction: [self delete: i from: db] text: 'Del']. html tableData: i type. html tableData: i entryDate. html tableData: i startTime. html tableData: i entryText. html tableData: i endTime. ]. ]. html tableRow: [] ] ------ and here is the PMLogsView>>renderAddOn: html " show add new log form" aRecord := PMLogItem new. aRecord initialize. html form: [ html table: [ html tableRow: [html tableHeading: 'New Log Entry']]. html text: 'TEST NEW ENTRY PAGE'. html text: aRecord entryDate.]

5 5

Deleting from GOODS.
by LK 28 Jul '04

28 Jul '04

OK, I've got a table that will display records from my GOODS database. Many thanks to Bany and Shaffer. Would someone tell me what's wrong with my delete: method.? I've taken code from a 'table tutorial' and modified it as follows: my PMLogsView class has an allRecords instance var which holds the PMLogs ( Ordered Collection ol PMLogItem objects). PMLogsView>>renderContentOn: html | | allRecords := db root at: 'logs'. html table: [ html tableRow: [html tableHeading: 'View all Log Entries']]. html attributeAt: 'cellspacing' put: 0; attributeAt: 'cellpadding' put: 5; attributeAt: 'border' put: 2. html table: [ allRecords do: [:i | html tableRow: [ html tableData: [html anchorWithAction: [self delete: i] text: 'Del']. html tableData: i type. html tableData: i entryDate. html tableData: i startTime. html tableData: i entryText. html tableData: i endTime. ]. ]. html tableRow: [] ] ----------------------------- The delete: method looks like this: PMLogsView>>delete: aRecord (self confirm: 'Are you sure you want to delete ', (aRecord entryText) printString, '?') ifTrue: [allRecords removeAt: aRecord] ---------------------------- When I excute it Seaside displays the following error: MessageNotUnderstood: PMLogItem>>< * PMLogItem(Object)>>doesNotUnderstand: #< self a PMLogItem aMessage a Message with selector: #< and arguments: #(1) * KKObjectProxy>>doesNotUnderstand: #< self a PMLogItem aMessage a Message with selector: #< and arguments: #(1) * PMLogs(OrderedCollection)>>at: self a PMLogs(a PMLogItem a PMLogItem a PMLogItem a PMLogItem) anInteger a PMLogItem * PMLogs(OrderedCollection)>>removeAt: self a PMLogs(a PMLogItem a PMLogItem a PMLogItem a PMLogItem) index a PMLogItem removed nil * KKObjectProxy>>doesNotUnderstand: #removeAt: self a PMLogs(a PMLogItem a PMLogItem a PMLogItem a PMLogItem) aMessage a Message with selector: #removeAt: and arguments: #(a PMLogItem) * PMLogsView>>delete: self a PMLogsView aRecord a PMLogItem * [] in PMLogsView>>renderContentOn: self a PMLogsView html a WAHtmlRenderer i a PMLogItem * WAActionCallback>>evaluateWithArgument: self a WAActionCallback anObject '' * WAActionCallback(WACallback)>>evaluateWithField: self a WAActionCallback anObject '' * WACallbackStream>>processCallbacksWithOwner: self a WACallbackStream anObject a PMLogsView callback a WAActionCallback * PMLogsView(WAPresenter)>>processCallbackStream: self a PMLogsView aCallbackStream a WACallbackStream * [] in PMLogsTask(WAPresenter)>>processChildCallbacks: self a PMLogsTask aStream a WACallbackStream ea a PMLogsView * PMLogsView(WAComponent)>>decorationChainDo: self a PMLogsView aBlock [] in PMLogsTask(WAPresenter)>>processChildCallbacks: * [] in PMLogsTask(WAComponent)>>nextPresentersDo: self a PMLogsTask aBlock [] in PMLogsTask(WAPresenter)>>processChildCallbacks: ea a PMLogsView * [] in PMLogsTask(WAComponent)>>childrenDo: self a PMLogsTask aBlock [] in PMLogsTask(WAComponent)>>nextPresentersDo: ea a PMLogsView * Array(SequenceableCollection)>>do: self #(a PMLogsView) aBlock [] in PMLogsTask(WAComponent)>>childrenDo: index 1 indexLimiT 1 * PMLogsTask(WAComponent)>>childrenDo: self a PMLogsTask aBlock [] in PMLogsTask(WAComponent)>>nextPresentersDo: ea a PMLogsView * PMLogsTask(WAComponent)>>nextPresentersDo: self a PMLogsTask aBlock [] in PMLogsTask(WAPresenter)>>processChildCallbacks: ea a PMLogsView * PMLogsTask(WAPresenter)>>processChildCallbacks: self a PMLogsTask aStream a WACallbackStream ea a PMLogsView * PMLogsTask(WAPresenter)>>processCallbackStream: self a PMLogsTask aCallbackStream a WACallbackStream * [] in WAToolFrame(WAPresenter)>>processChildCallbacks: self a WAToolFrame aStream a WACallbackStream ea a PMLogsTask * PMLogsTask(WAComponent)>>decorationChainDo: self a PMLogsTask aBlock [] in WAToolFrame(WAPresenter)>>processChildCallbacks: * [] in WAToolFrame(WAComponent)>>nextPresentersDo: self a WAToolFrame aBlock [] in WAToolFrame(WAPresenter)>>processChildCallbacks: ea a PMLogsTask * [] in WAToolFrame(WAComponent)>>childrenDo: self a WAToolFrame aBlock [] in WAToolFrame(WAComponent)>>nextPresentersDo: ea a PMLogsTask * Array(SequenceableCollection)>>do: self #(a PMLogsTask) aBlock [] in WAToolFrame(WAComponent)>>childrenDo: index 1 indexLimiT 1 * WAToolFrame(WAComponent)>>childrenDo: self a WAToolFrame aBlock [] in WAToolFrame(WAComponent)>>nextPresentersDo: ea a PMLogsTask * WAToolFrame(WAComponent)>>nextPresentersDo: self a WAToolFrame aBlock [] in WAToolFrame(WAPresenter)>>processChildCallbacks: ea a PMLogsTask * WAToolFrame(WAPresenter)>>processChildCallbacks: self a WAToolFrame aStream a WACallbackStream ea a PMLogsTask * WAToolFrame(WAPresenter)>>processCallbackStream: self a WAToolFrame aCallbackStream a WACallbackStream * [] in WARenderLoop>>processCallbacks: self a WARenderLoop aCallbackStream a WACallbackStream lastPosition 0 ea a WAToolFrame * WAToolFrame(WAComponent)>>decorationChainDo: self a WAToolFrame aBlock [] in WARenderLoop>>processCallbacks: * WARenderLoop>>processCallbacks: self a WARenderLoop aCallbackStream a WACallbackStream lastPosition 0 ea a WAToolFrame * WARenderLoop>>render self a WARenderLoop request a WARequest context a WARenderingContext document nil docRoot nil url nil response nil ea nil * [] in WARenderLoop>>run self a WARenderLoop notification nil * BlockContext>>on:do: self [] in WARenderLoop>>run exception WARenderNotification handlerAction [] in WARenderLoop>>withRenderNowHandler: handlerActive true * WARenderLoop>>withRenderNowHandler: self a WARenderLoop aBlock [] in WARenderLoop>>run n nil * [] in WARenderLoop>>run self a WARenderLoop notification nil * BlockContext>>on:do: self [] in WARenderLoop>>run exception WAPageExpired handlerAction [] in WARenderLoop>>withPageExpiredHandler: handlerActive true * WARenderLoop>>withPageExpiredHandler: self a WARenderLoop aBlock [] in WARenderLoop>>run n nil * [] in WARenderLoop>>run self a WARenderLoop notification nil * BlockContext>>repeat self [] in WARenderLoop>>run * WARenderLoop>>run self a WARenderLoop notification nil * WARenderLoopMain>>start: self a WARenderLoopMain aRequest a WARequest * WASession>>start: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest * [] in WASession>>performRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest key nil continuation nil * Dictionary>>at:ifAbsent: self a Dictionary() key '_k' aBlock [] in WASession>>performRequest: assoc nil * WASession>>performRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest key nil continuation nil * [] in WASession>>responseForRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest * BlockContext>>on:do: self [] in WASession>>responseForRequest: exception Error handlerAction [] in WASession>>withErrorHandler: handlerActive false * [] in WASession>>withErrorHandler: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aBlock [] in WASession>>responseForRequest: e MessageNotUnderstood: PMLogItem>>< w nil * BlockContext>>on:do: self [] in WASession>>withErrorHandler: exception Warning handlerAction [] in WASession>>withErrorHandler: handlerActive true * WASession>>withErrorHandler: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aBlock [] in WASession>>responseForRequest: e MessageNotUnderstood: PMLogItem>>< w nil * [] in WASession>>responseForRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest * BlockContext>>on:do: self [] in WASession>>responseForRequest: exception WACurrentSession handlerAction [] in WACurrentSession class(WADynamicVariable class)>>use:during: handlerActive true * WACurrentSession class(WADynamicVariable class)>>use:during: self WACurrentSession anObject a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aBlock [] in WASession>>responseForRequest: n WACurrentSession * [] in WASession>>responseForRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest * [] in WASession>>withEscapeContinuation: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aBlock [] in WASession>>responseForRequest: cc a Continuation * Continuation class>>currentDo: self Continuation aBlock [] in WASession>>withEscapeContinuation: * WASession>>withEscapeContinuation: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aBlock [] in WASession>>responseForRequest: cc a Continuation * WASession>>responseForRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest * [] in WASession>>incomingRequest: self a WASession(/seaside/logs?_s=YGJFCkUdbwMVquFZ) aRequest a WARequest e nil * BlockContext>>on:do: self [] in WASession>>incomingRequest: exception Error handlerAction [] in WASession>>incomingRequest: handlerActive true * [] in WAProcessMonitor>>critical:ifError: self a WAProcessMonitor aBlock [] in WASession>>incomingRequest: errorBlock [] in WASession>>incomingRequest: value a WAResponse * BlockContext>>ensure: self [] in WAProcessMonitor>>critical:ifError: aBlock [] in WAProcessMonitor>>critical:ifError: returnValue nil * [] in WAProcessMonitor>>critical:ifError: self a WAProcessMonitor aBlock [] in WASession>>incomingRequest: errorBlock [] in WASession>>incomingRequest: value a WAResponse * [] in BlockContext>>newProcess self [] in WAProcessMonitor>>critical:ifError: Thanks for the help. -Larry

3 5

RE: cssClass and cssID (was testing framework)
by Brian Brown 24 Jul '04

24 Jul '04

On Jul 22, 2004, at 4:30 PM, Avi Bryant wrote: > One thing this encourages is adding good CSS ids throughout the > render, which is something that's always seemed overly clunky to me. > That is, the necessity to put #cssClass: and #cssId:, as well as > #div:, #span:, etc everywhere, clutters up the more interesting parts > (like anchors and callbacks) of any given render method. Anyone have > any good ideas to keep these separated? I'm just throwing out random > thoughts here, but one possible pattern that occurs to me would be to > introduce a higher level wrapper around the HtmlRenderer, that was > specific to a particular component. For lack of a more imaginative > name, let's call this a View. The idea would be that the *structure* > of the rendering is still controlled by the component, but the > specifics (the actual tags and ids) are filled in by the View. So, > for example, take the following fairly typical render method: > > MyComponent>>renderItems: aCollection on: html > html cssClass: 'item-list'. > html unorderedList: > [aCollection do: > [:ea | > html listItem: > [html cssClass: 'item-choose'. > html anchorWithAction: [self choose: ea] text: ea description. > html spanClass: 'item-actions' with: [html anchorWithAction: [self > remove: ea] text: '(remove)']]]] > > Would it be better, or just more confusing and cumbersome, to split > this into something like: > > MyComponent>>renderItems: aCollection on: view > view itemList: > [aCollection do: > [:ea | > view item: > [view chooseItem: [self choose: ea] text: ea description. > view itemActions: [view removeItem: [self remove: ea]]]]] > > MyView>>itemList: aBlock > html cssClass: 'item-list'. > html unorderedList: aBlock > > MyView>>item: aBlock > html listItem: aBlock > > MyView>>chooseItem: actionBlock text: aString > html cssClass: 'item-choose'. > html anchorWithAction: actionBlock text: aString > > MyView>>itemActions: aBlock > html spanClass: 'item-actions' with: aBlock > > MyView>>removeItem: actionBlock > html anchorWithAction: actionBlock text: '(remove)' > > Anyway, just a thought. > > Cheers, > Avi > I think the second way introduces an unnecessary layer of abstraction - yes, each individual method is cleaner to read the CSS info, but overall it would be much more difficult building that component; I like the conciseness of the first one. What about the idea of assigning each component a default css name based on the name of the component. All elements rendered in that component would be in a namespace (from a CSS perspective) like: MyComponent.table MyComponent.h3 etc. This would follow the standard CSS inheritance, giving very fine grained control to each component only if desired. This doesn't help with <div /> but those are structural anyway, and it is very useful to see what is being rendered inside of a particular div element when editing the render methods. Just for various text styles, spanClass:with: and spanNamed:with: don't seem too cumbersome. Using this scheme, a #spanText: could also be created that acted like #text: So instead of: html span: [html text: 'Some words'] you would have: html spanText: 'Some words'. "This span would be covered by the default css component name space." I may be missing some things here, and I certainly am not using CSS to it's full potential in my own Seaside work, but what do you think? Brian

2 2

SeasideTesting released on SqueakMap
by C. David Shaffer 23 Jul '04

23 Jul '04

Thanks to all of you that provided feedback on my SeasideTesting package! I have created a SqueakMap package for it: http://map1.squeakfoundation.org/sm/package/f1f1e290-e55f-47d1-b82a-9c2f4f1… and made the tutorial avaiable as well: http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingCo… This new release has some improvements from the one I posted to the list previously: . you can debug errors during component rendering . I refactored the input component support to make dealing with the various components more uniform . the web test runner now supports viewing the responses generated during the test run (follow the History link) This will be my last release for Seaside 2.5a5 since my extensions to WAHalo tend to be fairly version dependent. There is still a fair amount to be done but I've been using it off and on for a couple weeks and I think that, if you're test infected, you'll find it makes a good framework upon which to build component tests. Feedback is always welcome ;-) David

2 3

2.5 beta 1
by Avi Bryant 23 Jul '04

23 Jul '04

Hi all, I feel like Seaside 2.5 has now settled down enough, and has accomplished enough of what I was shooting for, to freeze the feature set and move it into beta. I've put the first beta release on SqueakMap; this is essentially 2.5a6 with general fixes, and with modifications to WAHtmlDocument to allow streaming*. Anyone still using Seaside 2.3 should now feel pretty safe starting to port their code to 2.5 without feeling like there will be major changes to the system. This has been a pretty long alpha, I think due to my trying to bundle too many changes at once. Hopefully the beta will move along quicker. I'll be sitting here, eagerly awaiting bug reports... Have fun with it, Avi * Switching to a streaming mode should now require no changes to user code; however, a fully streaming configuration requires support from the webserver, and I haven't yet found a way to do this integration cleanly and portably. So although the streaming changes have eliminated an internal buffer (by hooking the document directly into the Response object), the Response object itself still buffers the output and gives it to the webserver as one chunk.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside July 2004