Theodore,

ERModernLook has 2 list page repetitions. ERMDSimpleListRepetitions is default. 
The other is strictly for compatibility reasons and is not used unless you 
explicitly enable it (I never do).

D

--
David LeBer
Codeferous Software

On 2012-01-04, at 10:02 PM, Theodore Petrosky wrote:

> This is beautiful and it is working WONDERfully. However, I don't understand 
> how we got here.
> 
> You were expecting a different ListRepetition. Does this imply that I am not 
> really using the Modern look and when I 'fix' that at some point everything 
> will break?
> 
> Would you be available to schedule an hour tutoring? Of course we would work 
> out an acceptable remuneration. We could record it and put it online. Perhaps 
> some other person struggling would find it useful.
> 
> Let me know what you think.
> 
> Ted 
> 
> 
> --- On Wed, 1/4/12, Ramsey Gurley <[email protected]> wrote:
> 
>> From: Ramsey Gurley <[email protected]>
>> Subject: Re: rules help
>> To: "Theodore Petrosky" <[email protected]>
>> Cc: "WebObjects Development" <[email protected]>
>> Date: Wednesday, January 4, 2012, 8:55 PM
>> That's a different list repetition
>> component than I was looking at.  It looks like you're
>> getting ERMDSimpleListRepetition. It seems all you should
>> need is
>> 
>> 100: entity.name = 'MyEntity' and object.status = 'AE'
>> => baseClassForObjectRow = "green ObjRow" [Assignment]
>> 
>> Ramsey
>> 
>> On Jan 4, 2012, at 10:42 AM, Theodore Petrosky wrote:
>> 
>>> 
>>> I attached a screen shot of the list page and css is
>> turned on.
>>> 
>>> are these the classes you would expect if I were using
>> ERModernLook? I am not having a good time with this.
>>> 
>>> Ted
>>> 
>>> --- On Mon, 1/2/12, Ramsey Gurley <[email protected]>
>> wrote:
>>> 
>>> From: Ramsey Gurley <[email protected]>
>>> Subject: Re: rules help
>>> To: "Theodore Petrosky" <[email protected]>
>>> Cc: [email protected]
>>> Date: Monday, January 2, 2012, 3:19 PM
>>> 
>>> I assume you're using the ERModern look.  In the
>> list repetition I see:
>>> 
>>> ListTableRow: WOGenericContainer {
>>>     _unroll = true;
>>>     elementName = "tr";
>>>     class = "ListRepetitionRow";
>>> }
>>> 
>>> That could easily be
>>> 
>>> class = d2wContext.tableRowClass;
>>> 
>>> With a default rule like
>>> 
>>> 10: *true* => tableRowClass = "ListRepetitionRow"
>> [Assignment] //default rule
>>> 
>>> Then you could specify the row based on object
>> attributes in rules like
>>> 
>>> 100: entity.name = 'MyEntity' and object.status = 'AE'
>> => tableRowClass = "green ListRepetitionRow" [Assignment]
>> //override
>>> 
>>> Ramsey
>>> 
>>> On Jan 2, 2012, at 10:11 AM, Theodore Petrosky wrote:
>>> 
>>>> I have an WO App that I am experimenting with. I
>> am trying to use it to learn D2W.
>>>> 
>>>> I have had to replace a shared excel spread sheet
>> with my app and it is working quite well. From the first day
>> my users were impressed and happy to get off of excel.
>>>> 
>>>> Of course I had to make it appear that they were
>> viewing an excel spread sheet in a browser. and they had
>> requirements. the main one being that rows are colored to
>> indicate status. Green = AE needs to resolve issues. Red =
>> Client must resolve text changes. and a few other colors.
>>>> 
>>>> When the traffic person looks at the app, she sees
>> multiple colored rows and she knows what to do. Of course
>> she could ask for only the Gold colored rows (Objects that
>> she must complete today).
>>>> 
>>>> I am storing the status of each row and I use the
>> CSS in my Wonder app to change the row colors (individual
>> columns have colors also to indicate other stuff).
>>>> 
>>>> How do I approach this in D2W?
>>>> 
>>>> I can not argue that the design is either good nor
>> bad. It is what it is. I had to match what was there or they
>> would still be using the excel spread sheet. You have no
>> idea how hard I had to work to get the users to understand
>> the concept of a row being complete so it no longer shows up
>> unless you ask for the completed rows or search including
>> completed rows.
>>>> 
>>>> I am redoing the app to allow log in with
>> permissions to various functions (i.e. the client can view
>> but not change meta data). I can continue as a Wonder app or
>> keep plugging along in D2W. I want to learn the D2W.
>>>> 
>>>> Ted
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will
>> be ignored.
>>>> Webobjects-dev mailing list     
>> ([email protected])
>>>> Help/Unsubscribe/Update your Subscription:
>>>> http://lists.apple.com/mailman/options/webobjects-dev/ramseygurley%40gmail.com
>>>> 
>>>> This email sent to [email protected]
>>> 
>>> <MYD2W classes.png>
>> 
>> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/dleber_wodev%40codeferous.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:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to