I also have a really big patched rhino that we use for our product
For example we need a lot more classes public or better overridable and
extendable classes (javamembers and so on)
I am also a committer of the Eclipse DLTK (Dynamich Languages ToolKit)
project where i do most of the javascript stuff
also there we needed for debugging in rhino to patch rhino (like
watchpoints)
and also code completion i needed to open up api to get the stuff what rhino
resolved out of rhino (MemberBox stuff and so on)
Last thing i patched was the XML Object toString() thing. I got a big null
pointer when debugging xml objects in rhino
because the xml objects where not complete constructed the right way for the
debugger.
What i could do is to make for many things patches but that will take me
quite some time :(
This are all patches on 1.6R7
johan
On Fri, Oct 3, 2008 at 4:15 PM, Attila Szegedi <[EMAIL PROTECTED]> wrote:
> On Oct 3, 2008, at 3:30 AM, Hannes Wallnoefer wrote:
>
> > I guess I'll have to come out as the one who was afraid of the beast
> > two years ago when Attila made me that offer. While I'm still very
> > busy and partially scared, I feel more confident I now about finding
> > the time and making decisions, especially since I work with Rhino as
> > part of my day job.
>
> That's okay. Most of us work like that. I was really contributing to
> Rhino when I was creating a system that used it as part of my day job
> too. After a while, it settled into a state where it was Good Enough
> for us -- we run half a million (maybe more) instances of big,
> nontrivial scripts per day in our systems for the last 5 years or so,
> and we didn't hit any bugs for long, long time. I think we're still on
> 1.6.x ("x" might mean a private build I did sometime from CVS HEAD
> still back in the day). So I don't have much of a business case to
> hack Rhino at the moment (not that I wouldn't love to, it's just that
> things that *now* constitute my business case are entirely unrelated
> and suck away all my time).
>
> As for being scared, that's again okay. I was too. I mean, anyone
> faced with the prospect of modifying a system of nontrivial complexity
> - one that he didn't create in the first place - might be a bit scared.
> I take it as a welcome sign that you, in fact, know what is it you
> don't know; a sign of a wise person.
>
> But you know, we have CVS. Nothing can be irretrievably broken.
>
> > So I'd be willing to become a committer if current committers want me.
> > Should I proceed as described in <http://www.mozilla.org/hacking/
> > committer/> or wait for some kind of agreement?
>
> I'm absolutely happy to hear that -- saw your Bugzilla issue, and
> already vouched for you.
>
> > Hannes
>
> Attila.
>
> >
> >
> >> Attila.
> >>
> >> On Oct 2, 2008, at 9:22 AM, Marc Guillemot wrote:
> >>
> >>> Hi,
> >>
> >>> what are the goals of the Rhino project? Are committers happy with
> >>> the
> >>> current state?
> >>
> >>> Personally I'm not happy at all with this lack of activity (1) as we
> >>> (HtmlUnit project) need an healthy Rhino.
> >>
> >>> I understand that current committers may not always have the time /
> >>> interest and this is not a critic to their engagement here but I
> >>> think
> >>> that more hands would help the project to progress faster!
> >>
> >>> So, please make the project more active, invite new committers (2),
> >>> improve quality control to facilitate safe changes! From my
> >>> experience
> >>> in HtmlUnit, I can say that new committers *really* help to bring
> >>> the
> >>> project further.
> >>
> >>> Cheers,
> >>> Marc.
> >>> --
> >>> Web:http://www.efficient-webtesting.com
> >>> Blog:http://mguillem.wordpress.com
> >>
> >>> (1) sorry if I don't see everything what you do. My appreciation is
> >>> only
> >>> base on what I can see in the mailing list and with regular update
> >>> from CVS
> >>> (2) this is not a request for myself. If you estimate that I can
> >>> help
> >>> based on the different patches that I've submitted, why not but what
> >>> really matters for me is that the project is active.
>
>
>
>
>
> _______________________________________________
> dev-tech-js-engine-rhino mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
>
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
