[ANN] PropertiesEditor Plugin 1.0
Hello,
Editor for properties files inspired by IDEA java and xml editors.
Features:
Highlighting
Syntax checking (wrong escaping for now)
Error stripe error marking
Error stripe navigation
Resource key navigation in tree
You can install plugin from IDEA Plugin Manager.
TIA,
Dmitry
Please sign in to leave a comment.
Cool.
One suggestion:
It would be nice if the content of the outline pane was displayed
inside of the Structure view.
"Dmitry Kashin" <no_mail@jetbrains.com> wrote in message
news:6476189.1079100311993.JavaMail.itn@is.intellij.net...
>
>
>
>
I'm filled request for it, now only Java and XML files can be displayed in structure, and no related API available at all.
http://www.intellij.net/forums/thread.jsp?forum=15&thread=79754&tstart=45&trange=15
TIA,
Dmitry
Sweet!
Now, can I configure my colors? :)
How about Ctrl-F12 (as in java: pop up a dialog with a list of properties
and let user select from it, with a quick search through the keyboard)
Very nice.
Vince.
"Dmitry Kashin" <no_mail@jetbrains.com> wrote in message
news:6476189.1079100311993.JavaMail.itn@is.intellij.net...
>
>
>
>
Color configuration not available cause for now I'm have some troubles with fonts coloring and wait for response of Jetbrains is it possible at all. The settings will be available after resolving this.
Structure view on Ctrl+F12 not planned yet cause you can use incremental search for find keys.
But probably will be implemented.
TIA,
Dmitry
Nice plugin, thank you! :)
--
Stanislav Davydov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Dmitry Kashin" <no_mail@jetbrains.com> wrote in message news:6476189.1079100311993.JavaMail.itn@is.intellij.net...
>
>
>
>
-1 for Ctrl+F12
It will be the same length long list of properties as file it self. The tree
will be beter, and tree already present.
Thank you!
"Vincent Mallet" <xmalletva@tripos.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:c2sjrl$kmv$1@is.intellij.net...
>
>
>
>
>
>
Excellent!! Thank you
"Dmitry Kashin" <no_mail@jetbrains.com> wrote in message
news:6476189.1079100311993.JavaMail.itn@is.intellij.net...
>
>
>
>
Very sweet. And the best part is that I get to request an inspection feature! It would be very handy if duplicate properties were highlighted as errors.
--Dave "inverting the normal order" Griffith
When I have a lengthy property file with lots of comments
and with properties grouped by functions rather than sorted
alphabetically, I want to be able to quickly jump to a property
with a quick-find on its name. Ctrl-F12 sounds like a good choice.
(argueably, using the tree on the right could work if I could
jump to it with the keyboard and start typing to narrow down
my selection. Right now typing only considers the first letter
and I haven't seen how to get to it without the mouse).
Vince.
"Alexey Efimov" <aefimov@tengry.com> wrote in message
news:c2slkb$c5$1@is.intellij.net...
>
tree
>
>
properties
>
>
Hi!
I think that something like Ctrl + N will be implemented for it, but not
same as Ctrl + F12, i guess
Thanks!
"Vincent Mallet" <xmalletva@tripos.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:c2svuu$v9e$1@is.intellij.net...
>
>
>
>
>
I tried to open following file:
============================================================
CHANGE FOR YOUR APP SERVER ###############
Deployment directory.
Sets xdoclet lib directory
#xdocletlib=/home/local/xdoclet/lib
This is where the script get J2EE jar files
j2ee.lib=/usr/local/j2ee/lib
#antpath=/usr/local/ant/lib
#jboss.home.dir=/usr/local/jboss
#jboss.deploy.dir=/usr/local/jboss/server/default/deploy
deploy.dir=/usr/local/tomcat/webapps
javadoc.dir=javadoc
DON'T CHANGE THESE
#ejbModule
#ejb.jar.name=game.ejb.jar
#webModule
war.file.name=rabbit.war
web.context.root=/rabbit
app.xml.file.name=application.xml
ds.file.name=postgres-ds.xml
ear.file.name=rabbit.ear
deploy_env.file=deploy.properties
============================================================
and I got following exception:
============================================================
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.(String.java:192) at com.resedit.propedit.structure.parser.PropertiesFileParser.parse(PropertiesFileParser.java:136) at com.resedit.propedit.PropertiesFileEditor.init(PropertiesFileEditor.java:75) at com.resedit.propedit.PropertiesFileEditor.]]>(PropertiesFileEditor.java:70)
at
com.resedit.propedit.PropertiesFileEditorProvider.createEditor(PropertiesFileEditorProvider.java:46)
at com.intellij.openapi.fileEditor.a.f.b(f.java:33)
at com.intellij.openapi.fileEditor.a.f.access$900(f.java:471)
at com.intellij.openapi.fileEditor.a.f$3.run(f$3.java)
at com.intellij.openapi.command.impl.a.executeCommand(a.java:78)
at com.intellij.openapi.fileEditor.a.f.a(f.java:181)
at com.intellij.openapi.fileEditor.a.f.openFile(f.java:55)
at com.intellij.ide.actions.de$4.run(de$4.java:4)
at com.intellij.ui.ListPopup.closePopup(ListPopup.java:43)
at com.intellij.ui.ListPopup$1.mouseClicked(ListPopup.java:2)
at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:212)
at java.awt.Component.processMouseEvent(Component.java:5103)
at java.awt.Component.processEvent(Component.java:4897)
at java.awt.Container.processEvent(Container.java:1569)
at java.awt.Component.dispatchEventImpl(Component.java:3615)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3207)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
at java.awt.Container.dispatchEventImpl(Container.java:1613)
at java.awt.Window.dispatchEventImpl(Window.java:1606)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
at com.intellij.ide.q.b(q.java:120)
at com.intellij.ide.q.a(q.java:51)
at com.intellij.ide.q.dispatchEvent(q.java:99)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
============================================================
--
drP
Nice plugin, but works very badly on OSX. When a property file is loaded all IDEA painting seems off, huge areas of grey show up etc. Moving the mouse over various things causes the underying stuff to be painted correctly.
Moving it over the IDEA toolbar area results in:
rror message: Error during dispatching of java.awt.event.InvocationEvent[INVOCATION_DEFAULT,runnable=javax.swing.SystemEventQueueUtilities$ComponentWorkRequest@133c2a,notifier=null,catchExceptions=false,when=1079198564626] on apple.awt.CToolkit@d2f5bf
java.lang.ClassCastException
at com.resedit.propedit.ui.ErrorStripeRendererImpl.paint(ErrorStripeRendererImpl.java:49)
at com.resedit.propedit.ui.ErrorStripeRendererImpl.paint(ErrorStripeRendererImpl.java:115)
at javax.swing.JComponent.paintChildren(JComponent.java:647)
at javax.swing.JComponent.paint(JComponent.java:817)
at javax.swing.JComponent.paintChildren(JComponent.java:647)
Hi
It's already planned but I don't know which property highlight:
Actually second property is error but after parsing properties file it will taken.
TIA,
Dmitry
Hi,
About painting off I'm try to examine this behaviour.
About exception:
I'm have no access to OSX jdk. Can you point where I'm can find info (or even sources like in Sun JDK) related to ScrollBarUI implementation for OSX?
TIA,
Dmitry
Hi,
Please attach this file cause copy pasted from forum file works fine.
TIA,
Dmitry
Very good!
I would like to see commented out properties to be formatted differently as comments which does not include property-definitions. Also they could show up in the tree-view, grayed out. Both optional, maybe.
Also maybe activation, deactivation of properties on a click may be supported. Or an ability to comfortably toggle between different values for one property.
In Short: The plugin should know about deactivated (commented out) properties in the same way as it knows about active properties. And it should be able to distinguish between commented definitions for which there exists an uncommented version and those for which it doesn't. At least I would like that as it would support some common usages of mine.
Hi,
How you suggest to distinguish commented properties from comments?
TIA,
Dmitry
If possible I would use a regular expression like this:
\#[ \t]+=.
which is able to recognize for example the following properties
#zero=0
#one= 1
two = 22 22
t__H_ree = 3 33 333
5 = five
Maybe it should be made configurable which characters are allowed in a property-name.
If the plugin would support to comfortably activate or deactivate properties by commenting it could use a special comment for this, maybe #% or some similar pattern. An alternative.