Hey Adrian, 2009/5/5 Wim Dumon <[email protected]>: > I would say to use Wt's server push capabilities to render updates to > the screen, and to attach slots to the key signals. I would write it > all in C++, and first do a version without custom JavaScript, which > updates the entire viewable area on every update. There's a good > chance that you will decide it is good enough. Lateron, you could > provide some optimizations with custom JavaScript (e.g. provide > functions to do scrolling, or update a single line on the client > side). > A separate thread can also interact with Wt widgets provided that it > grabs the global update lock (see documentation of WApplication), so > that part of your architecture is ok.
You could perhaps start with a separate widget per line. In that way you can more easily upgrade to smarter rendering strategies: - scrolling by deleting/adding lines - partial updates based on a specific line. Sounds like a fun project (except for the terminal handling part time-warp :-) ) Regards, koen ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
