||Tue, 25 November 2008 22:24
Registered: July 2009
I have big request somebody :$
I like eclipse because the jdt project is best of best java editor , and i
like eclipse perspectives.
much better. But i like eclipse wtp jpa support, it is a very good idea,
and i use every day.
Thank you very much :)
||Wed, 26 November 2008 10:19
Originally posted by: david_williams.linux.vnet.ibm.com|
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
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.
||Wed, 26 November 2008 10:52
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.
is... 90% of times?). The new validation routines do not support, for
- dereferencing HTML form elements from scripts, i.e.:
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
<input name="testInput" type="text">
- JSP tags inside <script> tags
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.
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
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...
||Mon, 01 December 2008 04:03
Originally posted by: knb.gfz-potsdam.de|
made tremendous improvements compared to previous versions or attempts
(although, the ATF toolset was also very good already). It is very easy
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.
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..
||Fri, 05 December 2008 12:51
| Rich Garrison
Registered: July 2009
I am also seeking JQuery support in JSDT.
If i was to consider investigating what it would take to make the JQuery
libraries available options as runtime libraries, would this be a complex
Would you be ameniable to providing some pointers into the source (or hte
approach) for how the DOJO libraries were integrated so that i could
perhaps mimic that for JQuery? Or is that such an absurdly complex
question or task to even consider?...
Powered by FUDForum
. Page generated in 0.02154 seconds