Re: ERD2WWizardCreationPage Rules for Creation vs Editing
Re: ERD2WWizardCreationPage Rules for Creation vs Editing
- Subject: Re: ERD2WWizardCreationPage Rules for Creation vs Editing
- From: ISHIMOTO Ken <email@hidden>
- Date: Mon, 28 Jan 2013 06:23:28 +0100
David,
I see for compatible Reason that makes sense.
But at the end of the day, 100% ERMODTabInspectPage is the winner.
Ken
On 2013/01/27, at 23:39, David LeBer <email@hidden> wrote:
> Ken,
>
> There are two different flavours of Inspect Page in Modern because there are two different flavours of Inspect Page in ERD2W, and it Modern was designed to be (initially anyway - not sure how well I succeeded on this front) a drop in replacement.
>
> D
>
> On 2013-01-27, at 4:30 PM, ISHIMOTO Ken <email@hidden> 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@hidden 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@hidden> 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@hidden> 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@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
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
> _______________________________________________
> 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