Windows FB Printing Lib
Windows FB Printing Lib
Is there a need for this? If so, I would like to give a crack at it.
What would you like to see in a printing lib?
Easily select target printer
printing and drawing commands
Easy to access printer object and properties
What else?
-Vince
What would you like to see in a printing lib?
Easily select target printer
printing and drawing commands
Easy to access printer object and properties
What else?
-Vince
Last edited by vdecampo on Sep 13, 2007 21:51, edited 1 time in total.
Re: Definitive FB Printing Lib
a easy way to generate html and PDF documents ;)
maybee look at htmldoc and others
i often write html and then let the result convert to pdf
have fun Thomas
maybee look at htmldoc and others
i often write html and then let the result convert to pdf
have fun Thomas
-
- Posts: 360
- Joined: Jun 07, 2005 20:59
- Location: england, somewhere around the middle
- Contact:
Well since this will be using the Windows API, making it cross compile will be difficult to say the least. I will concentrate on Windows and leave Linux compatibility to someone else.Hexadecimal Dude! wrote:cross platform, (at least windows + linux). Enough control so that your program can specify how the printed page should look accurately.
This RTF printer may be a good addition to the library.
http://www.network54.com/Forum/183705/m ... +FreeBasic.
http://www.network54.com/Forum/183705/m ... +FreeBasic.
-
- Posts: 1759
- Joined: May 23, 2007 21:52
- Location: Cut Bank, MT
- Contact:
You could try using wx or something else, perhaps... I think cross-platform is essential if you want to make a definitive, "official" library for FreeBasic. If you must use the windows API, try to use it minimally - create an interface module that interfaces the windows API directly, and have the rest of the library use cross-platform resources only. That way, it will be easier to port to other platforms.
FB is usint the standard libs everywhere, I'm against of using wx or something like this.
Printing is 90% about calling the API, at least in windows (how do yo do formatted printing in Linux? Postcript?), so no way of separating the OS-dependant functions in a module...
I guess a portable library will be two libs in a wrapper.
Printing is 90% about calling the API, at least in windows (how do yo do formatted printing in Linux? Postcript?), so no way of separating the OS-dependant functions in a module...
I guess a portable library will be two libs in a wrapper.
-
- Posts: 1759
- Joined: May 23, 2007 21:52
- Location: Cut Bank, MT
- Contact:
Come to think of it, I also think using wx would probably be a bad idea - it was just a suggestion.
Probably the best thing to do is have a standard interface for applications, then a separate module with the system calls. Unfortunately, like Antoni said, it probably will be 90% API calls, so I don't know... I guess if you want to make a Windows-only library that's fine, just don't call it fbprint or the like if it's not going to be cross-platform. Perhaps other users will be able to write libraries for other platforms with the same interface, then perhaps it could become the official fbprint library.
Probably the best thing to do is have a standard interface for applications, then a separate module with the system calls. Unfortunately, like Antoni said, it probably will be 90% API calls, so I don't know... I guess if you want to make a Windows-only library that's fine, just don't call it fbprint or the like if it's not going to be cross-platform. Perhaps other users will be able to write libraries for other platforms with the same interface, then perhaps it could become the official fbprint library.