From: Francesco M. <f18...@ya...> - 2005-09-04 21:06:08
|
> 'window container', 'dialog', 'control', 'window layout', > 'networking', 'stream', 'database', > 'data container', > 'graphics' > 'text processing' > 'printing' > 'import/export' > 'system', > 'tutorials/documentation' , > 'application' > 'miscellaneous', > 'wrapper' > >>>I added >>>graphics, text, and system (hardware and platform dep stuff here), >> >>I think it's a good idea group together platform-dependent stuff but I don't know if >>"graphics, text, and system" are good names; they sounds too generic for me... >> >>wx docs have a "device contexts" category; maybe this is better than "graphics" (even if >>to be honest "device contexts" sounds a little bit too specific for me ;-)) > > > I think graphics could cover wxImage stuff and wxDC anything to do > with drawing and images, wxPlot could go here then. wxPDFDocument > could be import/export and graphics. after looking at the component list, I see that it's not so generic.... so it's okay for me. >>text what would group ? > > Text processing, wxScintilla, wxSpellcheck... ok, "text processing" is a better name ;) >>system instead would be useful, for example for UnixfileDataClass; however to make it >>clear it's platform dependent stuff I would call it "system-dependent"... > > > I think just calling it "system" would allow it to cover wxCTB (serial > port) as well as filesystem stuff, there will probably only be a > couple of these. the best option would probably to create something like "hardware" for wxCTB but I think wxCTB would be the only component inside it :-) So "system" is okay, after all. Francesco |