Hi Abdullah,
It's a good Idea It's is possible to disable some calcul.
If your groovy compile some information, do findList, getRelated ... ,
if you deploy for a customer a screen that don't use all information,
you generate unnecessary work to your database.
So +1 for your suggestion with
Hi Nicolas
If your groovy compile some information, do findList, getRelated ... , if
you deploy for a customer a screen that don't use all information, you
generate unnecessary work to your database.
But in groovy you will need to get only that data from database which will
be required for the
Maybe I'm not understanding what you propose in this message... but how is this
different from the current common practice?
-David
On Dec 22, 2009, at 1:47 AM, Abdullah Shaikh wrote:
Hi All,
When I was working on ecommerce I also found it difficult/troublesome to
change the UI, so
David E Jones wrote:
The general idea is an interesting one, ie of really separating things by role
and eliminating dependencies.
I like the stuff you guys at Brainfood have done with WebSlinger, and it
certainly makes things easier for people in certain roles.
Webslinger definitely makes
Abdullah Shaikh wrote:
This way the FTL pages will be free of any logic and will just render the
data provided through context from Groovy.
If using this technique,
1) Every FTL page will require a Groovy file for data preparation logic
2) Any changes can be does easily as Groovy won't require
This is definitely the goal - it has some limitations, but that UI and usage is
downright awesome.
Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Dec 22, 2009, at 11:25 AM, Ean Schuessler wrote:
In some ways, SquareSpace.com's online
Abdullah Shaikh wrote:
If your groovy compile some information, do findList, getRelated ... , if
you deploy for a customer a screen that don't use all information, you
generate unnecessary work to your database.
But in groovy you will need to get only that data from database which will
be
: Sunday, December 20, 2009 2:09 AM
To: dev@ofbiz.apache.org
Subject: Re: Using Apache Wicket in Ofbiz presentation layer
To sum up:
1. you want a full separation of concerns for the different roles in your
organization, something that won't require additional training beyond
their
existing
Vasanth Kamatgi wrote:
But, the downside of this approach is - I would be losing the ofbiz community
improvements in the ecommerce front end. for any change / bugfix /
enhancement in the ecommerce module, I need to explicitly port it again in
my own implementation, which is kind of
/Using-Apache-Wicket-in-Ofbiz-presentation-layer-tp975468p977536.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
... :)
A tough problem can be fun.
--
View this message in context:
http://n4.nabble.com/Using-Apache-Wicket-in-Ofbiz-presentation-layer-tp975468p977539.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
On Tue, 2009-12-22 at 18:40 -0800, Vasanth Kamatgi wrote:
.
But, I would see some merit in continuing
the discussion to find the silver bullet for decoupling at rendering stage.
:)
it is called proof of concept?
--
Antwebsystems.com: Quality OFBiz services for competitive rates
-Apache-Wicket-in-Ofbiz-presentation-layer-tp975468p977544.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Hi Ean,
Below is the modification of the example you have given as per what I
propose.
Groovy:
def user = dispatcher.runSync(getSpecialUser, [])
context.userDetails = { user };
FTL:
table
#if(userDetails != null)
tr
td
span
David E Jones wrote:
To sum up:
1. you want a full separation of concerns for the different roles in your
organization, something that won't require additional training beyond their
existing skill set
2. you want no dependencies between different roles so they can't mess each
other up or
On Dec 21, 2009, at 8:12 AM, Ean Schuessler wrote:
David E Jones wrote:
To sum up:
1. you want a full separation of concerns for the different roles in your
organization, something that won't require additional training beyond their
existing skill set
2. you want no dependencies
Hi All,
When I was working on ecommerce I also found it difficult/troublesome to
change the UI, so regarding having separation of UI / Code in the
presentation layer, below are my thoughts, but I hadn't implemented them,
because I needed to complete the project and had no time for this.
What I
Hi all,
Firstly I would like to thank David E. Jones
http://www.blogger.com/profile/07283017166339658819 , for his
encouragement to use the community process.
I had previously posted a question in this community at
http://n4.nabble.com/Application-framework-technology-set-tp195713p963334.ht
To sum up:
1. you want a full separation of concerns for the different roles in your
organization, something that won't require additional training beyond their
existing skill set
2. you want no dependencies between different roles so they can't mess each
other up or slow each other down
3.
I had a quick look at wicket and this sounds pretty interesting for the
ecommerce component. Updating the ecommerce frontend UI is indeed
sometimes pretty cumbersome.
Looking forward to a proof of concept?
Regards,
Hans
On Sat, 2009-12-19 at 23:25 +0530, Vasanth Kamatgi wrote:
Hi all,
: Using Apache Wicket in Ofbiz presentation layer
To sum up:
1. you want a full separation of concerns for the different roles in your
organization, something that won't require additional training beyond their
existing skill set
2. you want no dependencies between different roles so they can't
: Using Apache Wicket in Ofbiz presentation layer
To sum up:
1. you want a full separation of concerns for the different roles in your
organization, something that won't require additional training beyond their
existing skill set
2. you want no dependencies between different roles so they can't
On Dec 19, 2009, at 9:32 PM, Vasanth Kamatgi wrote:
3) I am not aware, how to kick-off the analysis, requirement comparison, POC
etc. activities. Guidance by community gurus would be a great help.
This is what I use with clients to do requirements gathering, design, etc for
business
-Original Message-
From: David E Jones [mailto:d...@me.com]
Sent: Sunday, December 20, 2009 2:09 AM
To: dev@ofbiz.apache.org
Subject: Re: Using Apache Wicket in Ofbiz presentation layer
To sum up:
1. you want a full separation of concerns for the different roles in your
organization
24 matches
Mail list logo
