Re: Touchscreen support in d-i
Christian PERRIER (02/05/2011): > I don't understand why a project is rejected *because* you're not DM > or DD. Is that Alioth policy? I think a DD/DM needs to vouch for it; I can do that btw. Mraw, KiBi. signature.asc Description: Digital signature
Re: Touchscreen support in d-i
Quoting Thibaut Girka (t...@sitedethib.com): > I've tried to open an alioth project for it, but it got rejected, as I'm > not a DM. Either someone here could convince alioth admins to create > this project, or it could be put elsewhere. I don't understand why a project is rejected *because* you're not DM or DD. Is that Alioth policy? > > Although I would prefer a separate project, I'm fine with it being > maintained under say, d-i/touchkbd.git. Yes, that's not optimal but you can still do that. -- signature.asc Description: Digital signature
Re: Touchscreen support in d-i
Le jeudi 03 mars 2011 à 20:13 +0100, Samuel Thibault a écrit : [...] > I believe the name should clearly say that it's meant for touchscreens. > Else you'll get mixed with all the on-screen keyboards which are meant > for accessibility. > > Could be something like "touchkbd". Let's go with touchkbd, then! I've tried to open an alioth project for it, but it got rejected, as I'm not a DM. Either someone here could convince alioth admins to create this project, or it could be put elsewhere. Although I would prefer a separate project, I'm fine with it being maintained under say, d-i/touchkbd.git. signature.asc Description: This is a digitally signed message part
Re: Touchscreen support in d-i
On Thu, Mar 3, 2011 at 18:48, Thibaut Girka wrote: > Le jeudi 03 mars 2011 à 18:23 +0100, Cyril Brulebois a écrit : >> Don't you want to maintain it under d-i/something.git on alioth? :) > > Why not, although it could really be used outside of d-i or even Debian, > and we still have to figure out the "something" part :) touchkbd as suggested by Samuel seems good. Or: Yet Another TouchScreen Virtual Keyboard - yatkbd :-) -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTimwQyNQfCz7aPR5e6o1DQHzZUbP-+=gexrop...@mail.gmail.com
Re: Touchscreen support in d-i
Cyril Brulebois, le Thu 03 Mar 2011 18:23:54 +0100, a écrit : > As for the name, xvkbd being already taken, maybe osk for on screen > keyboard? But then, googling it up will lead to http://www.osk.com/ I believe the name should clearly say that it's meant for touchscreens. Else you'll get mixed with all the on-screen keyboards which are meant for accessibility. Could be something like "touchkbd". Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110303191317.gi5...@const.famille.thibault.fr
Re: Touchscreen support in d-i
Le jeudi 03 mars 2011 à 18:23 +0100, Cyril Brulebois a écrit : > Don't you want to maintain it under d-i/something.git on alioth? :) Why not, although it could really be used outside of d-i or even Debian, and we still have to figure out the "something" part :) > (I can stick to git-hg, but my sending patches might be less comfy for > you as far as merging is concerned?) Merges are not a problem for me, but it might be for you, I don't really know how git-hg handles that... signature.asc Description: This is a digitally signed message part
Re: Touchscreen support in d-i
Hi again, Cyril Brulebois (02/03/2011): > Is that one known? > […] > That's with xserver 1.10 in experimental, if that matters (didn't > check what happens with 1.9). patch proposed and merged in hg. > > Anyway, it is usable already, and the current code can be found at > > http://hg.sitedethib.com/gikbd/ > > (ewww, hg :D. Fortunately the first thing I tried worked: >hg clone http://hg.sitedethib.com/gikbd > ) Don't you want to maintain it under d-i/something.git on alioth? :) (I can stick to git-hg, but my sending patches might be less comfy for you as far as merging is concerned?) As for the name, xvkbd being already taken, maybe osk for on screen keyboard? But then, googling it up will lead to http://www.osk.com/ KiBi. signature.asc Description: Digital signature
Re: Touchscreen support in d-i
Hi, Thibaut Girka (01/03/2011): > Just so you know, I've started a new virtual keyboard project to > address the second issue. \o/ Go Thibaut go! > However, the project is pretty young, suffers from a few bugs, its > code should be cleaned up a bit, there should be some way to save > additional space, and improve its look, so, any help would be > appreciated! Oh, and more importantly, it needs a proper name. Is that one known? | -(cyril@talisker)-(/tmp/gikbd)-() | $ make | cc -c main.c `pkg-config --cflags cairo pangocairo` -Wall -O0 | cc -c keyboard.c `pkg-config --cflags cairo pangocairo` -Wall -O0 | cc -c ui.c `pkg-config --cflags cairo pangocairo` -Wall -O0 | cc -o gikbd keyboard.o ui.o main.o `pkg-config --libs cairo pangocairo` -lX11 -lXtst -lxkbfile | -(cyril@talisker)-(/tmp/gikbd)-() | $ ./gikbd | X Error of failed request: BadValue (integer parameter out of range for operation) | Major opcode of failed request: 12 (X_ConfigureWindow) | Value in failed request: 0x0 | Serial number of failed request: 27 | Current serial number in output stream: 30 | -(cyril@talisker)-(/tmp/gikbd)-() | ret:1$ That's with xserver 1.10 in experimental, if that matters (didn't check what happens with 1.9). > Anyway, it is usable already, and the current code can be found at > http://hg.sitedethib.com/gikbd/ (ewww, hg :D. Fortunately the first thing I tried worked: hg clone http://hg.sitedethib.com/gikbd ) KiBi. signature.asc Description: Digital signature
Re: Touchscreen support in d-i
Just so you know, I've started a new virtual keyboard project to address the second issue. It is inspired by matchbox-keyboard to a certain extent and compatible with its GTK input method (meaning, if you have matchbox-keyboard-im and use it, the keyboard will pop up only when needed, as matchbox-keyboard used to). The main concern of this project is i18n: indeed, where all (I honestly haven't found one that doesn't) on-screen keyboards use their own format, and thus, require someone write a config file for each layout, this one will fetch both keyboard geometry (currently, it will use the "Alpha" section of pc105 keyboards) and layout from X (using XKB). This, plus pango for text rendering, should make it work out of the box for any layout. However, the project is pretty young, suffers from a few bugs, its code should be cleaned up a bit, there should be some way to save additional space, and improve its look, so, any help would be appreciated! Oh, and more importantly, it needs a proper name. Anyway, it is usable already, and the current code can be found at http://hg.sitedethib.com/gikbd/ signature.asc Description: This is a digitally signed message part
Re: Touchscreen support in d-i
Thibaut Girka, le Tue 22 Feb 2011 22:30:15 +0100, a écrit : > > I mean you can fetch it dynamically from the X server, and automatically > > display a keyboard appropriately. > > I'm not sure how it works. > We need some really special keyboard, not the geometry of a real > keyboard. Ok, then you can limit yourself to a part of the standard PC keyboard and only show that. > > You can even watch for layout > > reconfiguration, thus no need to explicitely connect with console-setup, > > just watch it change the X server layout. > > That would be the best way to do it I think! That's simply the X1 MappingNotify event. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2011031153.gw5...@const.famille.thibault.fr
Re: Touchscreen support in d-i
Since Squeeze has been released, I'm bringing back this topic, as I find it quite important. Le samedi 06 novembre 2010 à 17:52 +0100, Samuel Thibault a écrit : > Thibaut Girka, le Sat 06 Nov 2010 17:43:39 +0100, a écrit : [...] > > > You mean XLookupString ? > > > > Well, XLookupString works, but i thought there was a better way. > > I've made a quick and dirty modification to matchbox-keyboard, and it > > kinda works, but I'm not sure storing a list of keycode is really a good > > idea. > > What do you mean by "storing a list of keycode"? In a package? In the keyboard definition, so, in a package, yes. > I mean you can fetch it dynamically from the X server, and automatically > display a keyboard appropriately. I'm not sure how it works. We need some really special keyboard, not the geometry of a real keyboard. > You can even watch for layout > reconfiguration, thus no need to explicitely connect with console-setup, > just watch it change the X server layout. That would be the best way to do it I think! > > > Have a look at xkbprint, it exactly is able to show your keyboard as X > > > knows it. > > > > xkbprint prints the name of the keysyms, not the corresponding > > character... or I'm missing something. > > Well, yes, you can use XLookupString to convert the few ones where it'd > be needed to get a nicer output for the user (like eacute -> é, degree > -> °). I guess I just don't see what you think is missing from the X11 > protocol. Yeah, XLookupString is what I've ended up using. signature.asc Description: This is a digitally signed message part
Re: Touchscreen support in d-i
Thibaut Girka, le Sat 06 Nov 2010 17:43:39 +0100, a écrit : > Le samedi 06 novembre 2010 à 16:31 +0100, Samuel Thibault a écrit : > > Thibaut Girka, le Fri 05 Nov 2010 22:03:54 +0100, a écrit : > > > Hm, but how to do that? > > > I've had a quick look at what the gnome tools do, but it really seems > > > overly complicated. Moreover, we want a simplified keyboard. > > > Maybe we could just have keycodes in the keyboard definition, and use > > > xlib to do the keycode to keysym lookup (that way, the layout of the > > > virtual keyboard is the one set in X), but AFAIK, keycodes are > > > vendor-dependant, and I can't find an xlib function to do KeyCode/KeySym > > > to utf8 lookup. > > > > You mean XLookupString ? > > Well, XLookupString works, but i thought there was a better way. > I've made a quick and dirty modification to matchbox-keyboard, and it > kinda works, but I'm not sure storing a list of keycode is really a good > idea. What do you mean by "storing a list of keycode"? In a package? I mean you can fetch it dynamically from the X server, and automatically display a keyboard appropriately. You can even watch for layout reconfiguration, thus no need to explicitely connect with console-setup, just watch it change the X server layout. > > Have a look at xkbprint, it exactly is able to show your keyboard as X > > knows it. > > xkbprint prints the name of the keysyms, not the corresponding > character... or I'm missing something. Well, yes, you can use XLookupString to convert the few ones where it'd be needed to get a nicer output for the user (like eacute -> é, degree -> °). I guess I just don't see what you think is missing from the X11 protocol. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101106165215.gn13...@const.famille.thibault.fr
Re: Touchscreen support in d-i
Le samedi 06 novembre 2010 à 16:31 +0100, Samuel Thibault a écrit : > Thibaut Girka, le Fri 05 Nov 2010 22:03:54 +0100, a écrit : > > Hm, but how to do that? > > I've had a quick look at what the gnome tools do, but it really seems > > overly complicated. Moreover, we want a simplified keyboard. > > Maybe we could just have keycodes in the keyboard definition, and use > > xlib to do the keycode to keysym lookup (that way, the layout of the > > virtual keyboard is the one set in X), but AFAIK, keycodes are > > vendor-dependant, and I can't find an xlib function to do KeyCode/KeySym > > to utf8 lookup. > > You mean XLookupString ? Well, XLookupString works, but i thought there was a better way. I've made a quick and dirty modification to matchbox-keyboard, and it kinda works, but I'm not sure storing a list of keycode is really a good idea. > Have a look at xkbprint, it exactly is able to show your keyboard as X > knows it. xkbprint prints the name of the keysyms, not the corresponding character... or I'm missing something. > Samuel > > signature.asc Description: This is a digitally signed message part
Re: Touchscreen support in d-i
Thibaut Girka, le Fri 05 Nov 2010 22:03:54 +0100, a écrit : > Le jeudi 04 novembre 2010 à 23:40 +0100, Samuel Thibault a écrit : > > Thibaut Girka, le Thu 04 Nov 2010 23:09:53 +0100, a écrit : > > > Does it worth the pain of fixing them/adding new ones? Can't it be done > > > in a semi-automatic way? > > > > It should just support xkb-data layouts. > > Hm, but how to do that? > I've had a quick look at what the gnome tools do, but it really seems > overly complicated. Moreover, we want a simplified keyboard. > Maybe we could just have keycodes in the keyboard definition, and use > xlib to do the keycode to keysym lookup (that way, the layout of the > virtual keyboard is the one set in X), but AFAIK, keycodes are > vendor-dependant, and I can't find an xlib function to do KeyCode/KeySym > to utf8 lookup. You mean XLookupString ? Have a look at xkbprint, it exactly is able to show your keyboard as X knows it. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101106153158.gg13...@const.famille.thibault.fr
Re: Touchscreen support in d-i
Quoting Xavier Oswald (xosw...@debian.org): > Eh :) here Im. About this, if you think about gparted and such, if I well > remember it's a matter of including 4 libs (libstdc++, libgtkmm and 2 other > small libs I cannot remember). I'd say it's worth giving it a try..:-) signature.asc Description: Digital signature
Re: Touchscreen support in d-i
On 18:14 Fri 05 Nov , Otavio Salvador wrote: > Hello, > > On Fri, Nov 5, 2010 at 1:06 PM, Xavier Oswald wrote: > > On 07:59 Fri 05 Nov , Christian PERRIER wrote: > > > >> That could even someday revive some work about having a graphical > >> partitioner (old old old debate). > > > > Eh :) here Im. About this, if you think about gparted and such, if I well > > remember it's a matter of including 4 libs (libstdc++, libgtkmm and 2 other > > small libs I cannot remember). > > It is not that simple. We need to have it integrated with the rest of > installer and add the features that are not covered by it (if there're > any). That's true. My point was only to say that 4 libs are mising for gparted. If the di team decision is to integrate some C++ libs in the future, Im willing to help getting those into di and help integrating gparted or another tool or maybe rewrite some partman part. I don't know right now. Working around partitionning tools in di is my plan after squeeze release. Greetings, -- Xavier Oswald GNU/Linux Debian Developer - http://www.debian.org/ GPG key ID: 0x464B8DE3 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101105220257.ga5...@venus
Re: Touchscreen support in d-i
Le jeudi 04 novembre 2010 à 23:40 +0100, Samuel Thibault a écrit : > Thibaut Girka, le Thu 04 Nov 2010 23:09:53 +0100, a écrit : > > - How to detect that there is no physical keyboard? > > In principle console-setup should be able to detect that. In some cases > it might not be possible to determine it accurately, so it may be good > to keep an icon available to start it from the touchpad. Yeah, I've seen that. But an icon? I'm not sure where/how to do it... > > - There are only a few layouts, and they are often incomplete/too basic. > > Does it worth the pain of fixing them/adding new ones? Can't it be done > > in a semi-automatic way? > > It should just support xkb-data layouts. Hm, but how to do that? I've had a quick look at what the gnome tools do, but it really seems overly complicated. Moreover, we want a simplified keyboard. Maybe we could just have keycodes in the keyboard definition, and use xlib to do the keycode to keysym lookup (that way, the layout of the virtual keyboard is the one set in X), but AFAIK, keycodes are vendor-dependant, and I can't find an xlib function to do KeyCode/KeySym to utf8 lookup. Gtk has its own functions and tables to do that, however, maybe we could use it, as it's already in d-i. > Samuel > > signature.asc Description: This is a digitally signed message part
Re: Touchscreen support in d-i
Hello, On Fri, Nov 5, 2010 at 1:06 PM, Xavier Oswald wrote: > On 07:59 Fri 05 Nov , Christian PERRIER wrote: > >> That could even someday revive some work about having a graphical >> partitioner (old old old debate). > > Eh :) here Im. About this, if you think about gparted and such, if I well > remember it's a matter of including 4 libs (libstdc++, libgtkmm and 2 other > small libs I cannot remember). It is not that simple. We need to have it integrated with the rest of installer and add the features that are not covered by it (if there're any). -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik_cjygjnxbg1dhcryb=uywd8if1pygjqvu-...@mail.gmail.com
Re: Touchscreen support in d-i
On 07:59 Fri 05 Nov , Christian PERRIER wrote: > That could even someday revive some work about having a graphical > partitioner (old old old debate). Eh :) here Im. About this, if you think about gparted and such, if I well remember it's a matter of including 4 libs (libstdc++, libgtkmm and 2 other small libs I cannot remember). Greetings, -- Xavier Oswald GNU/Linux Debian Developer - http://www.debian.org/ GPG key ID: 0x464B8DE3 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101105150644.ga3...@venus
Re: Touchscreen support in d-i
Hello, On Fri, Nov 5, 2010 at 4:59 AM, Christian PERRIER wrote: > In short:assuming we restrict it to be available in g-i, we could work > on having a c++ library udeb. I don't object the idea however xinput-calibrator is not that big that porting it to C would be too difficult. I would prefer this route in this specific case. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=5v=mm_lobvdp3qstlfei42v1tvjy4=ms0p...@mail.gmail.com
Re: Touchscreen support in d-i
Quoting Thibaut Girka (t...@sitedethib.com): > However, xinput-calibrator is written in C++, and I don't think it's > welcome in d-i? > Maybe this could be reconsidered, xinput-calibrator could rewritten in > C, or something else could be chosen... I thought deeper about this after we had this conversation with Thibaut at Paris MiniDebConf. When we had that discussion several years ago, the concern was about memory impact (the size of the c++ libraries in the initrd). However, these constraints are highly relaxed on machines that run g-i. So, finally, I wonder whether we could reconsider this, at the express condition that C++ is only used for stuff related to the graphical installer.. That could even someday revive some work about having a graphical partitioner (old old old debate). In short:assuming we restrict it to be available in g-i, we could work on having a c++ library udeb. signature.asc Description: Digital signature
Re: Touchscreen support in d-i
Thibaut Girka, le Thu 04 Nov 2010 23:09:53 +0100, a écrit : > - How to detect that there is no physical keyboard? In principle console-setup should be able to detect that. In some cases it might not be possible to determine it accurately, so it may be good to keep an icon available to start it from the touchpad. > - There are only a few layouts, and they are often incomplete/too basic. > Does it worth the pain of fixing them/adding new ones? Can't it be done > in a semi-automatic way? It should just support xkb-data layouts. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101104224039.gl5...@const.famille.thibault.fr
Touchscreen support in d-i
This might not be the best moment to talk about that, but well... With the rise of tablet PCs, smartphones, etc., there are more and more computers with touchscreen as the primary input device, and possibly no real keyboard. In order to properly support such computers, d-i needs two things: touchscreen calibration and an on-screen keyboard. To address the first issue, we can run something like xinput-calibrator right after X is started (and save the result in the target's xorg.conf.d), it'll take care of everything, and won't show up if it doesn't detect any touchscreen. However, xinput-calibrator is written in C++, and I don't think it's welcome in d-i? Maybe this could be reconsidered, xinput-calibrator could rewritten in C, or something else could be chosen... I've already been working a bit on the second issue and have working matchbox-keyboard and matchbox-window-manager (a WM is needed in order for matchbox-keyboard to run properly) udebs. However, there is still a lot to do: - When should it be started? Currently, it's started right after X, with a script in /lib/debian-installer.d/ - How to detect that there is no physical keyboard? - The on-screen keyboard should use the selected layout. This should be easy by (re)starting matchbox-keyboard with some environment variables. - There are only a few layouts, and they are often incomplete/too basic. Does it worth the pain of fixing them/adding new ones? Can't it be done in a semi-automatic way? - What to do if the selected layout doesn't exist for matchbox? Let it fallback to the default one? Or should we display only matchbox-supported layouts? I think the first three points can be addressed by starting matchbox-keyboard from somewhere within console-setup, but I'm not too sure yet, as I have only had a quick look at this part of d-i. Any comment is welcome, Thibaut Girka. signature.asc Description: This is a digitally signed message part
