4:32 a.m.
I have this recurring pattern that pier doesnt appear to handle at all
well, so would be grateful for ideas.
I want to embed a component that "does stuff" then when it is finished
goes back to, whence it came.
Better still I would like to be able to go to a page, with an embedded
component, and when finished return to the place of origin. This would
allow the component to be decorated with other things on that page,
rather than just being a dry form like Commands are. (although
Pier-Annotations can spice them up a bit)
For example, I have a "New User Registration" component written for
seaside. It would normally be invoked via a "call", and would return
something or nil if the user cancelled. I am not so interested in the
return value.
So if I pop this component in to pier, I can get to it via a link, and
when I have finished "doing stuff", or if I click "cancel", then it
does... nothing. Ideally I want it to go back to the source of the link,
from whence I came.
I have never found a non-hacky way of doing this. The only clean way of
doing such things appears to be to wrap your component into a command.
I was kind of hoping that LightBox links could be persuaded to close if
the component drawn answers nil.
Solution's I have contemplated...
1) Have contexts keep a history so at least you can find out where to
return to.
Have pier handle all seaside components not just root components, any
answers that are received from a component, are put into
PRContext-properties in case anyone cares, and embedded components may
propagate their answers out to the PRContentsWidget which then uses the
History in the PRContext to go back to whence you came.
2) Some special form of link, which stores the current structure
somewhere, before going to the next destination.
any ideas?
Keith
10:29 p.m.
New subject: [Ann] ??????
The framework I used before Seaside, a long long time ago, was Zope.
Zope suffered from being python and from horrible code and many other
things, but it was quite functional.
Seaside on the other hand has good clean code, and can do very little
out of the box.
I want to see a one-click image, that has pier for organising content,
and style of my site, seaside, testing tools, logging framework,
everything ready to go. I want to be able to chose the backend
component (say Magma or MySql, TT), click a button, it creates,
initializes the databases and starts serving!
I have been trying to use seaside and pier together for a long time, and
it has always been difficult to develop with traditional seaside
components within pier as a framework.
Finally, at last Pier can be used as a framework for structuring,
presenting and developing Seaside applications.
The enhancement required goes as follows.
When there is a change in pier context, the frame component is told and
remembers the previous context. This is handy because in my set up
everything is configured by the frame component, including choice of
PRViewRenderer.
In my view renderer class, I implement visitComponent: so that it
renders the component together with an answerHandler which handles the
answer by returning to the previous context (as saved above).
So now I can present a link "Forgot Password", which goes to a nice
'pier' page with content around a seaside component
WAForgotPasswordComponent. The user enters their details, clicks on a
link in an emails, edits their password, saves their password and pier
RETURNs them to whatever they were looking at before.
Together with the client framework, for organising front-end and
backend-components we finally have a solution for developing web
applications as you would in, say Zope.
The question now is what to call it... My previous big project for the
telecoms industry was called TelTalk....
How about "Webtalk" ?
Keith
p.s. I also thought about "Tourist" - taking in the seaside and the pier.
10:45 p.m.
New subject: [Seaside] [Ann] ??????
>>>> "Keith" == Keith Hodges
<keith_hodges(a)yahoo.co.uk> writes:
Keith> p.s. I also thought about "Tourist" - taking in the seaside and the
pier.
Dock, because it's how you get back, and tightly connecter to pier.?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
11:03 p.m.
New subject: [Ann] ??????
Beach :)
Atol
Laguna
make us dream
How about "Webtalk" ?
Webtalk looks heavily and not fun.
Keith
p.s. I also thought about "Tourist" - taking in the seaside and the
pier.
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
8:52 p.m.
New subject: [Ann] ??????
On Mar 29, 2009, at 5:20 PM, Keith Hodges wrote:
stéphane ducasse wrote:
> Beach :)
Bagsee "Beach" then!
It had to happen sooner or later. Someone had to come up with a
seaside
product call Beach.
Keith
---
"When you go to the seaside, the beach is really what you want to
see".
"It's hard to enjoy the Seaside without standing on the Beach"
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
12:26 p.m.
New subject: [Ann] ??????
brian wrote:
On Mar 29, 2009, at 5:20 PM, Keith Hodges wrote:
> stéphane ducasse wrote:
>> Beach :)
> Bagsee "Beach" then!
>
> It had to happen sooner or later. Someone had to come up with a seaside
> product call Beach.
>
> Keith
>
> ---
> "When you go to the seaside, the beach is really what you want to see".
"It's hard to enjoy the Seaside without standing on the Beach"
I like
it.... and more like it
To enjoy the Seaside, hit the Beach.
Keith
5100
days inactive
5113
days old
6 comments
4 participants
participants (4)
-
brian -
Keith Hodges -
merlyn＠stonehenge.com -
stéphane ducasse