Andrew,
I agree with everything you're saying here.
I managed to get the engine started on both Windows and Linux before I
even knew of the existence of this mailing list. So the OOTB start-up
part of the handbook is largely all there. Trouble then was figuring out
how to get it into first gear. Hitting the workshop manuals and the
mailing lists, one message quickly became clear. If you want to get this
baby out on the road you're going to need an engineering degree. As it
happens, I have a couple of those, but not in OOP. Which kindof leaves
me a bit up OFbiz creek without a paddle :)
A clear roadmap would be most useful so that the essential stuff gets read
first.
My feeling entirely. I'd like to contribute by helping to get something
like that going, but where to start?
And yes, there are already How to documents, architecture documents,
but there is too much to read plus every document starts with a brief resume
of OFBiz rather than getting down to the business at hand. Basically it
appears that every document has been written to stand alone and therefore
feels the need to fill in the back ground on OFBiz. I haven't yet read a
great deal of the available documentation, but there is a trend there.
Another big thumbs-up from me there too. That explains why I have no
problems getting started, but can't get out of first gear.
Please don't take offence at these comments, they are only intended to help.
That's such an important point. Imo what we need is a more robust kind
of forum where we can thrash-out these kind of front-end problems
without risking stepping on the toes of those who are already
up-to-their ears working on more delicate matters of engine design.
I also find that there is a lack of structure in the documents in that there
tends to be paragraph after paragraph of text which is neither reference nor
tutorial.
What struck me first is actually how literate and accomplished the
documentation is in comparison with other more mainstream Open Source
projects like osCommerce for instance. Which makes it all the more
difficult to understand why, several week later, I'm still stuck like a
rabbit in the headlights. Entranced by the power of what I see coming at
me, but with no idea where to jump next. Which is what makes me think
you may be onto something here.
And as I progress along the road to OFBiz heaven I will try to
document my path. In the mean time it might be useful to thrash out a style
and structure to the whole documentation suite. Heck I know this can be
difficult in the open source environment.
Too true. Is there anything I could do to help with this?
I would favour a wiki approach to doing documents provided the wiki is
restricted to named members to stop spammers wrecking it. In the wiki, users
should use a colour, perhaps blue to indicate a question or need for further
detail in the flow of the document and the remainder of the contents in
black. I am quite willing to start up a tutorial document if you are all
willing to contribute to it with David acting as umpire.
If you think a Wiki is the way to go then I'm prepared to help where I can.
I keep thinking of something I was taught at the very beginning of my
science training. That everything should be written-up in a form that
assumes no prior knowledge of the speciality at hand.
This is an ideal that can never be completely achieved. Not in this life
anyway. Only Allah makes things perfect. But it's the trying that makes
the difference. It has to be admitted that this seems to have gone out
of fashion in recent years, which might be just one reason why we seem
to have thrown the baby out with the bathwater in the western world at
least, and science departments are closing down at a rate of knots to be
replaced with media studies departments aimed at producing more Big
Brothers. And we all know where that leads!
Not the place to be discussing these things I know. But just one of the
trends I would like to try and help to reverse.
Please let me know what I can do to help to move what you're suggesting
on to the next step.
Best,
Ian
