Re: custom page ??
Re: custom page ??
- Subject: Re: custom page ??
- From: Ramsey Gurley <email@hidden>
- Date: Wed, 03 Apr 2013 14:31:39 -0700
Ewwww, WOOgnl makes it ten times worse! WOOgnl produces befuddling things like
<wo:str value = "$saveError|misc.html" />
I'm looking around for a file named misc.html. Nope! It's actually a method named html(String string) on a class named ChuckTesta. Pffft. Obviously! I'm sure if I command click it, it'll take me right to the source... oh wait, no, it doesn't.
It also produces stuff like
<wo:link directActionName = "style" id = "~\"theDesc-\" + anOrderDetailSale.orderLineNumber" ?id = "$anOrderDetailSaleStyle.styleNumber" ?cid = "$anOrderDetailSale.extraStorage.category.categoryId //VALID" ?pn = "$anOrderDetailSale.partNumber" disabled = "~(!anOrderDetailSaleStyle)" secure = "$false"><wo:str value = "$lineDescription" escapeHTML = "$false" /></wo:link>
I'm side scrolling on a 22" monitor in a maximized window just attempting to read it. No widescreen is wide enough for WOOgnl!
And then there's the plain ridiculous
<wo:str value = "~#A=new com.webobjects.foundation.NSMutableArray(),#A.addObject(name), #A.addObjectsFromArray(session.languages), #A"/>
I'm sure that stuff is fun to debug. All I need to know:
inline bindings == satan
and cmd-2 W is my friend :D
Ramsey
On Apr 3, 2013, at 1:23 PM, David LeBer wrote:
> Bah, inline bindings are a great idea.
>
> But only if you have them enabled, and the WOOgnl framework in your class path.
>
> D
>
> --
> David LeBer
> Codeferous Software
>
> On 2013-04-03, at 4:12 PM, Ramsey Gurley <email@hidden> wrote:
>
>> WOHyperLink? The class is WOHyperlink. Perhaps part of the problem?
>>
>> I blame the inline bindings. Inline bindings are never a good idea :-)
>>
>> Ramsey
>>
>> On Apr 3, 2013, at 1:03 PM, Theodore Petrosky wrote:
>>
>>> I have a d2w app and I wanted to add a component to act as a report listing page.
>>>
>>> I created a component called ReportsPage extending ERD2WInspectPageTemplate
>>>
>>> my idea was to add a few hyperlinks that would create some wonderful jasper report documents.
>>>
>>> my ReportsPage comes in fine but when I add a simple hyperlink:
>>>
>>> <ul>
>>> <li><wo:link action = "$projectReportAction">Project Report</wo:link></li>
>>> </ul>
>>>
>>> om.webobjects.appserver.parser.woml.WOMLTemplateParserException: ReportsPage: 5:6: Could not generate an element named: WOHyperLink
>>>
>>>
>>> so I assume that extending ERD2WInspectPageTemplate is my problem.
>>>
>>> Is there a better way to do this?
>>>
>>>
>>> _______________________________________________
>>> 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