EditorColorSet* cbEditor::GetColorSet()
{
return m_pTheme;
}
Done :)
mandrav: would you mind to add this to contrib?
Quotemandrav: 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 8)
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
HTML, RTF and maybe some other formatsOthers, like Open Document Format for example? :)
Others, like Open Document Format for example? :)
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 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 :P )
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).
Anyway, great thanks for the plugin. :D
Dealing with it I found there's no OptionColor object with value 11 in Code::Blocks' C/C++ color theme and it's used everywhere in wxScintilla (at least everywhere no special formatting is applied to the text).
11 is for "identifier". This means, according to my tests, every word that is not a keyword. So, we use the default text attributes for it.
There are a lot of styles in scintilla, depending on the language.
In PDF? But you can't embedd fonts inside a PDF (I don't remember well, but PDF wasn't a vectorial format?).
For ODT also, you can't embedd fonts?
All I know is wxPdfDocument has limited font support.That's not exactly true. By default wxPdfDocument supports the standard Adobe fonts, i.e. Courier, Times, Helvetica (=Arial), Symbol and ZapfDingBats. Additionally Type1, TrueType and TrueTypeUnicode fonts are supported if the user provides at least font metric files. Usually these fonts have to be embedded in the PDF document. What's missing in the current version of wxPdfDocument is a tool to create these font metrics files from AFM or TTF files.
I tried Courier and it works fine (but it knows nothing about "Courier New"). In fact, SciTE uses Helvetica as output for PDFs. wxPdfDocument developers seem to be working in some kind of solution, but I don't know the details.Courier New is essentially Courier, no need to embed the font Courier New unless you need Unicode or foreign language support; Helvetica should work without problems, too.
Regards,
Ulrich
(Developer of wxPdfDocument)
I would be very very careful about embedding fonts or font-related information in a PDF.
Certain companies can be get very nasty if you do that. Remember some companies even regard adjusting character stem widths or the mere drawing of cubic bezier curves as a violation of intellectual property.
Regards,
Ulrich
(Developer of wxPdfDocument)
Wow! :shock: It is an honor having you here! :) Welcome!
Wow! :shock: It is an honor having you here! :) Welcome!Ditto.
The question is: there will be a way to embed the fonts just by calling a class method and providing the font face name without calling external utilities?
Oh, could I also suggest wxPdfDocument's makefile allow static compilation using dynamic wxWidgets? I've got a working one already and seems to be working just fine.
Do you mean to compile wxPdfDocument as a static library while using wxWidgets as a shared/dynamic library?
Of course you always could simply add the wxPdfDocument source files to your own project.
pdf.Cell(pdf.GetStringWidth(text), 4, text);//, wxPDF_BORDER_NONE, 0, wxPDF_ALIGN_LEFT, 1);
Quote from: utelleDo you mean to compile wxPdfDocument as a static library while using wxWidgets as a shared/dynamic library?Yep, that's what I mean.
I've been working on the PDF exporter and it's... exporting, but I've been unable to allow text background to be drawn correctly, if any.
Codepdf.Cell(pdf.GetStringWidth(text), 4, text);//, wxPDF_BORDER_NONE, 0, wxPDF_ALIGN_LEFT, 1);
That's my current text drawing call (ugly hack to get it working). If I enable the commented piece, some of the previous text will be also painted white (or should I say erased?).
Any idea?
Could you please explain, what you are trying to accomplish?
In the editor, you can choose a background color for something, lets say... strings: blue text on black (I know they don't mix, but it's just an example).
[...]
I just played with those values and they seem to be causing the white border around that's deleting some of the previous written text.
In a few words: I set a font, style and color. Write some text using that function. Change style and color. Write some more text, and so on.
I hope it be of any use so you can track down the problem.
...
I committed the PDF exporter a few hours ago, even though I had some problems adding the folder with wxPdfDocument sources.
...
...
I just removed that function call and 1 is gone.
...
So, in save dialog, FileName field - empty string.
Why not set it an exported fileName (w/o extention, or with extention, need see)?
Ok, I just committed the changes to CVS. It should be visible for anonymous CVS in a few hours.
Ok, I just committed the changes to CVS. It should be visible for anonymous CVS in a few hours.
The method Write is the one that should be used there, but it's adding a lot of spacing between text and wouldn't allow me to add a background (I'd say the spacing is a bug in Write).
Cell isn't breaking line when it reaches the right margin, but it allows me to put a background (which currently I disabled due to the white border that erases the previous text).
2 will have to wait for a fixed Write, a fixed and smarter Cell, a fixed Write with a background option or a new function doing that.
I'll just commit that change and with my head in my hands I'll sit and cry.
I have trouble with my russian symbols in PDF, will see later.
Version 0.6 of wxPdfDocument including the fixes mentioned above and several other enhancements is available for download. The API documentation has been updated accordingly.