• 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: D2W and Direct Actions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: D2W and Direct Actions


  • Subject: Re: D2W and Direct Actions
  • From: Denis Frolov <email@hidden>
  • Date: Fri, 1 Jun 2007 11:02:58 +0400


On May 31, 2007, at 8:48 PM, Guido Neitzer wrote:

On 31.05.2007, at 00:23, Denis Frolov wrote:

You actually don't have to change layout of framework's D2W pages. I usually start a project by subclassing all the D2W-pages (InpsectPage extends ERD2WInspectPage, ListPage extends ERD2WListPage, MessagePage extends ERD2WMessagePage, etc) and use project-specific html markup. Java files for these pages most often have no logic at all.

There is a script for creating a "look framework" which basically does what you're saying. I have a project independent look framework which subclasses a lot of the ERD* classes and only implements its own HTML.

I have one too and use it for Admin apps.

So, all our projects have both admin and front-end driven by D2W. I also agree with Anjo saying that having session is not a problem since it's just memory and thinking about saving memory on the early stages of project sounds like a premature optimization to me. You normally get much more in return.

That doesn't work for me, as I need URLs that can be bookmarked, crawled by search engines, send via E-Mail and so on. So basically all my Admin apps are DirectToWeb to a certain degree and nearly all my "frontend" applications are DirectAction based.

All our "frontend" apps are bookmarkable. There is no reason you cannot use direct actions with D2W. You can either use ERD2WDirectAction to create pages by their pageConfigurations or you can write your own direct actions. D2W combined with direct actions can be effectively used to create list, inspect, edit, etc pages. Calling submitAction on edit page is normally component action - but you don't need this one to be bookmarkable. We also use component actions for sorting and batching since we don't need these to be bookmarked either but you can easily add support for direct action sorting and batching if you need it.


Consider an example (we don't own the project, so I hope you won't consider this an advertisement): http://www.legalsounds.com/ InspectArtist?__key=3339

This one is D2W inspect page (InpsectArtist) with an embedded pick list page (PickListAlbum). Sorting and submit (buy) are served by component actions. Sorting keys are defined in rules and ERCoreUserPreferences is used to save user's choice in db. All other pages have similar concept - they are normally one of: inspect, edit or list D2W pages.

--
Denis Frolov
Design Maximum MA

Tel: +7 863 2648211
Fax: +7 863 2645229
Web: http://www.designmaximum.com



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: D2W and Direct Actions
      • From: Guido Neitzer <email@hidden>
  • Next by Date: Re: [HOWTO] Profiling WO apps with Netbeans
  • Next by thread: Re: D2W and Direct Actions
  • Index(es):
    • Date
    • Thread