![]() #GEDIT FOR MAC OS X ARCHIVE#At their core, RPM and DEB are a tarball-like archive with some metadata. Havoc Pennington: I don’t really understand the motivation for autopackage. Some clients right now do things that are just stupid for example, allocating huge pixmaps (image buffers) and keeping them around improved profiling tools should help track down and fix these mistakes.Įugenia Loli-Queru: Is working towards a package management standard? While RPM and DEBs are well known, what is your opinion on ? The proposed Composite extension also allows double buffering the entire screen, which should let us fix virtually all flicker and tearing Most users will perceive all of those problems as “slowness.”Įliminating the round trip to clients to handle expose events will probably be a huge improvement in terms of both flicker and speed. Graphics will look bad if you have flicker, tearing, OR slow) won’t lead to understanding of the problem. Havoc Pennington: Talking only about speed (fast vs. You like to see the server do to make it easier to write fast client applications? Rayiner Hashem: From your experience with GTK+, what do you think are some of the properties that make it hard to write fast applications for X11? What would Many of the things on would be implemented in or used by the toolkit: icon themes, XEMBED, X server, Cairo, startup notification, and so forth. Rather, it’s an effort to build a base desktop platform that desktops can build on. Havoc Pennington: I don’t really think of as an interoperability effort anymore. Interoperation at the toolkit level is necessary? What form would this interoperation take? Yet, you mentioned GTK+ 3 and Qt 4 as well. Rayiner Hashem: Most of the examples listed in your Nove Hrady presentation were desktop level. The other issue requires even less explanation: application authors don’t support DND in enough places. #GEDIT FOR MAC OS X CODE#source code and document what types are already used. The starting point is to go through GNOME, KDE, Mozilla,, etc. ![]() So we need a registry of types documenting the type name and the format of the data transferred under that name. ![]() Applications simply don’t agree on what these types are. Types that you support dragging or dropping, such as “text/plain”. When you add drag and drop to an application you have a list of Havoc Pennington: The issue isn’t poor implementation in the libraries, it’s simpler than that. Are there plans for a drag-and-drop library to ease the implementation of XDND functionality? Rayiner Hashem: In your presentation at Nove Hrady, you point out that drag and drop still doesn’t work as it should, mainly because of poor implementations. In the article, we discuss about general goals, status and issues, the role of KDE/Qt in the road to interoperability with Gnome/GTK+, HAL (with new screenshots), the new X Server aiming to replace XFree86 and we even have an exclusive preliminary screenshot of a version of Mac OS X’s Exposé window management feature for this new X Server! This is one article not to be missed if you are into Unix/Linux desktop! Today we are very happy to publish a very interesting Q&A with major members: the founder Havoc Pennington (also of Debian, Gnome and Red Hat fame), Waldo Bastian (of SuSE & KDE fame), Keith Packard and Jim Gettys (of X/XFree86/fontconfig/w3c fame) and David Zeuthen, a new member who’s taking over the ambitious HAL project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |