On Tue, Jan 27, 2004 at 01:34:40PM -0600, McClain Looney wrote:
> > In the end, when you want to support javahl, you must either supply a
> > working DLL for all platforms on which you can have eclipse (that's seven,
> > when I last looked: Windows, Linux, Solaris, QNX, AIX, HP-UX and MacOSX)
> > *or* you must state that subclipse is Windows only. As it is currently,
> > it's very irritating because you say that you support Linux but in fact,
> > you don't (The current state of the Linux version basically says "Windows
> > only" despite your efforts).
> so i take it you are volunteering your time to maintain the *nix versions,
> either the cli or javahl (your choice)? Alternately, you can go ahead and
> implement your own pure java client and save us a bunch of hassles.
Choice? What choice? I'm interested in maintaining the Unix versions but I
only have access to Linux, so javahl is not an option for me. The cli version
will work on any *nix without me having access to it, that's why I want
the cli version.
> While I completely agree both the swig and javahl bindings approach
> abandonware status, carping about the state either is completely useless, and
> in fact, pisses off the very people who are laying this golden egg for you
> (we aren't even responsible for javahl anyway).
My point is: When we all agree that javahl is not a viable option right now,
then why putting any effort in it?
Or more precisely: Why is javahl the *default* when it only works on Windows
and even there only with an effort?
> I regularly use the linux and osX version. It works well enough for me despite
> some hiccups.
Well, a short howto would help. I'm on this list for only three days and
already, two people have asked how to get subclipse to work in linux.
I still have to see an answer to their questions.
> if it doesn't work well enough for you, fix it.
I think I made it clear by my actions that I'm willing to help to fix
the bugs which subclipse has but insisting on an API which I cannot
run nor test makes this very hard for me: Since most developers of
subclipse seem to prefer javahl, the bugs in there are given more priority
while cli would work better for everyone. Additional bonus: more people
could help to improve subclipse.
The username/password bug is an excellent example: It's probably a cli-only
bug. I've posted it here several times with a plea for help (I just need the
name of the classes where the password is read in in the GUI so I could try
to track this one down) but nobody cared.
Right now, the sources for subclipse are 35 kloc. My guess is that if someone
here answered my questions, it would take me a few minutes to fix this one.
If I'm on my own, I would spend a few hours to find the spot where the
password is read from the user. That time is wasted and I (same as you)
don't have much time to waste.
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
Received on Wed Jan 28 08:13:18 2004