D2W Navigate from Create to List

2013-11-06 Thread Markus Ruggiero
What is the best way to handle the following customer request in a Neutral Look 
D2W application?

After pressing Save on a create page the customer wants to got to a list page 
displaying the just created object. Maybe the user wants to add a bunch of 
objects and might eventually miss-type a code and then not be able to figure 
whether he has entered the correct value. And while working off a list of data 
to enter he might lose track of which entry he has to add next. In other cases 
the creation of an object is pretty simple but afterwards editing is necessary 
due to very complex background processing that cannot take place before an EO 
has been properly saved.

Standard D2W behaviour is going back to whatever page was shown when the user 
pressed New. Customer wants to see what was just created. I was thinking of a 
generic next page delegate on any Create* page configuration. I know how to 
create a list page and return that, but the problem is how to best populate 
that list with the one entry that has just been saved. I was thinking of 
creating an array datasource for the list page with that one object, but should 
this not be a database datasource? How would I then create a proper fetch spec? 
As there are many different types of EOs I cannot just pick some common 
attribute and create a qualifier for its value. The only real identifier would 
be the primary key but that is of course not modeled.

Thanks for any ideas.
---markus---

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: D2W Navigate from Create to List

2013-11-06 Thread Theodore Petrosky
Is there a reason that you should not create an attribute that describes a 
'New' item. 

I have to do this with duplicates. My users select an object and make 10 
duplicates. I set a boolean attribute (isADupe) to true. it remains true until 
they edit the object. 

when I return from 'duplicating' the original object, I select all objects that 
are marked 'isADupe', and present a short list. These object remain 'dupes' 
until they are edited and saved.

So if they want 10 duplicates of an object where each object is nearly 
identical except for the due date, make 9 duplicates and edit each one changing 
the due date. As you save the edited object, set isADupe to false.

BTW, thank you for Learning the Wonders'! It is really helping me learn the 
missing pieces.

Ted



On Nov 6, 2013, at 8:38 AM, Markus Ruggiero mailingli...@kataputt.com wrote:

 What is the best way to handle the following customer request in a Neutral 
 Look D2W application?
 
 After pressing Save on a create page the customer wants to got to a list 
 page displaying the just created object. Maybe the user wants to add a bunch 
 of objects and might eventually miss-type a code and then not be able to 
 figure whether he has entered the correct value. And while working off a list 
 of data to enter he might lose track of which entry he has to add next. In 
 other cases the creation of an object is pretty simple but afterwards editing 
 is necessary due to very complex background processing that cannot take place 
 before an EO has been properly saved.
 
 Standard D2W behaviour is going back to whatever page was shown when the user 
 pressed New. Customer wants to see what was just created. I was thinking of 
 a generic next page delegate on any Create* page configuration. I know how to 
 create a list page and return that, but the problem is how to best populate 
 that list with the one entry that has just been saved. I was thinking of 
 creating an array datasource for the list page with that one object, but 
 should this not be a database datasource? How would I then create a proper 
 fetch spec? As there are many different types of EOs I cannot just pick some 
 common attribute and create a qualifier for its value. The only real 
 identifier would be the primary key but that is of course not modeled.
 
 Thanks for any ideas.
 ---markus---
 
 ___
 Do not post admin requests to the list. They will be ignored.
 Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
 Help/Unsubscribe/Update your Subscription:
 https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
 
 This email sent to tedp...@yahoo.com


 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: D2W Navigate from Create to List

2013-11-06 Thread Ramsey Gurley
Yeah, you need something to define new. You could use a dateCreated timestamp 
or something. Just using D2W, I would

query page with showListInSamePage = true
set the query min on the dateCreated before returning the query page initially
set show list to true and fetch too
in the list configuration, include a branch delegate to provide a create button

That way, the client fetches everything since the page was loaded, which is 
nothing. And the list gets updated as new items are saved.

Alternately, you could do it without any additional data on the eo. If the 
client expects “new” to mean everything since starting the session, you could 
store the list on your wosession. 

If they’re only “new” when the client is working on that page, you could build 
a custom component using embedded d2w. The component could include a erxd2wlist 
and an erxd2winspect in a master-detail arrangement. You could catch the new EO 
saving using notifications and add it to your list when that happens.

On Nov 6, 2013, at 7:27 AM, Theodore Petrosky tedp...@yahoo.com wrote:

 Is there a reason that you should not create an attribute that describes a 
 'New' item. 
 
 I have to do this with duplicates. My users select an object and make 10 
 duplicates. I set a boolean attribute (isADupe) to true. it remains true 
 until they edit the object. 
 
 when I return from 'duplicating' the original object, I select all objects 
 that are marked 'isADupe', and present a short list. These object remain 
 'dupes' until they are edited and saved.
 
 So if they want 10 duplicates of an object where each object is nearly 
 identical except for the due date, make 9 duplicates and edit each one 
 changing the due date. As you save the edited object, set isADupe to false.
 
 BTW, thank you for Learning the Wonders'! It is really helping me learn the 
 missing pieces.
 
 Ted
 
 
 
 On Nov 6, 2013, at 8:38 AM, Markus Ruggiero mailingli...@kataputt.com wrote:
 
 What is the best way to handle the following customer request in a Neutral 
 Look D2W application?
 
 After pressing Save on a create page the customer wants to got to a list 
 page displaying the just created object. Maybe the user wants to add a bunch 
 of objects and might eventually miss-type a code and then not be able to 
 figure whether he has entered the correct value. And while working off a 
 list of data to enter he might lose track of which entry he has to add next. 
 In other cases the creation of an object is pretty simple but afterwards 
 editing is necessary due to very complex background processing that cannot 
 take place before an EO has been properly saved.
 
 Standard D2W behaviour is going back to whatever page was shown when the 
 user pressed New. Customer wants to see what was just created. I was 
 thinking of a generic next page delegate on any Create* page configuration. 
 I know how to create a list page and return that, but the problem is how to 
 best populate that list with the one entry that has just been saved. I was 
 thinking of creating an array datasource for the list page with that one 
 object, but should this not be a database datasource? How would I then 
 create a proper fetch spec? As there are many different types of EOs I 
 cannot just pick some common attribute and create a qualifier for its value. 
 The only real identifier would be the primary key but that is of course not 
 modeled.
 
 Thanks for any ideas.
 ---markus---
 
 ___
 Do not post admin requests to the list. They will be ignored.
 Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
 Help/Unsubscribe/Update your Subscription:
 https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
 
 This email sent to tedp...@yahoo.com
 
 
 ___
 Do not post admin requests to the list. They will be ignored.
 Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
 Help/Unsubscribe/Update your Subscription:
 https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
 
 This email sent to rgur...@smarthealth.com

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com