Umeet :: Talk

Alejandro Sánchez Acosta

The Organizing Comittee

MJesus	hola
MJesus	quienes van a traducir ?
ducky	yo colaboro con la presentacion
ducky	:)
MJesus	muy bien
MJesus	damage y ducky,
MJesus	alguien mas va a traducir a ingles ?
ducky	welcome to everyone
ducky	in this time, Alejandro Sanchez Acosta will present the Talk: Freedesktop: integration between desktops
ducky	he is a good member of the free software
ducky	he have done nice colaborations to the free software
ducky	he created hurd-es, colborates with kernelnewbies-es, mono
ducky	h
ducky	well lets begin
ducky	freedesktop is a free software proyect began by a red hat developer
ducky	Havop Pannington,
ducky	in order to integrate between the different desktops such as gnome or kde
ducky	this proyect tries to cover the needs that exist between the multiple desktops
ducky	in these days
ducky	for the integration is necessary, that exist integration at the applicationn level
ducky	under the used technologies
ducky	such as the standarization they manage
ducky	this proyect is helped by the X window technology
ducky	manly
ducky	and it uses technologies such as DnD, XClipboard, XFixes, Xlib, XDamage, etc.
ducky	in these moments have the support from gnome and kde developers
ducky	like Waldo Bastian or Alexander Larsson.
ducky	covering lot of needs this proyect have been collecting software which well talk later
ducky	Also to comment desktops such as XFCE, G
ducky	GNUstep,. or window managers as enlightment or window maker
ducky	are covered under this proyect
ducky	The freedesktop objective, apart from the integration
ducky	and standarization
ducky	is to create a common standard system for these desktops
ducky	is to offer to the user and developer the things they need
ducky	when an user wants to use a desktop he/she should find
ducky	applications with the same appariences. same management keys
ducky	same wey drag and drop
ducky	and it must gave to the developer a common base to develop this software
ducky	For example, DBUS use, an IPC mechanism, between the applications DCOP-like
ducky	with the advantage is indepent of the desktop is using
ducky	Apart from be released with this technology DBUS, it has its base wrote in C
ducky	let to use qt, glib based backends and others
ducky	as important data, it have been began used in gnome, with the gnome-volume-manager
ducky	and now kde 3.4 will use together with HAL
ducky	for the device detection trough DBUs, hotpluggind and sysfs
ducky	it supported on a library libhal, which provide the API to the developer
ducky	and it has a agent's set which are in charge of retrieve the information
ducky	an libhal example use, would be system-device-manager, which is obtain devices from the systema
ducky	such as pcmcias, network cards, etc..
ducky	and show information about these devices
ducky	this base together with DUBS, sysfs, udev y hotplugging
ducky	which lets that proyect such as
ducky	gnome-volume-manager or kde-volume-manger
ducky	obtain information when the device is plugged and what should do in that situation
ducky	on gnome, it would be is known as Robert love's utopia proyect
ducky	Also its adapted to device detection on gnome-vfs
ducky	for device acess
ducky	device://
ducky	or on kde
ducky	media:/
damage	in the part of KDE Volume Manager, actualy he can comprove the kdenonbeta like module of KControl, for the
damage	part of recognition of device, although it will not be integrated until KDE 4.0.
damage	Really serious the own mechanism of hot-and-plug, in which when introducing for example a camera says to you that it has
damage	been recognized or which if you want to export to GPhoto or digikam, the photos that it has in the own camera.
damage	Another one of the interesting projects within freedesktop, is the support rendez-vous. At the moment there is diverse implementations of rendez-vouses based on libmdns or Avahi.
damage	Like common project that it has been adopted within GNOME and KDE, the use of libmdns, that the discovery of devices in network allows, such as printing, switches, routers, discovery of services, like smb, ssh,..
damage	If somebody is interested, can watch the progress of gnome-vfs with the patches of Alexander Larsson on gnome-vfs or watch in kdebase/libmdns. At the moment in KDE it is used for discovery of services of Samba, ssh, machines in network or for the configuration of printers (kdeaddwizard).
damage	Freedesktop, another preoccupation that has arisen, is to have a common base multimedia for different writing-desks. Within GNOME it was the use of esound like sound servant and to gstreamer like framework multimedia.
damage	In KDE at the moment aRts, as much worked like framework multimedia, servant of sound. They are beginning to consider to use common technologies based on Gstreamer like framework, and Polypaudio like sound servant.
damage	Other options that are beginning to comment are based on networkmultimedia (nmm) to also assure transparency network, MAS, Jack, etc..
damage	Another one of the projects integrated in Freedesktop is Cairo, one libreria of vectorial graphs for the handling of pixmaps, drawn and renderizated, able to have several backends such as PostScript or openGL.
damage	This lib within GNOME tries to replace GDK for all the drawn one. Library in if it were XR/XC, their name of XRender and XComposite. The drawn part of does everything in off-screen in secondary memory, like XComposite XDamage works along with, and soon all render uses XRender.
damage	In GNOME it is tried to use for release it of gtk+ 2,8, reason why it will be necessary still to hope. Within the KDE project, the drawn part of makes QPainter, now in Qt 3.3.3, and it will migrate to the model of Arthur used in Qt4, reason why not yet there is no plan.
damage	Other projects, like gtk-qt-engine, try to obtain that the same appearance between several
damage	writing-desks exists. This library, which does is that applications of Gtk+,
damage	are seen in Qt, like native, drawing own the Gtk+ with QPainter to obtain a same appearance.
damage	At the moment the model used for drawn in writing-desks is based so much on pixmaps as in engines. The model of pixmaps is used less by the fact that he is slower, so the based one on engines will need to have engines for both platforms, is the example of bluecurve like industrial/qindustrial well.
damage	As much with gtk-qt-engine as with the model of engine for each platform the objective is able to have the same appearance, something wished by the end user. Also I will comment about Galago, of which there has been something of problematic in subjects of adoption between writing-desks.
damage	The Galago project is framework of notification within GNOME adopted within Freedesktop. This it allows to establish notifications between applications of any type, from an event of a connected contact, to lowering a new mail, etc..
damage	n KDE it would come to be what it is known like KNotify. The problem here is plus the own adoption of Galago when something in KDE already existed, perhaps reason why it is complicated that their use is standard, separate that is not independent of platform.
damage	i mean, Galago continues using glib, another problem that for example I see in Gstreamer, since both are not independent of platform, the base it is in C, and there is writing-desks in other languages like Objetive C or C++.
damage	In order to obtain that these technologies have a base of common software, they must add the smaller number of possible requirements, not to have a great load. It is perhaps why the possibility is watched of using network multimedia in KDE and to continue using KNotify.
damage	Although Freedesktop is considered as it bases common, in my opinion will be necessary to rectify the use of certain technologies, as it is the case previously commented. Soon other projects like enchant exist, that includes a base common for the use of spellcheckers in the writing-desk, using underneath as much ispell, as aspell among others.
damage	Also interesting he is libburn, one library for the recording of cds, although not very maintained. At the moment of the problem that is the developers, is that as much in cdrtools, as the passage to dvdrtools, by código/licences problems, is that they must end up using cdrecord for all the recording without telling on one library, being employee of much information that uses cdrecord.
damage	As for example it is the infromación of exit that gives the recording tool. Soon tools of validation of files exist, as desktop-it cases out-utils them, that are in charge of the validation of volders and .desktops.
damage	Now already having commented great variety of the technologies, it would only want to speak of Xorg, since there are many projects within Freedesktop. Xorg at the moment is within many distributions as they are Fedora, Mandrake or Gentoo like tecnology X Window, contributing improvements based so much on XFixes, as XDamage like XCompositor.
damage	These extensions came from Kdrive, the servant of Keith Packard. Providing characteristic like real transparencies. Having finished with all these technologies, there are many more like fribidi, eventuallity, dri, fontconfig, scim, jhbuild, pkgconfig, etc..
damage	you can consult in: http://www.freedesktop.org/wiki/Software
damage	If you want to consult on other projects, you can comment it to me, although now only I speak a little of the part of standardization. Common or consolidated standards so that they comment within the project are based on CORBA like model of communication, UTF-8 like codification of carccters or XML.
damage	Cradles in the writing-desk we would have ICCCM, EWMH, cradles in extensions of the Xs, the type XDnD, XClipboard, XFixes, XEiE, etc, menus, directory bases, keybindings, png, SVG, etc..
damage	For example, the part of desktop-cases out-utils is in charge of the validation according to certain specification of menus, folders and desktops.
damage	Desktops is not more than files than contain characteristics associated to entrances in menus, like name of application, icon, commando to execute, and even services.
damage	For example, something useful of desktops is the Service Menus, which they allow the possibility of associating services to certain applications, used for example in Konqueror.
damage	So that they allow these services us to install packages deb, to see an image, etc.. For the part of configuration there are standards based on XSettings.
damage	Also others based on recent files, the wastebasket or trash, subjects of icons exist...
damage	With this much interoperability is also obtained.
damage	For example, something useful would be to have an associated standard to post office or to mbox/maildir, so that they kept in certain format, certain directory and following such jerarquia.
damage	So that pudieramos to see the mail using as much Kmail, as Evolution, like Sylpheed or others.
damage	To the equal one with feeds of the news for the part to specify the RSS, where they keep, urls used, information of the lowered heads and the content..
damage	where the user indeterminely used the application that he wanted. And this he would be mainly what is freedesktop, that objective it has, that tecnologias are tried to include like as a greater integration can be obtained.
damage	As project website you have: http://www.freedesktop.org/
damage	And soon the lists of the projects and freedesktop in: http://lists.freedesktop.org/mailman/listinfo/
damage	so if there is some question, it doubts or explanation this is the moment.
damage	end.
damage	alejandro, you could comment the subject of PaX with XOrg?
damage	trulux: in the lists of xorg, according to I know not yet has commented nothing.
damage	trulux: I have not proven PaX with Xorg either, so surely that you know it better than I.
damage	you see very dificult that the different own writing-desks let their estandars to adapt to those of freedesktop?
damage	case gnome and kde?
damage	andipin: it is obtained, for example with the specification of subjects of icons, of folders/menus/desktops...