You should not have taken offense at my tone (not sure how you read that
though!)
Let's be frank, if a bug has been sitting out there for a number of
years untouched, then what response did you expect?
Unlike other engines, we are not going to pretend something is more than
it is.
My point with the Java code ... if you are versed with coding in
CFSCRIPT, then do not assume you can't look at Java code and make some
adjustments. The only person holding you back, is you. Looking at a
code base and making small changes can be a lot easier than you think it
is. Do not make assumptions on "complexities of java code and
implementations."
We released the code base as GPL so it was available to the community to
contribute changes. We get a number of patches that makes it all
great. Supporting coldbox is not a priority for us, because we long
ago gave up trying to support the other engines, as there is no official
standard and I do not believe it is worth it.
Now if ColdBox is that important to you, we are happy to enter into a
consultancy agreement and we'll pay someone to do it. This has been
done before.
There is always options Sana.
On 03/03/2015 20:09, Sana wrote:
Hi Alan,
I am sorry to hear that you would not fix it and to be honest it was
not nice response from your end.
As most of CF developers can't fix cf-engine bugs because of
complexities of java code and implementations.
I thought some parts will be fixed at your end and I will try to
adjust some parts of coldbox code-base to make sure it runs on OPENBD.
Anyway its your choice and I leave it at you...
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
