#805 JavascriptSideKick 1.0.0

[Matthieu Casanova]

{{{ JavascriptSideKick 1.0.0
Source: https://jedit.svn.sourceforge.net/svnroot/jedit/plugins/JavascriptSideKick/tags/JavascriptSideKick-1.0.0
Announcement: Initial release
Requires Java 1.6
Requires jEdit 04.04.99.00
Required plugins:
ErrorList 1.9 (errorlist.ErrorListPlugin)
RhinoPlugin 1.7R3 (rhino.RhinoPlugin)
SideKick 1.2 (sidekick.SideKickPlugin)

Short Description: JavascriptSideKick is a parser that will show you errors in your javascript code

Long Description: <p>JavascriptSideKick is a javascript parser that will highlight syntax errors of your javascript files. It will delegate
the source tree to the javascript parser included in XML plugin if this one is available</p>

}}}

[Matthieu Casanova]

I don't agree, Sidekick is a parser launcher, that launch parsers when typing, or saving, or loading, it also call code completion, the Sidekick tree is only one of the functionnality of Sidekick plugin.
Personnally I never use the Sidekick tree for any file type (and I don't use structure view in IntelliJ IDEA too.

Doing some actions for this is a problem because I think people want to have this called automatically when typing, not when calling an action with a shortcut (and we don't have shortcuts that are mode dependent).
My plugins do not depends on JavascriptSidekick plugin because this plugin do not exist anymore and will never come back (and it also do not depends on XML plugin, my plugin can work even if XML plugin is not installed).
I could rename it but does it really cause problems with plugin manager ?

[Matthieu Casanova]

And I would add that I could create a structure tree, but it would only work when there is no syntax error that why I fould that it was better to use the older javascript parser that use regexps and do not fail on parse error