ms2@doc.ic.ac.uk (M Shelley) (11/24/90)
I'm just a poor humble student who is just learning about X windows. I am just about to start writing a MacWrite style word processor that will run on Sun 3's under X windows, and I was wondering if anybody has any source code that might be interesting to look at. I will be using the toolkit widgets and so I suppose that xman is a good starting point? Or might it be a better idea to learn to use Motif? Also, I know that X uses pixel based fonts. Could anybody tell me anything/direct me to any information about vector font usage (i.e. where you specify the line that make up the characters, rather than the bitmap image of it.) I guess that laserprinter output will be a good idea, so is postscript the right thing to use? If so are there any good books on it? Cheers Martin ------------------------------------------------------------------------ --------- MArtin Shelley email: ms2@doc.ic.ac.uk Department of Computing Imperial College Dog and Bone: +44 (0)71 373 6127 London SW7 ------------------------------------------------------------------------ --------- Why do they call me MASh? ------------------------------------------------------------------------ --------- Q: How many IBM CPU's does it take to execute a job? A: Four; three to hold it down, and one to rip its head off.
mouse@LARRY.MCRCIM.MCGILL.EDU (11/24/90)
> Also, I know that X uses pixel based fonts. Could anybody tell me > anything/direct me to any information about vector font usage Core X does not have anything of the sort; if you want any sort of vector-based fonts you have to do them yourself. Various extensions support such things to varying degrees (for example, DPS does pretty much everything you could want). Of course, using extensions reduces portability. > I guess that laserprinter output will be a good idea, so is > postscript the right thing to use? Ick. I cannot in good conscience recommend it, but there really is no good single alternative. What I would actually suggest is that you produce some sort of printer-independent output (perhaps even just the internal representation), and provide programs to convert this to PostScript, Impress, whatever it is the Laserjet speaks, raw page bitmaps, etc., or alternatively modularize your program so users can simply drop in a new printer-support module for their printer if none of your supplied modules suffice, and then your "create printer file" command has some way to choose which printer-language support module is to be used. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu