David,
I have got absolutely no idea at all why it sounds like I don't like
your landing strip.
This is exactly opposite to the facts.
All analogies have their limits, and maybe this one has already been
stretched too far. But
Undersun and OpenSource Strategies are beautifully designed
David,
I'd agree with most everything you're saying here. I'd just want to edit
it slightly and put things in a different order (my insertions in
brackets where possible).
David E. Jones wrote:
The OOTB solutions are way too limiting, making it impossible to scale
operations.
There are lots
OK David. Maybe just one last thing.
No more soap-boxing. A simple question for a change :)
David E. Jones wrote:
Looking around the OFBiz documents and such I don't think this
distinction is adequately represented, so I added some text similar to
the above to the home page of ofbiz.apache.o
Ian,
It depends on what you're looking for.
If the focus is still a "small business accounting package" as the
subject line says - I know I know, there have been a zillion posts to
this thread, so perhaps not. - If it's accounting, two spring to mind...
For a desktop system, have a look at GnuCa
After an exchange with Ian McNulty about UI clarification, I thought a bit for
a solution (actually I did not thought a lot, the idea was there, clear, when I
waked up ;o)
Ian is not the 1st to complain about backend complexity. Yes, my propostion is
only about backend. Because IMO eCommerce an
This is great, Can we do this, Save Screen and Form definition in Database
(Sceeen and Form widget file will loaded into database.), Party Group
Preferences set of Entities can be designed to store the information like
which field should be visible/hidden for a Party Group..
By doing this we can c
Andrew,
I'm not looking for anything specific at the moment. Just trying to
evaluate current options and keep on top of developments in the hope of
offering clients the best, most flexible, most long-term solutions I can
find.
I checked out GnuCash and SQL Ledger before I discovered OFBiz. T
Ian,
About this question:
In my ignorance I kind of assumed that once I had a stable version
running it would - like my old QuickBooks 3 - keep on going without
too much trouble. Provided I didn't want to start customizing and
upgrading that is.
OK. So new security breaches and the nece
So, how do we decide which fields are required (mandatory) or not?
-David
On Jan 21, 2007, at 4:28 AM, Jacques Le Roux wrote:
After an exchange with Ian McNulty about UI clarification, I
thought a bit for a solution (actually I did not thought a lot, the
idea was there, clear, when I wake
On Jan 21, 2007, at 6:33 AM, Anil Patel wrote:
This is great, Can we do this, Save Screen and Form definition in
Database
(Sceeen and Form widget file will loaded into database.), Party Group
Preferences set of Entities can be designed to store the
information like
which field should be vi
Jacques,
On your suggestion, I think it would only make sense to make a subset of
the features if there was clear market evidence of what the subset would
be and who would benefit from it.
As I don't think anything like this is currently available, I'm inclined
to think that going in this directi
Yes, that's most part of the work. I will think about it and elaborate more my
proposition. Of course any help is welcome.
I guess we will have to make a consensus about which fields are preferably
shown. I regret to have used "mandatory" or even
"required" as this has no sense as I previously wr
Andrew,
Yes, maybe. But do you think that OOTB in a screen like Catalog/Product
following fields are really needed for a demo or a POC :
(this is the more efficient criterion I found for the moment; I found also that
it's easier to define fields not to be shown by
default than fields to be show
Okay, now behind curtain #2...
The whole point of my question was to get you and others thinking.
The policy on this was established years ago.
For OFBiz OOTB the point is to be as inclusive as possible. There is
one reason for this: it is easier to know something is there and
decide you
Hello,
I am Daniel Martínez, I have created a company in Spain which main
business is as an ERP service provider. I like a lot ofbiz. I am now
using to develop a custom application for a customer and it will surely
become my main tool for the business.
This said, I agree completely with Andrew. I
> bespoke integration with closed-source, proprietary systems is an arduous and
> expensive business that few clients can afford.
That's my business! :) Plus some IT managers screw things up big time, so we move in, sign NDAs,
and set things right, and then hush...
> Microsoft and Sage spotted
David, Ian,
I believe Ian has a point about "not yet fully developed". As discussed before, the OFBiz
framework is fine, complete. It's what's built around the engine (car body, doors, windscreen
wipers, seat ejection button, etc) that's incomplete, or to put it in a more PR way to potential
c
I agree with David here.
First off, how difficult is it to "customize" OFBiz and cut away some fields from the forms? If a
business only ever uses certain fields, what's the point of hiding the others away
programmatically? Why not just cut the front-end forms?
As I told my boss, many fields
Jonathon,
So, just to be clear and try to rephrase what you said: the problems
you are running into are caused by the approach used to customize and
install OFBiz rather than OFBiz itself.
You should know, if you don't already, that OFBiz is being used
effectively in various manufacturin
If we have Form meta data in Database then we can enhance the screen
rendering system to read field visibility attribute from the database.
So lets say, userLogin.userId belongs to Casher User group. So when
rendering a ScreenA::FormX, System will look for visibility attributes of
fields on FormX
So, you're thinking of more of a permission system?
-David
On Jan 21, 2007, at 9:10 PM, Anil Patel wrote:
If we have Form meta data in Database then we can enhance the screen
rendering system to read field visibility attribute from the database.
So lets say, userLogin.userId belongs to Cashe
yes we can also say that. true.
On 1/21/07, David E. Jones <[EMAIL PROTECTED]> wrote:
So, you're thinking of more of a permission system?
-David
On Jan 21, 2007, at 9:10 PM, Anil Patel wrote:
> If we have Form meta data in Database then we can enhance the screen
> rendering system to rea
Why don't we reuse the existing permissions infrastructure (no new Form meta data in database),
and simply code the front-end to show/hide fields based on those permissions?
Jonathon
Anil Patel wrote:
yes we can also say that. true.
On 1/21/07, David E. Jones <[EMAIL PROTECTED]> wrote:
S
It is not necessary to completely hide some fields, we could use AJAX
visibility and some option to change it without a page reload. It
could be a good idea to fill the form´s default values on BEFORE form
load, and not only if the user didn´t fill a field after submitting
the form. Tab navigation
David,
> So, just to be clear and try to rephrase what you said: the problems you are
> running into are caused by the approach used to customize and install OFBiz
> rather than OFBiz itself.
Sigh. Alright, I'll leave it at that. I concede that M2M could be an application that deviates
wildly f
Jonathon,
This is good feedback, and very unfortunate. It has been frustrating
to me for years that many users of OFBiz that even get it working
well for them in production real-world use simply don't get involved
and contribute back, and that happens to be the ONLY way anything
gets int
Guido,
> It is not necessary to completely hide some fields, we could use AJAX
Maybe we could incorporate Prototype (http://www.prototypejs.org/)? Build a convenient engine
around AJAX that the OFBiz framework can easily talk to?
> I am thinking of some kind of runtime templating for the visi
FYI - there are examples of use of dojo in OFBiz at the moment.
Check out the quick anonymous checkout process whenever you get a
chance. We have built a number of user interface enhancements using
this package.
You can also easily use hidden divs,etc with very simple javascript -
to ge
On Jan 22, 2007, at 12:03 AM, Jonathon -- Improov wrote:
> It could be very useful for new users to have a help icon link
next to
> each field or for each form with a full explanation of each field
and
> examples.
THAT is what I've been pushing for too! Anyway, I'm also happy that
the OF
Jonathon,
Thanks for the advice.
I just figure out another way to help me to have a more useful "Calculated
Completion Date" when I plan a production run.
I first create different tasks for the same purpose, e.g.
1) 10 workers to gather all the raw materials
2) 20 workers to gather all the raw
30 matches
Mail list logo
