Re: [ jEdit-devel ] Clear Properties Macro

[Shlomy R. <sre...@gm...>]

As far as I recall, the plugin's cache is built only when the plugin
is loaded, and contains only objects that are included in the jar, not
anything that is created later during runtime.

To continue what I wrote in the other email, I think that cleanup of
stale objects should not be automatic, as it's too risky. Instead,
there should be a tool to present it to the user in the most
user-friendly way possible, and let the user to decide what to delete
and what to keep.

Similar to my suggestion with project dependency types, it would be
useful if each property was registered with jEdit, associating it with
a meaningful description and the jar file that uses it (perhaps
several jars). This would help the user understand which properties
might still be needed, and in addition, jEdit would be able (with some
overhead of course) to remove properties that are no longer needed -
if all plugins that used a property are loaded, and the property is
not registered by any plugin, it can be removed.

Shlomy

On Sun, Jan 31, 2010 at 5:36 AM, Damien Radtke <dam...@gm...> wrote:
> It does make a backup; it saves the properties file to properties.orig. And
> it's based on a fixed set; anything defined in the property files that come
> with jEdit or in any plugin's property file will be kept. I understand that
> it's somewhat risky, but I posted it to jedit-devel with the idea of making
> it less so. This was partly in response to your comment in the other
> conversation about there not being a way to clear out unused properties, and
> so this was my first step in attempting to accomplish that.
>
> Regarding properties defined dynamically, if there is a way to save those in
> the plugin's cache then there's no problem, because each plugin's cache is
> where the macro searches for properties to keep, not necessarily in the
> hard-coded .props file.
>