|
| Re: Javascript editor pls do it something somebody :$ [message #224429 is a reply to message #224376] |
Wed, 26 November 2008 15:19   |
Eclipse User |
|
|
|
Originally posted by: david_williams.linux.vnet.ibm.com
Attila wrote:
>
> So guys please develop javascript support, because its not useful.
>
Which version of eclipse webtools are you using? I'm surprised anyone
would say it's not useful, after the improvements made
in WTP 3.0.
And, just so you know, in all kindness and respect, requests such as
this are too general and too vague to be very helpful.
It is a bit like saying "will 3 or 4 of you guys that read this list all
band together for the next 6 months or year and make my life better" :)
If you are not able yourself to to provide patches or improvements
directly to the JavaScript support, it would be more helpful to open
bugs and feature requests with detailed descriptions of features you
find most important, with a verbal description of relative importance.
This would give some specific idea of an "actionable" item that someone
from the community might want to tackle.
|
|
|
| Re: Javascript editor pls do it something somebody :$ [message #224461 is a reply to message #224429] |
Wed, 26 November 2008 15:52 |
| Eclipse User |
|
|
|
Originally posted by: mauro.molinari.cardinis.com
David Williams ha scritto:
> Which version of eclipse webtools are you using? I'm surprised anyone
> would say it's not useful, after the improvements made
> in WTP 3.0.
IMHO the problem is that the new JavaScript support becomes more
problematic when you are working with JavaScript inside HTML/JSPs (that
is... 90% of times?). The new validation routines do not support, for
instance:
- dereferencing HTML form elements from scripts, i.e.:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
<script type="text/javascript">
function c()
{
document.testForm.testInput.focus();
}
</script>
</head>
<body>
<form name="testForm">
<input name="testInput" type="text">
</form>
</body>
</html>
See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=240134
- JSP tags inside <script> tags
See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=119322
The new JSDT tools seem smarter to recognize problems, but because of
these bugs the result is that my JSPs are now full of red marks because
of false errors.
I also find the new JavaScript validator quite slow at analyzing
HTMLs/JSPs...
Because of these problems, in general I find myself to hit the problem I
exposed some time ago here in the newsgroup about Webtools source
editing tools (especially the JSP editor): in real-world examples of web
development, the current JavaScript and JSP editing tools provided by
WTP are not adeguate, unfortunately.
Yes, I know you need community help and I also know that criticisms have
to be constructive and that filing new bug reports and keeping on them
is the way to get things improved... however it's quite sad for me to
see that I have voted for more than 20 bugs in WTP that I consider
critical and no progress has been done even for a couple of years,
although I constantly check on them :-(
Please David, don't blame on me, if I say this it's because I love
Eclipse and I would like it to be better and better and I try to do my
best to support it... However in general I'm feeling like there's less
interest on improving it (the platform and some of its major plugins)
during the latest months... after all, the Visual Editor Project is
dead, the TPTP profiling tools seem to have difficulty on providing a
fruitful user experience (while they already are at version 4.5) and WTP
web development tools have been suffering from certain critical bugs for
years now... :-(
Maybe I just need to be said that the Eclipse ecosystem is still in good
health, although my worries...
Sorry for the outlet...
Mauro.
|
|
|
|
|
| Re: Javascript editor pls do it something somebody :$ [message #224574 is a reply to message #224461] |
Mon, 01 December 2008 09:03 |
| Eclipse User |
|
|
|
Originally posted by: knb.gfz-potsdam.de
I've just tried the new Javascript editor and I must say that it has
made tremendous improvements compared to previous versions or attempts
(although, the ATF toolset was also very good already). It is very easy
to use.
I agree with Mauro in the following: What is most annoying now are the
false errors that the editor creates. Some crucial objects cannot be
resolved although the library / .js file that contains them *is*
referenced in the build path dialog. The inability to resolve the object
for statement completion might be caused by the fact that the
references (to that object in my code) are nested in some way (but not
very deeply at all).
In other false errors, in places the Image() object can't be resolved,
a call to parent. can't be resolved etc. This is strange because these
are JS built-in objects.
I have
eclipse.buildId=M20080911-1700
eclipse.commands=-os
linux
-ws
gtk
-arch
x86_64
org.eclipse.wst.jsdt.core (1.0.1.v200807302212) "JavaScript Development
Tools Core" [Active]
I find it also impossible to upgrade the webtools. There is always some
strange dependency missing. I have spent Hours already finding this..
Knut
|
|
|
|
Powered by
FUDForum. Page generated in 0.02970 seconds
] 
Search
Help
Register
Login
Home
