From: Dominik K. <dom...@un...> - 2000-03-07 14:42:30
|
On Tue, Mar 07, 2000 at 09:31:06AM -0500, James Simmons wrote: > > This would be really nice. I don't have any manuals for various terminals > so it would be nice if you could send them to me. Or better yet if we get > them on the projects web page. If it's legal. > Well, i can not send them and i think scanning and putting them on the web is also a no-no. So i will act as a document server for these docs... ;-) I always intended to have the function description in the source right at the start of the function... > Yeap. I like to see this too. Eterm for the console :) So a great step > forward would be to move terminal emulation into a seperate file. Write a > common interface for terminal emulation and write a nice HOWTO to create > a terminal type. Either that or provide a way for userland to shape the > terminal to the type it wants. I like to see that also in a seperate > file. Which do we think is better to do? A userland interface to set the > console to some type of emulation or provide a interface so someone could > write their own terminal emulation module. I kind of like the userland > solution. It coudl get bloated really quick. Make the terminal emulation a loadable module. Have the console driver look for module "vte" and then you can use the alias mechanismen of modload to push the appropriate module. If that fails fall back to dumb line mode (similiar to the framebuffer initialization). Does that appear a workable solution? Dominik |