[Announcement] Plugin Manager v 0.1

http://www.intellij.org/twiki/bin/view/Main/PluginManager

ABOUT
-


This plugin provides an interface to view all installed and available
plugins and to download available plugins.

Once you download and install the plugin, there will be a "Plugins" section
in IDE Settings. From there you can view some details about plugins you
currently have installed as well as details about (nearly) all IDEA plugins.
Downloaded plugins are placed in a "downloadedPlugins" directory under
IDEA's home directory (see To Do item below about making this configurable).

The Plugin Manager retrieves the list of available plugins from an XML file
(idea-plugin-registry.xml) stored at the above URL. I encourage plugin
developers to update this XML file when they create or update their plugins.
I've pre-loaded the registry with info about nearly all the existing IDEA
plugins, but had a few problems with some:

  • None of Duane Fields' plugins are included since I had

trouble accessing his site.

  • The ViPlugin has the wrong name and description (maybe

version, too) in its plugin.xml file.

  • LogMonitor plugin has the wrong name, vendor, version,

and description in its plugin.xml file.

  • Plugins that are stored on SourceForge don't have a

download URL in the registry, so users are prompted to
just go to the plugin's web site for download info.

NOTE: I didn't actually download every single plugin and gather info from
each plugin's plugin.xml file (I only did a few, actually, e.g. when I
couldn't find the latest version number on the Wiki). Instead, I got almost
all the info from the Wiki. So, there are likely to be mistakes/omissions.
Sorry. So, if other plugin developers think this plugin is a good idea, I'd
appreciate help in keeping the plugin registry XML file up to date (sorry,
but I don't have time to do it all myself!). There's a (very simple) DTD
for the registry at the above URL, too--PLEASE make sure you validate the
registry file before you upload an update! Thanks! :D

KNOWN ISSUES
-


  • Didn't actually download every plugin and get the vendor/description/etc

from the plugin.xml. Just gathered the info from the Wiki. For the version
comparison (when implemented) to work correctly, the version in the registry
will have to match what's in your plugin.xml, so I'd appreciate any help
from plugin authors to make sure they're correct (as well as all other
info).

  • Needs refactoring/cleanup/better error handling, etc.

  • I don't know how to get text to flow nicely in Swing widgets, so I'm

currently dumping the plugin description into a JEditorPane with text/html
content type (so that extra whitespace is ignored). I think it looks kinda
weird that the description is in a white box, but the rest of the details
aren't. Suggestions on better ways to do this are welcomed and appreciated.
Thanks!

  • Would the Options menu be a more appropriate place for the Plugin Manager?

(perhaps as simply a "Plugins" menu item to go along with Live Templates,
Keymaps, etc.) I'm undecided on this, partially because I'm still not
entirely sure what the criteria are for placing something in IDE Settings
vs. the Options menu (e.g. to me, Code Styles and Color Schemes could
arguably be placed under the Options menu too). Thoughts?

  • Kinda weird that both Installed Plugins and Available Plugins lists can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?

  • Ugly interface


TO DO
-


  • Create an icon for the configurable in IDE Settings

  • Show icons for new and updated plugins in the list of available plugins

(i.e. make use of the last modified tag in the plugin registry)

  • Provide a way to open browser and go to a plugin's docUrl (right now the

docUrl is just appended to the description). But how on earth do you do
that in a cross-platform way? I've seen the JavaWorld article, but is that
the best way? Is there any way to get the browser path registered in IDEA's
IDE Settings?

  • Show min/max targeted IDEA versions in Plugin Detail area

  • Better interface for downloading: better error handling, progress bar,

change mouse pointer, etc.

  • Allow user to choose where downloaded plugins will be placed

  • Detect whether file(s) to be downloaded already exist(s).

  • Allow for multiple bin URLs and multiple bin URL groups. Multiple URLs

are useful for when the plugin depends on other libs. Multiple groups are
useful for, say, providing both .zip and .tar.gz versions.

  • Show some sort of icon for installed plugins when a new version is

available (will require parsing and comparison of version numbers)

  • Provide some kind of option to download the source as well (e.g. if made

available in a separate zip file).

  • Consider extending various elements in the DTD. E.g., allow multiple

vendors, provide support for vendor name, email, URL, etc.

  • Maybe provide an option to automatically update plugin list (daily?) and

provide notification when new versions are available.

  • Maybe have a "Developer Mode" checkbox that would provide an extra tab to

add/update plugins in the idea-plugin-registry.xml file? I don't know how
tricky it'd be to do a form post to the Wiki to update the
idea-plugin-registry.xml file without going through the actual Wiki
interface. At the very least, provide a simple Swing app (or maybe just
another plugin) to help developers view how their plugin(s) will be rendered
in the Plugin Manager's Plugin Detail area (so they can add HTML markup to
descriptions, etc.).


20 comments
Comment actions Permalink

Duane's plugins are included in the registry now. Sorry about that,
Duane--i was being stupid.

chris

"Chris Bartley" <spam@feynman.org> wrote in message
news:aqm8m8$g1l$1@is.intellij.net...

http://www.intellij.org/twiki/bin/view/Main/PluginManager

>

>

  • * None of Duane Fields' plugins are included since I had

trouble accessing his site.

>

>


0
Comment actions Permalink


You're da man! Great plugin!

There is one issue with my XPathView plugin. I included a simple
DTD for my plugin.xml in the .jar file (I made a copy&paste error
while writing the plugin.xml and decided that with a DTD this would
not happen again ;-).
Unfourtunately, the XML-parser tries to validate the file when there
is a doctype declaration in it and it expects the file to be in
/bin.
I would suggest turning off validation in your SAXBuilder, or, even
better, do not parse an InputStream but a URL instead. You can
construct a jar: URL like jar:file:C:/plugin.jar!/META-INF/plugin.xml.
This way the xml parser can deal with relative references.

Sascha

>

ABOUT
-----
This plugin provides an interface to view all installed and available
plugins and to download available plugins.

>

Once you download and install the plugin, there will be a "Plugins" section
in IDE Settings. From there you can view some details about plugins you
currently have installed as well as details about (nearly) all IDEA plugins.
Downloaded plugins are placed in a "downloadedPlugins" directory under
IDEA's home directory (see To Do item below about making this configurable).

>

The Plugin Manager retrieves the list of available plugins from an XML file
(idea-plugin-registry.xml) stored at the above URL. I encourage plugin
developers to update this XML file when they create or update their plugins.
I've pre-loaded the registry with info about nearly all the existing IDEA
plugins, but had a few problems with some:

>

  • * None of Duane Fields' plugins are included since I had

trouble accessing his site.

>

  • * The ViPlugin has the wrong name and description (maybe

version, too) in its plugin.xml file.

>

  • * LogMonitor plugin has the wrong name, vendor, version,

and description in its plugin.xml file.

>

  • * Plugins that are stored on SourceForge don't have a

download URL in the registry, so users are prompted to
just go to the plugin's web site for download info.

>

NOTE: I didn't actually download every single plugin and gather info from
each plugin's plugin.xml file (I only did a few, actually, e.g. when I
couldn't find the latest version number on the Wiki). Instead, I got almost
all the info from the Wiki. So, there are likely to be mistakes/omissions.
Sorry. So, if other plugin developers think this plugin is a good idea, I'd
appreciate help in keeping the plugin registry XML file up to date (sorry,
but I don't have time to do it all myself!). There's a (very simple) DTD
for the registry at the above URL, too--PLEASE make sure you validate the
registry file before you upload an update! Thanks! :D

>

KNOWN ISSUES
------------

>

  • Didn't actually download every plugin and get the vendor/description/etc

from the plugin.xml. Just gathered the info from the Wiki. For the version
comparison (when implemented) to work correctly, the version in the registry
will have to match what's in your plugin.xml, so I'd appreciate any help
from plugin authors to make sure they're correct (as well as all other
info).

>

  • Needs refactoring/cleanup/better error handling, etc.

>

  • I don't know how to get text to flow nicely in Swing widgets, so I'm

currently dumping the plugin description into a JEditorPane with text/html
content type (so that extra whitespace is ignored). I think it looks kinda
weird that the description is in a white box, but the rest of the details
aren't. Suggestions on better ways to do this are welcomed and appreciated.
Thanks!

>

  • Would the Options menu be a more appropriate place for the Plugin Manager?

(perhaps as simply a "Plugins" menu item to go along with Live Templates,
Keymaps, etc.) I'm undecided on this, partially because I'm still not
entirely sure what the criteria are for placing something in IDE Settings
vs. the Options menu (e.g. to me, Code Styles and Color Schemes could
arguably be placed under the Options menu too). Thoughts?

>

  • Kinda weird that both Installed Plugins and Available Plugins lists can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?

>

  • Ugly interface

>

TO DO
-----

>

  • Create an icon for the configurable in IDE Settings

>

  • Show icons for new and updated plugins in the list of available plugins

(i.e. make use of the last modified tag in the plugin registry)

>

  • Provide a way to open browser and go to a plugin's docUrl (right now the

docUrl is just appended to the description). But how on earth do you do
that in a cross-platform way? I've seen the JavaWorld article, but is that
the best way? Is there any way to get the browser path registered in IDEA's
IDE Settings?

>

  • Show min/max targeted IDEA versions in Plugin Detail area

>

  • Better interface for downloading: better error handling, progress bar,

change mouse pointer, etc.

>

  • Allow user to choose where downloaded plugins will be placed

>

  • Detect whether file(s) to be downloaded already exist(s).

>

  • Allow for multiple bin URLs and multiple bin URL groups. Multiple URLs

are useful for when the plugin depends on other libs. Multiple groups are
useful for, say, providing both .zip and .tar.gz versions.

>

  • Show some sort of icon for installed plugins when a new version is

available (will require parsing and comparison of version numbers)

>

  • Provide some kind of option to download the source as well (e.g. if made

available in a separate zip file).

>

  • Consider extending various elements in the DTD. E.g., allow multiple

vendors, provide support for vendor name, email, URL, etc.

>

  • Maybe provide an option to automatically update plugin list (daily?) and

provide notification when new versions are available.

>

  • Maybe have a "Developer Mode" checkbox that would provide an extra tab to

add/update plugins in the idea-plugin-registry.xml file? I don't know how
tricky it'd be to do a form post to the Wiki to update the
idea-plugin-registry.xml file without going through the actual Wiki
interface. At the very least, provide a simple Swing app (or maybe just
another plugin) to help developers view how their plugin(s) will be rendered
in the Plugin Manager's Plugin Detail area (so they can add HTML markup to
descriptions, etc.).

>
>


0
Comment actions Permalink

Just uploaded a version of the

http://www.intellij.org/twiki/bin/view/Main/LogMonitorPlugin

in which the plugin.xml is corrected.

Aiko

Chris Bartley wrote:

http://www.intellij.org/twiki/bin/view/Main/PluginManager

>

ABOUT
-----
This plugin provides an interface to view all installed and available
plugins and to download available plugins.

>

Once you download and install the plugin, there will be a "Plugins"
section
in IDE Settings. From there you can view some details about plugins you
currently have installed as well as details about (nearly) all IDEA
plugins.
Downloaded plugins are placed in a "downloadedPlugins" directory under
IDEA's home directory (see To Do item below about making this
configurable).

>

The Plugin Manager retrieves the list of available plugins from an XML
file
(idea-plugin-registry.xml) stored at the above URL. I encourage plugin
developers to update this XML file when they create or update their
plugins.
I've pre-loaded the registry with info about nearly all the existing IDEA
plugins, but had a few problems with some:

>

  • * None of Duane Fields' plugins are included since I had

trouble accessing his site.

>

  • * The ViPlugin has the wrong name and description (maybe

version, too) in its plugin.xml file.

>

  • * LogMonitor plugin has the wrong name, vendor, version,

and description in its plugin.xml file.

>

  • * Plugins that are stored on SourceForge don't have a

download URL in the registry, so users are prompted to
just go to the plugin's web site for download info.

>

NOTE: I didn't actually download every single plugin and gather info from
each plugin's plugin.xml file (I only did a few, actually, e.g. when I
couldn't find the latest version number on the Wiki). Instead, I got
almost
all the info from the Wiki. So, there are likely to be
mistakes/omissions.
Sorry. So, if other plugin developers think this plugin is a good
idea, I'd
appreciate help in keeping the plugin registry XML file up to date (sorry,
but I don't have time to do it all myself!). There's a (very simple) DTD
for the registry at the above URL, too--PLEASE make sure you validate the
registry file before you upload an update! Thanks! :D

>

KNOWN ISSUES
------------

>

  • Didn't actually download every plugin and get the vendor/description/etc

from the plugin.xml. Just gathered the info from the Wiki. For the
version
comparison (when implemented) to work correctly, the version in the
registry
will have to match what's in your plugin.xml, so I'd appreciate any help
from plugin authors to make sure they're correct (as well as all other
info).

>

  • Needs refactoring/cleanup/better error handling, etc.

>

  • I don't know how to get text to flow nicely in Swing widgets, so I'm

currently dumping the plugin description into a JEditorPane with text/html
content type (so that extra whitespace is ignored). I think it looks kinda
weird that the description is in a white box, but the rest of the details
aren't. Suggestions on better ways to do this are welcomed and
appreciated.
Thanks!

>

  • Would the Options menu be a more appropriate place for the Plugin

Manager?
(perhaps as simply a "Plugins" menu item to go along with Live Templates,
Keymaps, etc.) I'm undecided on this, partially because I'm still not
entirely sure what the criteria are for placing something in IDE Settings
vs. the Options menu (e.g. to me, Code Styles and Color Schemes could
arguably be placed under the Options menu too). Thoughts?

>

  • Kinda weird that both Installed Plugins and Available Plugins lists can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?

>

  • Ugly interface

>

TO DO
-----

>

  • Create an icon for the configurable in IDE Settings

>

  • Show icons for new and updated plugins in the list of available plugins

(i.e. make use of the last modified tag in the plugin registry)

>

  • Provide a way to open browser and go to a plugin's docUrl (right now the

docUrl is just appended to the description). But how on earth do you do
that in a cross-platform way? I've seen the JavaWorld article, but is
that
the best way? Is there any way to get the browser path registered in
IDEA's
IDE Settings?

>

  • Show min/max targeted IDEA versions in Plugin Detail area

>

  • Better interface for downloading: better error handling, progress bar,

change mouse pointer, etc.

>

  • Allow user to choose where downloaded plugins will be placed

>

  • Detect whether file(s) to be downloaded already exist(s).

>

  • Allow for multiple bin URLs and multiple bin URL groups. Multiple URLs

are useful for when the plugin depends on other libs. Multiple groups are
useful for, say, providing both .zip and .tar.gz versions.

>

  • Show some sort of icon for installed plugins when a new version is

available (will require parsing and comparison of version numbers)

>

  • Provide some kind of option to download the source as well (e.g. if made

available in a separate zip file).

>

  • Consider extending various elements in the DTD. E.g., allow multiple

vendors, provide support for vendor name, email, URL, etc.

>

  • Maybe provide an option to automatically update plugin list (daily?) and

provide notification when new versions are available.

>

  • Maybe have a "Developer Mode" checkbox that would provide an extra

tab to
add/update plugins in the idea-plugin-registry.xml file? I don't know how
tricky it'd be to do a form post to the Wiki to update the
idea-plugin-registry.xml file without going through the actual Wiki
interface. At the very least, provide a simple Swing app (or maybe just
another plugin) to help developers view how their plugin(s) will be
rendered
in the Plugin Manager's Plugin Detail area (so they can add HTML markup to
descriptions, etc.).

>
>

0
Comment actions Permalink

Cool. I've updated the plugin registry with the correct version number
(0.9) and plugin name (Log4jMonitor).

"Aiko Mastboom" <intellij@aiko.sh> wrote in message
news:aqmi1m$rj0$1@is.intellij.net...

Just uploaded a version of the

>

http://www.intellij.org/twiki/bin/view/Main/LogMonitorPlugin

>

in which the plugin.xml is corrected.

>

Aiko



0
Comment actions Permalink

"Sascha Weinreuter" <sascha.weinreuter@cit.de> wrote in message
news:aqmedv$n8e$1@is.intellij.net...
>

You're da man! Great plugin!


:D Hey, thanks, glad ya like it!

There is one issue with my XPathView plugin. I included a simple
DTD for my plugin.xml in the .jar file (I made a copy&paste error
while writing the plugin.xml and decided that with a DTD this would
not happen again ;-).
Unfourtunately, the XML-parser tries to validate the file when there
is a doctype declaration in it and it expects the file to be in
/bin.
I would suggest turning off validation in your SAXBuilder, or, even
better, do not parse an InputStream but a URL instead. You can
construct a jar: URL like jar:file:C:/plugin.jar!/META-INF/plugin.xml.
This way the xml parser can deal with relative references.


Wow, cool, thanks tons for letting me know and especially for the suggested
solution. I've changed the code to construct an URL like you said, and it
works great--no problems with your plugin anymore. I'll upload the new
build in the morning (dog tired now--too much late night coding this
weekend!)

thanks,

chris


0
Comment actions Permalink

Hello Chris,
I have "Refresh Failed" on "Refresh List" pressed. That does it mean?
The log file contains no errors or other messages...

PS. Cool plugin! :)

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Chris Bartley" <spam@feynman.org> wrote in message
news:aqm8m8$g1l$1@is.intellij.net...

http://www.intellij.org/twiki/bin/view/Main/PluginManager

>

ABOUT
-----
This plugin provides an interface to view all installed and available
plugins and to download available plugins.

>

Once you download and install the plugin, there will be a "Plugins"

section

in IDE Settings. From there you can view some details about plugins you
currently have installed as well as details about (nearly) all IDEA

plugins.

Downloaded plugins are placed in a "downloadedPlugins" directory under
IDEA's home directory (see To Do item below about making this

configurable).
>

The Plugin Manager retrieves the list of available plugins from an XML

file

(idea-plugin-registry.xml) stored at the above URL. I encourage plugin
developers to update this XML file when they create or update their

plugins.

I've pre-loaded the registry with info about nearly all the existing IDEA
plugins, but had a few problems with some:

>

  • * None of Duane Fields' plugins are included since I had

trouble accessing his site.

>

  • * The ViPlugin has the wrong name and description (maybe

version, too) in its plugin.xml file.

>

  • * LogMonitor plugin has the wrong name, vendor, version,

and description in its plugin.xml file.

>

  • * Plugins that are stored on SourceForge don't have a

download URL in the registry, so users are prompted to
just go to the plugin's web site for download info.

>

NOTE: I didn't actually download every single plugin and gather info from
each plugin's plugin.xml file (I only did a few, actually, e.g. when I
couldn't find the latest version number on the Wiki). Instead, I got

almost

all the info from the Wiki. So, there are likely to be

mistakes/omissions.

Sorry. So, if other plugin developers think this plugin is a good idea,

I'd

appreciate help in keeping the plugin registry XML file up to date (sorry,
but I don't have time to do it all myself!). There's a (very simple) DTD
for the registry at the above URL, too--PLEASE make sure you validate the
registry file before you upload an update! Thanks! :D

>

KNOWN ISSUES
------------

>

  • Didn't actually download every plugin and get the vendor/description/etc

from the plugin.xml. Just gathered the info from the Wiki. For the

version

comparison (when implemented) to work correctly, the version in the

registry

will have to match what's in your plugin.xml, so I'd appreciate any help
from plugin authors to make sure they're correct (as well as all other
info).

>

  • Needs refactoring/cleanup/better error handling, etc.

>

  • I don't know how to get text to flow nicely in Swing widgets, so I'm

currently dumping the plugin description into a JEditorPane with text/html
content type (so that extra whitespace is ignored). I think it looks kinda
weird that the description is in a white box, but the rest of the details
aren't. Suggestions on better ways to do this are welcomed and

appreciated.

Thanks!

>

  • Would the Options menu be a more appropriate place for the Plugin

Manager?

(perhaps as simply a "Plugins" menu item to go along with Live Templates,
Keymaps, etc.) I'm undecided on this, partially because I'm still not
entirely sure what the criteria are for placing something in IDE Settings
vs. the Options menu (e.g. to me, Code Styles and Color Schemes could
arguably be placed under the Options menu too). Thoughts?

>

  • Kinda weird that both Installed Plugins and Available Plugins lists can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?

>

  • Ugly interface

>

TO DO
-----

>

  • Create an icon for the configurable in IDE Settings

>

  • Show icons for new and updated plugins in the list of available plugins

(i.e. make use of the last modified tag in the plugin registry)

>

  • Provide a way to open browser and go to a plugin's docUrl (right now the

docUrl is just appended to the description). But how on earth do you do
that in a cross-platform way? I've seen the JavaWorld article, but is

that

the best way? Is there any way to get the browser path registered in

IDEA's

IDE Settings?

>

  • Show min/max targeted IDEA versions in Plugin Detail area

>

  • Better interface for downloading: better error handling, progress bar,

change mouse pointer, etc.

>

  • Allow user to choose where downloaded plugins will be placed

>

  • Detect whether file(s) to be downloaded already exist(s).

>

  • Allow for multiple bin URLs and multiple bin URL groups. Multiple URLs

are useful for when the plugin depends on other libs. Multiple groups are
useful for, say, providing both .zip and .tar.gz versions.

>

  • Show some sort of icon for installed plugins when a new version is

available (will require parsing and comparison of version numbers)

>

  • Provide some kind of option to download the source as well (e.g. if made

available in a separate zip file).

>

  • Consider extending various elements in the DTD. E.g., allow multiple

vendors, provide support for vendor name, email, URL, etc.

>

  • Maybe provide an option to automatically update plugin list (daily?) and

provide notification when new versions are available.

>

  • Maybe have a "Developer Mode" checkbox that would provide an extra tab

to

add/update plugins in the idea-plugin-registry.xml file? I don't know how
tricky it'd be to do a form post to the Wiki to update the
idea-plugin-registry.xml file without going through the actual Wiki
interface. At the very least, provide a simple Swing app (or maybe just
another plugin) to help developers view how their plugin(s) will be

rendered

in the Plugin Manager's Plugin Detail area (so they can add HTML markup to
descriptions, etc.).

>
>


0
Comment actions Permalink

I just disable the console output, here stack trace:
org.jdom.JDOMException: Error in building: Server returned HTTP response
code: 4
03 for URL:
http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-reg
istry.xml
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:306)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:682)
at
com.chrisbartley.idea.pluginmanager.PluginManagerConfigurable.buildAv
ailablePlugins(PluginManagerConfigurable.java:138)
at
com.chrisbartley.idea.pluginmanager.PluginManagerConfigurationPanel$1
.actionPerformed(PluginManagerConfigurationPanel.java:89)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknow
n Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown
Sour
ce)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.intellij.ide.q.a(q.java:118)
at com.intellij.ide.q.dispatchEvent(q.java:117)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.Dialog.show(Unknown Source)
at
com.intellij.openapi.ui.DialogWrapper$MyDialog.show(DialogWrapper.jav
a:35)
at
com.intellij.openapi.ui.DialogWrapper.show(DialogWrapper.java:136)
at com.intellij.ide.n.dg.actionPerformed(dg.java:2)
at com.intellij.openapi.actionSystem.a.l.actionPerformed(l.java:6)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
com.intellij.openapi.actionSystem.a.bb.fireActionPerformed(bb.java:61
)
at com.intellij.ui.a.a.p.doClick(p.java:39)
at com.intellij.ui.a.a.p.access$300(p.java:118)
at com.intellij.ui.a.a.q.mouseReleased(q.java:0)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.intellij.ide.q.a(q.java:118)
at com.intellij.ide.q.dispatchEvent(q.java:117)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 403 for
URL:

http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-registry.xm
l
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
urce)
at java.net.URL.openStream(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown
Source)
at
org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown S
ource)
at
org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:287)
... 56 more
Root cause: java.io.IOException: Server returned HTTP response code: 403 for
URL
:
http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-registry.xm
l
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
urce)
at java.net.URL.openStream(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown
Source)
at
org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown S
ource)
at
org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:287)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:682)
at
com.chrisbartley.idea.pluginmanager.PluginManagerConfigurable.buildAv
ailablePlugins(PluginManagerConfigurable.java:138)
at
com.chrisbartley.idea.pluginmanager.PluginManagerConfigurationPanel$1
.actionPerformed(PluginManagerConfigurationPanel.java:89)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknow
n Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown
Sour
ce)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.intellij.ide.q.a(q.java:118)
at com.intellij.ide.q.dispatchEvent(q.java:117)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.Dialog.show(Unknown Source)
at
com.intellij.openapi.ui.DialogWrapper$MyDialog.show(DialogWrapper.jav
a:35)
at
com.intellij.openapi.ui.DialogWrapper.show(DialogWrapper.java:136)
at com.intellij.ide.n.dg.actionPerformed(dg.java:2)
at com.intellij.openapi.actionSystem.a.l.actionPerformed(l.java:6)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
com.intellij.openapi.actionSystem.a.bb.fireActionPerformed(bb.java:61
)
at com.intellij.ui.a.a.p.doClick(p.java:39)
at com.intellij.ui.a.a.p.access$300(p.java:118)
at com.intellij.ui.a.a.q.mouseReleased(q.java:0)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.intellij.ide.q.a(q.java:118)
at com.intellij.ide.q.dispatchEvent(q.java:117)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Root cause: java.io.IOException: Server returned HTTP response code: 403 for
URL
:
http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-registry.xm
l
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
urce)
at java.net.URL.openStream(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown
Source)
at
org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown S
ource)
at
org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:287)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:682)
at
com.chrisbartley.idea.pluginmanager.PluginManagerConfigurable.buildAv
ailablePlugins(PluginManagerConfigurable.java:138)
at
com.chrisbartley.idea.pluginmanager.PluginManagerConfigurationPanel$1
.actionPerformed(PluginManagerConfigurationPanel.java:89)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknow
n Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown
Sour
ce)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.intellij.ide.q.a(q.java:118)
at com.intellij.ide.q.dispatchEvent(q.java:117)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.Dialog.show(Unknown Source)
at
com.intellij.openapi.ui.DialogWrapper$MyDialog.show(DialogWrapper.jav
a:35)
at
com.intellij.openapi.ui.DialogWrapper.show(DialogWrapper.java:136)
at com.intellij.ide.n.dg.actionPerformed(dg.java:2)
at com.intellij.openapi.actionSystem.a.l.actionPerformed(l.java:6)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
com.intellij.openapi.actionSystem.a.bb.fireActionPerformed(bb.java:61
)
at com.intellij.ui.a.a.p.doClick(p.java:39)
at com.intellij.ui.a.a.p.access$300(p.java:118)
at com.intellij.ui.a.a.q.mouseReleased(q.java:0)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.intellij.ide.q.a(q.java:118)
at com.intellij.ide.q.dispatchEvent(q.java:117)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Alexey Efimov" <aefimov@spklabs.com> wrote in message
news:aqno1p$8t0$1@is.intellij.net...

Hello Chris,
I have "Refresh Failed" on "Refresh List" pressed. That does it mean?
The log file contains no errors or other messages...

>

PS. Cool plugin! :)

>

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Chris Bartley" <spam@feynman.org> wrote in message
news:aqm8m8$g1l$1@is.intellij.net...

http://www.intellij.org/twiki/bin/view/Main/PluginManager

>

ABOUT
-----
This plugin provides an interface to view all installed and available
plugins and to download available plugins.

>

Once you download and install the plugin, there will be a "Plugins"

section

in IDE Settings. From there you can view some details about plugins you
currently have installed as well as details about (nearly) all IDEA

plugins.

Downloaded plugins are placed in a "downloadedPlugins" directory under
IDEA's home directory (see To Do item below about making this

configurable).
>

The Plugin Manager retrieves the list of available plugins from an XML

file

(idea-plugin-registry.xml) stored at the above URL. I encourage plugin
developers to update this XML file when they create or update their

plugins.

I've pre-loaded the registry with info about nearly all the existing

IDEA

plugins, but had a few problems with some:

>

  • * None of Duane Fields' plugins are included since I had

trouble accessing his site.

>

  • * The ViPlugin has the wrong name and description (maybe

version, too) in its plugin.xml file.

>

  • * LogMonitor plugin has the wrong name, vendor, version,

and description in its plugin.xml file.

>

  • * Plugins that are stored on SourceForge don't have a

download URL in the registry, so users are prompted to
just go to the plugin's web site for download info.

>

NOTE: I didn't actually download every single plugin and gather info

from

each plugin's plugin.xml file (I only did a few, actually, e.g. when I
couldn't find the latest version number on the Wiki). Instead, I got

almost

all the info from the Wiki. So, there are likely to be

mistakes/omissions.

Sorry. So, if other plugin developers think this plugin is a good idea,

I'd

appreciate help in keeping the plugin registry XML file up to date

(sorry,

but I don't have time to do it all myself!). There's a (very simple)

DTD

for the registry at the above URL, too--PLEASE make sure you validate

the

registry file before you upload an update! Thanks! :D

>

KNOWN ISSUES
------------

>

  • Didn't actually download every plugin and get the

vendor/description/etc

from the plugin.xml. Just gathered the info from the Wiki. For the

version

comparison (when implemented) to work correctly, the version in the

registry

will have to match what's in your plugin.xml, so I'd appreciate any help
from plugin authors to make sure they're correct (as well as all other
info).

>

  • Needs refactoring/cleanup/better error handling, etc.

>

  • I don't know how to get text to flow nicely in Swing widgets, so I'm

currently dumping the plugin description into a JEditorPane with

text/html

content type (so that extra whitespace is ignored). I think it looks

kinda

weird that the description is in a white box, but the rest of the

details

aren't. Suggestions on better ways to do this are welcomed and

appreciated.

Thanks!

>

  • Would the Options menu be a more appropriate place for the Plugin

Manager?

(perhaps as simply a "Plugins" menu item to go along with Live

Templates,

Keymaps, etc.) I'm undecided on this, partially because I'm still not
entirely sure what the criteria are for placing something in IDE

Settings

vs. the Options menu (e.g. to me, Code Styles and Color Schemes could
arguably be placed under the Options menu too). Thoughts?

>

  • Kinda weird that both Installed Plugins and Available Plugins lists

can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?

>

  • Ugly interface

>

TO DO
-----

>

  • Create an icon for the configurable in IDE Settings

>

  • Show icons for new and updated plugins in the list of available

plugins

(i.e. make use of the last modified tag in the plugin registry)

>

  • Provide a way to open browser and go to a plugin's docUrl (right now

the

docUrl is just appended to the description). But how on earth do you do
that in a cross-platform way? I've seen the JavaWorld article, but is

that

the best way? Is there any way to get the browser path registered in

IDEA's

IDE Settings?

>

  • Show min/max targeted IDEA versions in Plugin Detail area

>

  • Better interface for downloading: better error handling, progress bar,

change mouse pointer, etc.

>

  • Allow user to choose where downloaded plugins will be placed

>

  • Detect whether file(s) to be downloaded already exist(s).

>

  • Allow for multiple bin URLs and multiple bin URL groups. Multiple

URLs

are useful for when the plugin depends on other libs. Multiple groups

are

useful for, say, providing both .zip and .tar.gz versions.

>

  • Show some sort of icon for installed plugins when a new version is

available (will require parsing and comparison of version numbers)

>

  • Provide some kind of option to download the source as well (e.g. if

made

available in a separate zip file).

>

  • Consider extending various elements in the DTD. E.g., allow multiple

vendors, provide support for vendor name, email, URL, etc.

>

  • Maybe provide an option to automatically update plugin list (daily?)

and

provide notification when new versions are available.

>

  • Maybe have a "Developer Mode" checkbox that would provide an extra tab

to

add/update plugins in the idea-plugin-registry.xml file? I don't know

how

tricky it'd be to do a form post to the Wiki to update the
idea-plugin-registry.xml file without going through the actual Wiki
interface. At the very least, provide a simple Swing app (or maybe just
another plugin) to help developers view how their plugin(s) will be

rendered

in the Plugin Manager's Plugin Detail area (so they can add HTML markup

to

descriptions, etc.).

>
>

>
>



0
Comment actions Permalink

On Sun, 10 Nov 2002 21:09:34 +0100, Sascha Weinreuter wrote:

You're da man! Great plugin!

There is one issue with my XPathView plugin. I included a simple DTD for my


Can plugins be installed per-user??? All references seem to be in the main
idea home dir.

I was thinking about the plugin manager downloading plugins, I install idea
machine wide to /usr/java/idea and don't really want my normal user to have
free write access to that dir...


0
Comment actions Permalink

"Mark Derricutt" <mark@talios.com> wrote in message
news:pan.2002.11.11.12.14.09.625883@talios.com...

On Sun, 10 Nov 2002 21:09:34 +0100, Sascha Weinreuter wrote:

>

Can plugins be installed per-user??? All references seem to be in the

main

idea home dir.


This is probably a question for JetBrains. But, as far as I know, plugins
can only be installed in the plugins directory. See tracker # 5489 for a
request to change that
(http://www.intellij.net/tracker/idea/viewSCR?publicId=5489).


0
Comment actions Permalink


"Alexey Efimov" <aefimov@spklabs.com> wrote in message
news:aqno1p$8t0$1@is.intellij.net...

Hello Chris,
I have "Refresh Failed" on "Refresh List" pressed. That does it mean?
The log file contains no errors or other messages...


Hmm, strange. The stack trace in your next post mentions the 403 HTTP
status code ("Forbidden"). Do you still have problems with the Refresh List
button? I guess there's a chance that I was updating the registry file
while you were trying to refresh it and the Wiki software returned a 403 to
you.

PS. Cool plugin! :)


Thanks! :D


0
Comment actions Permalink
  • I don't know how to get text to flow nicely in

Swing widgets, so I'm
currently dumping the plugin description into a
JEditorPane with text/html
content type (so that extra whitespace is ignored). I
think it looks kinda
weird that the description is in a white box, but the
rest of the details
aren't. Suggestions on better ways to do this are
welcomed and appreciated.
Thanks!


Here what I have done to get around this.

0
Comment actions Permalink
  • I don't know how to get text to flow nicely in

Swing widgets, so I'm
currently dumping the plugin description into a
JEditorPane with text/html
content type (so that extra whitespace is ignored). I
think it looks kinda
weird that the description is in a white box, but the
rest of the details
aren't. Suggestions on better ways to do this are
welcomed and appreciated.
Thanks!


I wanted to do something like this also. I had to use a JTextArea instead of a JTextPane. Here is what I have done to get around this, hope it helps.


Tobin

0
Comment actions Permalink

Sorry about this... got some fat fingers today...

0
Comment actions Permalink

With new version i have the same error...
Maybe proxy, but very strange.
I try -Dhttp.proxyHost= and -Dhttp.proxyPort but still 403...
Thanks!

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Chris Bartley" <spam@feynman.org> wrote in message
news:aqogid$msp$1@is.intellij.net...
>

"Alexey Efimov" <aefimov@spklabs.com> wrote in message
news:aqno1p$8t0$1@is.intellij.net...

Hello Chris,
I have "Refresh Failed" on "Refresh List" pressed. That does it mean?
The log file contains no errors or other messages...

>

Hmm, strange. The stack trace in your next post mentions the 403 HTTP
status code ("Forbidden"). Do you still have problems with the Refresh

List

button? I guess there's a chance that I was updating the registry file
while you were trying to refresh it and the Wiki software returned a 403

to

you.

>

PS. Cool plugin! :)

>

Thanks! :D

>
>


0
Comment actions Permalink

Can you do other HTTP things in IDEA? For example, can IDEA successfully
auto-fetch DTDs?

Maybe try this to see what happens:

1) Download the plugin registry file to your machine with your web browser.
It's located at:


http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-registry.xm
l

2) Open the file in IDEA. IDEA should prompt you to download the DTD. Does
it work?

Anyone else seeing this problem and/or know a solution? Beyond the proxy
settings, I'm not sure what else to check.

thanks,

chris

"Alexey Efimov" <aefimov@spklabs.com> wrote in message
news:aqom55$36d$1@is.intellij.net...

With new version i have the same error...
Maybe proxy, but very strange.
I try -Dhttp.proxyHost= and -Dhttp.proxyPort but still 403...
Thanks!



0
Comment actions Permalink

Chris Bartley wrote:

http://www.intellij.org/twiki/bin/view/Main/PluginManager


Very cool!

  • Would the Options menu be a more appropriate place for the Plugin Manager?


I think the Options menu would be good.

  • Kinda weird that both Installed Plugins and Available Plugins lists can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?


How about using a tab to show either installed or available lists and
the visible list determines the selection?

I was thinking that having to update a central plugin registry every
time some detail about a plugin changes is a tad cumbersome. What if the
Plugin Manager requires that an XML file with the descriptive parts of
your registry be available in a known location for each plugin? Probably
the best place would be as an attachment on the Wiki page for the
plugin, for example:

http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-info.xml

That way, each plugin developer can individually update their own
plugin's description and the central registry only has to be updated
when a new plugin is created.

Alternatively, the central plugin registry could specify the URL to the
plugin info xml if it's not being hosted on the Wiki.

Ciao,
Gordon

--
Gordon Tyler
Software Developer, R&D
Sitraka -- Performance is Mission Critical

0
Comment actions Permalink

IntelliJ can't get. The same 403 without proxy, and 407 with proxy...
Ok, i will find some proxy bypasses

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Chris Bartley" <spam@feynman.org> wrote in message
news:aqomtk$4ss$1@is.intellij.net...

Can you do other HTTP things in IDEA? For example, can IDEA successfully
auto-fetch DTDs?

>

Maybe try this to see what happens:

>

1) Download the plugin registry file to your machine with your web

browser.

It's located at:

>
>
>
http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-registry.xm

l

>

2) Open the file in IDEA. IDEA should prompt you to download the DTD.

Does

it work?

>

Anyone else seeing this problem and/or know a solution? Beyond the proxy
settings, I'm not sure what else to check.

>

thanks,

>

chris

>

"Alexey Efimov" <aefimov@spklabs.com> wrote in message
news:aqom55$36d$1@is.intellij.net...

With new version i have the same error...
Maybe proxy, but very strange.
I try -Dhttp.proxyHost= and -Dhttp.proxyPort but still 403...
Thanks!

>
>


0
Comment actions Permalink

"Gordon Tyler" <gordon.tyler@sitraka.com> wrote in message
news:aqool9$8d1$1@is.intellij.net...

Chris Bartley wrote:

http://www.intellij.org/twiki/bin/view/Main/PluginManager

>

Very cool!


thanks! :D

  • Would the Options menu be a more appropriate place for the Plugin

Manager?
>

I think the Options menu would be good.


I'm leaning that way, too. I'll probably try it out in one of the next few
builds.

  • Kinda weird that both Installed Plugins and Available Plugins lists

can

both have selections at the same time (since Plugin Details displays the
latest selection). Maybe prevent selections in both at the same time?

>

How about using a tab to show either installed or available lists and
the visible list determines the selection?


That sounds nice, especially once I add code to detect updates and render
the list items appropriately (with "New!" and "Updated" icons, etc.). I'll
give it a shot (but I'm a total Swing idiot, so I'm not promising anything
soon! :) A "Check for updates" button in the "Installed Plugins" tab would
be nice, then, too.

I was thinking that having to update a central plugin registry every
time some detail about a plugin changes is a tad cumbersome.


Ya know, I thought the very same thing (and not just because I fear I'm
gonna get stuck with doing all the updates! :), but worried about the user
experience of waiting for dozens of separate HTTP requests when refreshing
the list. More thoughts below...

What if the
Plugin Manager requires that an XML file with the descriptive parts of
your registry be available in a known location for each plugin? Probably
the best place would be as an attachment on the Wiki page for the
plugin, for example:

>

http://www.intellij.org/twiki/pub/Main/PluginManager/idea-plugin-info.xml

>

That way, each plugin developer can individually update their own
plugin's description and the central registry only has to be updated
when a new plugin is created.

>

Alternatively, the central plugin registry could specify the URL to the
plugin info xml if it's not being hosted on the Wiki.


A couple alternatives come to mind:

1) Go with the approach you suggest above and modify the Plugin Manager so
that the user can refresh the info for plugins individually. Probably
have a "Refresh All" button too (with an appropriate "Go get some coffee in
the meantime" prompt ;) Refresh All could either go out and download the
info for every known plugin, or simply retrieve the list of known plugins
and then individual plugin info is just fetched lazily whenever requested.
I dunno, maybe a Refresh All that downloads all the info files wouldn't be
too bad if it's accompanied by a nice progress bar (which would be fairly
simple to do, i guess).

2) Maybe some sort of hybrid approach? Each plugin has its own info file
(as you suggest above), but we also keep the registry file and just update
it nightly via some simple app that fetches the info file for every plugin
and builds the registry. The trick is automating it so no one gets stuck
with doing this manually. Maybe if we beg JetBrains to help us out here...
;-D

Thoughts?

I appreciate your suggestions, Gordon. Thanks for your help in hashing all
this out!

chris



0
Comment actions Permalink

Chris Bartley wrote:

That sounds nice, especially once I add code to detect updates and render
the list items appropriately (with "New!" and "Updated" icons, etc.). I'll
give it a shot (but I'm a total Swing idiot, so I'm not promising anything
soon! :) A "Check for updates" button in the "Installed Plugins" tab would
be nice, then, too.


Would the "Check For Updates" button do what the current "Refresh List"
button does? Or would it compare the version of installed plugins versus
what is available?

1) Go with the approach you suggest above and modify the Plugin Manager so
that the user can refresh the info for plugins individually. Probably
have a "Refresh All" button too (with an appropriate "Go get some coffee in
the meantime" prompt ;) Refresh All could either go out and download the
info for every known plugin, or simply retrieve the list of known plugins
and then individual plugin info is just fetched lazily whenever requested.
I dunno, maybe a Refresh All that downloads all the info files wouldn't be
too bad if it's accompanied by a nice progress bar (which would be fairly
simple to do, i guess).


I think that a full refresh may go faster than you think, especially if
you create a thread for each info URL. A "Refresh List" button which
downloads the central list and all the individual plugin info files in
one go with an appropriate progress bar sounds good to me. Simple to
implement and simple for the user. The only complicated bit might be
getting the progress bar to play nice with multiple threads downloading
the info files.

Ciao,
Gordon

--
Gordon Tyler
Software Developer, R&D
Sitraka -- Performance is Mission Critical

0
Comment actions Permalink

Hey, thanks for the tip! I'll give it a shot.

chris

"Tobin Juday" <tsjuday@checkfree.com> wrote in message
news:4953843.1037030692824.JavaMail.jrun@is.intellij.net...

  • I don't know how to get text to flow nicely in

Swing widgets, so I'm
currently dumping the plugin description into a
JEditorPane with text/html
content type (so that extra whitespace is ignored). I
think it looks kinda
weird that the description is in a white box, but the
rest of the details
aren't. Suggestions on better ways to do this are
welcomed and appreciated.
Thanks!

>

I wanted to do something like this also. I had to use a JTextArea instead

of a JTextPane. Here is what I have done to get around this, hope it helps.

        myJTextArea.setEditable(false);
>
>        // set it to wrap the text if one line isn't enough room
>        myJTextArea.setLineWrap(true);
>
>        // the line above will break up words across lines, so this line
tells it to "smart" break the lines
>        myJTextArea.setWrapStyleWord(true);
>
>        // set the font to a hardcoded value
>        myJTextArea.setFont(new Font("SansSerif", Font.BOLD, 12));
>        // or make it match something else...like another label
>        myJTextArea.setFont(someJLabel.getFont());
>
>        // change the background color into something that matches...my
code lives in a
>        //class that extends JPanel, so I was able to get the background
color quite easily
>        myJTextArea.setBackground(this.getBackground());]]>

>

Tobin

>


0

Please sign in to leave a comment.