Re: D2W Embedded Component Questions
Re: D2W Embedded Component Questions
- Subject: Re: D2W Embedded Component Questions
- From: Johnny Miller <email@hidden>
- Date: Fri, 01 Mar 2013 11:08:45 -1000
Thank you that explains it. Which is too bad because I prefer the it works by "magic" definition.
Thanks a million,
Johnny
On Mar 1, 2013, at 10:59 AM, Ramsey Gurley <email@hidden> wrote:
> Not so much magic. Just a couple of rules in the JavaDirectToWeb framework's d2w.d2wmodel file.
>
> 0 : *true* => pageWrapperName = "PageWrapper" [com.webobjects.directtoweb.Assignment]
> 0 : frame = 1 => pageWrapperName = "D2WEmptyWrapper" [com.webobjects.directtoweb.Assignment]
>
> To answer your question: Yes, include the page wrapper switch just like the component you are cloning has. If you use the ERXD2WInspect it will set frame to true.
>
> Ramsey
>
> On Mar 1, 2013, at 12:50 PM, Johnny Miller wrote:
>
>> Thanks Jesse,
>>
>> So is it just the "magic" of D2W that says "OK, this is an embedded component so I can skip the PageWrapper"?
>>
>> Best,
>>
>> Johnny
>>
>> On Mar 1, 2013, at 9:41 AM, Jesse Tayler <email@hidden> wrote:
>>
>>>
>>> sure, you'll likely need your page wrapper in a page level component.
>>>
>>> and these steps sound about right.
>>>
>>> I don't think you'd need to make a whole new look framework unless you're going to do an entire, shared look -- others know better I'm sure but you can create just a few components that override the basic edit and inspect and list pages and design them to your liking.
>>>
>>> I think you'll have a GREAT time creating your own components for use with D2W rules!
>>>
>>> Got for it!
>>>
>>> you'll realize that you can write some java code and design your templates very specifically, and thus reduce dramatically the number of components and rules you actually need to create.
>>>
>>> write code to reduce rules, then write rules specific to your UI to reduce code - you'll end up with something really tight.
>>>
>>> I've seen a lot of D2W designs where to add a new attribute, you end up writing three rules for this, two rules for that and you make a tiny component to link here or there and so on -- if you take this level of control you have decided upon, you can really design super-tightly to your UI concept.
>>>
>>> Have fun!
>>>
>>> On Mar 1, 2013, at 2:28 PM, Johnny Miller <email@hidden> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm having a little trouble wrapping my head around this (no surprise I know)...
>>>>
>>>> I would like to start small and just use the ERXD2WInspect component to combat the component explosion Ramsey talks about in his Custom and Embedded D2W component presentation.
>>>>
>>>> I would like to use my own look...
>>>>
>>>> So to get started I should:
>>>>
>>>> 1. Create my own look framework.
>>>> 2. Create a component that subclasses ERD2WInspectPageTemplate
>>>> 3. In the framework's rule file create a rule that the component created in the step above is the right hand assignment for templateNameForInspectPage
>>>> 4. In my app I wouldn't reference the component I created I would just bind my embedded component to ERXD2WInspect.
>>>>
>>>> So far so good?
>>>>
>>>> If so when authoring my component... do I still wrap the component content with the PageWrapper?
>>>>
>>>> Thanks in advance,
>>>>
>>>> Aloha,
>>>> Mr. Johnny Miller
>>>> Web Development Manager
>>>> Kahalawai Media Company
>>>> Lahaina, HI 96761
>>>> tel: (808) 661-7962 | mobile: (808) 283-0791
>>>> website | e-mail
>>>>
>>>> _______________________________________________
>>>> 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