- This topic has 5 replies, 4 voices, and was last updated 19 years, 2 months ago by
.
-
Posts
-
I actually like MyEclipse pretty much. It allows me to use my favourite IDE for web app development.
But I must admit that MyEclipse has one particular weak point about which I’ll complain here and I sometimes have a feeling that MyEclipse tries to add as many features as possible and not be focus on the real vital features.In my opinion the JSP Editor should be the bread and butter feature for a web app IDE. It’s the one feature I use 99,5% of the time working with MyEclipse (as opposed to working with the Java source editors).
The JSP editor of MyEclipse has undergone several changes and at least one rewrite/replacement but it still has a lot of bugs:
* Syntax coloring can become completely screwed up
* Editing can slow down to a crawl
* Syntax checking works too slow and is (too) often wrong
* Sometimes code completion to add an export doesn’t work (it adds the fully qualified name in quotes instead of adding the import)And there’s one features that would make it much more useable:
* Search for references to allow use of refactoring. Currently it’s practially impossible to use refactoring and JSP scriptlets at the same time.I’d like to add that my experiences with myeclipse come from two applications. One of them is a small app using JSTL almost no scriptlets and no <%@includes. MyEclipse works a lot better for this application than for the second application which is a real big app with JSPs with more than 800 (!) lines and lot of <@%includes, scriptlets and even methods in JSP code. To clean up this code (or allow some simple changes) a real solid JSP editor would be absolutely necessary.
I can only say amen to this post!
Exactly my own thoughts and comments. The JSP editor really needs some -heavy- bug fixing and refactoring support.
Guys we can hear the frustration in your post and I am going to fire this off and start a dialog with management to see if we can fast track some things we had planned that should help. I would encourage you to speak up (as you have done now and in the past) when things are not the way they should be, when we seem something causing problems for our users and it’s loud and clear we really jump on it.
Additionally if you do purchase MyEclipse and are not getting the support you need from our tool, we offer a 100% money back garuntee. As much as we don’t want to loose you, we also don’t want you guys feeling trapped, that’s not the game we play here. We need to earn your money, and good software is how we plan to do it.
+1 on this MyEclipse guys!
Did you change the JSP editor recently, like some time in the last 18 months or so?
It doesn’t seem as friendly as the one I used when I first subscribed to MyEclipse.
There are syntax highlighting bugs and code-complete irritations that really shouldn’t be present in the heart of a J2EE web development IDE. However, the preview screen is pretty useful, but I don’t use it very often now that I’m reasonably proficient in HTML/JSP.
It doesn’t seem as friendly as the one I used when I first subscribed to MyEclipse.
It changed completely in the 3.8.0 release, that was the first release we started building on WTP.
There are syntax highlighting bugs and code-complete irritations that really shouldn’t be present in the heart of a J2EE web development IDE. However, the preview screen is pretty useful, but I don’t use it very often now that I’m reasonably proficient in HTML/JSP.
If you had to list your 3 top annoyances, what would they be? The more detail the better, also reproducable test cases are hugely important.
If you had to list your 3 top annoyances, what would they be?
Limiting me to three, huh? Okay…
(1) Code-assist is pretty poor. It should be as good as the Eclipse Java code editor, with pop-up JavaDocs and all (what use is a tooltip that regurgitates a DTD?). Auto-completing X/HTML elements etc. I spend half my life whacking CTRL-SPACE and those IDEs which dumbly stare back at me really get my goat.
(2) Auto-format (i.e. auto-layout) of JSP code is terrible. It’s a bug, surely?
(3) Syntax highlighting bug should be fixed ASAP. That’s the one where the highlighting goes askew and you get rainbow coloured JSP.
Just use the Netbeans 5.0 JSP editor for half a day and you’ll see what yours should be like. Actually, yours should be better shouldn’t it? Plus you’ve also got JSP preview.
