Re: Fremantle user interface behaviour and API
Brent Chiodo wrote: Anyway, there needs to be a solution, because right now it's unworkable. I filled a bug: https://bugs.maemo.org/show_bug.cgi?id=4619 Hopefully someone will change that. Please vote for it! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
Brent Chiodo wrote: Anyway, there needs to be a solution, because right now it's unworkable. I think the same, if there would be at least a property that could be set to enable/disable text selection, but just removing it cannot be the solution. Should a developer really be forced to use either scrolling or text selection? The question is, is it still possible to make changes to the hildon API or are we too late? Hmm, I asked that 2 minutes ago already - but still ;) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On 5/14/09, Cornelius Hald h...@icandy.de wrote: Panable Area How exactly should I use it? I replaced my ScrollableWindow with a PanableArea, the rest of the code I left as it is in Diablo. Inside the PanableArea is a GtkTextBox. Nothing else. Now, it renders correctly, that is it has only this small scroll indicator and not a real scroll bar. But I cannot pan. If I try to pan it always selects the text inside the text box. How is this supposed to work? How is the destinction made between selecting text and scrolling/panning the text? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers I have also run into this problem trying to update Quick Clip (the text viewer part). If anyone here uses Quick Clip in Diablo, you will see I have implemented Kinetic scrolling (via mokoui.FingerScroll) by having a toggle-button to toggle whether the TextView is selectable or not. The toggle-button callback is very simple (this is in Python): def select_mode_button_callback(self, widget, button=False, check=False): if button == True: active = self.select_mode_button.get_active() self.m_select_mode.set_active(active) if check == True: active = self.m_select_mode.get_active() self.select_mode_button.set_active(active) if active == True: self.textview.set_sensitive(True) self.textview.set_editable(False) else: self.textview.set_sensitive(False) Basically it just toggles the Textview sensitive/insensitive. But if you try to do this in Fremantle, it grays out the Textview (when insensitive) making the text unreadable. Maybe a viable solution would be to not gray out the Textview? Anyway, there needs to be a solution, because right now it's unworkable. -- Best Regards, Brent Chiodo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
There's API to set the orientation mode of your window in hildon, but I think this is not yet in the SDK. You can get a more recent version from git: git clone https://git.maemo.org/projects/hildon I just downloaded a snapshot of the git repository, but I cannot find anything related in hildon-window.h. Also grep -i orientation * -R doesn't show up anything interesting. For what do I have to search? Thanks! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
Graham Cobb escribiu: On Friday 22 May 2009 18:20:55 Sergio Villar Senin wrote: Modest uses a pannable area which contains the text editor. Thus it's not possible to select text in that way in Fremantle. You'll have to use the keyboard. Not having experienced this I don't want to overreact but ... Are you saying that in Freemantle there is no easy way to select and copy text out of an email to copy into somewhere else? E.g. copying a phone number or address into a contact, copying an email address from a forwarded email into the destination of another email, copying a portion of a URL (the base URL without all the tracking junk included) into a web browser, copying the directions for a meeting into a separate email, copying some text and a picture from one email into another? As Claudio said you can use the keyboard for copypaste (killyank) operations. Regarding Modest, take into account that we're trying to reduce as much as possible the need of copypaste. In order to do that, we try to identify as much as possible the relevant information for the user by hyperlinkifying things like email addreses, phone numbers, sip addresses. Clicking on those links could trigger external applications like contacts applications, web browsers, IM applications, SIP/VoIP applications or whatever is installed in the system. And if the information comes in the form of an attached file, then there is no problem as you could archive it using Modest. Br ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thu, 2009-05-21 at 14:47 +0200, Cornelius Hald wrote: On Thu, 2009-05-21 at 14:11 +0200, Alberto Garcia wrote: In principle that feature is not officially supported in Fremantle, and adding support in HildonTextView might create inconsistencies between similar-looking apps/dialogs that could be quite confusing. But of course we can reconsider it (I don't have the last word, though). I'll see what we can do. Well, if there is any chance to reconsider, that would be great. I myself would be very happy and I think a bunch of other developers too. I mean a big scrollable/panable text view is quite common for a lot of applications. Mail clients, ebook readers, word processors, chat programs, etc. all profit from copypast for which we need a way of selecting text. [snip] It would be interesting to know what UI Modest has for this in Fremantle when editing large emails. Personally I can't get that far in my own eccentric scratchbox target. -- murr...@murrayc.com www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
Murray Cumming escribiu: On Thu, 2009-05-21 at 14:47 +0200, Cornelius Hald wrote: On Thu, 2009-05-21 at 14:11 +0200, Alberto Garcia wrote: In principle that feature is not officially supported in Fremantle, and adding support in HildonTextView might create inconsistencies between similar-looking apps/dialogs that could be quite confusing. But of course we can reconsider it (I don't have the last word, though). I'll see what we can do. Well, if there is any chance to reconsider, that would be great. I myself would be very happy and I think a bunch of other developers too. I mean a big scrollable/panable text view is quite common for a lot of applications. Mail clients, ebook readers, word processors, chat programs, etc. all profit from copypast for which we need a way of selecting text. [snip] It would be interesting to know what UI Modest has for this in Fremantle when editing large emails. Personally I can't get that far in my own eccentric scratchbox target. Modest uses a pannable area which contains the text editor. Thus it's not possible to select text in that way in Fremantle. You'll have to use the keyboard. Br ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Friday 22 May 2009 18:20:55 Sergio Villar Senin wrote: Modest uses a pannable area which contains the text editor. Thus it's not possible to select text in that way in Fremantle. You'll have to use the keyboard. Not having experienced this I don't want to overreact but ... Are you saying that in Freemantle there is no easy way to select and copy text out of an email to copy into somewhere else? E.g. copying a phone number or address into a contact, copying an email address from a forwarded email into the destination of another email, copying a portion of a URL (the base URL without all the tracking junk included) into a web browser, copying the directions for a meeting into a separate email, copying some text and a picture from one email into another? Please tell me that these are all supported design goals for the Freemantle GUI. Have I just misunderstood this thread? Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
El vie, 22-05-2009 a las 18:52 +0100, Graham Cobb escribió: On Friday 22 May 2009 18:20:55 Sergio Villar Senin wrote: Modest uses a pannable area which contains the text editor. Thus it's not possible to select text in that way in Fremantle. You'll have to use the keyboard. Not having experienced this I don't want to overreact but ... Are you saying that in Freemantle there is no easy way to select and copy text out of an email to copy into somewhere else? You can use the keyboard to copy and paste. There are shift and arrows keys. Claudio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
On Tue, May 19, 2009 at 04:51:47PM +0200, Cornelius Hald wrote: When using HildonTextView inside a PanableArea panning is working fine, but I can no longer select text. Are those two mutual exclusive? In HildonTextView you cannot select text with the pointer. This is so by design: https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=commit;h=b34c64c879c7e86488adbe8000f2f3f2be162a73 I think that with both features enabled user interaction can be quite difficult/confusing if e.g. there's a big text view occupying a significant part of the screen. Berto ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
Alberto Garcia wrote: On Tue, May 19, 2009 at 04:51:47PM +0200, Cornelius Hald wrote: When using HildonTextView inside a PanableArea panning is working fine, but I can no longer select text. Are those two mutual exclusive? In HildonTextView you cannot select text with the pointer. This is so by design: https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=commit;h=b34c64c879c7e86488adbe8000f2f3f2be162a73 I think that with both features enabled user interaction can be quite difficult/confusing if e.g. there's a big text view occupying a significant part of the screen. Personally I think the developer should have the choice :) http://www.youtube.com/watch?v=4TxAIScXQvk Look at 3:20 onwards David -- Don't worry, you'll be fine; I saw it work in a cartoon once... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
On Thu, 2009-05-21 at 12:00 +0200, Alberto Garcia wrote: On Tue, May 19, 2009 at 04:51:47PM +0200, Cornelius Hald wrote: When using HildonTextView inside a PanableArea panning is working fine, but I can no longer select text. Are those two mutual exclusive? In HildonTextView you cannot select text with the pointer. This is so by design: https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=commit;h=b34c64c879c7e86488adbe8000f2f3f2be162a73 I think that with both features enabled user interaction can be quite difficult/confusing if e.g. there's a big text view occupying a significant part of the screen. Thanks for the clarification Berto! But then, what is the recommend way to produce a finger friendly text view that is editable and scrollable/panable? Big scrollbars again? I thought scrollbars where considered evil for Fremantle?! I'm a bit confused now, I thought that panning/selecting would probably work like in the Diablo webbrowser. That is, that you start a selection with a double tap. Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thu, May 21, 2009 at 12:57:00PM +0200, Cornelius Hald wrote: But then, what is the recommend way to produce a finger friendly text view that is editable and scrollable/panable? [...] I thought that panning/selecting would probably work like in the Diablo webbrowser. That is, that you start a selection with a double tap. In principle that feature is not officially supported in Fremantle, and adding support in HildonTextView might create inconsistencies between similar-looking apps/dialogs that could be quite confusing. But of course we can reconsider it (I don't have the last word, though). I'll see what we can do. Berto ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thu, 2009-05-21 at 14:11 +0200, Alberto Garcia wrote: In principle that feature is not officially supported in Fremantle, and adding support in HildonTextView might create inconsistencies between similar-looking apps/dialogs that could be quite confusing. But of course we can reconsider it (I don't have the last word, though). I'll see what we can do. Well, if there is any chance to reconsider, that would be great. I myself would be very happy and I think a bunch of other developers too. I mean a big scrollable/panable text view is quite common for a lot of applications. Mail clients, ebook readers, word processors, chat programs, etc. all profit from copypast for which we need a way of selecting text. And while I'm on it, I think a flag for enabling/disabling this feature would be good as well. Then for example I could turn selections and editing off when in portrait mode and turn it on if in landscape mode. This way it would be easier to create read-only (or limited) UIs when the device is in portrait mode. Thanks for caring :) Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
Thanks to Claudio and API almost all my questions have been answered and the Fremantle version of Conboy is looking better then ever :) There is (for now) only one question left: When using HildonTextView inside a PanableArea panning is working fine, but I can no longer select text. Are those two mutual exclusive? It would be nice if I could get another hint on that. Cheers! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
Cornelius Hald wrote: Thanks to Claudio and API almost all my questions have been answered and the Fremantle version of Conboy is looking better then ever :) There is (for now) only one question left: When using HildonTextView inside a PanableArea panning is working fine, but I can no longer select text. Are those two mutual exclusive? FWIW, I managed to implement this quite easily for Qt so I'm sure it's do-able in gtk too. The trick I used is to create a queue of mouse events until I could determine whether or not the incoming gesture was a panning gesture. If it was the queue was discarded; if not the events were replayed to the correct widgets. The decision was simply delta mouse movement within a time period. This allowed selection and even drag'n'drop to just work. David -- Don't worry, you'll be fine; I saw it work in a cartoon once... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
On Tue, 2009-05-19 at 16:48 +0100, David Greaves wrote: Cornelius Hald wrote: Thanks to Claudio and API almost all my questions have been answered and the Fremantle version of Conboy is looking better then ever :) There is (for now) only one question left: When using HildonTextView inside a PanableArea panning is working fine, but I can no longer select text. Are those two mutual exclusive? FWIW, I managed to implement this quite easily for Qt so I'm sure it's do-able in gtk too. The trick I used is to create a queue of mouse events until I could determine whether or not the incoming gesture was a panning gesture. If it was the queue was discarded; if not the events were replayed to the correct widgets. The decision was simply delta mouse movement within a time period. This allowed selection and even drag'n'drop to just work. That sounds nice, but I was more hoping for a out-of-the-box solution. I think this use-case is quite common - it's just a scrollable (ok panable) text view. So doing like you did I would consider as last resort. Anyways, thanks for explaining your solution :) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
Cornelius Hald wrote: That sounds nice, but I was more hoping for a out-of-the-box solution. I think this use-case is quite common - it's just a scrollable (ok panable) text view. So doing like you did I would consider as last resort. Anyways, thanks for explaining your solution :) Err I implemented that into the framework so it *is* an out of the box solution for Qt :) I kinda meant that it could/should be doable for the pannable gtk too. Nb the source to both is available so you can see how I did it in Qt and port it and submit it if you like. David -- Don't worry, you'll be fine; I saw it work in a cartoon once... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
On Thu, 2009-05-14 at 15:12 +0200, API wrote: From: Cornelius Hald h...@icandy.de Tree View I changes the code from using gtk_tree_view_new() to hildon_gtk_tree_view_new(). I thought this would give me a finger friendly version of the tree view, but I cannot see a difference between the hildon and the gtk version. Also the different HildonUIModes have no effect for me. What is the supposed outcome? How do I get the tree view to be finger friendly? I'm using a GtkListStore as backend and the view shows two sortable columns - if that matters. If you want to see the differences between the HildonUIModes, you can try to take a look to the hildon-pannable-area-touch-list-example, included on the examples directories. AFAIK, the example package is not included with the beta, but you can download the hildon-widgets source code and compile it by yourself. This example compare the two hildon modes and the old behaviour. Thanks, I didn't know that there were examples... I downloaded and compiled them. Now it's time for playing :) To avoid breaking legacy applications, the proper theming is done only to treeviews inside a pannable area. If you put your treeview inside a pannable area, you'll get finger-friendly sized rows. Ok, I changed that too and the result is looking good. Still I have two more questions: 1. Which signal gets emitted when one of the rows is selected? This is still a normal treeview, you use hildon_gtk_tree_view_new only to ensure to get the proper theming. So when one of the rows are selected the GtkTreeSelection of this treeview emits the signal changed [1]. I checked my code again and yes, the signals are emitted. The problem was, that I was using gtk_tree_view_get_selection() inside a row-activated handler which does not work with the hildonized tree view. I changed my code to use the provided GtkTreePath and now it's working fine. In the same way, recently a new signal was added to the maemo-flavoured gtk, so if a row is tapped on the treeview, the treeview emits the signal hildon-row-tapped, this could be useful to you too although I'm not sure if it was included on this beta, take a look to the gtk code to confirm that. I tried and it is included in the beta SDK. In which way should that be different from row-activated? For me it looks like both are doing the same. So I'll stick to row-activated for now. I hope this helps It helped a lot. Thank you very much! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
From: Cornelius Hald h...@icandy.de On Thu, 2009-05-14 at 15:12 +0200, API wrote: If you want to see the differences between the HildonUIModes, you can try to take a look to the hildon-pannable-area-touch-list-example, included on the examples directories. AFAIK, the example package is not included with the beta, but you can download the hildon-widgets source code and compile it by yourself. This example compare the two hildon modes and the old behaviour. Thanks, I didn't know that there were examples... I downloaded and compiled them. Now it's time for playing :) Yes, for any reason the package libhildon1-examples were not included with the SDK, when in the end, can be really useful, as currently we have an example for almost all hildon widgets, and in the complex ones, like pannable area, several examples. I hope that this package will be included on the future final SDK. This is still a normal treeview, you use hildon_gtk_tree_view_new only to ensure to get the proper theming. So when one of the rows are selected the GtkTreeSelection of this treeview emits the signal changed [1]. I checked my code again and yes, the signals are emitted. The problem was, that I was using gtk_tree_view_get_selection() inside a row-activated handler which does not work with the hildonized tree view. I changed my code to use the provided GtkTreePath and now it's working fine. Remember that row-activated is different to selection. On the desktop, on the treeview, if you select another element, the GtkTreeSelection emits the signal selection change, but this doesn't mean that the row is activated. To do that you need to explicitly activate the row, in the desktop you do a double-click on the row selected. In this sense, you can use a normal treeview on hildon (without the special modes), and this should work properly. In the same way, recently a new signal was added to the maemo-flavoured gtk, so if a row is tapped on the treeview, the treeview emits the signal hildon-row-tapped, this could be useful to you too although I'm not sure if it was included on this beta, take a look to the gtk code to confirm that. I tried and it is included in the beta SDK. In which way should that be different from row-activated? For me it looks like both are doing the same. So I'll stick to row-activated for now. The difference is that with the new HILDON_UI_MODE_NORMAL, used to select elements easily, the treeview will not have any selection, and any press on any row will emit the normal row-activated, as the interaction with the screen is different on a embeded device (the one hildon is oriente for). This new hildon-row-tapped was oriented to the mode HILDON_UI_MODE_EDIT, that requires to now when the user taps on any row, as the selection could not change, and it is slightly different to activate the row. I hope this helps It helped a lot. Thank you very much! You are welcome ;) === API (apinhe...@igalia.com) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
On Mon, 2009-05-18 at 11:35 +0200, API wrote: Thanks, I didn't know that there were examples... I downloaded and compiled them. Now it's time for playing :) Yes, for any reason the package libhildon1-examples were not included with the SDK, when in the end, can be really useful, as currently we have an example for almost all hildon widgets, and in the complex ones, like pannable area, several examples. I hope that this package will be included on the future final SDK. I contacted the SDK people regarding this; they will be adding the libhildon1-doc and libhildon1-examples packages to the next SDK release. The reason why they were missing is that these packages are new in Fremantle and when I added them to the distribution I forgot to contact the SDK people about it. Claudio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Fremantle user interface behaviour and API
Hi Everyone, I'm sitting on the train and my notebooks battery just went flat, the sockets are not working because of some electricity problems (yea Deutsche Bahn), so I don't have the API nor my code in front of me. That said please excuse wrong spelling of function names etc... I'm having some quesions about the Fremantle UI. Hopefully someone can help and save me hours of boring try-and-error :) Panable Area How exactly should I use it? I replaced my ScrollableWindow with a PanableArea, the rest of the code I left as it is in Diablo. Inside the PanableArea is a GtkTextBox. Nothing else. Now, it renders correctly, that is it has only this small scroll indicator and not a real scroll bar. But I cannot pan. If I try to pan it always selects the text inside the text box. How is this supposed to work? How is the destinction made between selecting text and scrolling/panning the text? Tree View I changes the code from using gtk_tree_view_new() to hildon_gtk_tree_view_new(). I thought this would give me a finger friendly version of the tree view, but I cannot see a difference between the hildon and the gtk version. Also the different HildonUIModes have no effect for me. What is the supposed outcome? How do I get the tree view to be finger friendly? I'm using a GtkListStore as backend and the view shows two sortable columns - if that matters. Context Menu How are context menues supposed to work in Fremantle? If the main menu is now finger friendly then the context menu should be too I think. How do I generate such a menu? Is there API or do I just create a GtkMenuShell with some big buttons in it? Does this new 2-finger-tap-thing generate a normal right-mouse-click event or something else? Changeing device orientation I think I read that using the device in portrait mode should give the user a simple version of the application. E.g. the user can only view, but not edit content. Also the UI then should be usable with one hand. Further it was written, that the HildonAppMenu changes in portrait mode from 2x5 items to 1x10 items. How do other widgets like the tree view react to changes of the device orientation? And is there a way to test this with the current SDK? Ok, I think that's it for now... I hope this mail doesn't contain too many stupid questions that have been answered elsewhere already. I welcome your input. Thanks :) Uff, this was probably the longest text I've ever written on my N810 :) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thu, May 14, 2009 at 11:02:45AM +0200, Cornelius Hald wrote: Hi Everyone, I'm sitting on the train and my notebooks battery just went flat, the sockets are not working because of some electricity problems (yea Deutsche Bahn), so I don't have the API nor my code in front of me. That said please excuse wrong spelling of function names etc... I'm having some quesions about the Fremantle UI. Hopefully someone can help and save me hours of boring try-and-error :) Just for the record, the hildon library team has moved the hildon code to garage, and we created there a mailing list for this kind of questions and to get some feedback. You can find it in https://garage.maemo.org/pipermail/hildon-devel/ Panable Area How exactly should I use it? I replaced my ScrollableWindow with a PanableArea, the rest of the code I left as it is in Diablo. Inside the PanableArea is a GtkTextBox. Nothing else. Now, it renders correctly, that is it has only this small scroll indicator and not a real scroll bar. But I cannot pan. If I try to pan it always selects the text inside the text box. How is this supposed to work? How is the destinction made between selecting text and scrolling/panning the text? In the particular case of text areas, panning is not really possible since the text area will process the dragging as text selection and won't propagate the event back to the pannable. A solution for this involves overriding some event handlers in the text area. You can check HildonTextView for a way to handle this, although I'd recommend you to use it directly. Tree View I changes the code from using gtk_tree_view_new() to hildon_gtk_tree_view_new(). I thought this would give me a finger friendly version of the tree view, but I cannot see a difference between the hildon and the gtk version. Also the different HildonUIModes have no effect for me. What is the supposed outcome? How do I get the tree view to be finger friendly? I'm using a GtkListStore as backend and the view shows two sortable columns - if that matters. To avoid breaking legacy applications, the proper theming is done only to treeviews inside a pannable area. If you put your treeview inside a pannable area, you'll get finger-friendly sized rows. Context Menu How are context menues supposed to work in Fremantle? If the main menu is now finger friendly then the context menu should be too I think. How do I generate such a menu? Is there API or do I just create a GtkMenuShell with some big buttons in it? For application menus it is recommended to use HildonAppMenu. For context sensitive menus, please create them using hildon_gtk_menu_new() to get proper theming. Does this new 2-finger-tap-thing generate a normal right-mouse-click event or something else? Changeing device orientation I think I read that using the device in portrait mode should give the user a simple version of the application. E.g. the user can only view, but not edit content. Also the UI then should be usable with one hand. Further it was written, that the HildonAppMenu changes in portrait mode from 2x5 items to 1x10 items. How do other widgets like the tree view react to changes of the device orientation? And is there a way to test this with the current SDK? There's API to set the orientation mode of your window in hildon, but I think this is not yet in the SDK. You can get a more recent version from git: git clone https://git.maemo.org/projects/hildon Claudio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thursday 14 May 2009 11:25:32 Claudio Saavedra wrote: On Thu, May 14, 2009 at 11:02:45AM +0200, Cornelius Hald wrote: I'm having some quesions about the Fremantle UI. Hopefully someone can help and save me hours of boring try-and-error :) Just for the record, the hildon library team has moved the hildon code to garage, and we created there a mailing list for this kind of questions and to get some feedback. You can find it in https://garage.maemo.org/pipermail/hildon-devel/ Please DO NOT move this sort of discussion to a hildon-devel list. This is exactly what maemo-developers is for! Surely I am not the only Maemo community developer who knows that at some time they may have to port their application's existing GUI to Freemantle? I am not a GUI guy and won't be re-designing the GUI. If someone else does, that is great but I am likely to end up trying to make whatever easy changes I can to make it work (or work better) on Freemantle. This sort of discussion is very useful. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
I definitely second Graham's opinion! Luca Donaggio On Thu, May 14, 2009 at 1:03 PM, Graham Cobb g+...@cobb.uk.netg%2b...@cobb.uk.net wrote: On Thursday 14 May 2009 11:25:32 Claudio Saavedra wrote: On Thu, May 14, 2009 at 11:02:45AM +0200, Cornelius Hald wrote: I'm having some quesions about the Fremantle UI. Hopefully someone can help and save me hours of boring try-and-error :) Just for the record, the hildon library team has moved the hildon code to garage, and we created there a mailing list for this kind of questions and to get some feedback. You can find it in https://garage.maemo.org/pipermail/hildon-devel/ Please DO NOT move this sort of discussion to a hildon-devel list. This is exactly what maemo-developers is for! Surely I am not the only Maemo community developer who knows that at some time they may have to port their application's existing GUI to Freemantle? I am not a GUI guy and won't be re-designing the GUI. If someone else does, that is great but I am likely to end up trying to make whatever easy changes I can to make it work (or work better) on Freemantle. This sort of discussion is very useful. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
Fully agree too Fred Luca Donaggio a écrit : I definitely second Graham's opinion! Luca Donaggio On Thu, May 14, 2009 at 1:03 PM, Graham Cobb g+...@cobb.uk.net mailto:g%2b...@cobb.uk.net wrote: On Thursday 14 May 2009 11:25:32 Claudio Saavedra wrote: On Thu, May 14, 2009 at 11:02:45AM +0200, Cornelius Hald wrote: I'm having some quesions about the Fremantle UI. Hopefully someone can help and save me hours of boring try-and-error :) Just for the record, the hildon library team has moved the hildon code to garage, and we created there a mailing list for this kind of questions and to get some feedback. You can find it in https://garage.maemo.org/pipermail/hildon-devel/ Please DO NOT move this sort of discussion to a hildon-devel list. This is exactly what maemo-developers is for! Surely I am not the only Maemo community developer who knows that at some time they may have to port their application's existing GUI to Freemantle? I am not a GUI guy and won't be re-designing the GUI. If someone else does, that is great but I am likely to end up trying to make whatever easy changes I can to make it work (or work better) on Freemantle. This sort of discussion is very useful. Graham ___ maemo-developers mailing list maemo-developers@maemo.org mailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thu, 2009-05-14 at 12:03 +0100, Graham Cobb wrote: On Thursday 14 May 2009 11:25:32 Claudio Saavedra wrote: On Thu, May 14, 2009 at 11:02:45AM +0200, Cornelius Hald wrote: I'm having some quesions about the Fremantle UI. Hopefully someone can help and save me hours of boring try-and-error :) Just for the record, the hildon library team has moved the hildon code to garage, and we created there a mailing list for this kind of questions and to get some feedback. You can find it in https://garage.maemo.org/pipermail/hildon-devel/ Please DO NOT move this sort of discussion to a hildon-devel list. This is exactly what maemo-developers is for! Surely I am not the only Maemo community developer who knows that at some time they may have to port their application's existing GUI to Freemantle? I am not a GUI guy and won't be re-designing the GUI. If someone else does, that is great but I am likely to end up trying to make whatever easy changes I can to make it work (or work better) on Freemantle. Yes, well, I kinda agree with you. To be honest, that was a bit of self-promotion for the mailing list; but what we would actually like to end up with in the hildon-devel mailing list is with discussion related to the development of the library itself, which would be off-topic here, IMHO. So, sorry for misleading you, I am watching this mailing list and will be answering questions here, no worries about that. Claudio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
On Thursday 14 May 2009 12:15:18 Claudio Saavedra wrote: On Thu, 2009-05-14 at 12:03 +0100, Graham Cobb wrote: Please DO NOT move this sort of discussion to a hildon-devel list. This is exactly what maemo-developers is for! Surely I am not the only Maemo community developer who knows that at some time they may have to port their application's existing GUI to Freemantle? Yes, well, I kinda agree with you. To be honest, that was a bit of self-promotion for the mailing list; but what we would actually like to end up with in the hildon-devel mailing list is with discussion related to the development of the library itself, which would be off-topic here, IMHO. That sounds good to me. So, sorry for misleading you, I am watching this mailing list and will be answering questions here, no worries about that. Thanks. I am sure I will have some questions for you! Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Aw: Re: Fremantle user interface behaviour and API
Thank you very much for your answer. I got back electricity for about one hour, so i was able to test most of what you wrote. My comments are below. Panable Area How exactly should I use it? I replaced my ScrollableWindow with a PanableArea, the rest of the code I left as it is in Diablo. Inside the PanableArea is a GtkTextBox. Nothing else. Now, it renders correctly, that is it has only this small scroll indicator and not a real scroll bar. But I cannot pan. If I try to pan it always selects the text inside the text box. How is this supposed to work? How is the destinction made between selecting text and scrolling/panning the text? In the particular case of text areas, panning is not really possible since the text area will process the dragging as text selection and won't propagate the event back to the pannable. A solution for this involves overriding some event handlers in the text area. You can check HildonTextView for a way to handle this, although I'd recommend you to use it directly. I'm now using HildonTextView inside a PanableArea and panning is working fine. Hmm, the only problem now is that selecting text is nolonger possible. Are those two mutally exclusive? Tree View I changes the code from using gtk_tree_view_new() to hildon_gtk_tree_view_new(). I thought this would give me a finger friendly version of the tree view, but I cannot see a difference between the hildon and the gtk version. Also the different HildonUIModes have no effect for me. What is the supposed outcome? How do I get the tree view to be finger friendly? I'm using a GtkListStore as backend and the view shows two sortable columns - if that matters. To avoid breaking legacy applications, the proper theming is done only to treeviews inside a pannable area. If you put your treeview inside a pannable area, you'll get finger-friendly sized rows. Ok, I changed that too and the result is looking good. Still I have two more questions: 1. Which signal gets emitted when one of the rows is selected? 2. What is the recommended icon size to use in the finger friendly version of a tree view row to match the size of the text? Context Menu How are context menues supposed to work in Fremantle? If the main menu is now finger friendly then the context menu should be too I think. How do I generate such a menu? Is there API or do I just create a GtkMenuShell with some big buttons in it? For application menus it is recommended to use HildonAppMenu. For context sensitive menus, please create them using hildon_gtk_menu_new() to get proper theming. I will try that as soon as I get back electricity :) Does this new 2-finger-tap-thing generate a normal right-mouse-click event or something else? Any thoughts on that? Changeing device orientation I think I read that using the device in portrait mode should give the user a simple version of the application. E.g. the user can only view, but not edit content. Also the UI then should be usable with one hand. Further it was written, that the HildonAppMenu changes in portrait mode from 2x5 items to 1x10 items. How do other widgets like the tree view react to changes of the device orientation? And is there a way to test this with the current SDK? There's API to set the orientation mode of your window in hildon, but I think this is not yet in the SDK. You can get a more recent version from git: git clone https://git.maemo.org/projects/hildon One last question, how do I create a text label that matches the size of a HildonTextEntry field? Thanks again Claudio for all this useful information! Cheers! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Aw: Re: Fremantle user interface behaviour and API
From: Cornelius Hald h...@icandy.de Tree View I changes the code from using gtk_tree_view_new() to hildon_gtk_tree_view_new(). I thought this would give me a finger friendly version of the tree view, but I cannot see a difference between the hildon and the gtk version. Also the different HildonUIModes have no effect for me. What is the supposed outcome? How do I get the tree view to be finger friendly? I'm using a GtkListStore as backend and the view shows two sortable columns - if that matters. If you want to see the differences between the HildonUIModes, you can try to take a look to the hildon-pannable-area-touch-list-example, included on the examples directories. AFAIK, the example package is not included with the beta, but you can download the hildon-widgets source code and compile it by yourself. This example compare the two hildon modes and the old behaviour. To avoid breaking legacy applications, the proper theming is done only to treeviews inside a pannable area. If you put your treeview inside a pannable area, you'll get finger-friendly sized rows. Ok, I changed that too and the result is looking good. Still I have two more questions: 1. Which signal gets emitted when one of the rows is selected? This is still a normal treeview, you use hildon_gtk_tree_view_new only to ensure to get the proper theming. So when one of the rows are selected the GtkTreeSelection of this treeview emits the signal changed [1]. In the same way, recently a new signal was added to the maemo-flavoured gtk, so if a row is tapped on the treeview, the treeview emits the signal hildon-row-tapped, this could be useful to you too although I'm not sure if it was included on this beta, take a look to the gtk code to confirm that. I hope this helps === API (apinhe...@igalia.com) [1] http://library.gnome.org/devel/gtk/stable/GtkTreeSelection.html#GtkTreeSelection-changed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle user interface behaviour and API
Hi, Graham Cobb wrote: On Thursday 14 May 2009 11:25:32 Claudio Saavedra wrote: Just for the record, the hildon library team has moved the hildon code to garage, and we created there a mailing list for this kind of questions and to get some feedback. You can find it in https://garage.maemo.org/pipermail/hildon-devel/ Please DO NOT move this sort of discussion to a hildon-devel list. This is exactly what maemo-developers is for! Surely I am not the only Maemo community developer who knows that at some time they may have to port their application's existing GUI to Freemantle? ... This sort of discussion is very useful. In general, the example of something like gtk-devel-list is probably useful - if you have a question about *using* the GTK+ library as a developer, then a GNOME devel list is probably appropriate. If you have a question about the actual implementation, then gtk-devel-list is the right place. I see Hildon as similar - hildon-devel-list could be the mailing list for the developers of Hildon, maemo-developers would be for developers building on the Maemo platform - which, of course, includes libhildon*. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
