• 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: Default D2W Rules for Components
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Default D2W Rules for Components


  • Subject: Re: Default D2W Rules for Components
  • From: Anjo Krank <email@hidden>
  • Date: Thu, 03 May 2012 19:47:00 +0200

Been using this for years, eg:

> 35 : ((entity.userInfo.isLarge != 'YES' and not (entity.name like '*Statistic')) => showResultsImmediately = true [BooleanAssignment]

Cheers, Anjo



Am 03.05.2012 um 19:33 schrieb David Holt:

> Hi all,
>
> A few of us have been discussing creating an additional default rule set for Modern D2W applications based on a new optional key in the user info dictionary and the existing prototypeName for an attribute.
>
> We were thinking of using a new key such as d2wComponentType = mailto as a new key that sets the default component to be used for an attribute. We were thinking that if there was no key the fallback could be to using the prototypeName from entity modeler, and if neither of those is available to go with the current rules.
>
> Given that there are now so many little specialized components available in Wonder for all sorts of different things, we are hoping to avoid continuing to have to create a bunch of rules such as:
>
> 50 : propertyKey like '*Post' => componentName = "ERD2WEditLargeString" [com.webobjects.directtoweb.Assignment] because the current rules are not very specific (the default would just be EditString).
>
> Replacing them with more generic rules such as:
>
> 35 : (smartAttribute.userInfo.d2wComponentType = displaySmallIntNumber => componentName = "ERD2WDisplaySmallInteger" [com.webobjects.directtoweb.Assignment]
> 35 : (smartAttribute.userInfo.d2wComponentType = editSmallIntNumber => componentName = "ERMD2WEXTEditSmallInteger" [com.webobjects.directtoweb.Assignment]
>
> 25 : (smartTaskDisplay = 1 and smartAttribute.prototypeName = 'intNumber') => componentName = "ERMD2WEXTDisplay_intNumber" [com.webobjects.directtoweb.Assignment]
> 25 : (smartTaskEdit = 1 and smartAttribute.prototypeName = 'intNumber') => componentName = "ERMD2WEXTEdit_intNumber" [com.webobjects.directtoweb.Assignment]
>
> Given that Wonder was created by geniuses I can't imagine that this idea has been overlooked. What are the drawbacks to the approach that are we missing?? Or do you think it's a good idea?
>
> Thanks,
> David
> _______________________________________________
> 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


 _______________________________________________
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: 
 >Default D2W Rules for Components (From: David Holt <email@hidden>)

  • Prev by Date: Re: Default D2W Rules for Components
  • Next by Date: WOWODC lodging and other news
  • Previous by thread: Re: Default D2W Rules for Components
  • Next by thread: Re: [Wonder-disc] Default D2W Rules for Components
  • Index(es):
    • Date
    • Thread