RE: Contents of one of my workspaces

I doubt it. I vaguely remember creating this monster myself, when for some reason I couldn't think of the obviously better name. Just to eliminate some useless C code. Currently, under Windows this frame pops up almost immediately, and then many seconds later, after much path grinding, it goes away and the normal frame appears. This frame could also be used for any messages prior to popping up the first frame, and eventually for moving the creation of the first normal frame till *after* loading the init file, which would make it extremely easy to customize the size of the first frame. (This is an *ooollllldddd* proposal from Arch. XEmacs.) BTW This "splash-frame" is a normal frame of the sort used in dialog boxes, with the added feature of having no title bar (the new `no-title-bar' frame property; only implemented on Windows currently, I need to get docs on the various ways of communicating with window managers under X to control the decorations. Can all of you X-ers go look up any docs on window managers you may have at hand and tell me what the tricks are? Also I'd like the names of the most common Window managers out there. Alternatively, maybe this should just be created override-redirect or something? DOes that make sense?) Because it's FSF-compatible. 1] it's already done. 2] it's probably not a waste of time. (NB In my glyphs workspace I have also factored out much of the code shared between redisplay-x.c and redisplay-gtk.c in the form of "xlike" input methods that implement lower-level operations.) Most of what has been factored is stuff that's not specific to X or GTK, with the appropriate X or GTK stuff stuck in through ifdefs, or sometimes device methods. As long as GTK v2 is parallel to X in its basic model, the same approach will apply, and I strongly suspect it will be, especially at the lower level where we care about because [1] GTK v2 will surely want to be networkable, and X is the only well-known networking system that's built ground-up to do this; [2] GTK v2 is going to be running on top of X much of the time, hence it would not behoove it to have a conceptually incompatible low level; [3] people rarely completely throw away previous conceptual models, esp. at the lower levels, and in the cases they do, it's all the rarer (and usually suicidal) for them to start from scratch without looking at any model at all -- so what would they choose? Windows or MAC? Doesn't seem too likely. But I may be putting my foot in my mouth. Yes Most likely. But don't we already have an `inherit' syntax code, which works fine? Presumably this is not what you're referring to?