Posted by
cjhowe on
URL: http://ofbiz.116.s1.nabble.com/Dev-Ordering-Units-of-Measure-tp167406p167419.html
I too have felt Adrian's frustrations in the past.
However instead of voicing my frustration, I submitted
the "differences app" patch and went on my campaign
for
individual developers who don't know OFBiz inside and
out (after 18 months of working on OFBiz, I can say
that I'm still in that boat) to NEVER touch OFBiz
code. Make a "differences app" instead.
Now, I know I go on and on about it. But really, it's
the solution for the majority of those who don't have
commit privileges. It's also the solution for not
having to maintain applications that have thousands of
man hours put into making them work. It's also the
solution to keep you involved with the improvement of
the underlying application you're differencing.
The differences app idea is the same as taking the
idea of the U.S. Highway system. While the highway
system can take you just about anywhere that you want
to
go, there are heavily congested areas near
metropolitan cities that you would prefer not to go
thorugh. So you make a Spur. You still have the
opportunity to go anywhere you want to go, and when
you get to the area you're not too fond of, you take
the Spur. Now you only have to maintain the Spur and
nothing else.
Now the differences app does fall short in two
circumstances. One with the EECAs and one with the
SECAs. You have to disable them by commenting them
out in the OFBiz code if they're not to you're liking.
Everything else you can work around. Java files,
widgets, minilangs, freemarker files, beanshell
scripts, SVN updtates, etc.
Now there is a bit of work to do to allow all of the
OFBiz applications to be differenced. The calls for
the decorator screens need to be dynamic in their
location (like they are in the ecommerce application).
Other than that, you're good to go.
And then what's even better, sourceforge.net will host
your "project" and give you an SVN of your own so that
YOU have commit privileges (you do need to consider
licensing issues though). Then when you'come up with
something spectacular that you wnat all the OFBizers
to see, submit a patch for the ofbiz.org website
telling everybody where they can download the SVN,
post something to the maillists, write up a how to for
the wiki, etc. Don't worry about making a patch for
it (unless you really want to), if it can benefit the
OFBiz project, the committers know OFBiz well enough
to incorporate your code without it. And they'll be
able to download a differences app and see what it
does instead of having to double check a patch to see
if it's going to break their environment.
Try doing your OFBiz developing this way and I
gaurantee you'll get a lot more done, a lot quicker
and more people can take advantage of it a lot sooner.
--- "David E. Jones" <
[hidden email]> wrote:
>
>
> Adrian Crum wrote:
> > As far as getting Jira issues committed is
> concerned - regardless of what David
> > says, it boils down to whether or not your patch
> will benefit the few who have
> > commit priviledges. There has been some really
> good work submitted to Jira, but
> > it just sits there. The voting thing was suggested
> before, but I haven't seen
> > where that really affects anything. One thing that
> puzzles me is why Si Chen can
> > ask to have his Jira issues committed and it gets
> done without question (and
> > without voting). What makes his submissions so
> special?
> >
> > The best thing to do is submit the patch to Jira
> and then don't hold your
> > breath. Just apply the patch to your own copy
> whenever you update. One day a
> > committer will find your enhancement useful and
> will integrate it into the project.
>
> Nice attitude Adrian. If this were true OFBiz would
> simply not exist at all.
>
> Why do I pay attention to Si's requests and not as
> much to others (ie sometimes prioritizing his
> higher)? Because Si is actively involved in the
> project and contributes a great deal. He also stays
> actively involved with Jira and what is happening in
> the project by compiling his list every week and
> regularly reviewing the Jira issues and helping with
> many of them, and identifying other important ones.
>
> If you're not happy with the work done for free in
> OFBiz then why don't you do something about it. Be
> creative.
>
> -David
>
>
> _______________________________________________
> Dev mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/dev>
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev