Re: [ jEdit-devel ] Revisions to installation macros

[Slava P. <sl...@je...>]

On Wed, Nov 07, 2001 at 03:22:17AM -0500, John Gellene wrote:
> Sure, that's fine. The changes that I found were necessary were
> 
> (1) textArea.addSelection() instead of textArea.select();
> (2) buffer.insert() instead of buffer.insertString();
> (3) DockableWindowManager.getDockable() instead of getDockableWindow().

You might want to mention the new APIs that should be used in favor
of the Swing Element stuff. Also, any macros that call
physicalToVirtual()/virtualToPhysical()/getVirtualLineCount() on
buffer instances now need to call this on the text area.

The changes for plugins are a bit more involved.

> Maybe I'm the only one who does this, but I use this macro to have other
> macros work like abbreviations.  It lets you do shortcuts to macros that are
> easier to remember.  For example, I assign "bname" as an abbreviation to the
> relative path of a one line macro that calls Buffer.getBufferName(). I also
> assign C+SPACE to Run_Macro_At_Caret.  Then I can type "bname", press space
> to expand the abbreviation, and C+SPACE to run the macro.  Much easier than
> trying to remember whether to press A+F12 or CS+F11.  I keep these shortcut
> macros in a separate subdirectory of the user macro directory.
>
> I would keep this one unless we are going over our limit.

I think it is a bit confusing. I still suggest you move it to the
archive, along with some example macros for use with it.

> I got the script thanks to Mike Dillon finding the link in the mailing list
> archive.  I also got your later post suggesting some modifications
> occasioned by API changes.  I will put something "nice looking" together.
> That would make 30 macros exactly.

Sounds good.

> If you put the wrapper methods in for dockable components, I'll do another
> round of revisions.  Then we can move the non-keepers to the CVS Attic and
> I'll use my local copies to post them on jEdit Community.

I'd rather not add wrappers to the view class.

Right now, my main priority is updating the documentation. I would
like to update the first part of the user's guide for the new features,
and sprinke in some indexterms. I would also like to write a 3.2 to
4.0 API porting guide. We can also both start updating the macro and
plugin guides; I think these will be finished up later in the 4.0
series, along with more comprehensive indexing throughout the user's
guide. pre2 will have the necessary support in the help viewer to
support index browsing and searching.

Do you think it is worth using
http://jakarta.apache.org/lucene/docs/index.html to implement
searchable online help?

Slava