• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: State machines in WO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State machines in WO


  • Subject: Re: State machines in WO
  • From: email@hidden
  • Date: Thu, 18 Mar 2004 09:13:39 +0000

Hello Alex

On 18 Mar 2004, at 01:14, Alex Boster wrote:

Newbie here gone through the Apple Web Apps tutorial and most of Ravi
Mendess book. Im try to design a task/defect tracking system and need
some insight in what would be the WebObjects Way to do some things.

Note that I have very less experience in developing WebObjects applications. I will still try to offer some answer.



In particular, the thing is basically a large state machine. Depending on
the current state, the user will have access to a different set of the tasks
attributes. Links or buttons will be displayed for the valid state
transitions.

Interesting application.


So does anyone have a recommendation for a strategy here, in keeping with
the zen of WO? (Or a recommendation on how NOT to proceed.)


A naive idea would simply have one page per state.  An incremental
improvement on that would be to factor out common features into custom
components.

Sounds good.

 Another naive idea would be to have one page with a lot of
logic.

I wouldn't go for that. Though you may have to create a page with lots of logic at some point, you should think hard on how to break it in smaller pieces that are more manageable and better organised.


Use Groups in Xcode and partial documents with API in WebObjects Builder. Separate business logic and display logic.

 Neither idea seems ideal

A much more ambitious approach would be to keep the state diagram, task
attributes, and such as metadata and build things dynamically. But I don't
anticipate that the payoff in this case would be worth the effort.

Why not? But it seems to me this approach would be better implemented as a Web Service. You would have to develop a desktop application to access said web service. It would correspond essentially to the presentation layer.


My 2c.
Cheers,
-- Denis.


Alex
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >State machines in WO (From: "Alex Boster" <email@hidden>)

  • Prev by Date: [OT] Update Pulled?
  • Next by Date: Re: NULL matching my displaygroup...
  • Previous by thread: State machines in WO
  • Next by thread: Losing my mind
  • Index(es):
    • Date
    • Thread