Hi ! Did I understand it right:
You've got objects with diffent states and want to have lists of objects with same states ? Isn't that comparable wit PITS ? you have many objects (=Problems) with diffenert states (e.g. reported, in work, solved, tested etc) an different views (implemented via pagelist-markup) If yes: - take a page per object in an own group - use pagetextvariables to set up the states (e.g.: State: this or that) - use pagelist-pages for each possible state (stateselection done by $:state=this as a pagelist-parameter) To change a state from within the pagelist-list we're using a macro implementing a kind of "autoedit": an icon in the pagelist-entry can be clicked and this will call the corresponding page with action=autoedit,autoeditmacro=this which calls a php-script called "this.php". This will do some page-editing (e.g.: change a state) and showing the resulting page. the pagelist mus be updated manually. But this is a lot easier than calling the page from the pagelist in edit-mode, edit the state manually and saving the page again. But to be honest: that sounds to be to simple, there must be more, right ? Cheers Knut Jean DEMARTINI schrieb: > I have to design a rather complex online PMS. PmWiki can help to solve > many problems but I am stuck on a nasty little problem : > > A PMS is typically a set of objects which have to traverse a Finite > State Machine (FSM). All the objects are not in the same state. > Permanently new objects enter the PMS and produced objects quit the PMS. > > My problem is : how to implement a FSM to manage changing lists of > objects in the spirit of PmWiki. > > To implement an event is easy : a form with its submit button can easily > do that. > > The problem is : how to implement a State and its associated list of > objects. > > The easy way could be : a state is denoted by a page and the events to > change of state is a set of forms whose submit buttons are the > event-triggers. That's cool. > > Managing a list of all the object in this given state is not so simple. > > I can use Fox form to add, remotely, content in any page I want, that's > fine. > > But how to remove(change), remotely, content from(in) a page to model an > object leaving a state and entering another one? A mean to mimic the > delete button of foxdelrange from another page could be great. > > Thanks for any kind of help. > > > > > > > _______________________________________________ > pmwiki-users mailing list > [email protected] > http://www.pmichaud.com/mailman/listinfo/pmwiki-users > > _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
