A plea for a new build

After the Nth time I get that JavaScript editor exception, I am asking
humbly - give me a new fixed build...

Kudos for JavaScript plug-in, it's a step in the right direction!

Amnon

9 comments
Comment actions Permalink

That's nothing, you can just delete the plugin and you'll be fine.

Pity me though, where on OSX, 4 out of every 5 times IDEA is hung on startup due to them cleverly managing to display two modal dialogs, neither of which can be dismissed. This of course has been going on since the very first eap.

0
Comment actions Permalink

That's nothing, you can just delete the plugin and you'll be fine.

Not quite. Some of us (and we are many), really must program javascript too.
Deleting the plug-in, brings us in the stone age again - reagrding javascript.
I tried to fix a little the javascript plug-in, since the sources are delivered
for it too, but I really don't understand how it really works(or it is supposed
to work), and I can't make my own compile for it.
I understood how the javascript plug-in for JEdit, and Eclipse works, and
I was able to change them. For IDEA's plug-in: no chance :(.

I would really appreciate if JetBrains would document/explain *for the first
time* how the plug-in really works. I think the plug-in development in Idea
is really odd: no real explanations/documentation about it - for Eclipse
there are entire books about it :).
I have a lot of ideas for improvements and plug-ins, but I just can't make
them for IDEA(maybe I'm just too stupid, or just the documentation is missing).
I do not want to make them for Eclipse :).

Thanks in advance,

Ahmed.

0
Comment actions Permalink

Hani Suleiman wrote:

That's nothing, you can just delete the plugin and you'll be fine.

But I'm now spoiled with the new features... I don't want to go back to
just a text editor for JavaScript ;)


Pity me though, where on OSX, 4 out of every 5 times IDEA is hung on startup due to them cleverly managing to display two modal dialogs, neither of which can be dismissed. This of course has been going on since the very first eap.

Well, I guess an EAP is an EAP and we shouldn't wine (but I just had to
ask...).

I'm not complaining, I enjoy being a part of the EAP process...

Amnon

0
Comment actions Permalink

Work in Win2K, develop pure Java modules, don't look for JSP, EJB, JS, or even XML support, and EAP is pure heaven.

(Although as a plugin developer, the memoory leaks are becoming a problem).

0
Comment actions Permalink

Hello Dave,

Well, the debugger is not in too great a shape either (at least when using
an IBM jdk), so keeping a Pallada installation around isn't a bad idea.

Andrei

Work in Win2K, develop pure Java modules, don't look for JSP, EJB, JS,
or even XML support, and EAP is pure heaven.

(Although as a plugin developer, the memoory leaks are becoming a
problem).




0
Comment actions Permalink

In article <18390983.1108873167501.JavaMail.itn@is.intellij.net>,
Dave Griffith <dave.griffith@cnn.com> wrote:

Work in Win2K, develop pure Java modules, don't look for JSP, EJB, JS, or
even XML support, and EAP is pure heaven.


Actually JSP is not too bad, very usable, so is html and css.

R

0
Comment actions Permalink

Dave,
I've just fixed a severe memory leak in inspections. Please report if this
is still a problem with the new > 3227 build, OK?

-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

Work in Win2K, develop pure Java modules, don't look for JSP, EJB, JS,
or even XML support, and EAP is pure heaven.

(Although as a plugin developer, the memoory leaks are becoming a
problem).




0
Comment actions Permalink

3227?? OK, I'll wait patiently :)

0

Please sign in to leave a comment.