The User Interface
To discuss (among others, not yet listed here)
Here opens the discussion of how and what to extract from the webpage to get content for the print manual.
Some structural issues to find an optimal way to organize the information
(max) Not so very confinced, but... how about some kind of public rating system? like "did this solve your problem?"
(ampop) the tiki has a built in rating system. should we enable it?
Design issues. I assure you, that it will be perfectly readable and that I'm not going to use just black and white as "colours".
(max) yeah, grey, too! (As I'd generally vote for a Version that's also a PDF, that means that the basic color schemes should be B/W-Printer-friendly, too! On paper, color costs.
(ampop) the color cost issue is a big one. but color is needed by example patches, project exibition, diagrams, etc... and color makes things prettier
(sbn)but should really be backwards compatible with b/w copies. patterns!
(max) A few Preferences for the choice of engine:
Open Source over Proprietary: OpenOffice, Ghostscript rather than PDFLib, FrameMaker, InDesign et al.
(ampop) I would also prefer OpenSource Tools. I'll have to do some recherce!
What about multiplatformability? PDF ranks first. after that, nothing. or?
(ampop) Just PDF. What else? Seond Option is html which is this page.
Hellö - does someone have a RealSense R200 or SR300 in Germany that could be bought or rented for two weeks?
@mrboni, thanks i filed us a bug
@ joreg - i sent you a patch
reg video signal extension: I made a post collecting all your inputs
windows gesture nodes work just with dx9?
Hd SDI, you can get HDMI-> SDi convertors easily, and BNC will run 100's of meters
@dottore: a friend of mine (mfx) suggested a pair of Kramer TP-580 transmitters and a HDBaseT cable. 4K at 100m.
@dottore it has to be 6G-SDI to handle 4k
checkout my stuff
follow on twitter
| Page created by
, last modification by
on 01.06.10 [14:56 UTC], read 1884 times