- This topic has 5 replies, 3 voices, and was last updated 21 years, 1 month ago by
Scott Anderson.
-
AuthorPosts
-
kutterMemberI just got it all running, and I would like to post the things
which could have been show-stoppers for less technical people.
Thus I have the following 3 feature requests.I fear they will not be implemented, because they can be done
within 1 hour, and thus you may consider them as too trivial.
From my own tool development experience, I can however
guarantee you, that the speed your community grows depends
more from the following three points, than from any more technical
point.Here they are:
– If I startup MyEclipse, display a welcome page with
– link to the existing Tutorial
– link to the existing documentation– In the tutorial, add a *little* paragraph about how to
1- start the server
2- deploy the generated HelloWorld
3- open a browser displaying the HelloWorld,
e.g. give the URL where you can see it,
for instance http://localhost:8080/HelloWorld/helloWorld.jspPossibly move the material about completion to a different
place.– add further a little paragraph telling what may be the problems with
running Jboss:– point the Java thing to the sdk home, not the jre home
– stop other servers running on localhost:8080, such as Zope
(users who used Zope before may be an interesting client group
for you, most of them have some Zope server running while
trying your thing out)
– having Jboss installed in the “Program Files” directory or another
directory with spaces
– not the newest JavaBest, Philipp
Scott AndersonParticipantPhilipp,
Thank you for taking the time to post this. While we try to put ourselves into the positions of “first time users” it’s really impossible to do since we all have deep experience in both J2EE development and our product. As a result, we’re often “too close” to the issue to give it some objective improvement suggestions. This post really helps us out and I’ve entered the entire thing as a high priority enhancement request into our internal tracking system.
I fear they will not be implemented, because they can be done
within 1 hour, and thus you may consider them as too trivial.Have no fear. We look for anything to improve the user experience. The fact it can be implemented quickly is a bonus, not a deterrant.
– If I startup MyEclipse, display a welcome page with
– link to the existing Tutorial
– link to the existing documentationGreat ideas.
– In the tutorial, add a *little* paragraph about how to…
Our concentration between EA2 and GA is documentation. An expanded tutorial has already been written to address these points. Once the new doc set is available, if you could review it and offer improvement suggestions it would be great.
point the Java thing to the sdk home, not the jre home
This one is both in the doc and on the JDK configuration page itself. I don’t know what else we can do on it to make people aware of this. By the way, this is an app server requirement, not one of ours.
– having Jboss installed in the “Program Files” directory or another
directory with spacesWhile this was a problem with the EASIE plugins in a standalone fashion and with EA1, this problem was specifically addressed in EA2. If you replicated a problem with the EA2 release, please post the details to the ‘Bugs’ forum. I’m pretty sure this one is a non-issue now.
– not the newest Java
Can you elaborate on this one?
Thanks,
–Scott
MyEclipse Support
kutterMemberThanks for your quick response. I think the two
issues about spaces and not-newest Java have been done by me only because someone on the net wrote it, and I thought I was fixing it, when I changed it.I will be very happy to comment new documentation sections once you have them ready.
Best, Philipp
Scott AndersonParticipantI think the two issues about spaces and not-newest Java have been done by me only because someone on the net wrote it, and I thought I was fixing it, when I changed it.
Well, not using the newest version of Java is always a good idea, since often the betas have compatability problems and bugs, just like any beta software. The latest 1.4.1 release version works well. The “enspaced paths” thing really is working at this point, though. 🙂
If you run into any other issues please be sure to post them.
–Scott
MyEclipse Support
Tom ColeParticipantMy biggest gripes:
1. Finish the help files. They are missing a lot of information.
2. Add better tag support. You should be able to have a Tag option from the add/new wizard and it should create/update a .tld file like the servlets do the web.xml.
Scott AndersonParticipantGood news, the help files are much more extensive in the GA release and we’ll be continuing to add content to them going forward. In fact, we’ve broken out our help feature completely separately so that you’ll be able to download new help versions using Eclipse’s update manager.
Add better tag support.
While this is the second time this has been requested, and I certainly understand what you want, I have to ask a question. Why are you guys writing tags at all? There are a ton of very complete tag libraries that are available for use. Surely you’re not putting your application logic into tags, are you?
–Scott
MyEclipse Support -
AuthorPosts