Export as HTML, RTF, ...

[Ceniza]

I've been considering to write a plugin to export the current opened file in Code::Blocks with highlighted syntax to HTML, RTF and maybe some other formats, just like Dev-C++ and SciTE do.

I've spent a lot of time trying to get all I need to extract the information from the wxScintilla component and Code::Blocks itself so I can get the colors and style.

ATM I've only needed to add a GetColorSet() method to get m_pTheme from cbEditor and it seems to be the only decent way to get what I need, and the only thing I'd really need to be added in the SDK (I hope).

Any complaints, ideas, support, ...?

[mandrav]

No problem for me, after RC2 of course.

[Ceniza]

It seems like that will be really the only needed change in the SDK to get the plugin working.

I've made a few tests, played a bit with some stuff and everything else I'll need is in there.

mandrav: Would you really mind to add that function before RC2 is released? It won't change any behavior of it.

Code Select Expand

EditorColorSet* cbEditor::GetColorSet()
{
  return m_pTheme;
}

EDIT: Yeah, forgot why: the idea is to get it done maybe, just maybe, before RC2 is released or at least have RC2 ready for it.

[mandrav]

Done

[Ceniza]

Done

Oh, great!

I just finished the first version of it.

It currently exports HTML and seems to be working fine. I still need to add some more things to get it more "real" (WYSIWYG).

A sample file is here

mandrav: would you mind to add this to contrib?

[mandrav]

mandrav: would you mind to add this to contrib?

Done.
I hope you don't mind, I converted it to cbPlugin and now creates a "File->Export to HTML" menu item.
Btw, very nice work 

[Ceniza]

mandrav: would you mind to add this to contrib?

Done.
I hope you don't mind, I converted it to cbPlugin and now creates a "File->Export to HTML" menu item.
Btw, very nice work

Heh, in the first tests I was doing something similar (adding it in the File menu) but then decided to make it more... er... plugin-like.

Having it in the File menu will make it consistent 'cause there's where ppl can find it in both SciTE and Dev-C++, so I don't really mind the change.

Last night I was checking some other minor things so it'll also export the font (name and size). This should be ready today.

I just hope you didn't forget to give me access to the plugin in CVS, oh, and still have access to the other two

[mandrav]

I just hope you didn't forget to give me access to the plugin in CVS, oh, and still have access to the other two

I hope I haven't

[Ceniza]

I just committed the latest changes and CVS didn't complain

Changes include:

* Current font type and size exported to the HTML file.
* Background colors also exported.
* Applied my coding style to mandrav's changes
* Removed the unnecessary checking mandrav pointed out (because of the new way to execute).
* Probably a few bugs introduced in the code

[squizzz]

HTML, RTF and maybe some other formats

Others, like Open Document Format for example?

[Ceniza]

Others, like Open Document Format for example?

I'mn't any familiar with that format, but yeah, it could be part of other formats.

I'll consider it

[rickg22]

OpenDocument format is the format used by OpenOffice, KOffice and other OpenSource word processors. There was quite a political stir when the state of Massachusetts rejected the Microsoft format in govt. offices for an open document format to avoid vendor lock-in. The OpenDocument format is XML based, and currently is proposed to be an ISO standard.

[Ceniza]

I just tried converting a RTF file (generated with Dev-C++) to ODT and it's too bloated.

I think the ODT format will have to wait some time until I get enough information to generate it in a simple, non-bloated, way.

I hope to get the RTF format soon though.

[Urxae]

I think the ODT format will have to wait some time until I get enough information to generate it in a simple, non-bloated, way.

I haven't looked at the details myself, but the information is probably available somewhere on this site.

[squizzz]

I think the ODT format will have to wait some time until I get enough information to generate it in a simple, non-bloated, way.

I'm afraid that everything XML-based is bloated by default. The good thing is that it usually compresses very well (*.odt uses zip compression I think).

There was quite a political stir when the state of Massachusetts rejected the Microsoft format in govt. offices for an open document format to avoid vendor lock-in.

Yeah, that's when I've heard of this and decided to switch. (btw. OOo 2.0 itself is good enough reason to switch )

Anyway, great thanks for the plugin.