*entry* 44 RelTOCPointer 43156 *entry* 1372 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:06 pm PDT 1069 191 Date: Fri, 31 Jan 92 13:25:38 PST From: jacobi:PARC:Xerox Subject: X11Tcl for PCedar2.0 To: PCedarUsers:Parc:Xerox Cc: jacobi Reply-to: Christian P Jacobi:PARC:Xerox X11Tcl DF files: [PCedar2.0]X11Tcl-Suite.df Documentation: [PCedar2.0]X11TclDoc.tioga Maintainer: Jacobi New package. Abstract Tcl is a "tool command language" desined by John Ousterhout. It contains a general interpreter, C language interfaces so this interpreter can be embedded in C programs. It contains a simple X11 toolkit Tk. Most important to us, Tk has a relatively simple convention how otherwise independent applications can communicate. X11Tcl is a package which supports Tcl/Tk's remote execution or communication convention. While it itself does not support general Tcl interpretation it allows to send commands to registered Tcl interpreters. It also allows to register interpreters from Cedar. These interpreters might not implement the Tcl-language (as no real interpreter is delivered), but they can nevertheless implement specific Tcl commands. ʹ˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ˜Jšœ˜ Jš œ˜'J˜headšœ˜IindentšÏt œž ˜*Lšžœ)˜9Lšž œ˜L˜Lšœ ˜ L˜LšÏb˜LšœÆ˜ÆLšœ¡˜¡L˜L˜L˜L˜——…—.í *entry* 1204 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:13 pm PDT 921 171 Date: Fri, 31 Jan 92 13:42:09 PST From: jacobi:PARC:Xerox Subject: X11, X11Viewers for PCedar2.0 To: PCedarUsers:Parc:Xerox Cc: jacobi, PCedar Coordinator:Parc:Xerox Reply-to: Christian P Jacobi:PARC:Xerox X11, X11Viewers DF files: [PCedar2.0]X11-Suite.df, [PCedar2.0]X11Viewers-Suite.df Documentation: available Maintainer: Jacobi New features XTkWidgets: Improved behaviour in case of inappropriate input focus handling of window managers. (Useful on liveboards.) X11: Some internal improvements. X11Viewers allows to withdraw the window. (This means the window goes away but the unix process stays alive and alert. This is useful if the cedar world also serves as server for something. This feature is aimed at liveboards which currently are terminating Cedar worlds too frequently.) There is also a way to make the withdrawn window reappear, but you need a remote commander to issue the command. Ê¥˜JšÐbsœ˜!Jšœ˜Jšœ˜&Jšœ˜Jšœ'˜)Jš œ˜'J˜headšœ˜IindentšÏt œž œž ˜LLšžœ ˜Lšž œ˜˜ Lšœz˜zLšœ!˜!Lšœ”˜”———…—šE *entry* 732 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:18 pm PDT 499 121 Date: Thu, 06 Feb 92 15:56:28 PST From: jacobi:PARC:Xerox Subject: Preventing shared memory To: Willie-Sue, Nichols Cc: jacobi All done and smodelled... Convention: The PARC_ServerHost property in the x server (on the root window) allows to check which machine implements the x server. New command X11TrustedSetServerHost Initializes the PARC_ServerHost property of the server "HostName" to "HostName" X11 Shared memory usage is disabled when PARC_ServerHost property shows unexpected value. Ês˜JšÐbsœ˜!Jšœ˜Jšœ˜!Jšœ˜Jšœ˜ J˜J˜J˜J˜…J˜˜ Jšœ˜J˜PJ˜—˜J˜U—J˜—…—ôm *entry* 12078 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:31 pm PDT 11249 717 Date: Mon, 17 Feb 92 12:14:30 PST From: jacobi:PARC:Xerox Subject: Trip report from X window conference To: XWindows:All areas, ComputerResearch:PARC, UIAC-Core:All Areas Cc: jacobi Reply-to: Christian P Jacobi:PARC:Xerox Trip report from the 6th Annual Technical Conference on the X Window System. Boston, Massachusetts 13-16 January 1991 I apologize if this report is too opinionated, but if you want a less subjective trip report you can read the conference announcements instead. (See also last years trip report) I was not too much impressed; X windows is getting a big standard, but it is not in itself an interesting research topic. Some of the great interoperability opportunities seem to have been forgotten. I was also surprized about the large number of toolkits presented. If you want to read just about 1 talk and you are a Xerox executive, I think "Achieving Pixel-Precise Rendering in X" is the most consequential one. I was not pleased by the small number of Xerox folks. I would think that XSoft ought to have some feelers into the X culture. (X environment window in GlobalView, GlobalView in X, ...) The group supporting the X server on daybreak wasn't represented at all either. Tutorial on Tcl. By John Ousterhout I have enjoyed this tutorial. It showed some fresh ideas and wasn't one more silly thing going along with the crowd. I was contemplating whether I should use Tcl in my X toolkit. (I decided that SchemeXerox was better suited extension language for my purposes after all, but that the Tcl way of interoperability is desirable nevertheless; See X11Tcl-Suite.df) Tcl is an interpreter which can be invoked from C programs. It integrates nicely with C and is good as an extension language. It reinvents many lisp ideas (but it is far too unsafe against user errors). Tk is an X toolkit built for use with Tcl. It has nice features; e.g. simplicity and power. It is very impressive how few lines are needed to write small applications. The lack of module concept in Tcl and the missing naming conventions in Tk make it unsuited for really large applications. Like everithing else it is not thread safe. One more problem with Tk is the fact that the widget tree must be assembled using Tcl and not in C. It is very nice to do this task in an extension language, but I would nevertheless prefer to do it in a real programming language 80% of the time. The one feature of Tcl/Tk which I have decided to use myself is the global communications feature. An application can send some string to any other application to be interpreted. This might be poohed as a poor mans RPC, but it allows real interesting applications. Maybe this is the "windowing applications pipe" mechanism. I would think it worth while for John to make this functionality available separately without the risks of a general interpreter. John Ousterhout dreams of simplifying applications a lot because they need to do the basics only, and, delegate certain functions to other more specified applications. I share his dream in parts. However thanks to dynamic loading, definition modules and shared adress space, Cedar has accomplished this long ago. Instead of being interested in general simplifications I am interested in cross language operations which enrich the functionality of the systems. Question and Answer session I used the opportunity to complain about problems with the input extension. I have found that that Bob Scheifler was very much in agreement with my complaints. I have asked for features to nest widgets from different toolkits. I got answers with many words, neither acknowledging nor understanding the problem, but claiming it would be impossible. (The Cedar XTk toolkit can do it). I got the impression that different toolkits start to proliferate. I found a surprising number of people worrying about issues of multi-threading. However, the state of this art is not very good. Birds of a feather session: X Application Performance Characterization Jim Stearns, Hewlett-Packard I had very high expectations as I thought this to be an extremely important topic to XSoft. However, it was a complete disappointment. They were speaking about server benchmarks. I then left the room as I couldn't stand it anymore (The other sessions I was walking into wasn't interesting either). Can You Bet Your Life On X? - Using X Windows for Command and Control Displays Jeff Malacarne, Hughes Aircraft Company, Displays Laboratory The talk did not answer this question to me, but gave me nice insights anyway. Quote: "Operator fatigue is a main cause of catastrophic errors" Detail: "The navy uses smaller screens" Performance seem to be really an issue. They consider multiprocessing for the server. I asked what percentage of cpu power is used in the server and in the client. (I worked very hard to work out a question which wasn't too agressive). 50 % unused for reserve, from the rest: 50 % Application. 30 % Extensions, e.g. video. 20 % X server. The GL/X binding Phil Karlton, Silicon Graphics Computer Systems As I didn't really had any knowledge of Gl, I didn't understand this talk. I liked the idea of combining X imaging with other imaging methods however. The XRemote Serial Line Protocol Dave Cornelius, Network Computing Devices No surprise. We know the data from Dave Nichols work. They decided to handle GrabServer and UnGrabServer specially. In first approximation this is absurd, as this request is very rare. It however makes sense to prevent buffer overflows... Is there no more basic method to prevent buffer overflow? A PostScript X Server William Raves, Sunquest Information Systems Inc. This talk was absurd. They have chosen the wrong approach. A Smart Frame Buffer Joel McCormack, DEC Western Research Laboratory Remember Joel usually gave a talk about "dumb" frame buffers. Quite good presentation of an a topic for which I do not have much interest. I didn't understand everything he did. How Not to Implement Overlays Todd Newman, Silicon Graphics I don't understand why this is not an easy problem. NFB, Porting Layer for the X Server Jeff Weinstein, Silicon Graphics Computer Systems Uncomprehensible (at least to me) talk about inner workings of an X server. This was the first talk where nobody had a question. The Multi-Threaded X Server John Allen Smith, Data General Corporation The goal is not increased performance but that slow request don't block the server. I guess a good thing stays a good thing even if done for the wrong reasons. This talk was a lot better than last years talk with the same topic by a different speaker. The PEX extension has requests which keep the server blocked for a long time. They want to go to all this effort and fixing the server instead the PEX protocol. I bet, someday they will find out that making the server multithreaded doesn't prevent the window manager from blocking anyway. Prototyping multi-thread-safe Xt and XView libraries Bart Smaalders, SunSoft, Inc. I thought this was a good talk. I think his token approach is too simple. However, I must admit that I belive that it will work, and, it is much better then not doing anything. Achieving Pixel-Precise Rendering in X Paul Asente, Adobe Systems, Inc. This was a good talk; maybe not deep enough for us. Adobe is implenting the same thing we did with Chris Kents ImagerX11. To them it is not just having postscript; it is a alternate way of dealing with servers without the Display poscript extension. This might be good step in making Display Postscript more ubiquitous. Implementing Resolution Independence on top of the X Window System Mark Linton, Silicon Graphics Not very interesting, but everything Mark said was dead true. Of course using the Imager, or, Postscript would be superior. I'd whish some XSoft people (doing DDR) would have listened to this talk. Don't Fidget with Widgets, Draw! Joel F. Bartlett, DECWRL Very nice toy. This might be worthwhile tracing as I could imagine combining this with window system independence. Birds of a feather session: Multi-threaded X server John Smith, Data General I was much surprised how many prople cared. (Half of them for the wrong reasons). See notes about talk. Bart and I tried to lead the discussion in direction of multithread applications and corresponding libraries. We had little success, mainly because people had so little experiance and a multithreaded server is something they can grasp. A Keyboard Macro Facility for X Kuntal G. Rawal, Solbourne Computer, Inc. A nice little feature. However, of quite limited interest. Testing Widget Geometry Management Daniel Dardailler, Motif team, Open Software Foundation A special approach using intermediate widgets which works sometimes and is lots of work. I can't believe this is useful. Migrating Widgets Christian P. Jacobi, Xerox PARC ... I was asked the question about social implification of active badges. I truthfully answered that we have different opinions and that some people care. A Method for Handling Extension Events in Xt Ralph R. Swick, Digital Equipment Corporation This is a trivial improvement. However, it is very hard to incorporate this into existing systems. (XTk doesn't have this problem). Implementing Drag and Drop for X Gabe Beged-Dov, Hewlett Packard Ellis Cohen, Open Software Foundation It is very, very complex. One of the major reasons is interoperability and presence of slow applications. I was also pointing out a difference between slow applications and slow communications. OSF payed me a lunch just so I could participate in some interoperability discussions with Ellis. I used my chance to make sure things won't be too bad for Cedar. Virtual Screen: A Framework for Task Management Jin-Kun Lin, University of North Carolina at Chapel Hill I didn't make notes. Using XTrap to Support People with Manual Disabilities Keith Packard, MIT X Consortium Your lawyer could make this relevant. The nice thing about Keith's approach is that it works independently of the application, for any application. It might not be wonderful, but it enables this technology to handicaped people. User Interface Through Spoken Language: Recent Development at MIT Victor Zue, MIT Laboratory for Computer Science I don't know what this talk has in common with X windows. I thought this to be the most interesting talk of the conference. This might be relevent in LONG TERM. If I did understand it right, the two hard problems speech recognition and language understanding were combined. The combined problem is easier to solve. The demo was extremely impressive; it is not known to me how much was canned, nor, how it internally worked. Attacking the Learning Curve for X: Using SRGP and SUIT to Teach Concepts Matthew J. Conway, University of Virginia Yet another small toolkit. Actually if we consider this to be a teaching tool only, they did a marvelous job. MuX: An X Co-Existent, Time-based Multimedia I/O Server Earl Rennison, SRI International Completely lost on me. It was either too boring or I was too tired. Using X to Display Moving Pictures Tim Glauert, Olivetti Research Limited I didn't make notes. ÊǘJšÐbsœ˜!Jšœ˜Jšœ&˜-Jšœ@˜BJšœ ˜ Jš œ˜'J˜šÏbL˜LJ˜J˜J˜—J˜²J˜J˜yJ˜J˜‘J˜Jšœ”˜”J˜J˜ŒJ˜J˜šž˜J˜J˜uJ˜óJ˜ÍJ˜¥J˜¤J˜ÉJšœÎ˜Î—J˜šž˜J˜Jšœ ˜ J˜J˜àJ˜J˜BJ˜J˜J˜—JšžFœÍ˜“šžNœ>˜ŒJ˜NJ˜@J˜(J˜XJ˜–J˜'J˜?—J˜šžœ1˜AJ˜——J˜šž œ+˜KJ˜8J˜ô—J˜šžœ2˜GJ˜;—J˜šžœ1˜EJšœ=˜=J˜t—J˜šžœ˜" Message-ID: "<9202261909.AA02529@explain.lcs.mit.edu>" To: jacobi:PARC Cc: janssen:PARC From: rws@expo.lcs.mit:edu:Xerox Received: from expo.lcs.mit.edu ([18.24.0.11]) by alpha.xerox.com with SMTP id <11870>; Wed, 26 Feb 1992 11:09:37 PST Received: from explain.lcs.mit.edu by expo.lcs.mit.edu; Wed, 26 Feb 92 14:09:42 EST Received: by explain.lcs.mit.edu; Wed, 26 Feb 92 14:09:09 -0500 Original-From: Bob Scheifler Date: Wed, 26 Feb 1992 11:09:06 PST I would like to request registration of 3 "private" KeySyms. i need to know what vendor prefix to attach to the names, e.g. as in osfXK_Copy. can be the registered organization name (you haven't registered one yet), or some abbreviation of it. nominally i will assign vales 0x10070001,0x10070002,0x10070003. ʘJ˜Â—…—Äç *entry* 977 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:49 pm PDT 717 148 Date: Mon, 23 Mar 92 18:43:28 PST From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox Reply-to: Jacobi X11 DF files: [Cedar10.1]X11.df Documentation: plenty Maintainer: Jacobi Now uses FanoutStream instead of exporting IODribble. Hurray, one module less to support. Also made many real changes including interface changes since the last release message. The one change I remember is that I made the help strings for pop up menus really work. Sorry, this addition required about 3 new internal interfaces. If you have ever seen XMaintain, you now why those help strings are worth so much trouble. Critical changes This is not critical. ÊŽ˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ ˜"Jšœ˜!Jšœ˜J˜head˜IindentšÏt œž˜!Lšž˜Lšž œ˜L˜ZL˜Ì˜L˜———…—Îb *entry* 3056 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:54 pm PDT 2593 351 Date: Tue, 24 Mar 92 17:18:53 PST From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox Reply-to: jacobi:PARC:Xerox X11 DF files: [Cedar10.1]X11.df Documentation: look in the df file to find it Maintainer: Jacobi Improved error handling. Changes are not critical The following list of details is probably not interesting to you but included for the benefit of historians. All known clients in Cedar10.1 are recompiled. Xl Error handling Xl.Detail: localErrors parameter allows to avoid generation of local errors. Xl.SetButtonGrabOwner: does no more raise errors but might return failedFutureTime. Do not generate errors (in default case) when accessing dead connection RequestFromDeadConnection, ClientError error are replaced by special code in XError Bug fixes in error handling mechanism Resource handling Connection: Did build ref count into connections. Removed finalization mechanism for Connection. Made pseudo event for notification when connection dies. Efficiency, track keeping, byte order, Terminology Connection: Removed speed hacks which would fail IO's new exposed buffers. Get rid of KeyArray, KeyArrayIndex make QueryKeymap return a correctly swapped structure. Use of the new Keyboards interface. Improved terminology about EventMask a little EventSet ==> EventFilter EventSetRep ==> EventFilterRec CreateEventSet ==> CreateEventFiler Set of events correctly byte swapped for little endian machines. XTk HasClass and similar functions use the class instead of just an atom. XTk.Class has a flags concept similar to widgets. Use of dummy connection instead of NIL when no connection is used while migrating is in progress. Results in less errors generated by careless applications like pop up menus. XTkShellWidgets New IsShell predicate procedure. Changed to use Xl's new ref counting of connections (Removed more complex previous mechanism). XTkLabels Paint requests are forked and executed in a protected paint thread. XTkFields Take the input focus on click. XTkStreamWidgets Scrolling changed to look nicer in XAdobe. (This change is even backported to PCedar2.0) XTkPopUps Redesigned to be less insane; more special cases for the simple use. Use the new help facility New interfaces for help facility XTkHelpWidgets.mesa XTkHelpShells.mesa XTkHelpStrings.mesa HelpStrings.mesa XTkInputFocus Uses class flags to figure out what widget knows how to handle focus XTkCredentialsWidgetImpl More code sharing XTkTIP Use the new Cedar10.1 TIP. Things look nicer inside now. ÊY˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ ˜"Jšœ˜!Jšœ˜J˜head˜IindentšÏt œž˜!Lšžœ˜.Lšž œ˜Lšœ˜˜J˜lJ˜.J˜˜˜J˜LJ˜SJ˜GJ˜SJ˜%J˜—˜J˜aJ˜9J˜—˜2J˜JJ˜€˜-J˜Jšœ˜J˜#—J˜B——J˜˜J˜EJ˜2J˜°J˜—˜J˜ J˜^J˜—˜ J˜CJ˜—˜ J˜J˜—˜J˜YJ˜—˜ J˜DJ˜—J˜˜ J˜J˜J˜J˜—J˜˜ J˜DJ˜—˜J˜J˜—˜J˜9—J˜———…— " *entry* 1235 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:46:59 pm PDT 923 200 Date: Thu, 26 Mar 92 16:01:04 PST From: jacobi:PARC:Xerox Subject: XTkFeedback for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox, Bier Reply-to: Jacobi:PARC:Xerox XTkFeedback DF files: [Cedar10.1]XTkFeedback.df Documentation: [Cedar10.1]XTkFeedbackDoc.tioga Maintainer: Jacobi:PARC:Xerox XTkFeedback enables feedback (SimpleFeedback.mesa, Feedback.mesa) using XTk widgets. Critical changes New package. Questions 1) I'm not that sure I got the spirit of this packahe right; suggestions please. 2) Feedback seems not to be capable of multi threaded use. 3) I'm quite sure I got the selection of the X server to be used not really right. I don't know how to find this out with the Feedback interface. 4) How can I set the default feedback right? A viewerless world ougth to use this as default where a viewer containing world ought to use the system script as default. ʘJšÐbsœ˜!Jšœ˜Jšœ˜"Jšœ ˜"Jšœ%˜'Jšœ˜J˜head˜ IindentšÏt œž˜)Lšžœ žœžœž˜9Lšž œ˜LšœT˜T˜Lšœ ˜ —˜ LšœP˜PLšœ:˜:Lšœ“˜“Lšœ¨˜¨———…—œd *entry* 2963 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:05 pm PDT 2365 486 Date: Fri, 27 Mar 92 11:57:31 PST From: jacobi:PARC:Xerox Subject: 8 packages for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox Reply-to: Jacobi:PARC:Xerox ScannerTool DF files: [Cedar10.1]ScannerTool.df Documentation: [Cedar10.1]ScannerToolDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. ScannerTool is a very simple tool driving a scanner Maintain DF files: [Cedar10.1]Maintain.df Documentation: ? Maintainer: ? Recompiled "Xmaintain" to match current versions of X software. XlShape DF files: [Cedar10.1]XlShape.df Documentation: [Cedar10.1]XlShapeDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. X11 nonrectangular window shape extension. The purpose of providing this package was to test extensability of the X mechanisms so the debugging of XlInputExtension will be easier. XlInputExtension DF files: [Cedar10.1]XlInputExtension.df Documentation: [Cedar10.1]XlInputExtensionDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. Supports the input extension for the X Window system. This package is not yet useful; it is made in anticipation of multi-pen liveboards. ScreenSpy DF files: [Cedar10.1]ScreenSpy.df Documentation: [Cedar10.1]ScreenSpyDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. Little groupware hack; allows to watch the screen of a cedar world from a different machine. XCommander DF files: [Cedar10.1]XCommander.df Documentation: [Cedar10.1]XCommanderDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. A viewer-free command tool using an X window for typscript. This is still lacking from a very poor typscript implementation. X11Eval DF files: [Cedar10.1]X11Eval.df Documentation: [Cedar10.1]X11EvalDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. X11Eval is a hack which allows acessing commander and other intepreters through X window mechanisms. It is useful for implementing hacks like whistle up windows or interoperable applications in different programming languages. X11Tcl DF files: [Cedar10.1]X11Tcl.df Documentation: [Cedar10.1]X11TclDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. X11Tcl supports communication with John Ousterhouts Tcl Êà˜JšÐbsœ˜!Jšœ˜Jšœ˜!Jšœ ˜"Jšœ˜!JšœÏt˜J˜headšž ˜ Iindentšž œž˜)Lšžœ žœž˜ $ *entry* 2273 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:08 pm PDT 1735 426 Date: Fri, 27 Mar 92 17:32:40 PST From: jacobi:PARC:Xerox Subject: 7 more packages for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox Reply-to: Jacobi:PARC:Xerox PopUpCommand DF files: [Cedar10.1]PopUpCommand.df Documentation: [Cedar10.1]PopUpCommandDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. I think this is a really neat package. I use it to make commander buttons pop up menus. TerminalIO DF files: [Cedar10.1]TerminalIO.df Documentation: [Cedar10.1]TerminalIODoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. You probably won't need this but our DA tools will if they get ported. I haven't ported the mix master stuff yet. SimpleStreams DF files: [Cedar10.1]SimpleStreams.df Documentation: [Cedar10.1]SimpleStreamsDoc.tioga Maintainer: Jacobi:PARC:Xerox Ported from PCedar2.0. Somebody sometimes said we won't need this package. That person might be right but I like this package and therefore ported it. SimpleStreamsOnViewers DF files: [Cedar10.1]SimpleStreamsOnViewers.df Documentation: none Maintainer: Jacobi:PARC:Xerox Ported and renamed from PCedar2.0. (Old name was ViewerSimpleStreams) SimpleStreamsOnX DF files: [Cedar10.1]SimpleStreamsOnX.df Documentation: none Maintainer: Jacobi:PARC:Xerox New df file for old but improved functionality. Also did add a test program. X11 DF files: [Cedar10.1]X11.df Documentation: plenty Maintainer: Jacobi:PARC:Xerox Removed the SimpleStreams stuff as it got a home of its own. X11TIP DF files: [Cedar10.1]X11TIP.df Documentation: oops Maintainer: Jacobi:PARC:Xerox Improved error behaviour; fixed small memory leak. ʤ˜JšÐbsœ˜!Jšœ˜Jšœ˜&Jšœ ˜"Jšœ˜!JšœÏt˜J˜headšž ˜ Iindentšž œž˜*Lšžœ žœž˜>Lšž˜L˜L˜X—šž ˜ Lšž œž ˜(Lšžœ žœž˜:Lšž˜L˜L˜FL˜*—šž ˜ Lšž œž˜+Lšžœ žœž˜@Lšž˜L˜L˜€—šž˜Lšž œž˜4Lšžœ˜Lšž˜Lšœ2žœ˜F—šž˜Lšž œž˜.Lšžœ˜Lšž˜LšœM˜M—šž˜Lšž œž˜!Lšžœ˜Lšž˜Lšœ ž œ#˜<—šž˜Lšž œž ˜$Lšžœ˜Lšž˜Lšœ2˜2——…—Èr *entry* 917 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:14 pm PDT 643 162 Date: Tue, 21 Apr 92 17:03:20 PDT From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox, Henderson Reply-to: jacobi X11 DF files: [Cedar10.1]X11.df Uses different implementation for property lists. Event data type now has a property list. (XlEventProperties.mesa) New widget classes: XTkNumberLabel.mesa, XTkBasics.mesa Changed widget class: XTkSlider.mesa replaces XTkSliders.mesa Not necessarily recognizable, but the high order bit of these changes is about gathering new insights on how to compose widgets. All known clients (except packaged worlds) are updated Êœ˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ ˜"Jšœ*˜,Jšœ˜J˜headšœ˜IindentšÏt œž˜!L˜L˜1LšœA˜ALšœ7˜7Lšœ=˜=L˜L˜€L˜L˜6——…—„& *entry* 1816 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:33 pm PDT 1451 253 Date: Mon, 11 May 92 11:33:58 PDT From: jacobi:PARC:Xerox Subject: X11, X11Demos, X11Viewers, Customize for Cedar10.1 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox, CedarUsers:Parc:Xerox Reply-to: Christian P Jacobi:PARC:Xerox X11 DF files: [Cedar10.1]X11.df Removed demo programs from df file. Bug fixes in XTkMigrationImpl, XTkPopUpsImpl. Bug fix to handle case if default font is not supported by server. (Tadpole) New interface X11CommanderOps.mesa. Fixed sevaral applications to use X11CommanderOps to access a connection. (The purpose of this is to get connection reference counting right (To know when to close a connection (No, finalization wouldn't work for this))) X11Demos DF files: [Cedar10.1]X11Demos.df 1) New df file. New home for old demos removed from X11.df. 2) New multi user demo: X11SimpleChat. Try it. There is no documentation available yet, but the source text nearly fits on one single screen. X11Viewers DF files: [Cedar10.1]X11Viewers.df New interface: ViewerHelpStrings.mesa Improved help information of X11Viewers menu. New ImagerX11 command replaces suite of old commands to specify how ImagerX11 shall be used. (No, ImagerX11 has not yet been ported to Cedar10.1). Customize DF files: [Cedar10.1]Customize.df New extras interface: CustomizeExtras.mesa New database merge operations will be useful for X11R5's new convention with per screen resource databases. Ê÷˜JšÐbsœ˜!Jšœ˜JšœÏt$œ˜;Jšœ ˜"Jšœ6˜8Jš œ˜'J˜headšž˜Iindentšž œž˜!L˜#L˜-L˜ML˜ƒ—šž˜Lšž œž ˜&šÏb˜L˜+—šŸ&˜&L˜g——šž ˜ Lšž œž ˜(L˜&L˜.L˜”—šž ˜ Lšž œž ˜'Lšœž œ ˜+Lšœ5Ðbfœ6˜l——…—¬© *entry* 658 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:38 pm PDT 395 151 Date: Tue, 12 May 92 16:48:57 PDT From: jacobi:PARC:Xerox Subject: X11 and X11Viewers for PCedar2.0 To: Cedar10Implementors:Parc:Xerox Cc: PCedar Coordinator:Parc:Xerox Reply-to: Christian P Jacobi:PARC:Xerox X11 and X11Viewers DF file: [Cedar10.1]X11.df DF file: [Cedar10.1]X11Viewers.df Documentation: lots I fixed the documentation. Critical changes I fixed the documentation. Ê‘˜JšÐbsœ˜!Jšœ˜Jšœ"˜)Jšœ ˜"Jšœ˜!Jš œ˜'J˜head˜IindentšÏt œž˜ Lšž œž˜'Lšžœ˜L˜˜L˜——J˜—…—Œ# *entry* 1790 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:49 pm PDT 1503 175 Date: Thu, 11 Jun 92 18:12:23 PDT From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: CedarUsers Cc: jacobi, Henderson Reply-To: Jacobi X11 DF files: [Cedar10.1]X11.df New interfaces XTkScrollbar.mesa A plain scroll bar (without scrollee). Replaces XTkScroller.mesa, which now is obsolete (It still has clients). Changes to fit new widget composition style. XTkBiScrollerFrame.mesa A frame with scroll bars and a place to plug in something which listens to scroll requests and knows how to do scrolling. Replaces XTkBiscroller.mesa, which has been removed. New feature for selective vertical and/or horizontal scroll bars. Changes for new composition style. XTkXScroller.mesa A container which can scroll a child which doesn't know or help about scrolling. New primitive package XTkXBiScroller.mesa A frame with scroll bars and a place to plug in something to be scrolled which doesn't know or help about scrolling. XTkXBiScrollerImpl := XTkBiScrollerFrame + XTkXScroller + glue This is a nice exercise in using composition and inheritance. (Of course, XTkXBiScroller is itself defined in a way which supports further composition and inheritance). If composition and inheritance were perfect, XTkXBiScrollerImpl (the glue) would be a very short module. However, it happens to fill 3 screens; something to learn and improve is still left... XTkBitmapScroller(Impl) Changed implementation but unchanged interface. XTkBitmapScrollerImpl := XTkBiScrollerFrame + XTkBitmapWidgets + glue Ê©˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ ˜Jšœ˜Jšœ˜J˜head˜IindentšÏt œž˜!L˜L˜˜L˜œ—˜L˜”—˜L˜g—˜L˜³L˜L˜îL˜—˜L˜/L˜E———…—à *entry* 711 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:53 pm PDT 469 130 Date: Wed, 01 Jul 92 15:45:14 PDT From: jacobi:PARC:Xerox Subject: X11Demos for Cedar10.1 To: CedarUsers:Parc:Xerox Cc: Cedar Coordinator:Parc:Xerox Reply-to: Jacobi:PARC:Xerox X11Demos DF files: [Cedar10.1]X11Demos.df Added "demo" XShowPixmap The faces program got so popular that I thought something to display a face in Cedar would be a nice building block... I left the user-interface off: The XShowPixmap simply wants simply a filename as argument. Ê|˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ˜Jšœ˜ JšœÏt˜J˜head˜Iindentšž œž˜&L˜L˜×—L˜—…—ÖX *entry* 563 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:47:58 pm PDT 317 134 Date: Mon, 13 Jul 92 15:22:59 PDT Sender: jacobi:PARC:Xerox From: Jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: CedarUsers Reply-To: Cedar Coordinator:PARC:Xerox X11 DF files: [Cedar10.1]X11.df Critical changes Improved text field widgets. Changed access of x icons (for the benefit of shrink wrapping). Ê€˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ˜Jšœ ˜Jšœ˜&J˜head˜IindentšÏt œž˜!˜L˜L˜?——J˜J˜—…—>Ä *entry* 1439 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:48:02 pm PDT 1165 162 Date: Wed, 15 Jul 92 14:47:53 PDT Sender: jacobi:PARC:Xerox From: Jacobi:PARC:Xerox Subject: XCommander for Cedar10.1 To: CedarUsers Reply-To: Cedar Coordinator:PARC:Xerox XCommander DF files: [Cedar10.1]XCommander.df The Xcommander has a completely new user interface. It has less then half the number of buttons and features then it used to have. It is now much easier to use, and, nevetheless slightly more powerfull. It is not yet quite wonderfull as it still lacks tioga output. (This means the output can't be scrolled or edited) Critical changes New user interface. BTW The user interface contains an interesting idea: A text field is edited, and only when the contents is finished the contents is stuffed into the input stream. This is not clumsy as it sounds because it does not require any additional button click; the CR key does it. The reason this is interesting is that this input model would work perfectly using a pen input widget. Somebody ought to make pen input available for Cedar. To successfully try it out your Cedar world must be 24 hours old or less, because XCommander depends on a newly created extras interface in X11. Êœ˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ˜!Jšœ ˜Jšœ˜&J˜head˜ IindentšÏt œž˜(L˜ÌL˜t˜L˜—˜L˜L˜fL˜5LšÏs“˜“——J˜J˜—…—Ž0 *entry* 2280 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:48:18 pm PDT 1923 245 Date: Wed, 22 Jul 92 15:39:06 PDT From: jacobi:PARC:Xerox Subject: SafeStorage, X11 for Cedar10.1 To: CedarUsers:PARC:Xerox Cc: Cedar Coordinator:PARC:Xerox Reply-to: Christian P Jacobi:PARC:Xerox SafeStorage DF files: [Cedar10.1]SafeStorage.df Two new interfaces in SafeStorage.df Finalize New interface. Finalize is supposed to replace Finalization. It adds a clientData field to Finalization. As this is not just an additional procedure but a real change, I have made a new module to avoid incompatibilities. FinalizeOps New interface. Access to Finalize using fewer resources (mainly threads). I have put this functionality in a separate interface because maybe not all Finalize clients want to depend on it. Why: I was running out of threads once too often. Debugging showed me that 10ish threads were used by Finalization clients... Thats why I made FinalizeOps. The new Finalize was necessary because I needed its clientData feature for FinalizeOpsImpl. Independent on how light or heavyweight you consider threads, an added clientData field does not make a module more ugly. What next: I have also smodelled 3 clients of FinalizeOps (all in X11.df). After running a day or so with FinalizeOps not causing problems, I will eventually exchange Finalization with one of the new packages in all clients. Finalization will not be removed until all its clients have been updated. Other packages [Cedar10.1]X11.df Uses the new FinalizeOps [Cedar10.1]FinalizeOps.df This old package is withdrawn. All known clients have been updated. [Cedar10.1]FinalizeOps0.df New packages, but, use of this package is discouraged. This is the new home of the old FinalizeOps package; saved just in case there were clients I didn't know about which are not willing to change. [Cedar10.1]CedarCore.df Remade. [Cedar10.1]XlShape.df Remade. [Cedar10.1]XlInputExtension.df Remade. Êï˜JšÐbsœ˜!Jšœ˜Jšœ ˜'Jšœ˜Jšœ˜ Jš œ˜'J˜head˜ IindentšÏt œž˜)Lšœ!ž˜$šÏb˜L˜á—šŸ ˜ L˜¾—šŸœ˜L˜õL˜z—šŸ œ˜ L˜×L˜IL˜——˜šœž˜L˜—˜L˜D—˜L˜É—˜L˜ —˜L˜ —˜#L˜ —L˜——…—„y *entry* 1653 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:48:33 pm PDT 1353 188 Date: Tue, 25 Aug 92 15:28:08 PDT From: jacobi:PARC:Xerox Subject: TIP, X11, X11TIP for Cedar10.1 To: CedarUsers:Parc:Xerox Cc: Cedar Coordinator:Parc:Xerox, jacobi Reply-to: Christian P Jacobi:PARC:Xerox TIP Fixed a PROCESS leak. Each stop and restarting used to leak 1 process as the process was neither Detached nor joined. This was never noticed with RawViewers, but it limited the lifetime of applications using X11 migration. Thanks to Hans Boehm for giving me the right hint. X11 1) Fixed another PROCESS leak: Reference counting of connections for shell widgets was wrongly initialized too high. 2) (Some weeks ago but no message was sent) Replaced locking implementation of CallWithLocks (from Ada like rendez-vous) to real two phase locking. (Comments in Xl.mesa now are wrong. "Caller MUST NOT hold lock of either TQ" is not true anymore) X11TIP Another PROCESS leak fixed; however this error did prevent the very same processes from beeing reused which also leaked in TIP. The two process leaks together did limit Slate to 23 migrations... Fixing only the first leak did increase the number of possible migrations to about 45... These debugging session was started because I was told "slate gets slugish after an hour use". None of the fixed problems would explain sluggishness, but, they were worth fixing nevertheless. ʶ˜JšÐbsœ˜!Jšœ˜Jšœ ˜'Jšœ˜Jšœ&˜(Jš œ˜'J˜head˜IindentšœÏkœÓ˜âL˜4—˜Lšœžœ_˜wLšœ•Ïs`œ˜ö—˜Lšœžœp˜—Ibode˜M˜M˜àM˜M˜—…—J *entry* 1248 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:49:29 pm PDT 1009 127 Date: Mon, 31 Aug 92 15:26:09 PDT From: jacobi:PARC:Xerox Subject: Re: Cedar10 X11ViewersI misbehavior In-reply-to: "Mike Spreitzer's message of Sat, 29 Aug 92 19:34:28 PDT" To: Mike Spreitzer Cc: Christian Jacobi 1) the cursor no longer changes shape Fixed after 4 hours of painful debugging; race condition: Notification of horrible death was slower then re-creation of new connection. 2) migration... Don't know what to do (I think I completely understand it, but I don't know how to fix it without efficiency loss). Given the major opcodes mentioned in the XError messages given, I assume that ImagerX11 was used. Viewers do asynchronous painting which doesn't stop immediately after widget destruction, ImagerX11 does not eat up the error messages. (Actually XlBitmapWindowImpl has the same problem painting asynchronously, except, the time window is much smaller) How bothering is this? I assume that all it does is some seconds of messages after migration, tell me if that is wrong. Christian Êy˜JšÐbsœ˜!Jšœ˜Jšœ%˜,Jš œ;˜FJšœ˜Jšœ˜J˜˜%J˜‡—J˜˜J˜sJ˜àJ˜J˜x—J˜J˜ J˜—…—òq *entry* 824 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:48:40 pm PDT 549 163 Date: Tue, 15 Sep 92 11:38:44 PDT From: jacobi:PARC:Xerox Subject: X11Handwriting for Cedar10.1 To: CedarUsers:PARC:Xerox, ParcPadInterest:PARC:Xerox Cc: Cedar Coordinator:Parc:Xerox, jacobi Reply-to: Christian P Jacobi:PARC:Xerox X11Handwriting DF files: [Cedar10.1]X11Handwriting.df Documentation: [Cedar10.1]X11HandwritingDoc.tioga Maintainer: Christian Jacobi New package Interactive handwriting recognition. While this is released and therefore working, it still needs some tweaking before I can promise stability... ʘJšÐbsœ˜!Jšœ˜Jšœ˜%Jšœ3˜5Jšœ&˜(Jš œ˜'J˜head˜IindentšÏt œž˜,Lšžœ žœžœž˜BLšž œ˜L˜LšÏb ˜ L˜$L˜l——…—&É *entry* 489 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:48:45 pm PDT 253 124 Date: Fri, 18 Sep 92 10:20:44 PDT From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: CedarUsers:Parc:Xerox Cc: jacobi Reply-to: Christian P Jacobi:PARC:Xerox X11 DF files: [Cedar10.1]X11.df Bug fix. Now can access little endian X servers. Êv˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ˜Jšœ˜ Jš œ˜'J˜head˜IindentšÏt œž˜!L˜L˜1——…—þz *entry* 635 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:49:00 pm PDT 393 130 Date: Thu, 01 Oct 92 21:12:52 PDT From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: CedarUsers:Parc:Xerox Cc: Cedar Coordinator:Parc:Xerox, Jacobi, FerretsII:OSBU North Reply-to: Christian P Jacobi:PARC:Xerox X11 DF files: [Cedar10.1]X11.df Tioga scrolling approximately 10 to 20 % faster. (Measured with wrist watch on black and white screen) (New module XlBWFriendsImpl.mesa) Ê|˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ˜Jšœ<˜>Jš œ˜'J˜head˜IindentšÏt œž˜!L˜L˜1L˜5L˜!——…—Š *entry* 1089 CreateMsg NoName:Parc:Xerox $ Selected@October 9, 1992 3:49:06 pm PDT 815 162 Date: Thu, 08 Oct 92 18:21:25 PDT From: jacobi:PARC:Xerox Subject: X11 for Cedar10.1 To: CedarUsers:Parc:Xerox, PCedarUsers:Parc:Xerox Cc: jacobi Reply-to: Christian P Jacobi:PARC:Xerox X11 DF files: [Cedar10.1]X11.df Bug fix; now also works on IBM PC X servers. As sort of a surprise, IBM PC X servers use % X11 -display parcfaxc -- X11MoreServerInfo bitmapFormatScanlineUnit: 8 bitmapFormatScanlinePad: 32 max request length words: 16376 max request length bytes: 65504 imageByteOrder: msbFirst bitmapFormatBitOrder: mostSignificant { 0.69 sec } % It is NOT a little endian X protocol (I'm glad I had access to a MIPS to debug the little endian access before). However, it is the first time I have encountered an X server with bitmapFormatScanlineUnit # bitmapFormatScanlinePad. That got me. Êœ˜JšÐbsœ˜!Jšœ˜Jšœ˜Jšœ/˜1Jšœ˜ Jš œ˜'J˜head˜IindentšÏt œžœ.˜OL˜˜+LšÏbœãÏiœŸ˜÷—L˜öL˜L˜L˜L˜——…—0Ò *entry* 2202 RelTOCEntries 24 31 Jan 92 jacobi:PARC... X11Tcl for PCedar2.0 155 1069 1224 191 44 1372 31 Jan 92 jacobi:PARC... X11, X11Viewers for PCedar2.0 1527 921 2448 171 1416 1204 06 Feb 92 jacobi:PARC... Preventing shared memory 2731 499 3230 121 2620 732 17 Feb 92 jacobi:PARC... Trip report from X window conference 3463 11249 14712 717 3352 12078 26 Feb 92 rws@expo.lc... Re: Request for registration of KeySyms 15541 963 16504 35 15430 1110 23 Mar 92 jacobi:PARC... X11 for Cedar10.1 16651 717 17368 148 16540 977 24 Mar 92 jacobi:PARC... X11 for Cedar10.1 17628 2593 20221 351 17517 3056 26 Mar 92 jacobi:PARC... XTkFeedback for Cedar10.1 20684 923 21607 200 20573 1235 27 Mar 92 jacobi:PARC... 8 packages for Cedar10.1 21919 2365 24284 486 21808 2963 27 Mar 92 jacobi:PARC... 7 more packages for Cedar10.1 24882 1735 26617 426 24771 2273 21 Apr 92 jacobi:PARC... X11 for Cedar10.1 27155 643 27798 162 27044 917 11 May 92 jacobi:PAR... X11, X11Demos, X11Viewers, Customize for Cedar10.1 28072 1451 29523 253 27961 1816 12 May 92 jacobi:PAR... X11 and X11Viewers for PCedar2.0 29888 395 30283 151 29777 658 11 Jun 92 jacobi:PARC... X11 for Cedar10.1 30546 1503 32049 175 30435 1790 01 Jul 92 jacobi:PARC:... X11Demos for Cedar10.1 32336 469 32805 130 32225 711 13 Jul 92 jacobi:PARC:... X11 for Cedar10.1 33047 317 33364 134 32936 563 15 Jul 92 jacobi:PARC:... XCommander for Cedar10.1 33610 1165 34775 162 33499 1439 22 Jul 92 jacobi:PARC:... SafeStorage, X11 for Cedar10.1 35049 1923 36972 245 34938 2280 25 Aug 92 jacobi:PARC... TIP, X11, X11TIP for Cedar10.1 37329 1353 38682 188 37218 1653 31 Aug 92 jacobi:PARC... Re: Cedar10 X11ViewersI misbehavior 38982 1009 39991 127 38871 1248 15 Sep 92 jacobi:PARC... X11Handwriting for Cedar10.1 40230 549 40779 163 40119 824 18 Sep 92 jacobi:PARC... X11 for Cedar10.1 41054 253 41307 124 40943 489 01 Oct 92 jacobi:PARC... X11 for Cedar10.1 41543 393 41936 130 41432 635 08 Oct 92 jacobi:PARC... X11 for Cedar10.1 42178 815 42993 162 42067 1089