create new tag
, view all tags
Collecting xlib resources.

See also:

See AboutThesePages.



Aside: It's clear that (if I write a keyboard macro utility with xlib) there are two possibilities -- writing a program which uses xlib or modifying xlib (or possibly a combination of the two). In most cases, I believe the resources on this page relate to writing a program using xlib -- when I find information useful for modifying xlib, I will explicitly note that.

UPDATE: Ok, the above is not as clear as I thought it was. wink From reading the O'Reilly manual (below) (or other resources) I've learned that xlib is the interface to x from a client program, and I think I want / need to make most of my changes in the x server program (not sure what that's called at this point) so that the macro keys I define work in all applications (there's a good diagram in one of the earlier chapters of the manual that illustrates this). Aside: It looks like X has "hooks" to allow keyboard macro definitions in a client, thus they are valid in one client. I want my keyboard macros to be valid system wide for a variety of reasons which I should list here (before Sunir Shah (??) asks me to "motivate" my requirements):

Basically, I want my keyboard macros to work in all applications so that (or because)

  • I haven't picked a final set of applications that I expect to use in Linux forever, when I switch from one to another, either on a trial basis, a permanent basis, or sort of a one time basis (because maybe a particular page can't be viewed properly in one browser) I'd like my macros to be available.
  • Many applications will need the same keyboard macro definitions -- if I use several different browsers to read and then edit WikiLearn, I will want the same (or very similar) macros in all of them -- likewise I may pull some pages to Nedit or some other editor to edit them more conveniently. Abbreviations that I use in Nedit or a web browser will probably also be useful in my email and newsreader clients.

Followup: It would be nice if keyboard macros could be defined in a "hierarchic" manner -- that is I could make a set of global macros which might be overridden in any of several applications.

Aside: I'm learning (I think) that I had some misunderstandings about X (I don't know for sure -- maybe X has been modified significantly since some of my early reviews of it)

  • (no change, and still crazy after all these years) -- client and server are backwards (IMAONSHO) (In My, And Other's, Not So Humble Opinion) (you can argue all you want that the X approach is more correct, and I can see your point, but of the world's 6,000,000,000 people, how many are you going to clarify that to??? And how many minutes / hours will it take per person?? And which of those 6,000,000,000 is not worthy of a correct understanding???) (the phaseology in the foregoing could be improved)
  • (different than I understood) I did not think X had the capability to exchange short messages from client to server to specify things like widgets and so forth -- somehow I thought the bandwidth between client and server was tied up transmitting bitmapped images. But, X in the days I fooled with it (or avoided fooling with it) was very slow, and used (for those days) outrageous amounts of memory. (Was this around 1992 or even earlier -- we intentionally did not use X on the C Furnace Reline nor the Level 1 portion of the No. 1 Caster Rebuild -- I'm confused right now about what was done at Level 2 -- display was on a PC shared with Level 1, so I don't think it was X, but it might have been. Did we consider X for the joint caster project around 1982 to 1986 -- don't think we could have -- don't think it was around then (but we did choose IDG (??) and intentionally stored graphics images in the terminals and only transmitted data to the extent possible). (But, back to the initial point -- maybe the implementations of X in those days, or the particular programmers / designers chose to send bitmapped images instead of specifying widgets?? Anyway, I still think our decision (at that time) to not use X was appropriate.)


See ResourceRecommendations. Feel free to add additional resources to these lists, but please follow the guidelines on ResourceRecommendations including ResourceRecommendations#Guidelines_for_Rating_Resources.


Recommended for Specific Needs

  • (rhk) [[][]] --

Recommended by Others

  • (rhk) [[][]] --

No Recommendation

  • (rhk) GPS' Home Page -- a page with several sample xlib programs
  • (rhk) Beginner Xlib Tutorial -- one of the sample xlib programs referred to above -- "This document describes how to create a simple window, display the window on the screen, and how to draw two green rectangles."
  • (rhk) XWindow programming - XLib -- a page listing several xlib resources including various manuals and tutorials
  • (rhk) README for ~4Dgifts/examples/X11/Xlib source code examples -- "This directory contains 10 X Windows programming examples which implement X11 graphics capabilities. These programs are designed and commented in such a way as to aid beginning X Windows programmers."
  • (rhk) XLib Manual Search Engine; -- "This is a dedicated xlib search-engine which searches through XLib Manual."

Not Recommended

  • (rhk) [[][]] --


  • () RandyKramer - 19 Sep 2002
  • <If you edit this page: add your name here; move this to the next line; and include your comment marker (initials), if you have created one, in parenthesis before your WikiName.>

Page Ratings

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2002-09-26 - RandyKramer
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by PerlCopyright 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding WikiLearn? WebBottomBar">Send feedback
See TWiki's New Look