Re: Default mail client settings
:2010-05-02T16:29:Matthew Smith: Hi Folks I am looking for the system settings which determine the default e-mail client for Maemo 5. I want to try running Claws Mail in place of Modest and want all the Share by Email buttons and the like to point to the new application. Google has not given me an answer - where is this configured? Cheers M PS - it appears that Claws Mail doesn't integrate with Contacts in that it can't access it as an address book, but I'm planning to move everything over to LDAP, so not an issue. I've been making some noise on the forums a while ago about a similar thing. Though in my case I want it to be for alpine. I'd really like to see a generic switchboard application that allows changing: mime/filetype associations - i.e. I want all videos and audio opened with mplayer browser selection - just incorporate browser switchboard into it mail client selection - make it possible to define who handles it easily There's probably a few things more but those are the things I'd like to see. I know that contacts sends a mailto: dbus event so I guess to have it run that on email one would need to listen on that and then pass the mailto param off to an arbitrary(as in anything script, direct command etc..) command for further processing. I believe but am not sure that browser-switchboard already does this for links. Maybe someone here will have enough interest to get this off the ground. Regards -- Andraž 'ruskie' Levstik Source Mage GNU/Linux Games/Xorg grimoire guru Re-Alpine Coordinator http://sourceforge.net/projects/re-alpine/ Geek/Hacker/Tinker Be sure brain is in gear before engaging mouth.___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Displaying the information of the MMC card and the phone memory
not sure if you are using the QT framework for writing your code. have you considered using the QT mobility framework, its still beta, but seems close to completion/delivery. *for storage device info.* http://doc.qt.nokia.com/qtmobility-1.0/qsystemstorageinfo.html http://doc.qt.nokia.com/qtmobility-1.0/qsystemstorageinfo.html *status of the api's* http://doc.qt.nokia.com/qtmobility-1.0/index.html#platform-compatability http://doc.qt.nokia.com/qtmobility-1.0/index.html#platform-compatability http://qt.nokia.com/developer/new-qt-apis http://qt.nokia.com/developer/new-qt-apis if you arent using QT, then how about some command line stuff ? http://wiki.maemo.org/Desktop_Command_Execution_Widget_scripts#Disk_usage http://wiki.maemo.org/Desktop_Command_Execution_Widget_scripts#Disk_usage you could also use hal-device command to get various device info. cheers krk969 - Original Message - From: Pallavi Kandhare Sent: 05/12/10 06:39 AM To: maemo-developers@maemo.org Subject: Displaying the information of the MMC card and the phone memory Hi All I want to write code in Maemo for the foll: 1. Displaying the information of the MMC card and the phone memory (ie. used space, free space) When i use functions in libhal-storage.h i get an error: undefined reference to function_name 2. On mobile certain aplications are running at a time. (ed. clock, calender etc). How can i find out and list all these applications. Can anybody help me with the API or any info in this matter? Regards. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Keeping backlight on
Thanks, the first method (dbus) works with no issue. Regards, -Saurabh On Tue, May 11, 2010 at 10:07 PM, Yves-Alexis Perez cor...@debian.orgwrote: On 11/05/2010 12:54, David Weinehall wrote: An (undocumented) alternative is: gconftool -s --type int /system/osso/dsm/display/inhibit_blank_mode 3 Replace the 3 for whatever inhibit mode you want: 0 -- No display blanking inhibit 1 -- Inhibit dimming/blanking if charger is connected 2 -- Allow dimming, but inhibit blanking if charger is connected 3 -- Inhibit dimming/blanking 4 -- Allow dimming, but inhibit blanking And that'll change the user setting, which might not be a good idea from an application developer pov. Cheers, -- Yves-Alexis ___ 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: Displaying the information of the MMC card and the phone memory
Hi Pallavi! On Wed, May 12, 2010 at 8:39 AM, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: Hi All I want to write code in Maemo for the foll: 1. Displaying the information of the MMC card and the phone memory (ie. used space, free space) When i use functions in libhal-storage.h i get an error: undefined reference to function_name Where are you using libhal-storage? Did you include output of $(pkg-config --libs hal-storage) to appropriate place of what you are using? 2. On mobile certain aplications are running at a time. (ed. clock, calender etc). How can i find out and list all these applications. ps -e shows all active processes including all applications. hildon-desktop definitely knows it as it shows all apps in dashboard, however, I'm not sure there is an API available for this purpose. Can anybody help me with the API or any info in this matter? Regards. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers @Ram: The name of framework is Qt. QT is Apple's QuickTime. Thanks, Daniil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Displaying the information of the MMC card and the phone memory
Hi,
On Wed, 2010-05-12 at 07:39 +0200, ext Pallavi Kandhare wrote:
..
2. On mobile certain aplications are running at a time. (ed. clock,
calender etc). How
can i find out and list all these applications.
There is nothing very convenient for this but you can do it using the
same API as the window manager (hildon-desktop) uses: XQueryTree and
reading some window properties with XGetWindowProperty. You could get a
some kind of list by taking top-level (== parent is the root window)
windows that have _NET_WM_WINDOW_TYPE property set to
_NET_WM_WINDOW_TYPE_NORMAL.
I'm attaching the source code of a small utility that uses XQueryTree,
you could use it as a starting point.
-Kimmo
#include X11/Xlib.h
#include X11/Xatom.h
#include stdio.h
#include stdlib.h
#include string.h
static Atom class_atom, name_atom, name_atom2, xembed_atom, pid_atom,
trans_atom, hildon_stack_atom,
utf8_string_atom,
current_app_atom, win_type_atom, wm_state_atom, theme_atom,
portrait_support, portrait_request, non_comp_atom;
static char *get_atom_prop(Display *dpy, Window w, Atom atom)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
Atom *value;
char *copy;
rc = XGetWindowProperty (dpy, w, atom, 0, 1, False,
XA_ATOM, type, format,
items, left, (unsigned char**)value);
if (type != XA_ATOM || format == 0 || rc != Success) {
copy = strdup();
} else {
char *s = XGetAtomName(dpy, *value);
copy = strdup(s);
XFree(s);
}
return copy;
}
static Window get_win_prop(Display *dpy, Window w, Atom atom)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
Window *value;
rc = XGetWindowProperty (dpy, w, atom, 0, 1, False,
XA_WINDOW, type, format,
items, left, (unsigned char**)value);
if (type == None || rc != Success)
return 0;
else
{
return *value;
}
}
static unsigned long get_card_prop(Display *dpy, Window w, Atom atom)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
unsigned long *value;
rc = XGetWindowProperty (dpy, w, atom, 0, 1, False,
XA_CARDINAL, type, format,
items, left, (unsigned char**)value);
if (type == None || rc != Success)
return 0;
else
{
return *value;
}
}
static long get_int_prop(Display *dpy, Window w, Atom atom)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
unsigned long *value;
rc = XGetWindowProperty (dpy, w, atom, 0, 1, False,
XA_INTEGER, type, format,
items, left, (unsigned char**)value);
if (type == None || rc != Success)
return -1;
else
{
return *value;
}
}
static long get_xembed_prop(Display *dpy, Window w)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
unsigned long *value;
rc = XGetWindowProperty (dpy, w, xembed_atom, 0, 2, False,
XA_CARDINAL, type, format,
items, left, (unsigned char**)value);
if (type == None || rc != Success)
return -1;
else
{
long ret;
ret = value[1] (1 0);
XFree(value);
return ret;
}
}
static char *get_str_prop(Display *dpy, Window w, Atom atom)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
char *value;
rc = XGetWindowProperty (dpy, w, atom, 0, 200, False,
XA_STRING, type, format,
items, left, (unsigned char**)value);
if (type == None || rc != Success)
return NULL;
else
{
char *s = strdup((const char*)value);
XFree(value);
return s;
}
}
static char *get_utf8_prop(Display *dpy, Window w, Atom atom)
{
Atom type;
int format, rc;
unsigned long items;
unsigned long left;
char *value;
rc = XGetWindowProperty (dpy, w, atom, 0, 200, False,
utf8_string_atom, type, format,
items, left, (unsigned char**)value);
if (type == None || rc != Success)
return NULL;
else
{
char *s = strdup((const char*)value);
XFree(value);
return s;
}
}
static const char
Re: Why should I write apps for Maemo?
Eero Tamminen wrote: Hi, (standard disclaimer: below are my personal opinions) Thanks for taking the time to reply. Who/where is the best place to contact in regards to my Ovi Store questions? Today, I received a notice that the Ovi Store is new and improved but the Maemo section is still without any for-profit apps. Michael ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Why should I write apps for Maemo?
Hi, AFAIK PR1.2 needs to be released before paid content will be available. This should be done this month (if everything go to plan - which is has not done so far). Ronan. PS Michael you can contact me, and I will redirect you to the right person if I do not know the answer. -Original Message- From: maemo-developers-boun...@maemo.org [mailto:maemo-developers- boun...@maemo.org] On Behalf Of ext Michael Cronenworth Sent: 12 May, 2010 16:19 To: maemo-developers@maemo.org Subject: Re: Why should I write apps for Maemo? Eero Tamminen wrote: Hi, (standard disclaimer: below are my personal opinions) Thanks for taking the time to reply. Who/where is the best place to contact in regards to my Ovi Store questions? Today, I received a notice that the Ovi Store is new and improved but the Maemo section is still without any for-profit apps. Michael ___ 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: Howto grab all Maemo5 zoom key events in SDL/SDL_gles app?
Hi, Hamalainen Kimmo (Nokia-D/Helsinki) wrote: On Sun, 2010-05-02 at 13:26 +0200, ext Till Harbaum / Lists wrote: i'd like to access the zoom keys in a SDL/SDL_gles app (the 3d globe i uploaded to extras-devel). The odd thing is that my solution only partly works. Some key presses actually reach my app as function key presses, but still most of them reach the volume control. So when repeatedly pressing the zoom buttons my app zooms but also the volume is changed. I am using the following code which is inspired by code from scummvm. I am calling this code once immediately after the SDL setup is done. Any idea why this still delivers some key events to the volume control? It could be that _NET_ACTIVE_WINDOW or MB_CURRENT_APP_WINDOW on the root window does not correspond to your window. The volume app is tracking one of these (I think _NET_ACTIVE_WINDOW) to determine the window whose ZOOM_KEY window property matters. Maemo SDL doesn't seem to set all required window properties for fullscreen windows for tracking of the topmost application to work properly. See this bug: https://bugs.maemo.org/show_bug.cgi?id=6175#c3 xprop -root produces this when there's a fullscreen SDL window: _NET_ACTIVE_WINDOW(WINDOW): window id # 0x3e2 _MB_CURRENT_APP_WINDOW(WINDOW): window id # 0x3e1 I.e. for SDL applications the value in these properties differ, unlike for normal applications. _MB_CURRENT_APP_WINDOW is the fullscreen SDL window and _NET_ACTIVE_WINDOW is the non-fullscreen SDL window. (I think SDL uses fullscreen window for output and non-fullscreen one for input.) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
upstart and dbus
Hello, I've wrote a little daemon that basically listen on DBus for some events and now I want to automatically start it through upstart. But, upstart doesn't like my app :( I discovered that if I use a DBUS_BUS_SYSTEM for the DBusConnection, everything works fine. Instead, if I use a DBUS_BUS_SESSION it makes upstart fails to start my app. Any hints? Thanks. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: upstart and dbus
I cant provide a full solution now but to use the session bus you will need the session bus address I think which changes every restart. Are you doing that in your upstart script already ? ( setting the dbus session address something like here /tmp/session_bus_address.user ) -krk969 - Original Message - From: b0unc3 Sent: 05/12/10 08:52 PM To: maemo-developers Subject: upstart and dbus Hello, I've wrote a little daemon that basically listen on DBus for some events and now I want to automatically start it through upstart. But, upstart doesn't like my app :( I discovered that if I use a DBUS_BUS_SYSTEM for the DBusConnection, everything works fine. Instead, if I use a DBUS_BUS_SESSION it makes upstart fails to start my app. Any hints? Thanks. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: upstart and dbus
On Wednesday 12 May 2010 21:50:31 Ram Kurvakat wrote: I cant provide a full solution now but to use the session bus you will need the session bus address I think which changes every restart. Are you doing that in your upstart script already ? ( setting the dbus session address something like here /tmp/session_bus_address.user ) Using run-standalone.sh to start your application should set up the session bus info. You always need to use run-standalone.sh to start user apps if they are not being invoked from the hildon environment (from upstart, from a root terminal, from an ssh session, in scratchbox, etc.). Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: qt 4.6 without pt1.2
On Sat, May 8, 2010 at 12:48 AM, ac...@dsic.upv.es wrote: Hi everyone, I suceeded to compile a program that uses the state machine framework for fremantle but using the madde program provided by Nokia SDK. Nevertheless, when I pass this program to my N900 it sais that some Qt libraries are missing. Should I wait till pr1.2 or can I install Qt 4.6 without it. On Maemo.org forum Venemo posted a way to get new Qt 4.6.2 in your N900 without PR1.2 by installing some files from the SDK repository: http://talk.maemo.org/showthread.php?p=654370 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: upstart and dbus
If you do use run-standalone.sh in an Upstart script, please be aware of https://bugs.maemo.org/show_bug.cgi?id=8148. Lucas Maneos' awesomeness helped me to fix my issue. On 5/12/10, Graham Cobb g+...@cobb.uk.net wrote: On Wednesday 12 May 2010 21:50:31 Ram Kurvakat wrote: I cant provide a full solution now but to use the session bus you will need the session bus address I think which changes every restart. Are you doing that in your upstart script already ? ( setting the dbus session address something like here /tmp/session_bus_address.user ) Using run-standalone.sh to start your application should set up the session bus info. You always need to use run-standalone.sh to start user apps if they are not being invoked from the hildon environment (from upstart, from a root terminal, from an ssh session, in scratchbox, etc.). 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: upstart and dbus
Using run-standalone.sh everything works as expected. Thanks to all! On Thu, May 13, 2010 at 12:07 AM, Faheem Pervez tripp...@gmail.com wrote: If you do use run-standalone.sh in an Upstart script, please be aware of https://bugs.maemo.org/show_bug.cgi?id=8148. Lucas Maneos' awesomeness helped me to fix my issue. On 5/12/10, Graham Cobb g+...@cobb.uk.net g%2b...@cobb.uk.net wrote: On Wednesday 12 May 2010 21:50:31 Ram Kurvakat wrote: I cant provide a full solution now but to use the session bus you will need the session bus address I think which changes every restart. Are you doing that in your upstart script already ? ( setting the dbus session address something like here /tmp/session_bus_address.user ) Using run-standalone.sh to start your application should set up the session bus info. You always need to use run-standalone.sh to start user apps if they are not being invoked from the hildon environment (from upstart, from a root terminal, from an ssh session, in scratchbox, etc.). 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: upstart and dbus
On Wednesday 12 May 2010 23:07:47 Faheem Pervez wrote: If you do use run-standalone.sh in an Upstart script, please be aware of https://bugs.maemo.org/show_bug.cgi?id=8148. Lucas Maneos' awesomeness helped me to fix my issue. Interesting. For others (who don't want to read through 37 comments which demonstrate Lucas Maneos' awesomeness in both perseverance and debugging skills!), this boiled down to Faheem's app using run-standalone.sh in an upstart script and needing to add: pre-start script /usr/sbin/waitdbus system end script Faheem, what were you using as the start condition for your upstart script? I would have assumed that if it were anything after start on started dbus then the waitdbus would be unnecessary. In particular, I normally use start on XSESSIONS_STARTING for user applications, which is long after dbus. However, adding the pre-start script if you plan to use run-standalone.sh in an upstart script seems like a good rule for safety. Graham P.S. This probably explains a problem I have with taking backups on my test N900, which I couldn't understand despite poring over strace output for hours! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: upstart and dbus
On 5/13/10, Graham Cobb g+...@cobb.uk.net wrote: Faheem, what were you using as the start condition for your upstart script? I would have assumed that if it were anything after start on started dbus then the waitdbus would be unnecessary. In particular, I normally use start on XSESSIONS_STARTING for user applications, which is long after dbus. Thanks for that -- noted. I was using: start on started dbus stop on stopping dbus stop on stopped fmtx Though, I finally realized that I didn't need to start the daemon upon boot at all due to D-Bus' auto-activation mechanism. Yeah... Best regards, Faheem ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
QR-Code
Hi !Is there a project to QT QR-Code Is there a project to QT QR-Code ? Thank's ! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
