From: John G. <jgo...@mk...> - 2005-03-28 14:32:44
|
Ian Bicking wrote: > Component 0.1 is the first (well overdue) release of a component > system for Webware servlets. > > This release does not update the code in any way -- the code has > remained stable in the repository for some time now -- but adds some > documentation and a version number. > > You can read about Component at: > http://wiki.webwareforpython.org/component.html > Download it at: > http://webwareforpython.org/downloads/Component-0.1.tar.gz > See the repository at: > http://svn.webwareforpython.org/Component/trunk > > Alone it doesn't do anything, but LoginKit is useful and uses it: > http://svn.w4py.org/LoginKit > > This release is actually spurred by a package I'll be releasing that > depends on Component, and I feel silly giving that package a release > and version number when it depends on something without a release or > version. > I have a question about the Component model (I think) I want to create a system that binds multiple pages together something similar to a wizard. The situation is as follows. We would like to implement Webware pages that work on there own and do some given task however it is desirable to link multiple pages together to form a workflow. Ideally each page would not need to know about the others in the flow of the wizard. So when Page1 completes flow would move onwards to Page2. I guess the design would follow that of a PropertySheet which contains one or more PropertyPages. The Container sheet would contain any logic needed to tie the Pages together. So my question; is Component the right way to do this? if so could someone give me a very high level run down of how this would work as the examples I can find don't seem to make it clear as to how I would do this. Regards John Goodyear |