Xcurses - revision history

Dank: /* See Also */

2020-02-19T23:46:06Z

Dank at 03:24, 18 October 2019

2019-10-18T03:24:23Z

← Older revision		Revision as of 03:24, 18 October 2019
Line 73:		Line 73:

	==See Also==		==See Also==
	[[TANGE]]		* [[Outcurses]] which is actually going somewhere
			* [[TANGE]]

	[[CATEGORY: Projects]]		[[CATEGORY: Projects]]

Dank at 03:23, 18 October 2019

2019-10-18T03:23:22Z

← Older revision		Revision as of 03:23, 18 October 2019
Line 73:		Line 73:

	==See Also==		==See Also==
	* [[TANGE]]		[[TANGE]]
	* [[Outcurses]], ncurses work which is actually going somewhere

	[[CATEGORY: Projects]]		[[CATEGORY: Projects]]

Dank: /* See Also */

2019-10-18T03:13:02Z

Dank at 03:06, 18 October 2019

2019-10-18T03:06:56Z

← Older revision		Revision as of 03:06, 18 October 2019
Line 4:		Line 4:

	Whereas libaa and libcaca (beautifully) attenuate high-resolution graphics, reducing them to input suitable for low-resolution "character cell"-based displays, Xcurses (faithfully) renders programmatic character cell output as virtual vector primitives, applies optional transforms, and renders them to a high-resolution bitmap display. Xcurses will have knowledge of the input forms at the '''character set''' level, which ought allow for interesting effects...		Whereas libaa and libcaca (beautifully) attenuate high-resolution graphics, reducing them to input suitable for low-resolution "character cell"-based displays, Xcurses (faithfully) renders programmatic character cell output as virtual vector primitives, applies optional transforms, and renders them to a high-resolution bitmap display. Xcurses will have knowledge of the input forms at the '''character set''' level, which ought allow for interesting effects...
	* Scalable brackets (		* Scalable brackets
	* True support of GTK/QT themes		* True support of GTK/QT themes
	** Palette initialized with the theme palette as opposed to [http://stackoverflow.com/questions/8686368/how-can-the-original-terminal-palette-be-acquired-preferably-using-ncurses-rout a bunch of useless horseshit]		** Palette initialized with the theme palette as opposed to [http://stackoverflow.com/questions/8686368/how-can-the-original-terminal-palette-be-acquired-preferably-using-ncurses-rout a bunch of useless horseshit]

Dank: /* Hybrid linking */

2012-07-29T12:03:10Z

Hybrid linking

← Older revision		Revision as of 12:03, 29 July 2012
Line 46:		Line 46:
	** Bad kind of in the same way burning one's testicles is bad, which is to say unpleasant.		** Bad kind of in the same way burning one's testicles is bad, which is to say unpleasant.
	====Hybrid linking====		====Hybrid linking====
	* Link all the X crap into libXcurses-~~helper~~		* Link all the X crap into libXcurses-bigfatbagofshit.so
	* Dynamically open it from libXcurses once we've verified it's safe to do so, meaning both that:		* Dynamically open it from libXcurses once we've verified it's safe to do so, meaning both that:
	** all component objects' _init functions (see [[GCC]] documentation, "[http://gcc.gnu.org/onlinedocs/gccint/Initialization.html How Initialization Functions Are Handled]") may be safely invoked, and		** all component objects' _init functions (see [[GCC]] documentation, "[http://gcc.gnu.org/onlinedocs/gccint/Initialization.html How Initialization Functions Are Handled]") may be safely invoked, and
	** resource consumption in the event of non-use is negligible		** resource consumption in the event of non-use is negligible

	===Take over libcurses.so===		===Take over libcurses.so===
	===[[Working_with_libraries#Interpositioning\|Interpositioning]]===		===[[Working_with_libraries#Interpositioning\|Interpositioning]]===

Dank: /* How might it work? */

2012-07-29T12:02:41Z

How might it work?

← Older revision		Revision as of 12:02, 29 July 2012
Line 44:		Line 44:
	====Dynamically open X.org libraries====		====Dynamically open X.org libraries====
	* '''Bad:'''		* '''Bad:'''
	** I'~~d rather have my balls cut off~~.		** Bad kind of in the same way burning one's testicles is bad, which is to say unpleasant.
			====Hybrid linking====
			* Link all the X crap into libXcurses-helper
			* Dynamically open it from libXcurses once we've verified it's safe to do so, meaning both that:
			** all component objects' _init functions (see [[GCC]] documentation, "[http://gcc.gnu.org/onlinedocs/gccint/Initialization.html How Initialization Functions Are Handled]") may be safely invoked, and
			** resource consumption in the event of non-use is negligible
	===Take over libcurses.so===		===Take over libcurses.so===
	===[[Working_with_libraries#Interpositioning\|Interpositioning]]===		===[[Working_with_libraries#Interpositioning\|Interpositioning]]===

Dank: /* How would it work */

2012-07-29T11:58:12Z

How would it work

@@ Line 12: / Line 12: @@
 If non-automatic augmentation is considered, we can do fairly tremendous things, all at the level of ncurses complexity.
-==How would it work==
+==How might it work?==
 Currently...
 <pre>[skynet](0) $ ls -l /usr/lib/x86_64-linux-gnu/libcurses.*
 lrwxrwxrwx 1 root root 12 Jun 27 12:28 /usr/lib/x86_64-linux-gnu/libcurses.a -> libncurses.a
 lrwxrwxrwx 1 root root 13 Jun 27 12:28 /usr/lib/x86_64-linux-gnu/libcurses.so -> libncurses.so
 [skynet](0) $ </pre>
 ===Take over libcurses.so===
 ===[[Working_with_libraries#Interpositioning|Interpositioning]]===
@@ Line 34: / Line 61: @@
 ===Relinking===
 ==Complications==
 * '''Graceful degradation'''

Dank at 11:44, 29 July 2012

2012-07-29T11:44:04Z

← Older revision		Revision as of 11:44, 29 July 2012
Line 1:		Line 1:
	A [[Ncurses\|curses]] variant implemented purely with [[X.org]] objects, perhaps even [[OpenGL]] objects or something. The result ought be significantly faster than a fullscreen [[Ncurses]] program atop a terminal emulator -- not to mention worlds more attractive -- all without so much as relinking existing applications. There exists one grim central theme behind Xcurses, and I call it UNTIE: <center>''Unnecessary terminal emulation is everywhere!''</center>		A [[Ncurses\|curses]] variant implemented purely with [[X.org]] objects, perhaps even [[OpenGL]] objects or something. The result ought be significantly faster than a fullscreen [[Ncurses]] program atop a terminal emulator -- not to mention worlds more attractive -- all without so much as relinking existing applications. There exists one grim central theme behind Xcurses, and I call it UNTIE:

			<center>'''Unnecessary terminal emulation is everywhere!'''</center>

	Whereas libaa and libcaca (beautifully) attenuate high-resolution graphics, reducing them to input suitable for low-resolution "character cell"-based displays, Xcurses (faithfully) renders programmatic character cell output as virtual vector primitives, applies optional transforms, and renders them to a high-resolution bitmap display. Xcurses will have knowledge of the input forms at the '''character set''' level, which ought allow for interesting effects...		Whereas libaa and libcaca (beautifully) attenuate high-resolution graphics, reducing them to input suitable for low-resolution "character cell"-based displays, Xcurses (faithfully) renders programmatic character cell output as virtual vector primitives, applies optional transforms, and renders them to a high-resolution bitmap display. Xcurses will have knowledge of the input forms at the '''character set''' level, which ought allow for interesting effects...

Dank at 11:43, 29 July 2012

2012-07-29T11:43:44Z

← Older revision		Revision as of 11:43, 29 July 2012
Line 1:		Line 1:
	A [[Ncurses\|curses]] variant implemented purely with [[X.org]] objects, perhaps even [[GL]] objects or something. The result ought be significantly faster than a fullscreen [[Ncurses]] program atop a terminal emulator -- not to mention worlds more attractive -- all without so much as relinking existing applications. There exists one grim central theme behind Xcurses, and I call it UNTIE: <center>''Unnecessary terminal emulation is everywhere!''</center>		A [[Ncurses\|curses]] variant implemented purely with [[X.org]] objects, perhaps even [[OpenGL]] objects or something. The result ought be significantly faster than a fullscreen [[Ncurses]] program atop a terminal emulator -- not to mention worlds more attractive -- all without so much as relinking existing applications. There exists one grim central theme behind Xcurses, and I call it UNTIE: <center>''Unnecessary terminal emulation is everywhere!''</center>

	Whereas libaa and libcaca (beautifully) attenuate high-resolution graphics, reducing them to input suitable for low-resolution "character cell"-based displays, Xcurses (faithfully) renders programmatic character cell output as virtual vector primitives, applies optional transforms, and renders them to a high-resolution bitmap display. Xcurses will have knowledge of the input forms at the '''character set''' level, which ought allow for interesting effects...		Whereas libaa and libcaca (beautifully) attenuate high-resolution graphics, reducing them to input suitable for low-resolution "character cell"-based displays, Xcurses (faithfully) renders programmatic character cell output as virtual vector primitives, applies optional transforms, and renders them to a high-resolution bitmap display. Xcurses will have knowledge of the input forms at the '''character set''' level, which ought allow for interesting effects...

← Older revision		Revision as of 23:46, 19 February 2020
Line 73:		Line 73:

	==See Also==		==See Also==
	* [[Outcurses]] which is actually ~~going~~ somewhere		* [[Outcurses]], which actually went somewhere
			* [[Notcurses]], which modernizes NCURSES
	* [[TANGE]]		* [[TANGE]]

	[[CATEGORY: Projects]]		[[CATEGORY: Projects]]

← Older revision		Revision as of 03:13, 18 October 2019
Line 73:		Line 73:

	==See Also==		==See Also==
	[[TANGE]]		* [[TANGE]]
			* [[Outcurses]], ncurses work which is actually going somewhere

	[[CATEGORY: Projects]]		[[CATEGORY: Projects]]