From mboxrd@z Thu Jan 1 00:00:00 1970 From: dexen deVries To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Date: Tue, 12 Jul 2011 17:26:28 +0200 User-Agent: KMail/1.13.6 (Linux/3.0.0-rc6-l34+; KDE/4.5.5; x86_64; ; ) References: <201107121631.05140.dexen.devries@gmail.com> <20110712155612.5b174266@lahti.ethans.dre.am> In-Reply-To: <20110712155612.5b174266@lahti.ethans.dre.am> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201107121726.29100.dexen.devries@gmail.com> Subject: Re: [9fans] interesting(?) widgets idea Topicbox-Message-UUID: ffc1ccec-ead6-11e9-9d60-3106f5b1d025 Ethan got me thinking there :-) consider a window consisting of text area and some widgets around it. instead of making the widgets as small as possible, render as margins when = not needed. most, or all, window's widgets would be rendered as solid background color = (functionally margins) when user is reading or typing text. when user wants to activate any widget, actual menus, scrollbars, statusbar= etc. would be drawn. if the user hovers mouse over widget area, it would be understood as intent= ion to activate widgets, triggering their visibility. some symmetry of the left/right and perhaps top/bottom would be called for. one downside is that the widgets would literally `flash' in and out of user= 's vision, possibly irritating or tiring him. in other words, all the widgets (menus included) of an app turned into marg= ins when mouse's /not/ over those widgets. =2D-=20 dexen deVries [[[=E2=86=93][=E2=86=92]]] =46or example, if the first thing in the file is: an XML parser will recognize that the document is stored in the traditional= ROT13 encoding. (( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))