Martin Sevior wrote:

>Hi David,
>        I've been thinking about this too. I think we should at the very
>least call a halt to changes to abiword's UI in the very near term.
>
>So abiword won't change how it does the things it does. Regarding new
>features I know of a number of projects in varying stages of completeness.
>
>1. RTF import/export => Still need header export, Lists import/export
>needs improvement.
>
>2. TOC Dom expressed an interest in doing this.
>
>3. Perl scripting, Joaquin keeps on pumping out new and useful code here
>that will help us with plugins and embedding as well as Perl scripting.
>Maybe Joaquin could give us an update?
>
That's mostly finished.  The only points that are still lacking are 
keybindings, selecting new positions next a know item, and delete items.
I don't plan to implement right now the last one, but I will implement 
the first & the second one asap.

In the perl scripts front there are still some work to be done:
* I should make work the XS wrappers in windows
* Finish make install (this one it's easy)
* Rationalize a bit more the exposed API.
* Make it a plugin.

But basically now it's good enough (in unix).  When points 2 & 4 will be 
finished, I would like to start distributing binaries and start getting 
feedback from outside perl hackers.

I would also write some little & useful scripts, to make the download & 
install of perl wrappers worth it (I'm taking suggestions here), for 
instance a script that takes a C file and writtes in the current abiword 
document with a correct indentation & colouring key words (I need 
something like that for my "exposes").

>5. Plugin's, inparticular Aikasaurus. This is a really cool feature from
>Jared Davis.
>
btw, I've changed AikSaurus to make it compile with the latest changes 
to the menus that I've done.  I will send a patch asap.
(Can I commit directly, or should I first send a patch to Jared for peer 
review?)

Cheers,

--
Joaquin Cuenca Abela
[EMAIL PROTECTED]



Reply via email to