[ANN] PropertiesEditor Plugin 1.1

Changes

  • Two files editing(first file fixed, second file selectable from "bundle"(from current matching files in source file directory for now)). Feedback highly appreciated.

  • Synchronized key navigation in editor(between splitted "bundle" item editors)

  • Not fully translated keys highlightning in navigation tree(hierarchical)

  • Next/Previous not fully translated key node(sibling) in tree (F2/Shift+F2)

  • Escaping of special save chars supported(' ',':','=')

  • Error stripe change markers

  • Major improvements and bug fixes


There are some known minor issues but they didn't fixed cause may become obsolete in case of concepts changing.

Discussion on bundle editing welcome.

Settings page doesn't working with Pallada. Will be fixed ASAP.

TIA,
Dmitry

23 comments
Comment actions Permalink

The new version is marking all of my targets in build files(build.xml) as
warnings ("Duplicate property name").

"Dmitry Kashin" <no_mail@jetbrains.com> wrote in message
news:2290914.1081351345506.JavaMail.itn@is.intellij.net...

Changes

>

  • Two files editing(first file fixed, second file selectable from

"bundle"(from current matching files in source file directory for now)).
Feedback highly appreciated.

  • Synchronized key navigation in editor(between splitted "bundle" item

editors)

  • Not fully translated keys highlightning in navigation tree(hierarchical)

  • Next/Previous not fully translated key node(sibling) in tree

(F2/Shift+F2)

  • Escaping of special save chars supported(' ',':','=')

  • Error stripe change markers

  • Major improvements and bug fixes

>

There are some known minor issues but they didn't fixed cause may become

obsolete in case of concepts changing.
>

Discussion on bundle editing welcome.

>

Settings page doesn't working with Pallada. Will be fixed ASAP.

>

TIA,
Dmitry



0
Comment actions Permalink

Looks like the escaping problems are fixed. Thanks 8)

One little request: Could double-clicking a node in the tree switch the
focus to the editor in addition to moving the caret?

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink

Brad wrote:

The new version is marking all of my targets in build files(build.xml) as
warnings ("Duplicate property name").


And other XML files.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink

Hi,
In which position? Where to place focus in case of 2 editors?

TIA,
Dmitry

0
Comment actions Permalink

Thanks for your reports will be fixed ASAP.

TIA,
Dmitry

0
Comment actions Permalink

Hi,

Why are some of my properties showing in red in the tree on the left had side of the editor?

Thanks

Scott

Changes

  • Two files editing(first file fixed, second file selectable from

"bundle"(from current matching files in source file directory for
now)). Feedback highly appreciated.

  • Synchronized key navigation in editor(between splitted "bundle" item

editors)

  • Not fully translated keys highlightning in navigation

tree(hierarchical)

  • Next/Previous not fully translated key node(sibling) in tree

(F2/Shift+F2)

  • Escaping of special save chars supported(' ',':','=')

  • Error stripe change markers

  • Major improvements and bug fixes


There are some known minor issues but they didn't fixed cause may
become obsolete in case of concepts changing.

Discussion on bundle editing welcome.

Settings page doesn't working with Pallada. Will be fixed ASAP.

TIA,
Dmitry


-- Posted by JetBrains OmniaMea

0
Comment actions Permalink

Fixed in 1.1a

TIA,
Dmitr

0
Comment actions Permalink

Dmitry Kashin wrote:

In which position?


When I select a node in the tree, the caret is already being moved in
the editor (I can see the yellow line selection move), so you should
just need to switch focus to the editor. Or am I misunderstanding your
question?

Where to place focus in case of 2 editors?


As for 2 editors, I have no idea since I haven't used that particular
feature yet. Perhaps double-clicking a node should do nothing when there
are 2 editors?

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink

Hi,
Most probably you have in directory with editing file another that can be in bundle with source. And in some of files marked as red properties doesn't present.
(It was description of intended behaviour, your case description highly appreciated)

TIA,
Dmitry

0
Comment actions Permalink

Hi
If you press Tab then focus transfered to editor(earlier it works).

2 editors mode used for bundle editing and experimental for now. To activate it enough to have in directory couple of files, for example:
application.properties
application_ru.properties

TIA,
Dmitry

0
Comment actions Permalink

Dmitry Kashin wrote:

If you press Tab then focus transfered to editor(earlier it works).


That's what I'm using now. But I'm lazy and I would like double-click to
do the Tab for me ;)

2 editors mode used for bundle editing and experimental for now. To activate it enough to have in directory couple of files, for example:
application.properties
application_ru.properties


I see that now. Nice feature. Perhaps double-click could switch to
whichever editor last had focus before focus moved to the tree?

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink

Gordon Tyler wrote:

Dmitry Kashin wrote:

>> If you press Tab then focus transfered to editor(earlier it works).


That's what I'm using now. But I'm lazy and I would like double-click to
do the Tab for me ;)


A better argument for this is that it would match the behaviour of
double-click in the Structure pane and other similar places.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink

Well, the functionality is fantastic (I was wondering if we could have something like this just ten minutes ago!), but needs debugging, now: I have a lot of properties red even if they are present on both files. I attach the files. ;)



Attachment(s):
ApplicationResources.properties
ApplicationResources_it.properties
0
Comment actions Permalink

Moreover, if a key is present in one file only, and is correctly marked as red, deleting that key in the editor does not delete the key in the tree.

0
Comment actions Permalink

Uhm, I'm sorry, I think the errors depend on the fact that I had a THIRD property file for the same bundle in the same directory, having the properties that were missing in the other two files, and missing the properties that resulted as red in the tree. I think that if only 2 files can be shown at the same moment, the tree colors should only depend on those files, or at least it should be indicated that the red color depends on a third file, no? Otherwise with a large number of property files it could quickly become difficult understanding which file is missing which property.

0
Comment actions Permalink

Hi,
Your case shows that coloring based only on displayed files is not enough ;)
Display more than 2 files is possible but I'm think not a very good idea, the editing become more complicated.
Do you have any suggestions in improvement of display such kind of problem?

TIA,
Dmitry

0
Comment actions Permalink

Well... I think that the coloring which indicates missing properties could be good, but:
1) it should be possible to rapidly know which files are missing the property. You could provide a hover or a popup telling, for example: "missing in _it, _ru, _fr".

2) a good way to deal with this issue could be having intention actions to fill a property file with one or all properties missing, populated with some sort of placeholder value.

0
Comment actions Permalink

Hi,
May be not coloring, it was first thought in visualization.

Kind of intentions planned but where to place newly created properties and other details not decided for a while.

TIA,
Dmitry

0
Comment actions Permalink

I haven't noticed this before, but I really like the light-grey dots which line up the key-value pairs. Nice touch!

0
Comment actions Permalink

Hi,
It's not me :)
IDE Settings->Editor->Display->Show whitespaces

Or you mean something else?

TIA,
Dmitry

0
Comment actions Permalink

It only appears in the PropertiesEditor, not in other editor screens.
In the attached image you'll see the light colored dots



Attachment(s):
pe_whitespaceing.gif
0
Comment actions Permalink

Dmitry,

Thanks; That was the case. I am incredibly impressed with this plugin! I ran my Resource bundles through compare/merge tools over and over throughout the development of my project, yet somehow three different properties in different resource bundles managed to get out of synch and the errors are now in the Live deployment!! From now on though, this wont be an issues thanks to your amazing plugin.

Just one small issue. I use Source Safe integration on my project and when trying to edit the second properties file it doesn't prompt to check it out.

Thanks again

Scott

Hi,

Most probably you have in directory with editing file another that can
be in bundle with source. And in some of files marked as red
properties doesn't present.

(It was description of intended behaviour, your case description
highly appreciated)

TIA,
Dmitry


-- Posted by JetBrains OmniaMea

0
Comment actions Permalink

Hi,
It's exactly that feature I'm described, but in my editors this dot's showing even if setting not activated.
If problems with it will occure I'll use system setings in future.

TIA,
Dmitry

0

Please sign in to leave a comment.