[langevin]

I was about to post another bug report on the nearly useless XML editor in MyEclipse 2.7rc1. When checking my log file for info to post, I noticed a few references to org.xmen in the stack dumps. Suddenly, I realized why all of the problems I was having seemed so familiar!

I specifically downloaded MyEclipse to get away from all the stupid bugs in the Lomboz JSP editor and the Xmen editor that were destroying my productivity. (How many times can you take losing your work as your PC locks up when you type an opening quote?)

You’ve done a great job with the JSP editor probably because it’s net new work. I know that you’re pushing to get more features out the door quickly, but you should think twice before you attach your name to the Xmen editor. My experience today with it was so bad that I’m going to disable it and go back to the featureless but stable Extenion Point editor.

[support-michael]

We understand your concern and we would not couple ourselves to XMen if we did not believe that achieving closure on some of the buggy features could not be resolved in short order. We resolved a number of bugs before the RC1 release and have more recently addressed additional issues that will be part of the upcoming RC2.

Regards,

Michael
MyEclipse Support

[Scott Anderson]

I’ll also add that the xmen codebase we have now has been substantially modified and enhanced over the original version. As Michael said, we fixed a slew of problems before RC1, but apparently missed a couple that we’ve now addressed for RC2. It’s truly unfortunate that you had a bad experience with this, but I hope you can look past the point that we began with the XMen codebase to create our editor as we resolve the additional issues and move forward.

–Scott
MyEclipse Support

[langevin]

Scott/Michael,

Thanks for the responses. I don’t want to beat this to death, but Genuitec should not have released the XML editor in its current state — let’s face it, the thing is basically unusable for anything beyond browsing/validating XML files.

A couple of the bugs that I hit have been posted on the Xmen comments section at eclipse-plugins.info for months and months, and the rest were so fundamental (“replace all” is not an advanced function!) that it makes me wonder if anyone actually tested the editor in even a cursory way. You should have known that it wasn’t ready for prime time!

(Before giving up, I also noticed that the screen jumps around when you start inserting new text, and that using the tab key to indent a selected block of text behaves erratically. These are referenced at eclipse-plugins.info also, but please add these to your bug list as well.)

I’m a software developer too, so I understand that rushing for a deadline means you make the odd mistake — but these things should be in the tertiary aspects of the software, not the primary functions. Your credibility is at stake otherwise. I’m happy enough with the JSP editor that I’ll give the XML editor a second chance, so I’ll look again when the next MyEclipse release comes out.

Andre

[Riyad Kalla]

Andre,
I can definately feel your frustration; my first experiences with XMen were so hair-rippingly wonderful that don’t even need to get into it 😉

It is unfortunate that those bugs snuck in (all of the 3 you have mentioned have been reported and verified by the ME team). I think what we can (should) do now is ask that 2.7 final doesn’t come out until these easily discovered bugs are fixed.

Also if you can hang in there and continue to help give good feedback and suggestions it will really help ME become quite a competative product.

Best,
Riyad

[Scott Anderson]

Andre,

We are working on improving the XML editor and we thank you for your feedback and agree that the quality must remain very high. I have a quesiton about your last post:

(“replace all” is not an advanced function!)

Can you tell us exactly what problem you had with Replace All? Can you provide a reproducible test case? We don’t currently have a bug open for anything around this functionality so if there is an issue we’d like to pin it down.

–Scott
MyEclipse Support

[Riyad Kalla]

I got the impression he was just commenting on its placement, not necessarily a bug.

[Scott Anderson]

It’s placement? In what way?

–Scott
MyEclipse Support

[Riyad Kalla]

I’m sorry, I don’t know for certain. Andre can you elaborate on what you were referring to with the “Replace All” functoinality? (I’m using 2.6.4 right now so I can’t quickly open up the editor and see what he means)

[Author]

Posts