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 From avi at beta4.com Fri Jul 23 21:45:20 2004 From: avi at beta4.com (Avi Bryant) Date: Fri Jul 23 21:45:23 2004 Subject: [Seaside] RE: cssClass and cssID (was testing framework) In-Reply-To: <5E1CD850-DCC0-11D8-989C-003065F89450@techgame.net> References: <5E1CD850-DCC0-11D8-989C-003065F89450@techgame.net> Message-ID: On Jul 23, 2004, at 8:52 AM, Brian Brown wrote: > 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. Probably true. > 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. Yes, this makes good sense. The question is, I guess, where you hang that class. Do you wrap every component in a div automatically? But some components should be in spans instead, and some probably shouldn't be in either. So are there methods #wantsDiv, #wantsSpan that can be overridden? Or maybe there are #divClass and #spanClass methods, and if either is overridden to return something non-nil, then the appropriate tag is used (and you could have, by default, divClass ^ self class name ) > This doesn't help with

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'. There's no need for #spanText: - this will already work: html span: 'Some words'. Methods like #span: aren't actually expecting a block specifically (though a block is the most common thing to give them), they're expecting anything that implements #renderOn:. It's just that: BlockContext>>renderOn: aRenderer self value Avi From avi at beta4.com Fri Jul 23 21:46:36 2004 From: avi at beta4.com (Avi Bryant) Date: Fri Jul 23 21:46:44 2004 Subject: [Seaside] SeasideTesting released on SqueakMap In-Reply-To: <41009DC0.90904@acm.org> References: <40FD7D93.4040905@acm.org> <41009DC0.90904@acm.org> Message-ID: <02216502-DCE1-11D8-B33C-000A95DB7844@beta4.com> On Jul 22, 2004, at 10:10 PM, C. David Shaffer wrote: > Did the Seaside blog (Smallblog?) include generation of feeds in > various syndication formats? If so, how was that done? Just RSS. And the RSS output was totally separate from the Seaside UI. Avi From rbb at techgame.net Sat Jul 24 01:11:00 2004 From: rbb at techgame.net (Brian Brown) Date: Sat Jul 24 01:11:08 2004 Subject: [Seaside] RE: cssClass and cssID (was testing framework) In-Reply-To: References: <5E1CD850-DCC0-11D8-989C-003065F89450@techgame.net> Message-ID: <1090624260.8209.3.camel@siniwali.ablelinktech.com> On Fri, 2004-07-23 at 13:45, Avi Bryant wrote: > On Jul 23, 2004, at 8:52 AM, Brian Brown wrote: > > > 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. > > Probably true. > > > 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. > > Yes, this makes good sense. The question is, I guess, where you hang > that class. Do you wrap every component in a div automatically? But > some components should be in spans instead, and some probably shouldn't > be in either. So are there methods #wantsDiv, #wantsSpan that can be > overridden? Or maybe there are #divClass and #spanClass methods, and > if either is overridden to return something non-nil, then the > appropriate tag is used (and you could have, by default, > > divClass > ^ self class name > Yes, I was initially thinking you would wrap every component automatically, but having the #divClass and #spanClass would work well, and give a lot of control for components. We would only have to resort to the current way of doing things in limited cases. > There's no need for #spanText: - this will already work: > > html span: 'Some words'. > > Methods like #span: aren't actually expecting a block specifically > (though a block is the most common thing to give them), they're > expecting anything that implements #renderOn:. It's just that: > > BlockContext>>renderOn: aRenderer > self value > I probably should have tried it that way ;) Brian From s002 at landr.net Sat Jul 24 04:22:18 2004 From: s002 at landr.net (LK) Date: Sat Jul 24 04:22:44 2004 Subject: [Seaside] Deleting from GOODS. Message-ID: <4101C7DA.1070303@landr.net> 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 From adi at netstyle.ch Sat Jul 24 11:54:57 2004 From: adi at netstyle.ch (Adrian Lienhard) Date: Sat Jul 24 11:55:05 2004 Subject: [Seaside] Deleting from GOODS. In-Reply-To: <4101C7DA.1070303@landr.net> References: <4101C7DA.1070303@landr.net> Message-ID: <855F5A27-DD57-11D8-A70F-000A95E07986@netstyle.ch> Hi Larry It should say "allRecords remove: aRecord" and not #removeAt: (latter takes an integer to remove an item from the ordered collection at a specific index). Adrian On Jul 24, 2004, at 4:22 AM, LK wrote: > 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 > > > _______________________________________________ > Seaside mailing list > Seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside > > ___________________ Adrian Lienhard www.adrian-lienhard.ch www.netstyle.ch From s002 at landr.net Sat Jul 24 16:35:48 2004 From: s002 at landr.net (LK) Date: Sat Jul 24 16:35:56 2004 Subject: [Seaside] Deleting from GOODS. In-Reply-To: <855F5A27-DD57-11D8-A70F-000A95E07986@netstyle.ch> References: <4101C7DA.1070303@landr.net> <855F5A27-DD57-11D8-A70F-000A95E07986@netstyle.ch> Message-ID: <410273C4.1000505@landr.net> Adrian Lienhard wrote: > Hi Larry > > It should say "allRecords remove: aRecord" and not #removeAt: (latter > takes an integer to remove an item from the ordered collection at a > specific index). > > Adrian Thanks, That executed w/o error, but. nothing was removed from GOODS. I added this method: delete: aRecord from: aDatabase (self confirm: 'Are you sure you want to delete: ', (aRecord entryText) printString, '?') ifTrue: [allRecords remove: aRecord. aDatabase commit.]. It says that it cannot understand #commit. In workspace, db commit executes properly. What am I missing here????? -Larry > > On Jul 24, 2004, at 4:22 AM, LK wrote: > >> 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 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: [] >> ] >> ----------------------------- >> 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: > > ----- SNIP ----- From avi at beta4.com Sat Jul 24 23:33:52 2004 From: avi at beta4.com (Avi Bryant) Date: Sat Jul 24 23:33:57 2004 Subject: [Seaside] Deleting from GOODS. In-Reply-To: <410273C4.1000505@landr.net> References: <4101C7DA.1070303@landr.net> <855F5A27-DD57-11D8-A70F-000A95E07986@netstyle.ch> <410273C4.1000505@landr.net> Message-ID: <283AB590-DDB9-11D8-B33C-000A95DB7844@beta4.com> On Jul 24, 2004, at 7:35 AM, LK wrote: > Adrian Lienhard wrote: > >> Hi Larry >> >> It should say "allRecords remove: aRecord" and not #removeAt: (latter >> takes an integer to remove an item from the ordered collection at a >> specific index). >> >> Adrian > > Thanks, That executed w/o error, but. nothing was removed from GOODS. > I added this method: > delete: aRecord from: aDatabase > (self confirm: 'Are you sure you want to delete: ', (aRecord > entryText) printString, '?') > ifTrue: [allRecords remove: aRecord. > aDatabase commit.]. > > It says that it cannot understand #commit. In workspace, db commit > executes properly. What am I missing here????? Well, you must somehow have the wrong object passed in as aDatabase. When the MNU #commit error comes up, what class does it say aDatabase is? That might give you a clue as to what's going wrong. Avi From s002 at landr.net Mon Jul 26 18:34:17 2004 From: s002 at landr.net (s002) Date: Mon Jul 26 18:34:29 2004 Subject: [Seaside] Add button not showing it's page Message-ID: <20040726163417.32099.qmail@mail.taricco.net> 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.] From avi at beta4.com Mon Jul 26 22:08:07 2004 From: avi at beta4.com (Avi Bryant) Date: Mon Jul 26 22:08:16 2004 Subject: [Seaside] 2.5b2 Message-ID: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> 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 From avi at beta4.com Mon Jul 26 22:15:05 2004 From: avi at beta4.com (Avi Bryant) Date: Mon Jul 26 22:15:15 2004 Subject: [Seaside] request termination Message-ID: <7BE57416-DF40-11D8-96A0-000A95DB7844@beta4.com> 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 From avi at beta4.com Mon Jul 26 22:17:17 2004 From: avi at beta4.com (Avi Bryant) Date: Mon Jul 26 22:17:24 2004 Subject: [Seaside] Add button not showing it's page In-Reply-To: <20040726163417.32099.qmail@mail.taricco.net> References: <20040726163417.32099.qmail@mail.taricco.net> Message-ID: On Jul 26, 2004, at 9:34 AM, s002 wrote: > 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: [] > ] You don't want two methods on the same class here, you want two different classes. So your #renderAddOn: method should be the #renderContentOn: of a PMLogsAddItem component. And then your 'Add' link should be this: html anchorWithAction: [self call: PMLogsAddItem new] text: 'Add'. Does that make sense? > 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.] > > _______________________________________________ > Seaside mailing list > Seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside From julian at beta4.com Mon Jul 26 22:42:40 2004 From: julian at beta4.com (Julian Fitzell) Date: Mon Jul 26 22:44:10 2004 Subject: [Seaside] Add button not showing it's page In-Reply-To: <20040726163417.32099.qmail@mail.taricco.net> References: <20040726163417.32099.qmail@mail.taricco.net> Message-ID: <41056CC0.1050007@beta4.com> Hi s002, Say, do you have a name? :) So the problem below is that you are using a render method as your callback, which is not at all what you want to do. Every time a request comes in, the callbacks are executed and then the root component is obtained and asked to render itself to be displayed to the user. Your callback needs to perform some action to cause the display state to change before the next render pass is executed. When you call #renderAddOn: in your callback, nothing changes that would cause PMLogsView to render itself any differently than the last time, which is why you see the same page drawn again. What you probably want to do here is have another component, say PMLogItemEditor, which you pass a new instance of PMLogItem into. For example you could write an action method like: addNewItem |item| item := PMLogItem new. "store the item however you do that" self call: (self editorComponentFor: item) And then in your render method use: html anchorWithAction: [self addNewItem] text: 'Add' Obviously you'd have to implement a #children method as well as #editorComponentFor: to keep track of the editor component... Julian s002 wrote: > 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.] > > _______________________________________________ > Seaside mailing list > Seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside From chris.double at double.co.nz Tue Jul 27 01:43:03 2004 From: chris.double at double.co.nz (Chris Double) Date: Tue Jul 27 01:43:15 2004 Subject: [Seaside] 2.5b2 In-Reply-To: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> References: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> Message-ID: <1090885383.30502.201124331@webmail.messagingengine.com> On Mon, 26 Jul 2004 13:08:07 -0700, "Avi Bryant" said: > 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: That is very cool. The WALiveRequestTest is nifty. Is it making a server request in the background when entering text in the input boxes and clicking the time button? It's fast! At first I thought it was javascript just changing the time locally but it's actually done by the server and the javascript is replacing the result from the server inline on the page right? Chris. -- Chris Double chris.double@double.co.nz From avi at beta4.com Tue Jul 27 04:52:54 2004 From: avi at beta4.com (Avi Bryant) Date: Tue Jul 27 04:53:06 2004 Subject: [Seaside] 2.5b2 In-Reply-To: <1090885383.30502.201124331@webmail.messagingengine.com> References: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> <1090885383.30502.201124331@webmail.messagingengine.com> Message-ID: <0EFBF565-DF78-11D8-96A0-000A95DB7844@beta4.com> On Jul 26, 2004, at 4:43 PM, Chris Double wrote: > On Mon, 26 Jul 2004 13:08:07 -0700, "Avi Bryant" said: >> 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: > > That is very cool. The WALiveRequestTest is nifty. Is it making a > server > request in the background when entering text in the input boxes and > clicking the time button? It's fast! At first I thought it was > javascript just changing the time locally but it's actually done by the > server and the javascript is replacing the result from the server > inline > on the page right? > Right. From rbb at techgame.net Tue Jul 27 17:22:56 2004 From: rbb at techgame.net (Brian Brown) Date: Tue Jul 27 17:24:19 2004 Subject: [Seaside] request termination In-Reply-To: <7BE57416-DF40-11D8-96A0-000A95DB7844@beta4.com> References: <7BE57416-DF40-11D8-96A0-000A95DB7844@beta4.com> Message-ID: On Jul 26, 2004, at 2:15 PM, Avi Bryant wrote: > 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? > This would be phenomenal! That is another issue I've had problems with in the past in OWF (Other Web Frameworks) The stop button doesn't mean a whole lot to them if you stop a big request in the middle. > 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. > And we care about other dialects why? (Just kidding!) > A > > _______________________________________________ > Seaside mailing list > Seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside From rbb at techgame.net Tue Jul 27 22:21:58 2004 From: rbb at techgame.net (Brian Brown) Date: Tue Jul 27 22:23:24 2004 Subject: [Seaside] 2.5b2 In-Reply-To: <0EFBF565-DF78-11D8-96A0-000A95DB7844@beta4.com> References: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> <1090885383.30502.201124331@webmail.messagingengine.com> <0EFBF565-DF78-11D8-96A0-000A95DB7844@beta4.com> Message-ID: <9C7E0EE8-E00A-11D8-9F69-003065F89450@techgame.net> On Jul 26, 2004, at 8:52 PM, Avi Bryant wrote: >> That is very cool. The WALiveRequestTest is nifty. Is it making a >> server >> request in the background when entering text in the input boxes and >> clicking the time button? It's fast! At first I thought it was >> javascript just changing the time locally but it's actually done by >> the >> server and the javascript is replacing the result from the server >> inline >> on the page right? >> > > Right. > This is seriously cool stuff. I'll definitely be using this. thanks Avi! From s002 at landr.net Wed Jul 28 05:58:37 2004 From: s002 at landr.net (LK) Date: Wed Jul 28 05:59:07 2004 Subject: [Seaside] Deleting from GOODS. In-Reply-To: <283AB590-DDB9-11D8-B33C-000A95DB7844@beta4.com> References: <4101C7DA.1070303@landr.net> <855F5A27-DD57-11D8-A70F-000A95E07986@netstyle.ch> <410273C4.1000505@landr.net> <283AB590-DDB9-11D8-B33C-000A95DB7844@beta4.com> Message-ID: <4107246D.5020509@landr.net> Avi Bryant wrote: > > On Jul 24, 2004, at 7:35 AM, LK wrote: > >> Adrian Lienhard wrote: >> >>> Hi Larry >>> >>> It should say "allRecords remove: aRecord" and not #removeAt: >>> (latter takes an integer to remove an item from the ordered >>> collection at a specific index). >>> >>> Adrian >> >> >> Thanks, That executed w/o error, but. nothing was removed from GOODS. >> I added this method: >> delete: aRecord from: aDatabase >> (self confirm: 'Are you sure you want to delete: ', (aRecord >> entryText) printString, '?') >> ifTrue: [allRecords remove: aRecord. >> aDatabase commit.]. >> >> It says that it cannot understand #commit. In workspace, db commit >> executes properly. What am I missing here????? > > > Well, you must somehow have the wrong object passed in as aDatabase. > When the MNU #commit error comes up, what class does it say aDatabase > is? That might give you a clue as to what's going wrong. > > Avi > It says aDatabase is nil. So, it's not getting passed to the PMLogsView method properly. Moving the db connect method to the PMLogsView class solves the problem. But, it would be nice if the database connection was opened in the object that calls PMLogsView, and passed to the subcomponents. PMLogsTask>>RenderLoop db := dbConnection new.. PMLogsView ( which would include calls to PMLogsAddItem, PMLogsModifyItem, PMLogsDeleteITem, etc which would need access to the db connection in order to do #commit and #refresh) . . . db logout. ----------------- How would I make the db object available to nested subcomponents? -Larry From s002 at landr.net Wed Jul 28 06:42:53 2004 From: s002 at landr.net (LK) Date: Wed Jul 28 06:43:16 2004 Subject: [Seaside] Add button not showing it's page In-Reply-To: <41056CC0.1050007@beta4.com> References: <20040726163417.32099.qmail@mail.taricco.net> <41056CC0.1050007@beta4.com> Message-ID: <41072ECD.3080807@landr.net> Sorry, I'm Larry Kelly. the addNewItem needs a #children method? What would go in it? I'm unclear what the #children method is for? Sorry to be so dense.:) -Larry Julian Fitzell wrote: > Hi s002, > > Say, do you have a name? :) > > So the problem below is that you are using a render method as your > callback, which is not at all what you want to do. > > Every time a request comes in, the callbacks are executed and then the > root component is obtained and asked to render itself to be displayed > to the user. Your callback needs to perform some action to cause the > display state to change before the next render pass is executed. > > When you call #renderAddOn: in your callback, nothing changes that > would cause PMLogsView to render itself any differently than the last > time, which is why you see the same page drawn again. > > What you probably want to do here is have another component, say > PMLogItemEditor, which you pass a new instance of PMLogItem into. For > example you could write an action method like: > > addNewItem > |item| > item := PMLogItem new. > "store the item however you do that" > self call: (self editorComponentFor: item) > > And then in your render method use: > > html anchorWithAction: [self addNewItem] text: 'Add' > > Obviously you'd have to implement a #children method as well as > #editorComponentFor: to keep track of the editor component... > > Julian > > s002 wrote: > >> 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.] >> _______________________________________________ >> Seaside mailing list >> Seaside@lists.squeakfoundation.org >> http://lists.squeakfoundation.org/listinfo/seaside > > _______________________________________________ > Seaside mailing list > Seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside > > From avi at beta4.com Wed Jul 28 06:44:33 2004 From: avi at beta4.com (Avi Bryant) Date: Wed Jul 28 06:44:39 2004 Subject: [Seaside] Deleting from GOODS. In-Reply-To: <4107246D.5020509@landr.net> References: <4101C7DA.1070303@landr.net> <855F5A27-DD57-11D8-A70F-000A95E07986@netstyle.ch> <410273C4.1000505@landr.net> <283AB590-DDB9-11D8-B33C-000A95DB7844@beta4.com> <4107246D.5020509@landr.net> Message-ID: On Jul 27, 2004, at 8:58 PM, LK wrote: > It says aDatabase is nil. So, it's not getting passed to the > PMLogsView method properly. Moving the db connect method to the > PMLogsView class solves the problem. But, it would be nice if the > database connection was opened in the object that calls PMLogsView, > and passed to the subcomponents. > > PMLogsTask>>RenderLoop > db := dbConnection new.. > PMLogsView ( which would include calls to PMLogsAddItem, > PMLogsModifyItem, PMLogsDeleteITem, etc which would need access to the > db connection in order to do #commit and #refresh) > . . . > db logout. > ----------------- > How would I make the db object available to nested subcomponents? The usual way is to access it through the session, which is available to any component through #session, or anything else through "WACurrentSession value". Just subclass WASession to include a db instance variable, and configure your app to use that session class. Brian Brown has some documentation of this pattern here: http://www.techgame.net/projects/Seaside/wiki/SetupSessionForGOODS Avi From rbb at techgame.net Wed Jul 28 07:30:37 2004 From: rbb at techgame.net (Brian Brown) Date: Wed Jul 28 07:31:26 2004 Subject: [Seaside] Add button not showing it's page In-Reply-To: <41072ECD.3080807@landr.net> References: <20040726163417.32099.qmail@mail.taricco.net> <41056CC0.1050007@beta4.com> <41072ECD.3080807@landr.net> Message-ID: <1090992636.31386.8.camel@siniwali.ablelinktech.com> On Tue, 2004-07-27 at 22:42, LK wrote: > Sorry, I'm Larry Kelly. > > the addNewItem needs a #children method? What would go in it? I'm > unclear what the #children method is for? Sorry to be so dense.:) > -Larry > The #children method is a recent addition to Seaside; the renderer uses it to determine what should be rendered. What goes in it are all the components of a component (or subcomponents if you will). For example, if you have a component ParentComponent that has two instance variables; child1 and child2. For to make this really easy to try, put an initialize method on ParentComponent: initialize child1 := WACounter new. child2 := WACounter new. Then in ParentComponent>>renderContentOn: renderContentOn: html html heading: 'Check out my children!' level: 3. html render: child1; br; render child2. In order for callbacks to work properly, in this case you would have a #children like this: children ^ Array with: child1 with: child2 Please note that if you put sub components that have forms rendered from the renderContent on of a component, they will show up fine even if not being returned from #children. You just won't be able to actually submit the forms without a traceback. :) HTH, Brian > Julian Fitzell wrote: > > > Hi s002, > > > > Say, do you have a name? :) > > > > So the problem below is that you are using a render method as your > > callback, which is not at all what you want to do. > > > > Every time a request comes in, the callbacks are executed and then the > > root component is obtained and asked to render itself to be displayed > > to the user. Your callback needs to perform some action to cause the > > display state to change before the next render pass is executed. > > > > When you call #renderAddOn: in your callback, nothing changes that > > would cause PMLogsView to render itself any differently than the last > > time, which is why you see the same page drawn again. > > > > What you probably want to do here is have another component, say > > PMLogItemEditor, which you pass a new instance of PMLogItem into. For > > example you could write an action method like: > > > > addNewItem > > |item| > > item := PMLogItem new. > > "store the item however you do that" > > self call: (self editorComponentFor: item) > > > > And then in your render method use: > > > > html anchorWithAction: [self addNewItem] text: 'Add' > > > > Obviously you'd have to implement a #children method as well as > > #editorComponentFor: to keep track of the editor component... > > > > Julian > > > > s002 wrote: > > > >> 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.] > >> _______________________________________________ > >> Seaside mailing list > >> Seaside@lists.squeakfoundation.org > >> http://lists.squeakfoundation.org/listinfo/seaside > > > > _______________________________________________ > > Seaside mailing list > > Seaside@lists.squeakfoundation.org > > http://lists.squeakfoundation.org/listinfo/seaside > > > > > > _______________________________________________ > Seaside mailing list > Seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside From julian at beta4.com Wed Jul 28 07:32:31 2004 From: julian at beta4.com (Julian Fitzell) Date: Wed Jul 28 07:32:39 2004 Subject: [Seaside] Add button not showing it's page In-Reply-To: <41072ECD.3080807@landr.net> References: <20040726163417.32099.qmail@mail.taricco.net> <41056CC0.1050007@beta4.com> <41072ECD.3080807@landr.net> Message-ID: <41073A6F.1090201@beta4.com> LK wrote: > Sorry, I'm Larry Kelly. > the addNewItem needs a #children method? What would go in it? I'm > unclear what the #children method is for? Sorry to be so dense.:) > -Larry Hi Larry, not a problem. So a component's #children method is supposed to return an array of all the subcomponents it is currently displaying within itself. Unfortunately it was me who was being dense for even mentioning it in this context: you don't need to implement a #children method when you call another component. I think I must have confused myself between what you had been trying to do and the solution I was suggesting for you. You could probably ignore all the #editorComponentFor: stuff I was talking about as well as #children for now and just implement addItem more like: addItem self call: (PMLogItemEditor new item: PMLogItem new) (noting again that you need to do something with the new item to store it somewhere presumably). To explain #children a little more, since I brought it up, let's look at WAMultiCounter as an example that needs to implement #children. It's render method looks like: renderContentOn: html counters do: [:ea | html render: ea] separatedBy: [html horizontalRule] and it implements #children as follows: children ^ counters Seaside uses #children when handling callbacks, decorations, etc. to make sure each of the embedded components has its chance to do processing. You can see some weird behaviour if you don't have #children properly defined in those cases. Cheers, Julian -- Julian Fitzell -- Beta4 Productions julian@beta4.com -- http://www.beta4.com Seaside: http://www.beta4.com/seaside2 From kamk at volny.cz Wed Jul 28 11:03:47 2004 From: kamk at volny.cz (Kamil Kukura) Date: Wed Jul 28 11:07:50 2004 Subject: [Seaside] Re: 2.5b2 In-Reply-To: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> References: <82B76E3D-DF3F-11D8-96A0-000A95DB7844@beta4.com> Message-ID: <41076BF3.70703@volny.cz> Avi Bryant wrote: > Hi folks, > > Just released Seaside 2.5b2. The changes from b1, mostly thanks to > Adrian Lienhard and Michel Bany, are: I just upgraded to this version and here are some remarks: - still don't have asMutator used in WAHtmlRenderer)>>radioButtonInGroup:withValue:on:of: so I needed to backfix this. - using scripts and styles in external files I had to put everything regarding ... content into #updateRoot: while holding on its super's counterpart. I use #addHeadElement: so now I'm not sure if it will survive next versions. More on that below. - now updating document's title from #updateRoot: in the root component. Perhaps there could be better way for a component to alternate document's title. Now back to your announcement. > 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 Urgh, what that space after question mark... Anyway, it's cool to see support for client-side scripting. Btw, I call these "continuation" web applications as "web-terminal applications" and scripting turns web browser to great terminal front-end. To me it's like next evolution of IBM's 3270 batch terminal :) > 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. Well, but I see all of WAStandardScripts and WAStandardStyles in every application configured. First I was shocked why simple counter has so many stylesheets attached to it. I must admit I don't understand library browser much. I think WARenderedHtmlRoot>>write[Script|Style]:on: is quite rough. I see there idea of "EITI - Everything In The Image" but I guess there could be finer control for styles/scripts inclusion. How do you like the idea of having classes such as WAScriptContent having #scriptType and #isDeferred that would correspond to