[ANN] PropertiesEditor Plugin 1.7.1

Description:
Editor for properties files like built-in editors (highlighting, navigation, find usages, intentions, properties files specific features, bundle editing mode etc.)

Changes:

  • Export searching for unused properties result

  • Pallada 2072 compatible (I'm hope at least in reported place ;) )

  • Minor improvements and reported bugs fixes


TIA,
Dmitry

15 comments
Comment actions Permalink

Dmitry Kashin wrote:

Description:
Editor for properties files like built-in editors (highlighting, navigation, find usages, intentions, properties files specific features, bundle editing mode etc.)

Changes:

  • Export searching for unused properties result

  • Pallada 2072 compatible (I'm hope at least in reported place ;) )

  • Minor improvements and reported bugs fixes


TIA,
Dmitry

cool plugin ...
one small enhancement would be a Autoscroll from Source

regards

cK

0
Comment actions Permalink

Hi,
You mean scroll in key navigation tree? If it required most possible will be implemented.

TIA,
Dmitry

0
Comment actions Permalink

Christian Köstlin wrote:

Dmitry Kashin wrote:

>> Description:
>> Editor for properties files like built-in editors (highlighting,
>> navigation, find usages, intentions, properties files specific
>> features, bundle editing mode etc.)
>>
>> Changes:
>> * Export searching for unused properties result
>> * Pallada 2072 compatible (I'm hope at least in reported place ;) )
>> * Minor improvements and reported bugs fixes
>>
>> TIA,
>> Dmitry


cool plugin ...
one small enhancement would be a Autoscroll from Source

regards

cK


I agree. It would be a nice feature. For some reason I expected it to do
this for properties editing even though I always disable autoscroll
everywhere else in Idea.

But nevertheless its a great plugin. I have now used it to find several
inconsistencies in my properties files in different projects.

Keep up the good work.

regards

Anders Holmbech Nielsen

0
Comment actions Permalink

Hi,
How about directions of further development?

TIA,
Dmitry

0
Comment actions Permalink

Gladly :)

1. print / copy to clipboard unused properties list.
2. CtrlAltU under Analyze menu in Pallada
3. Make Rename button in the usages pane consistent with IJ respective
refactor button, so that renaming a class and a property will be more
similar.
4. Expand functionality to other editors. For example, if I am editing an
XML that has a reference to a resource (property), I want to be able to
search usages and rename it from that point. I also want to press Ctrl+B and
go to the definition of the property. Same from any other file.
5. In the CtrlAltU panel, allow not only deletion of properties but also
commenting them out.
6. Background button for searches (like in IJ searches)
7. Configuration of linkage between property files and directories (with
recursive option) or files and according to some regular expression, and
base intentions or inspections on it. For example, We have XML files that
link to a resource file. The contents of some specific tag names are
references to properties from that specific resource file. We also have a
wrapper class for loading resources that returns property values. If we can
configure the system to be aware of these connections instead of relying
only on text searches, this would make it a much stronger system. You could
do things like a red underline under a non existing property. You could more
easily understand what is a property reference and what is not. This is a
big feature but it would be very powerful.

I should say again that we use PE daily, it is a life saver with our 4000
entry property file.

Amnon


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

Hi,
How about directions of further development?

>

TIA,
Dmitry



0
Comment actions Permalink

Export to file dialog issues:
1. When there are many unused entries, the dialog is too high. I had to
resize it and drag it as the buttons were under the task bar.
2. What is selection for?
3. Could it remember the last file path?

Amnon


0
Comment actions Permalink

Hi Amnon, welcome back :)
1. Will fix, but it must remember it's last size right now.
2. You can copy it to clipboard.
3. I'll look into.

TIA,
Dmitry

0
Comment actions Permalink

Dmitry Kashin wrote:

Hi,
How about directions of further development?

TIA,
Dmitry


Heres something:

- After using the "unused properties list" there is now way to get away
againg. I saw the "x" icon and thought it did as the "x" icons on ie cvs
and find, but indstead it deleted one of my properties.

- It could be cool to have some way to define collections of properties
files. In one project I have 3 properties files to each of out server
environments which are named something like:
test_blabla_1.properties
test_blabla_2.properties
test_blabla_3.properties

prod_blabla_1.properties
prod_blabla_2.properties
prod_blabla_3.properties

where both the 3 test properties have the same properties files and also
have the same properties file as those named prod*.

regards

Anders

0
Comment actions Permalink

Hi Anders,
You suggest change icon or add close action? You may revert changes by invoke undo action.

Your second request not fully clear. You mean that something like bundle editing required? If your files in one folder they automatically added to bundle and edited together.

TIA,
Dmitry

0
Comment actions Permalink

Dmitry Kashin wrote:

Hi Anders,
You suggest change icon or add close action? You may revert changes by invoke undo action.


I think adding an close dialog icon like in the find dialog would do the
trick. But then the "delete property" icon may look too much like the
close dialog icon. But we'll see.


Your second request not fully clear. You mean that something like bundle editing required? If your files in one folder they automatically added to bundle and edited together.


Well - they sort of do. I have 9 properties files in the same dir but
only 3 of the is opened and i sorta guessed that they are opened in
bundles that matches their names. ie:

the 3 files:
test_blabla_1.properties
test_blabla_2.properties
test_blabla_3.properties
are opened in a bundle

and
prod_blabla_1.properties
prod_blabla_2.properties
prod_blabla_3.properties
in another bundle.

But I would like some way to define that all these properties belong
together and have them opened in on bundle.


TIA,
Dmitry

0
Comment actions Permalink

Hi,
Actually 1 st issue fixed in 1.7.1a (I'm think so).

About 2 I'm affraid it won't not possible in near future :(

TIA,
Dmitry

0
Comment actions Permalink

Hi,
About 4 there are some troubles in it implementation. It partially done but on project open I'm not able iterate over file list and I'm determine all bundles and keys set after first properties file parsing. This process may take a long time but due some problems I'm not able use Progress API here.
It's very usefull feature even now and in future can help make thing even more better but first steps is not so good and I'm don't know release partial implementation with specified issues or not :(

Feedback highly appreciated. (Especially from Amnon Govrin as author of the request)

TIA,
Dmitry

0
Comment actions Permalink

The way I imagine it, a rename (for example) is how this may be implemented:
1. User selects string (in Java, XML, etc.).
2. User asks to rename resource.
3. PE does a search of that resource just like the usual (without initially
knowing if it's even a resource or not), after validating that the selection
might be a resource id (i.e. not empty, not with double quotes, etc.).
4. If resource wasn't found in any property file, you can tell the user that
it is not a resource. If it is found in a property file, we can rename it.

Does this make it clearer?

Amnon

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

Hi,
About 4 there are some troubles in it implementation. It partially done

but on project open I'm not able iterate over file list and I'm determine
all bundles and keys set after first properties file parsing. This process
may take a long time but due some problems I'm not able use Progress API
here.

It's very usefull feature even now and in future can help make thing even

more better but first steps is not so good and I'm don't know release
partial implementation with specified issues or not :(
>

Feedback highly appreciated. (Especially from Amnon Govrin as author of

the request)
>

TIA,
Dmitry



0
Comment actions Permalink

Hi,
It's not IDEA like :(
And may takes a long time on every invocation(for example Ctrl+B or completion). So full parsing and bundles resolving is required anyway and this will happen only one time per project open and sounds better.
If not locks without progress bar and project opening issues... :(

TIA,
Dmitry

0
Comment actions Permalink

Well, we might not understand eachother very well. I count on you to do the
right thing to implement this, so assume I just didn't understand your
explanation.

I'd be happy to test any stage of it if you would like that.

Amnon

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

Hi,
It's not IDEA like :(
And may takes a long time on every invocation(for example Ctrl+B or

completion). So full parsing and bundles resolving is required anyway and
this will happen only one time per project open and sounds better.

If not locks without progress bar and project opening issues... :(

>

TIA,
Dmitry



0

Please sign in to leave a comment.