Ok -
So I guess my next question. I can then go in and out of D2W?
What do I need to know about the context's then?
Say my login page is custom and say a few others.
Page A Custom
Page B Custom
Page C D2W
Page D D2w
Page E Custom
Say I needed to move through all five pages. What do I need to do or concern
myself with
when I go from page B to C and from page D to E ?
Thanks
PS: I really do have the hang of using all D2W for backend admin stuff and it
works really well.
On Apr 20, 2010, at 7:14 AM, David LeBer wrote:
>
> On 2010-04-20, at 2:44 AM, Mark Wardle wrote:
>
>> I've got so many different structured medical questionnaires / forms mapped
>> as entities that it would be burdensome to create a component to edt and and
>> every one. D2W is the solution!
>>
>> However, for custom complex pages - particularly landing pages or
>> integration pages, I use a normal component and perhaps leverage D2W by
>> using embedded D2W list(s) if I want all the pagination and batch stuff for
>> free.
>>
>> I do have a complex SNOMED CT browser/chooser and although it is a D2W
>> component (supporting editrelationship or select) it can only be used with
>> one kind of entity. I suppose I could spend a little longer and make
>> everything very generic but sometimes you've just got to get something
>> working haven't you?
>>
>> What I'm trying to say is, don't give up on non-d2w components!
>
> Yes.
>
> D2W is awesome, often in a "I can't believe I built apps before I discovered
> it" kind of way, but it does come to the table with certain expectations and
> doesn't cover all situations. Sometimes you just have to make the pragmatic
> choice to do something custom because that's going to be the straightest
> route to your solution.
>
> All of our apps have a significant ('ly high) percentage of them supplied by
> D2W components and governed by D2W rules, but there are always sections that
> are custom built the 'old fashioned'* way.
>
> When we discover we are solving the same problem multiple times, it is time
> to look for a general solution, and often that results in a new D2W widget.
>
> * term specifically chosen to raise the ire of list curmudgeons.
>
>>
>> Mark
>>
>> --
>> Dr. Mark Wardle
>> Specialist registrar, Neurology
>> (Sent from my mobile)
>>
>>
>> On 20 Apr 2010, at 01:01, James Cicenia <[email protected]> wrote:
>>
>>> well say let's talk hypothetical.
>>>
>>> In portion we have some dynamic graphs and in the other
>>> are we have a dynamic spreadsheet of changing values.
>>>
>>> All of this is read only data compiled from many different EO sets.
>>>
>>> James
>>>
>>>
>>> On Apr 19, 2010, at 5:47 PM, Ramsey Lee Gurley wrote:
>>>
>>>>
>>>> On Apr 19, 2010, at 5:06 PM, James Cicenia wrote:
>>>>
>>>>> Hello -
>>>>>
>>>>> This has baffled me about D2W. It definitely seems to need to have an
>>>>> entity.
>>>>>
>>>>> So my question is ... how do you model custom screens?
>>>>>
>>>>> Do you create a dummy entity with dummy attributes associated with the
>>>>> "areas" on the screen?
>>>>>
>>>>> D2Wondering,
>>>>> James Cicenia
>>>>
>>>> What is going in the "areas" on the screen specifically?
>>>>
>>>> Ramsey
>>>>
>>>
>>> _______________________________________________
>>> 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/mark%40wardle.org
>>>
>>> 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/dleber_wodev%40codeferous.com
>>
>> This email sent to [email protected]
>
> ;david
>
> --
> David LeBer
> Codeferous Software
> 'co-def-er-ous' adj. Literally 'code-bearing'
> site: http://codeferous.com
> blog: http://davidleber.net
> profile: http://www.linkedin.com/in/davidleber
> twitter: http://twitter.com/rebeld
> --
> Toronto Area Cocoa / WebObjects developers group:
> http://tacow.org
>
>
>
>
_______________________________________________
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]
