Hello Jacques,

Please hold on for sometime. Pranay is on leave since last few days and I
am sure he will post comment here as he is back to work. I hope you are not
in hurry?

Thanks!

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997

On Thu, May 14, 2015 at 3:04 PM, Jacques Le Roux <
[email protected]> wrote:

> It's a pity nobody cares about this tutorial. Wrong or not up to date
> documentation is worse than no documentation. Moreover this tutorial is/was
> a most important piece for newcomers discovery.
>
> Still hoping feedback...
>
> Jacques
>
>
> Le 09/05/2015 11:41, Jacques Le Roux a écrit :
>
>> Hi All, Adrian,
>>
>> Adrian I have looked at your ApacheCon 15 presentation, good it has been
>> advertised on the user ML!
>>
>> One point, I read:
>>
>> <<The Best Practice to follow is:
>> “When a screen is split up into multiple templates or screens thedata
>> preparation action should be associated only with the individualsmall
>> screen
>> that it prepares data for. This makes it easier to move templates and
>> content
>> pieces around and reuse them in many places. “
>>
>> In other words, the data preparation logic should be contained within the
>> screen widget that renders it –including forms, menus, and trees.
>>
>> But the tutorial found on the Wiki:
>>
>> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide
>> does not follow this best practice –the data preparation is done in the
>> screen
>> and not in the form that displays the data. Consequently, that form is not
>> reusable –it will be empty (not contain any data) if it is used in any
>> other  screen.>>
>>
>> It seems that the Hotwax System contribution policy has changed and this
>> is no longer maintained by them (was mostly Pranay).
>>
>> Pranay, HS team, could you please confirm this tutorial is no longer
>> maintained by you and if we should rather link a page on HS blog?
>>
>> Of course I'm not thinking about only the point Adrian outlined, but in
>> general.
>>
>> Thanks
>>
>> Jacques
>>
>>

Reply via email to