Re: Not getting hildon theme for Armel terget and unable to build for Armel terget
Hi, I think you should use a x86 target for working with Hildon/Xephyr definitely right. The armel target is only meant for cross-compiling. Please use the x86 target for your applications and in combination with Xephyr. This you find as well in the release notes [1]. And Bruno Araújo pointed as well to the right place to solve the mmap problem [2] [1] http://repository.maemo.org/stable/4.1.2/maemo-sdk-relnotes_4.1.2.txt [2] http://maemo.org/community/maemo-developers/re-not_getting_hildon_theme_for_armel_terget_and_unable_to_build_for_armel_terget/?org_openpsa_qbpager_net_nemein_discussion_posts_page=1#482ea660464811dea98a9727c370bb95bb95 Cheers Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 device and Maemo Fremantle SDK beta
Hi, all important information about Fremantle and links to the documentation you find here: http://wiki.maemo.org/Task:Maemo_roadmap/Fremantle Cheers daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 device and Maemo Fremantle SDK beta
Hi, just for the records: The beta sdk doesn't run on the beagleboard (yet). So at this very moment there is no arm hardware to run fremantle stuff on. Till Am Freitag 22 Mai 2009 schrieb Frank Banul: No and no. You can use the x86 scratchbox target or get a beagleboard. Frank On Thu, May 21, 2009 at 6:57 PM, diptiman roy roy.dipti...@yahoo.co.in wrote: Hi, Is maemo fremantle beta is compiable with N810. Can we use it for developing application for N810? Please, inform me. DIPTIMAN ROY Explore and discover exciting holidays and getaways with Yahoo! India Travel Click here! ___ 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GtkAction vs. AppMenu
On Thu, 2009-05-21 at 17:28 +0200, Alberto Garcia wrote: On Tue, May 19, 2009 at 05:24:47PM +0200, Cornelius Hald wrote: First of all, sorry for the delay :) No problem at all. I really appreciate your help :) They are not supposed to show up, but they should work. I've just tested it here and it works fine. If you can send your test case I can take a look at it. Well, I don't really have a test case, but rather a complete application ;) The complete source can be found here: https://garage.maemo.org/viewvc/trunk/conboy/src/interface.c?view=markuproot=conboypathrev=134 The menu starts around line 280. Note that Fremantle specific code is marked with #ifdef HILDON_HAS_APP_MENU. But so that you don't have to read through this big and ugly file, I'll try to outline what I do with one of the actions. Casts etc. are removed to make it less cluttered: action = gtk_toggle_action_new(bold, Bold, NULL, GTK_STOCK_BOLD)); gtk_action_set_accel_group(action, accel_group); gtk_action_set_accel_path(action, ACCEL_PATH_STYLE_BOLD); gtk_accel_map_add_entry(ACCEL_PATH_STYLE_BOLD, GDK_b, GDK_CONTROL_MASK); text_style_menu = hildon_app_menu_new(); menu_bold = gtk_button_new(); gtk_action_connect_proxy(action_bold, menu_bold); hildon_app_menu_append(text_style_menu, menu_bold); The result is a menu with the correct labels on the buttons and the correct behavior - only the accelerators (here Ctrl+b) do not work. 2) How do I get my GtkRadioActions to work with the HildonAppMenu? I created the the buttons with gtk_radio_button_new() and then used gtk_action_connect_proxy() like with the normal GtkActions above. The problem is that now all of the radio buttons are selected active at the same time. Try using gtk_radio_button_new_from_widget () to create all buttons after the first one. I'll tried in three different ways with different outcomes. Unfortunately non of them was good :( First, my GtkRadioActions are set up like this: a1 = gtk_radio_action_new(size:small, Small), NULL, NULL, 0); a2 = gtk_radio_action_new(size:normal, Normal), NULL, NULL, 1); a3 = gtk_radio_action_new(size:large, Large), NULL, NULL, 2); gtk_radio_action_set_group(a1, action_group); action_group = gtk_radio_action_get_group(a1); gtk_radio_action_set_group(a2, action_group); action_group = gtk_radio_action_get_group(a2); gtk_radio_action_set_group(a3, action_group); action_group = gtk_radio_action_get_group(a3); gtk_radio_action_set_current_value(a2, 1); Now we come to the part, where I create the buttons. I tried these three different ways: /* Correctly shown, but not reacting on gtk_radio_action_set_current_value() */ but1 = gtk_radio_button_new(NULL); but2 = gtk_radio_button_new_from_widget(but1); but3 = gtk_radio_button_new_from_widget(but1); /* All shown as active */ but1 = gtk_radio_button_new(NULL); but2 = gtk_radio_button_new(NULL); but3 = gtk_radio_button_new(NULL); /* Same effect as with NULL /* but1 = gtk_radio_button_new(action_group); but2 = gtk_radio_button_new(action_group); but3 = gtk_radio_button_new(action_group); Then I simply connect the buttons with the actions gtk_action_connect_proxy(a1, but1); gtk_action_connect_proxy(a2, but2); gtk_action_connect_proxy(a3, but3); In all cases the label text is correctly taken from the actions, so I would say there is a connection somehow. I couldn't find examples for using GtkRadioAction with GtkRadioButton and gtk_action_connect_proxy() on the net, so it would really help me if you would take the time to look into it again :) Thanks! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 device and Maemo Fremantle SDK beta
hi, but at least the alpha sdk works following the [1] instructions. https://garage.maemo.org/forum/forum.php?forum_id=3532 Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 device and Maemo Fremantle SDK beta
hi, but at least the alpha sdk works following the [1] instructions. [1] https://garage.maemo.org/forum/forum.php?forum_id=3532 Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GtkAction vs. AppMenu
On Fri, 2009-05-22 at 16:00 +0200, Alberto Garcia wrote: On Fri, May 22, 2009 at 03:24:01PM +0200, Cornelius Hald wrote: Try also this: gtk_window_add_accel_group (window, accel); I have this, it was only not included in my mail. Look at the correction I sent in a subsequent e-mail: try using gtk_toggle_button_new() instead of gtk_radio_button_*() Ah sorry, I was reading your correction wrong. I was reading radio instead of toggle. So now I tried it with gtk_toggle_button_new() and with gtk_radio_button_new() and the result is the same only the graphical representation is different. Then I started again the Diablo version just to notice that the behavior is the same there... Arrg it looks like at some point I completely f***ed up my event handling... So it seems like the solution was already in your post from yesterday. I'll check my code and then report back here. I'm sorry if I have caused you unnecessary work. Thanks again! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GtkAction vs. AppMenu
On Fri, 2009-05-22 at 16:20 +0200, Cornelius Hald wrote: So it seems like the solution was already in your post from yesterday. I'll check my code and then report back here. Good, I checked again. I had a small bug which prevented the radio buttons to select the normal entry, but the rest was still working. The result now is: - gtk_toggle_button_new() is working but it displays the buttons as toggle buttons not as radio buttons. - Everything else what I tried is not working. Here are two screenshots to show the difference. RadioButtons: http://zwong.de/wp-content/uploads/2009/05/conboy_new_style_menu.png ToggleButtons: http://zwong.de/wp-content/uploads/2009/05/toggle_buttons.png The thing is, that semantically those buttons should really be radio buttons not toggle buttons, so if anyone has more suggestions please write them. If not I'll shut up for now. Hmm... and there is still this accelerator thing... ;) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo Eclipse Integration 2nd Edition Beta 1 released
Hi, Maemo team is happy to announce the availability of Maemo Eclipse Integration 2nd Edition Beta 1 release. Official release information is here: - Announcement: http://maemo.org/news/announcements/maemo_eclipse_integration_2nd_edition_beta_1_released/ - Release Notes: http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_beta1 - Known Issues: http://wiki.maemo.org/Eclipse_integration/KnownIssues_beta1 - Beta 1 New Features and plan for Beta 2: http://wiki.maemo.org/Eclipse_integration I want to thank everyone who has contributed and helped to get this release done! Next project milestone is Beta 2 end of June as said in our public release and feature plan. Cheers, //Jarmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Eclipse Integration 2nd Edition Beta 1 released
That's very good news! Big thanks to everyone who was involved. I'm using Alpha 2 at the moment and I really really do like it :) I'll switch to the Beta as soon as I can. If here is anyone who never tied it - try it! It's good :) Cheers! Conny On Fri, 2009-05-22 at 17:25 +0200, jarmo.ti...@nokia.com wrote: Hi, Maemo team is happy to announce the availability of Maemo Eclipse Integration 2nd Edition Beta 1 release. Official release information is here: - Announcement: http://maemo.org/news/announcements/maemo_eclipse_integration_2nd_edition_beta_1_released/ - Release Notes: http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_beta1 - Known Issues: http://wiki.maemo.org/Eclipse_integration/KnownIssues_beta1 - Beta 1 New Features and plan for Beta 2: http://wiki.maemo.org/Eclipse_integration I want to thank everyone who has contributed and helped to get this release done! Next project milestone is Beta 2 end of June as said in our public release and feature plan. Cheers, //Jarmo ___ 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: GtkAction vs. AppMenu
On Fri, May 22, 2009 at 05:08:08PM +0200, Cornelius Hald wrote:
The result now is:
- gtk_toggle_button_new() is working but it displays the buttons as
toggle buttons not as radio buttons.
Well, that's what looks better in the Fremantle UI style. So even
if you use gtk radio buttons directly (i.e, without gtk actions) I
suggest you to do something like this:
gtk_toggle_button_set_mode (GTK_TOGGLE_BUTTON (radio_button), FALSE);
Of course you can still use the traditional radio button look if you
want, see the attached example (it might help you with the keyboard
accelerators too).
Berto
#includehildon/hildon.h
static void
radio_action_changed(GtkAction *action,
GtkAction *current)
{
g_debug (Radio action changed: %s, gtk_action_get_name (current));
}
static void
action_activated(GtkAction *action)
{
g_debug (Button clicked: %s, gtk_action_get_name (action));
}
static GtkAction *
create_action (const gchar *name,
const gchar *accel,
GtkActionGroup *actiongroup,
GtkAccelGroup *accelgroup)
{
GtkAction *action = gtk_action_new (name, name, NULL, NULL);
gtk_action_group_add_action_with_accel (actiongroup, action, accel);
gtk_action_set_accel_group (action, accelgroup);
gtk_action_connect_accelerator (action);
g_signal_connect (action, activate, G_CALLBACK (action_activated), NULL);
return action;
}
static GtkButton *
create_item (GtkAction *action)
{
HildonSizeType buttonsize = HILDON_SIZE_FINGER_HEIGHT | HILDON_SIZE_AUTO_WIDTH;
GtkWidget *button = hildon_gtk_button_new (buttonsize);
gtk_action_connect_proxy (action, button);
return GTK_BUTTON (button);
}
static GtkRadioAction *
create_radio_action (const gchar *name,
GtkRadioAction *previous)
{
static gint count = 0;
GtkRadioAction *action = gtk_radio_action_new (name, name, NULL, NULL, count++);
if (previous) {
gtk_radio_action_set_group (action, gtk_radio_action_get_group (previous));
}
return action;
}
static GtkButton *
create_radio_item (GtkRadioAction *action)
{
static GSList *group = NULL;
HildonSizeType buttonsize = HILDON_SIZE_FINGER_HEIGHT | HILDON_SIZE_AUTO_WIDTH;
GtkWidget *button = hildon_gtk_radio_button_new (buttonsize, group);
group = gtk_radio_button_get_group (GTK_RADIO_BUTTON (button));
gtk_action_connect_proxy (GTK_ACTION (action), button);
return GTK_BUTTON (button);
}
static HildonAppMenu *
create_menu (GtkAccelGroup *accel)
{
HildonAppMenu *menu = HILDON_APP_MENU (hildon_app_menu_new ());
GtkActionGroup *group = gtk_action_group_new (actiongroup);
GtkAction *action;
GtkRadioAction *radioaction;
/* Items */
action = create_action (Action one, Ctrl1, group, accel);
hildon_app_menu_append (menu, create_item (action));
action = create_action (Action two, Ctrl2, group, accel);
hildon_app_menu_append (menu, create_item (action));
action = create_action (Action three, Ctrl3, group, accel);
hildon_app_menu_append (menu, create_item (action));
action = create_action (Action four, Ctrl4, group, accel);
hildon_app_menu_append (menu, create_item (action));
/* Filters */
radioaction = create_radio_action (Radio one, NULL);
g_signal_connect (radioaction, changed, G_CALLBACK (radio_action_changed), NULL);
gtk_toggle_action_set_active (GTK_TOGGLE_ACTION (radioaction), TRUE);
hildon_app_menu_add_filter (menu, create_radio_item (radioaction));
radioaction = create_radio_action (Radio two, radioaction);
hildon_app_menu_add_filter (menu, create_radio_item (radioaction));
radioaction = create_radio_action (Radio three, radioaction);
hildon_app_menu_add_filter (menu, create_radio_item (radioaction));
gtk_widget_show_all (GTK_WIDGET (menu));
return menu;
}
int
main(int argc,
char **argv)
{
GtkWidget *win;
GtkWidget *label;
HildonAppMenu *menu;
GtkAccelGroup *accel;
hildon_gtk_init (argc, argv);
label = gtk_label_new (This is an example of the\nHildonAppMenu widget.\n\n
Click on the titlebar\nto pop up the menu.);
gtk_label_set_justify (GTK_LABEL (label), GTK_JUSTIFY_CENTER);
win = hildon_stackable_window_new ();
accel = gtk_accel_group_new ();
menu = create_menu (accel);
hildon_window_set_app_menu (HILDON_WINDOW (win), menu);
gtk_window_add_accel_group (GTK_WINDOW (win),
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
mmap: No such device or address
Hi, I am not able to build application for ARMEL terget. [sbox-DIABLO_ARMEL:~]qmake mmap: No such device or address I already modified /etc/sysctl.conf: vm.vdso_enabled = 0 vm.mmap_min_addr = 4096 net.ipv4.ip_local_port_range = 1024 65535 and executed 'sysctl -p' as root DIPTIMAN ROY Explore and discover exciting holidays and getaways with Yahoo! India Travel http://in.travel.yahoo.com/___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GtkAction vs. AppMenu
On Fri, 2009-05-22 at 19:00 +0200, Alberto Garcia wrote: On Fri, May 22, 2009 at 05:08:08PM +0200, Cornelius Hald wrote: The result now is: - gtk_toggle_button_new() is working but it displays the buttons as toggle buttons not as radio buttons. Well, that's what looks better in the Fremantle UI style. Yes, the Hildon HIG seems to suggest this, though it's very vague due to the non-native-speaker English and the lack of screenshots (I filed bugs about that already): http://maemo.org/api_refs/5.0/beta/hig/html/ch06s08.html However, if radio buttons are meant to look a certain way in Maemo, why isn't that just a matter of theming or even of making a change in the GTK+ code instead of asking people to use the GTK+ API in an abnormal way? So even if you use gtk radio buttons directly (i.e, without gtk actions) I suggest you to do something like this: gtk_toggle_button_set_mode (GTK_TOGGLE_BUTTON (radio_button), FALSE); Of course you can still use the traditional radio button look if you want, see the attached example (it might help you with the keyboard accelerators too). Berto ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- 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
Could not start Xephyr (Maemo 5 Beta SDK). Please help me to resolve. ()
Hi, I have installed Maemo 5 Beta SDK. I followed the installation instructions from, http://maemo.org/development/sdks/maemo_5-0_installation/#sdkinstaller. After installing scratchbox and Maemo SDK, I tried to start Xephyr, I could not start and I am getting the following error message, Please help me to resolve. kksr...@kksrini-laptop:~$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac [1] 13354 kksr...@kksrini-laptop:~$ Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed Thanks, Srini ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
