From: "Ruth Hoffman" <[email protected]>
Did say that?
Well I guess that is a typo...what I meant to write is:
If we had a core feature like this (and I didn't have to prototype it and then build it each time), well that could make my life
much easier.
Yes everybody life I guess
By the time I get into a project and this sort of thing comes up, the competition has long since be bested by OFBiz and all the
other cool features it offers.
Arg, sorry I don't get this sentence (tried twice to read ;o). I mean
<<
the competition has long since be bested by OFBiz and all the other cool
features it offers.
excuse: English is not my mother's tongue :p
This is something that most OFBiz adopters don't understand and/or don't see until much later in the development cycle - if at
all.
We need Shiro for sure, "we" agreed. What we will need after the slimdown effort is to get a consensus between developers about what
should be done next. And not only, but as some requested already, *a road map*, with tasks ordered (and if possible assigned,
whisful thinking, I'm an optimist). This can stay simple with only big tasks (projects?) referred to, like
http://blog.jquery.com/2012/06/28/jquery-core-version-1-9-and-beyond/
Jacques
Ruth
On 7/16/12 5:32 PM, Jacques Le Roux wrote:
From: "Ruth Hoffman" <[email protected]>
IMHO the OFBiz way of using SecurityPermissions, SecurityGroups etc. is much
too complex (and error prone) to achieve what is
effectively role based access control.
This needs really more thoughts and exchanges in the community before going
ahead. It's really a very important core feature...
I think so. And I've seen many real-world cases where a core feature like this is something that sets OFBiz apart from its
competitors.
Which competitors are you thinking about?
Jacques
