• 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: ERXPatcher and component templates
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERXPatcher and component templates


  • Subject: Re: ERXPatcher and component templates
  • From: David Aspinall <email@hidden>
  • Date: Mon, 12 Feb 2007 11:55:52 -0500

Naturally, and we do this all over the place, however this is not a simple linear problem. Its not as if client A gets a traditional left nav, plus a custom search field div over the header image, plus wants a Calendar on the right column and wants Account list table with a column for last contact date instead of last updated date. Oh, and client B wants the same but with an EGO image on the right and a task list and not the custom search box, and client c wants a JavaScript drop down menu, no left nav, so the center content can increase 20% and we need 3 additional columns on the Account list ....

What I am thinking is we do one 'default' layout with standard design, but optionally we could dynamically replace key components without the ever growing Switch/Case, if condition ... logic.

We already define the menu in an XML document that the app reads at runtime. So we can place different component items in for pages and tab's within pages. But where one component is heavily customized, this 'might' be a better way. My task to to investigate and compare to the more traditional switch/case/ifconditions. I think this 'could' be a useful concept (like 'patching') and may be a valuable addition to the options available for controlling customization.

David



On 12-Feb-07, at 11:28 AM, Guido Neitzer wrote:

On 12.02.2007, at 08:45, David Aspinall wrote:

I am investigating use of a feature like ERXPatcher to switch two components at runtime in a simple way. For example if component looks like:

Hmmm. For my point of view: the easiest way might be a WOSwitchComponent and a way of defining which component is used for which client.


I do this a lot with a CMS system I'm currently building.

cug

_______________________________________________ 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
References: 
 >ERXPatcher and component templates (From: David Aspinall <email@hidden>)

  • Prev by Date: ERXPatcher and component templates
  • Next by Date: Re: WebObjects Position at Penn State
  • Previous by thread: ERXPatcher and component templates
  • Next by thread: Re: ERXPatcher and component templates
  • Index(es):
    • Date
    • Thread