So I just have to ask...

[DiapDealer]

Any plans/provisions for editor plugins?

Custom routines able to be applied to current/selected files would be a dream come true!

[kovidgoyal]

Sure adding support for plugins into the editor is fairly trivial, since it's in python. But I dont still have a good idea for what sorts of functionality to expose via the plugin API, since no one has floated any particular ideas for plugins yet. What would you write plugins to do?

[DiapDealer]

My own personal needs wouldn't be that elaborate: just the ability to launch a dialog that lets me input various criteria to parse/modify the (x)html of the selected file(s). Mostly for the purposes of cleaning: removal of empty/extraneous spans/divs, etc...

Give me a menu to launch a plugin's dialog (if it needs a dialog), a handle to the selected file (or a list of the selected files), and maybe a way examine the results of my meddling before "committing" and I'd be happy as a pig in mud!

[kovidgoyal]

Sure, should be no problem. I'll get around to it eventually. Writing the plumbing for the plugins is a bit of a chore, it will have to wait for when I'm bored with other stuff.

[DiapDealer]

it will have to wait for when I'm bored with other stuff.

Perfectly understandable.

[theducks]

Originally Posted by kovidgoyal

Sure, should be no problem. I'll get around to it eventually. Writing the plumbing for the plugins is a bit of a chore, it will have to wait for when I'm bored with other stuff.

You must have very high ceilings in your office,

Because your 'to do' bin gains 2 items for every 1 you take out.

I can't imagine you have time to get 'bored'

[kovidgoyal]

Originally Posted by theducks

Because your 'to do' bin gains 2 items for every 1 you take out.

It's nice not to have to worry about what I'll be doing tomorrow

[DiapDealer]

Probably wouldn't hurt to toss in hooks to the NCX and OPF as well.

Would it make sense to be able to access all files in the ebook via some sort of iterable dictionary or class structure?

for sheet in book.css:
  if sheet.name == file_name_parsed_from_link_in_current_xml:
    do_stuff

With the ability to add/remove files to the ebook's structure?

Just spitballin'.

[theducks]

:baloon3: I would like a text sequencing tool
That could generate sequences in a Search and Replace situation since REGEX can't do this(math or increment).

Search; (<body.*>)
Replace: \1<h3 class="chapno"> Chapter <sequential value> </h3>

[DrChiper]

I like a recording facility to record / playback repeating tasks like often used search & replace sequences. Kind of macro's as in popular editors.

[BetterRed]

Originally Posted by DrChiper

I like a recording facility to record / playback repeating tasks like often used search & replace sequences. Kind of macro's as in popular editors.

Me too - I've been assuming it would be on the list of todo's for the Editor core.

Would spell checkers be a good candidate for plugins, i.e. different PI's for different languages.

BR

[eschwartz]

Originally Posted by BetterRed

Me too - I've been assuming it would be on the list of todo's for the Editor core.

Would spell checkers be a good candidate for plugins, i.e. different PI's for different languages.

BR

That would be a good candidate for the built-in plugins.

[BetterRed]

Originally Posted by eschwartz

That would be a good candidate for the built-in plugins.

Which 'That' would that be then Macros or language specific spell checkers ?

I would have thought that some day the former would be in the core, I don't care if its plugged in or bolted on

BR

[AnotherCat]

Originally Posted by BetterRed

Which 'That' would that be then Macros or language specific spell checkers ?...

Strine and New Zild dictionaries at least .

[BetterRed]

Originally Posted by AnotherCat

Strine and New Zild dictionaries at least .

Strewth - that'd be bonzer cobber, should only take a wee while.