Le 20/03/2012 12:47, Jacopo Cappellato a écrit :
L) framework/birt (and related dependencies/reports spread around): move to
Extras
M) framework/bi (and related dependencies - ecas/business rules and data - spread
around): move to Extras
This is an area where Hans and I are in disagreement
I believe the original purpose of the Example component was to provide
a very basic application that new developers can analyze and learn
from. Running the ant task creates an empty application - there is
nothing to see there.
So, here is the use case: I need to train new developers to
I like the idea of keeping reporting tools separate from OFBiz. In my
experience, IT departments are already using a reporting tool for
other applications and they would prefer to integrate that tool with
OFBiz, instead of learning/using a new tool that comes bundled with it.
-Adrian
My preference is to keep Flat Grey and one other theme - I have no
preference on what that other theme is.
-Adrian
Quoting Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com:
I) $OFBIZ_HOME/themes/*: move a few of them to Attic and a few of
them to Extras; keep just one (or two)
+1 birt to Extra.
On Tue, Mar 20, 2012 at 10:31 AM, adrian.c...@sandglass-software.com wrote:
I like the idea of keeping reporting tools separate from OFBiz. In my
experience, IT departments are already using a reporting tool for other
applications and they would prefer to integrate that
Flat Gray is simple, and clear.
It serves well as a basic theme.
AFAIK, it the only theme that supports both directions for languages
LTR and RTL.
On Tue, Mar 20, 2012 at 10:33 AM, adrian.c...@sandglass-software.com wrote:
My preference is to keep Flat Grey and one other theme - I have no
I have always had a problem with OS-specific code being maintained in
OFBiz. Granted, we have some artifacts that must take the OS into
consideration in order to get OFBiz to work, but it appears to me the
Debian stuff doesn't fall into that category (I could be wrong, please
correct me if
is it possible to download the example separately for new comers ?
On Tue, Mar 20, 2012 at 10:28 AM, adrian.c...@sandglass-software.com wrote:
I believe the original purpose of the Example component was to provide a
very basic application that new developers can analyze and learn from.
Yes, making it an extra is an option.
-Adrian
Quoting Mansour Al Akeel mansour.alak...@gmail.com:
is it possible to download the example separately for new comers ?
On Tue, Mar 20, 2012 at 10:28 AM,
adrian.c...@sandglass-software.com wrote:
I believe the original purpose of the Example
Sounds like a plan
Jacques
From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com
Hi,
1) keep it in framework
+1
2) but remove it from the upcoming new release branch 12.04
+1 - for now the JCR implementation provide the the developer an API
which helps to create, read, update or
From: Nicolas Malin malin.nico...@librenberry.net
Le 20/03/2012 11:48, Jacopo Cappellato a écrit :
Or alternatively we could:
1) keep it in framework
2) but remove it from the upcoming new release branch 12.04
3) and then, as a community, we could start the effort (i.e. top priority for
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
A) move framework/guiapp out of the framework; after all these years no code made advantage of it being part of the framework and
it is only used by the specialpurpose/pos component (which was the component for which it was built for); so
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
H) specialpurpose/*: move several (if not all, apart ecommerce) of the components to Extras (if there are persons interested to
become committers/maintainers) or to Attic
There seems to be a general agreement to slim down the number
From: adrian.c...@sandglass-software.com
I believe the original purpose of the Example component was to provide
a very basic application that new developers can analyze and learn
from. Running the ant task creates an empty application - there is
nothing to see there.
So, here is the use
From: Mansour Al Akeel mansour.alak...@gmail.com
Flat Gray is simple, and clear.
It serves well as a basic theme.
AFAIK, it the only theme that supports both directions for languages
LTR and RTL.
Right and Tomahawk is the last evolution of all others. I prefer Tomahawk: it's easier to find you
Makes sense
Jacopo
On Mar 20, 2012, at 3:58 PM, Jacques Le Roux wrote:
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
A) move framework/guiapp out of the framework; after all these years no
code made advantage of it being part of the framework and it is only used
by the
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
O) framework/documents: move the content to Wiki and then move to Attic
The broader topic is to move all the artifacts related to online help out of the framework; they should all live under
applications.
What about documents
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
C) $OFBIZ_HOME/debian: move to Attic
D) the seleniumxml code in framework/testtools: move to Attic
E) specialpurpose/workflow: move to Attic
F) specialpurpose/shark: move to Attic
J) framework/appserver: move to Extras
This one I
From: Nicolas Malin malin.nico...@librenberry.net
Agree with Jacopo, specialpurpose should be on extras.
Huho? ;o)
Scrum depend of projectmgr, the OFBiz extra will be have a dependency management to ensure that all needed components will be
present.
Good point!
To all: is crowd dependent
From: Nicolas Malin malin.nico...@librenberry.net
Le 20/03/2012 12:47, Jacopo Cappellato a écrit :
Q) framework/example and framework/exampleext: move to specialpurpose
Adrian would like to keep Example in the framework but slim it down a lot to
the essential (no form widgets examples, no
I currently use jetty, and keep it updated internally to track the jetty 6
codebase. I have no problem with it being removed from the framework, as long
as we don't assume or require tomcat in the future.
On Mar 20, 2012, at 7:48 AM, Jacopo Cappellato wrote:
C) $OFBIZ_HOME/debian: move to
Ant+Ivy would fit easier with the structure of ofbiz components.
If we want to move to maven, then a modification to
org/ofbiz/base/location/FlexibleLocation.java has to be
done to allow loading resource from a jar file. I am assuming with
maven, you want to package the whole component in
a jar
You could maybe contribute your work on it?
Jacques
From: J. Eckard eckar...@redrocketcorp.com
I currently use jetty, and keep it updated internally to track the jetty 6 codebase. I have no problem with it being removed from
the framework, as long as we don't assume or require tomcat in the
I did not intend to use Maven at all, but good catch and yes for a (possible
far) future iteration
Jacques
From: Mansour Al Akeel mansour.alak...@gmail.com
Ant+Ivy would fit easier with the structure of ofbiz components.
If we want to move to maven, then a modification to
Le 20/03/2012 16:38, Jacques Le Roux a écrit :
From: Nicolas Malin malin.nico...@librenberry.net
Le 20/03/2012 12:47, Jacopo Cappellato a écrit :
Q) framework/example and framework/exampleext: move to specialpurpose
Adrian would like to keep Example in the framework but slim it down
a lot to
I prefer keep Flat Gray theme in Ofbiz over others.
Thanks and Regards
Anil Patel
On Mar 20, 2012, at 9:18 AM, Jacques Le Roux wrote:
From: Mansour Al Akeel mansour.alak...@gmail.com
Flat Gray is simple, and clear.
It serves well as a basic theme.
AFAIK, it the only theme that supports
I use example component as my reference for best practice guide. Still I think
its better placed in Ofbiz Extras.
Thanks and Regards
Anil Patel
HotWax Media Inc
On Mar 20, 2012, at 10:17 AM, Nicolas Malin wrote:
Le 20/03/2012 16:38, Jacques Le Roux a écrit :
From: Nicolas Malin
Another data point: I've been in several OFBiz shops recently and have
observed that many people end up using Flat Grey. Not sure why this is.
IMHO Tomahawk looks nice, but in the end, the mixture of dark and light
is hard on the eyes. Having to scroll over to expose links makes
navigation
My vote will be to keep two themes in the project. IMO Flatgrey theme is
the best to keep as the default one for the project.
--
Ashish
On Tue, Mar 20, 2012 at 5:18 PM, Jacopo Cappellato
jacopo.cappell...@hotwaxmedia.com wrote:
I) $OFBIZ_HOME/themes/*: move a few of them to Attic and a few
I'm in favor of moving all special purpose apps to Extras (or Attic for some of
the older/unused ones) except for ecommerce. Even then the only reason I'd
like to keep ecommerce is because it is the only special purpose app that is
almost universally useful to OFBiz users and I'd like to keep
Le 20/03/2012 12:48, Jacopo Cappellato a écrit :
G) specialpurpose/ofbizwebsite: move to Attic
Jacques and Olivier proposed to move it to Extras instead just in case someone
will pick up the work and complete it in the future.
I would like to mention that, if the original goal was to eat
Le 20/03/2012 12:47, Jacopo Cappellato a écrit :
Q) framework/example and framework/exampleext: move to specialpurpose
Adrian would like to keep Example in the framework but slim it down a lot to the essential (no form
widgets examples, no Ajax examples, no content examples etc...). Adrian
On 21/03/2012, at 9:24 AM, Erwan de FERRIERES wrote:
Le 20/03/2012 12:48, Jacopo Cappellato a écrit :
G) specialpurpose/ofbizwebsite: move to Attic
Jacques and Olivier proposed to move it to Extras instead just in case
someone will pick up the work and complete it in the future.
I
Everyone has different preference about how would the basic component
skeleton looks like (ie, with ajax, without, exta functionality
).
Even if a basic example included with ofbiz distribution, in the
future it will grow again with extra unneeded functionality, or it
will be an on going
I see that most people prefer Flat Grey.
Let me explain why I prefer Tomahawk.
Did you ever wonder why the paper we write on has more than often a greater
height than width, why newspaper have many columns, etc.
Here is an answer
From: Scott Gray scott.g...@hotwaxmedia.com
On 21/03/2012, at 9:24 AM, Erwan de FERRIERES wrote:
Le 20/03/2012 12:48, Jacopo Cappellato a écrit :
G) specialpurpose/ofbizwebsite: move to Attic
Jacques and Olivier proposed to move it to Extras instead just in case someone
will pick up the
Jacques,
We use RTL.
May be you are right about the the ease of use to find an item, but
the user who has permission to all these functionality is an admin,
and normally, she is comfortable finding any item quickly. The rest of
the uses don't have that much items and menus shown.
I know, other
From: Mansour Al Akeel mansour.alak...@gmail.com
Everyone has different preference about how would the basic component
skeleton looks like (ie, with ajax, without, exta functionality
).
Even if a basic example included with ofbiz distribution, in the
future it will grow again with extra
On Mar 19, 2012, at 12:26 AM, Anne wrote:
Basic ideas all look very good to me. IMO anything that is incomplete or
not maintained should be moved to Attic or Extras, unless there is a very
good reason for keeping it. The reason for moving it should be well
documented. That way it is obvious
Hi Jacopo,
Thank you for the effort you spend with OFBiz the last few months. I
generally agree that sure we have to cut the dead wood in the system.
Components and functions which are not used or only halfway implemented
sure, sounds like a good idea to move them out.
However the reasons
Hi Hans,
please see inline:
On Mar 19, 2012, at 9:05 AM, Hans Bakker wrote:
Hi Jacopo,
Thank you for the effort you spend with OFBiz the last few months. I
generally agree that sure we have to cut the dead wood in the system.
Components and functions which are not used or only halfway
Hi Hans,
I don't want to argue the merits of removing specific portions of
code/features/components but I think it's worth mentioning some of the benefits
of moving features to Extras:
- Greater access to contributors, if someone is making regular quality
contributions to a specific Extra then
A point I'd like to emphasize: before moving things out we should check all
related pending Jiras
Jacques
Scott,
I appreciate your reply , but this apache extra's stuff is not
working.: the Apache extra's is now over one year old, in that time
there are 125 extra's for 84 projects. I even counted all the test
and apple dirs.most projects are empty and do not have any extra's
sorry i
Jacopo,
I appreciate you reply and effort, can however not agree with you.
Perhaps for you good reasoning, not for me.
Regards,
Hans
On 03/19/2012 05:08 PM, Jacopo Cappellato wrote:
Hi Hans,
please see inline:
On Mar 19, 2012, at 9:05 AM, Hans Bakker wrote:
Hi Jacopo,
Thank you for
Thank you Scott.
I will wait a bit more before summarizing some of the concepts/opinion
expressed so far and then I will initiate, as you suggested, separate threads.
Jacopo
On Mar 18, 2012, at 9:15 PM, Scott Gray wrote:
I agree with the concept completely. I wonder though if each of the
I want also to emphasize that having many possible syntaxes in use-when, set, etc. is not a plus for me. We could make it possible
but have a single way in OFBiz OOTB. I guess there are no needs to argue about...
Jacques
From: Jacques Le Roux jacques.le.r...@les7arts.com
A point I'd like to
I think Example should stay in the framework, but get rid of all of
the showroom stuff that has been added to it. In other words, keep
it and return it to its original purpose - a very basic component for
new users to understand OFBiz.
I use datafile to connect legacy systems to OFBiz.
I
Thanks for the proposition Jacopo,
Inline...
From: adrian.c...@sandglass-software.com
I think Example should stay in the framework, but get rid of all of
the showroom stuff that has been added to it. In other words, keep
it and return it to its original purpose - a very basic component for
Jacopo,
seeing you are such a believer in community discussion, i assume this is
a proposal which gets properly discussed and will be voted upon?
Regards,
Hans
On 03/18/2012 04:10 PM, Jacopo Cappellato wrote:
In the last period the OFBiz project has grown a lot in shape: the implicitly
Quoting Jacques Le Roux jacques.le.r...@les7arts.com:
Thanks for the proposition Jacopo,
Inline...
From: adrian.c...@sandglass-software.com
I think Example should stay in the framework, but get rid of all of
the showroom stuff that has been added to it. In other words,
keep it and
Le 18/03/2012 10:10, Jacopo Cappellato a écrit :
In the last period the OFBiz project has grown a lot in shape: the implicitly
accepted (or tolerated) strategy operated by the active committers was that the
more features you could add to the official repository the better was: you make
happy
Inline
Le 18/03/2012 13:05, Jacques Le Roux a écrit :
Thanks for the proposition Jacopo,
Inline...
From: adrian.c...@sandglass-software.com
I think Example should stay in the framework, but get rid of all of
the showroom stuff that has been added to it. In other words, keep
it and return
From: adrian.c...@sandglass-software.com
Quoting Jacques Le Roux jacques.le.r...@les7arts.com:
Thanks for the proposition Jacopo,
Inline...
From: adrian.c...@sandglass-software.com
I think Example should stay in the framework, but get rid of all of
the showroom stuff that has been added to
Here is what I am suggesting:
1. Keep the Example component in the framework folder.
2. Return the Example component to its original purpose: A stripped
down, very basic application for a new user to evaluate and
understand. That would require removing all of the things that have
been
Jacopo,
thank you for opening this subject. I agree with you on everything.
I started few days ago, cleaning ofbiz on my local machine
restructuring as I go. I am new to the internals of the framework, and
doing this as an exercise.
Stuck on the few things but that's another post. The bottom
Le 18/03/2012 14:43, adrian.c...@sandglass-software.com a écrit :
Here is what I am suggesting:
1. Keep the Example component in the framework folder.
2. Return the Example component to its original purpose: A stripped
down, very basic application for a new user to evaluate and
understand.
The main purpose of this thread is discussing the ideas; then we can proceed
with the plan where there is agreement, discuss more (as it is happening for
the example component) and find a good solution; if there are different
opinions on specific components, and we will not find a good solution
From: Olivier Heintz holivier.lis...@nereide.biz
Le 18/03/2012 14:43, adrian.c...@sandglass-software.com a écrit :
Here is what I am suggesting:
1. Keep the Example component in the framework folder.
2. Return the Example component to its original purpose: A stripped down, very basic
On Mar 18, 2012, at 1:05 PM, Jacques Le Roux wrote:
O) framework/documents: move the content to Wiki and then move to Attic
So get rid of the online help also?
We can keep the online help (we can maybe review the implementation of the
mechanism... and the content itself really needs some
From: Olivier Heintz holivier.lis...@nereide.biz
Le 18/03/2012 13:05, Jacques Le Roux a écrit :
Quoting Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com:
O) framework/documents: move the content to Wiki and then move to Attic
So get rid of the online help also?
online help is more
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
On Mar 18, 2012, at 1:05 PM, Jacques Le Roux wrote:
O) framework/documents: move the content to Wiki and then move to Attic
So get rid of the online help also?
We can keep the online help (we can maybe review the implementation of
I agree with the concept completely. I wonder though if each of the suggested
changes should get their own thread rather than be discussed in this one, a
thread with too many topics flying around is a little difficult to follow. Or
perhaps even just tackle each of these consecutively after an
On 19 March 2012 07:15, Scott Gray scott.g...@hotwaxmedia.com wrote:
Or perhaps even just tackle each of these consecutively after an
agreement on the course of action is reached and a volunteer to do the work
is found then we could move on to the next suggestion?
+1
Basic ideas all look
101 - 164 of 164 matches
Mail list logo
