summaryrefslogtreecommitdiff
path: root/xlib.c
AgeCommit message (Collapse)AuthorLines
2007-10-031000l: key table was global var rather than static constRich Felker-1/+1
2007-09-01lame partial support for input methods that give long input stringsRich Felker-1/+3
2007-08-23minimally working input method support!Rich Felker-1/+5
2006-10-29major internal changes in representation of character cells.Rich Felker-2/+2
we now use 12 bytes per cell instead of 10. however, this allows us to support 256-color mode (not yet implemented but the framework is in place) and to mix scripts when using combining characters. while the latter sounds ridiculous at first, being able to visibly see a combining letter attached to a [, ", or ' is extremely useful in scripting and regular expressions with some languages. some code is left slightly messy, but overall it's much cleaner now since struct uucell is now properly encapsulated.
2006-10-26no need to check thisRich Felker-2/+0
2006-10-2610l: multiple-free!Rich Felker-1/+3
2006-10-26basic, primitive paste support. it is blatently incorrect for non-utf8Rich Felker-5/+39
locales, and will also fail when the selection owner cannot provide utf-8 encoded text. much more support code is needed, but at least this is a start.
2006-10-25stupid omission; still a glitch though..?Rich Felker-0/+1
2006-10-25major changes to input handling in preparation for pasting, which willRich Felker-26/+22
require support for large blocks of input: output which cannot be written to the tty (pty) is no longer discarded. instead, the display module is responsible for keeping the buffer alive until it has been entirely consumed. one simple (and smart) way to ensure this is to refuse to process events that could generate new input text as long as there is unwritten data. this works as long as there is an earlier layer of buffering (for fbcon, kernel; for x11, xlib). a direct-on-x-protocol display implementation will have to do its own buffer management. this architecture allows pasting to be performed direct from a buffer owned by the display module, which could reside in static or shared memory, or even as a memory-mapped file. it also facilitates reuse of the code in non-tty-connected settings.
2006-10-16mistaken line left over from old codeRich Felker-1/+0
2006-10-16don't know if this is a bug somewhere else, but for whatever reason iRich Felker-0/+1
was getting non-null-terminated strings sometime?!
2006-10-15remove server-side glyph rendering/cache entirely. client side is justRich Felker-66/+55
as fast or faster even with remote displays due to horribly inefficient X protocol...
2006-10-15revert "performance increase" that actually hurt performance on betterRich Felker-30/+19
X servers.. :( some better approach is really needed; at this rate, even client side images would be faster...
2006-10-15large performance increaseRich Felker-19/+30
2006-10-15preliminaries for input method supportRich Felker-2/+13
2006-10-13better now, perhapsRich Felker-1/+4
2006-10-13nonlatin input, attempt 2Rich Felker-2/+2
2006-10-13try to support non-latin input.. does this work?Rich Felker-12/+26
2006-10-13remove margin nonsense i got from reading bad sourceRich Felker-4/+3
2006-10-13remove the horribly incorrect XImage handling and replace it withRich Felker-21/+16
something much simpler that won't corrupt memory.
2006-10-13x11 window resizing supportRich Felker-36/+52
2006-10-12broken backspace; Xlib is stupidRich Felker-0/+1
2006-10-12possibly fix crash on last glyph page?Rich Felker-2/+2
2006-10-12missing prototypesRich Felker-0/+1
2006-10-121% less messy/hackishRich Felker-6/+7
2006-10-12first try at porting to X. very broken, minimal functionality,Rich Felker-0/+375
but it does work..