I think it amounts to the same thing. From ERDirectToWeb rules: 55 : ((subTask = 'tab') and ((task = 'edit') or (task = 'inspect'))) => pageName = templateNameForTabInspectPage [er.directtoweb.ERDKeyValueAssignment]
On 2013-01-27, at 1:30 PM, ISHIMOTO Ken <[email protected]> wrote: > The componentName for Editing has to be 'ERMODTabInspectPage' > > There are 2 different InspectPage in Modern, i really don't know why, but 1 > is supporting this Tags, > and one not. > > take a look and changes the rule i do. > > 20 : look = 'ERModernLook' => templateNameForInspectPage = > "ERMODTabInspectPage" [com.webobjects.directtoweb.Assignment] > 20 : look = 'ERModernLook' => templateNameForTabInspectPage = > "ERMODTabInspectPage" [com.webobjects.directtoweb.Assignment] > > Greetings > > Ken > > > > On 2013/01/27, at 22:24, [email protected] wrote: > >> He's just talking about a page to create the EO, not initializing the EO. >> >> David >> >> >> On 2013-01-27, at 1:19 PM, Jesse Tayler <[email protected]> wrote: >> >>> >>> I don't use rules but rather, I use code for that sort of thing. >>> >>> There are handy methods on your EOs for handling init, willUpdate, >>> didInsert and others you'd want, so I seem to use those without troubles. >>> >>> here's an example of initializing an active flag, and some dates from the >>> Wonder/EO's standard init method. >>> >>> maybe that helps. >>> >>> >>> public void init(EOEditingContext ec) { >>> super.init(ec); >>> NSTimestamp now = new NSTimestamp(); >>> setActive(true); >>> setCreated(now); >>> setAdjusted(now); >>> >>> … >>> >>> >>> >>> >>> >>> On Jan 27, 2013, at 1:14 PM, Kevin Hinkson <[email protected]> wrote: >>> >>>> I have a rule which works well when creating an EO and it's relationships >>>> for the first time. >>>> >>>> 100 : (task = 'edit' and entity.name = 'Periodic') => displayPropertyKeys >>>> = ("[Page 1]", "(Periodic Details)", "title", "details", "[Page 2]", >>>> "(Publish Details)", "published", "visible", "hyperlinkReferences") >>>> [com.webobjects.directtoweb.Assignment], >>>> >>>> >>>> However, when editing an existing EO I encounter an exception due to the >>>> wizard keys being interpreted as EO properties. >>>> >>>> <com.webobjects.foundation.NSKeyValueCoding$UnknownKeyException message >>>> '<co.name.eo.Periodic 0x1cc3b4c1> valueForKey(): lookup of unknown key: >>>> '[Page 1]'. This class does not have an instance variable of the name >>>> [Page 1] or _[Page 1], nor a method of the name [Page 1], _[Page 1], >>>> get[Page 1], or _get[Page 1]' object '<co.name.eo.Periodic pk:"2">' key >>>> '[Page 1]'> >>>> >>>> >>>> Does anyone know how to avoid this other than removing the keys that >>>> indicate how to split the property editing across pages? Any help would be >>>> appreciated. >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list ([email protected]) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com >>>> >>>> This email sent to [email protected] >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com >>> >>> This email sent to [email protected] >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/ken%40ksroom.com >> >> This email sent to [email protected] > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
