• 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: extended bindings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: extended bindings


  • Subject: Re: extended bindings
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 3 Nov 2006 12:02:16 -0800

One word.  Wonder.

See the WOOGNL framework, for what it can do see http://www.ognl.org/

I am pretty sure that I have written some things like your XYConditional. I just can't recall where they are now...

Chuck


On Nov 3, 2006, at 11:47 AM, YL wrote:

I can see two reasons to extend binding conventions. Once we can do such, WO can really beat other web solutions. Because WO is almost there and others are not. The whole motivation is to make web application evolvable at runtime so that people can use the app doing business without too many upgrading requests for developers, and also make the app more managable by business people.

(1)reduce coding efforts.
     In wod file, instead of saying

UseBatching: WOConditional { condition = useBatching; } // and implement method "useBatching"

     We can do (more handy binding sugestions are welcome)

UseBatching: XYConditional {
testingValueOne = searchingResults.count;
testingValueTwo = session.sessionUser.userPreferences.batchSize;
operator = ">";
}


// So that we don't need to write method "useBatching", which is an ugly method anyway

     Instead of doing
     MyImage:   WOImage { src = myImageSource; ...}
.....

We can do
MyImage XYImage { src = contentEO.@imageUrlWithImageName?ofType? _apple|jpg; }


expect url from method call
[contentEO imageUrlWithImageName:@"apple" ofType: @"jpg"]
or  contentEO.imageUrlWithImageName("apple","jpg")

will be assigned to src

(2)support runtime manageable contents and more.

MayImage:  XYField { dataDict = aDataDict; }

// Where XYField is a WOSwitchComponent, the component name is specified in aDataDict:
{
WOComponentName = XYImage;
sourceObjectKeyPath = contentEO;
fieldKey = src;
valueKeyPath = "@imageUrlWithImageName?ofType?_apple|jpg:";
border = 0;
width = 135;
...
}
And aDataDict can be from database, etc. that way one can have a meta page (WOComponent) to handle various contentEOs and those EOs are editable at runtime.


I hope to be able to make some changes at WOAssociation level to solve most of the issues towards the featues I like. Any advises are greatly appreciated.





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


This email sent to email@hidden


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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: extended bindings
      • From: Mike Schrag <email@hidden>
References: 
 >extended bindings (From: "YL" <email@hidden>)

  • Prev by Date: extended bindings
  • Next by Date: Re: extended bindings
  • Previous by thread: extended bindings
  • Next by thread: Re: extended bindings
  • Index(es):
    • Date
    • Thread