RE: Maemo Info Center library service released with first set of official maemo Fremantle 5 documentation
Hi again, -Original Message- From: Tikka Jarmo (Nokia-D/Helsinki) Sent: 19 April, 2010 07:45 -Original Message- From: ext Aniello Del Sorbo [mailto:ani...@gmail.com] Sent: 16 April, 2010 21:52 Hi, Thanks about report. This logo link is theme problem and will be fixed as part of next document update to the site. We had some last minute problems with our theme just before publishing the service, and some of those problems are still (unfortunately) visible for users... I could not reproduce Downloads link and moving back with browser problem so I did not write bug report for that. I think I now managed to reproduce this Downloads menu problem and I added bug report also for that. My Info Center theme related bug reports are now these: https://bugs.maemo.org/show_bug.cgi?id=9959 https://bugs.maemo.org/show_bug.cgi?id=9961 https://bugs.maemo.org/show_bug.cgi?id=9960 Cheers, //Jarmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Inhibiting device auto-lock on N900
I'm writing a talking clock application. The purpose of this application is to answer the ever-so-frequent question mghhnm, what time is it in the morning, just before you've been able to open your eyes properly much less put on your glasses. I've already written the application itself, it was a fairly simple project that took a couple of hours. In testing, however, I discovered a slight drawback to my planned approach of start the program before falling asleep, mash the screen in the morning and it'll tell me the time. 1. The screen itself will stop accepting taps when the device is turned off. It seems this particular feature can be inhibited by leaving the phone slided open (with the qwerty keyboard exposed) or by setting the gconf setting /system/osso/dsm/locks/touchscreen_keypad_autolock_enabled to false. This requires you to slide the lock button on the side of the phone to unlock the screen. Annoying, but still doable even in a half-awake stupor. And besides, you can always leave the phone activated in its opened mode. 2. The device will automatically lock itself after 5 minutes, for security purposes. Now, remembering and correctly entering the device lock code in a half-awake stupor is considerably more difficult. This can be disabled by setting the gconf setting /system/osso/dsm/locks/devicelock_autolock_enabled. However - I don't really like this approach of changing gconf user settings to inhibit device locks. The last thing I want is for the phone or my application to crash (or more likely, to run out of battery) while the program is running and leaving the device unlocked, requiring the user to set the automatic lock option on again (if he even notices it's been disabled). Whoever coded the built-in media player agrees with this. He's found some way to tell the system not to automatically lock itself without changing the gconf settings. I have not yet figured out how. One other option worth considering is the fact that some applications, such as the phone (for an incoming call) and the alarm application (to silence the infernal bleeping of an alarm) will allow you to throw up a screen to the user that'll be accessible even if the lock code has not been entered. This would also solve the potential security issue of somebody stealing your phone while you're sleeping to get to it while it's unlocked. :-) So, does anybody have any ideas as to how I might acheive this in some way? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Info Center library service released with first set of official maemo Fremantle 5 documentation
Dnia piątek, 16 kwietnia 2010 o 19:40:22 jarmo.ti...@nokia.com napisał(a): The Maemo documentation infrastructure project has released new Maemo Info Center documentation service for Maemo platform. Together with Maemo Info Center service we released also the first set of official Maemo Fremantle 5 documentation. More Fremantle 5 documentation will be updated to the Maemo Info Center service end of April. I worked for few years in Web development. When I enter this page I feel like back in 90's... Why? 1. Frames - this thing died long time ago. After few clicks I have to go to location bar, enter mainpage URL to get page usable again. 2. Javascript trees? 3. I used Search box - just to get information that there is no index and have to wait until it will index all documentation. Why it was not indexed at start? 4. Amount of arrows on screen is insane: - there are yellow arrows which duplicate Back/Forward from web browser - there are black arrows in non-Qt documentation which are Prev/Next chapter - there are green arrows in maemomm documentation 5. Each part of tree uses other type of navigation, other formatting... Long way before it will be useful. Regards, -- JID: h...@jabber.org Website: http://marcin.juszkiewicz.com.pl/ LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Inhibiting device auto-lock on N900
Hello. To unlock the device : http://wiki.maemo.org/User:Jebba/DBUS#dbus-send-unlock To keep the display on and device unlocked : http://maemo.org/api_refs/4.0/libosso/group__Devstate.html#g93fe32aeb992e128c94b890d6f801bfd David. Per von Zweigbergk wrote: I'm writing a talking clock application. The purpose of this application is to answer the ever-so-frequent question mghhnm, what time is it in the morning, just before you've been able to open your eyes properly much less put on your glasses. I've already written the application itself, it was a fairly simple project that took a couple of hours. In testing, however, I discovered a slight drawback to my planned approach of start the program before falling asleep, mash the screen in the morning and it'll tell me the time. 1. The screen itself will stop accepting taps when the device is turned off. It seems this particular feature can be inhibited by leaving the phone slided open (with the qwerty keyboard exposed) or by setting the gconf setting /system/osso/dsm/locks/touchscreen_keypad_autolock_enabled to false. This requires you to slide the lock button on the side of the phone to unlock the screen. Annoying, but still doable even in a half-awake stupor. And besides, you can always leave the phone activated in its opened mode. 2. The device will automatically lock itself after 5 minutes, for security purposes. Now, remembering and correctly entering the device lock code in a half-awake stupor is considerably more difficult. This can be disabled by setting the gconf setting /system/osso/dsm/locks/devicelock_autolock_enabled. However - I don't really like this approach of changing gconf user settings to inhibit device locks. The last thing I want is for the phone or my application to crash (or more likely, to run out of battery) while the program is running and leaving the device unlocked, requiring the user to set the automatic lock option on again (if he even notices it's been disabled). Whoever coded the built-in media player agrees with this. He's found some way to tell the system not to automatically lock itself without changing the gconf settings. I have not yet figured out how. One other option worth considering is the fact that some applications, such as the phone (for an incoming call) and the alarm application (to silence the infernal bleeping of an alarm) will allow you to throw up a screen to the user that'll be accessible even if the lock code has not been entered. This would also solve the potential security issue of somebody stealing your phone while you're sleeping to get to it while it's unlocked. :-) So, does anybody have any ideas as to how I might acheive this in some way? ___ 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: j2me
On Sun, Apr 18, 2010 at 7:12 PM, Christopher Intemann intem...@gmail.comwrote: Is there any stupid security mechanism in maemo preventing me to change permissions for files or what am I doing wrong? Its working now. The cvm files were in the MyDocs directory, which is mounted non-executeable. I've moved them somewhere else now. However, it seems to crash (cannot start jvm). I will perform some more testing later. Die anyone else ever try to run phoneme on the N900? Is there any reason for MyDocs beeing mounted noexec? Or, furthermore, any good reason for not remounting it exec? Regards, Chris ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Building hildon library
From: André Hänsel an...@webkr.de I'm trying to make an enhancement to the Hildon library. Unfortunately I cannot figure out how to build it for N900/Fremantle. I have installed the Scratchbox VM and I know how to build applications using ESbox. But how do I build the libraries? Sorry, I'm not familiar with ESbox, but, if you are able to build applications it shouldn't be difficult to build libraries. Both (programs and libraries) use autotools-autoconf stuff. I already fail at finding the current source: Is it http://maemo.gitorious.org/hildon/hildon? Or is it https://garage.maemo.org/scm/?group_id=939? The garage one is a previous-old-legacy repository, the correct one is the gitorious one. So, you can get the code doing something like this: git clone git://gitorious.org/hildon/hildon.git Needs the source to be put in a certain dir inside the scratchbox? No. In fact, normally to put the source in your home directory. But, sometimes, to make quick tests I use directly the /tmp, and it works fine for me. Then do I have to run autogen.sh? In chroot /scratchbox/users/maemo/? Or in chroot /scratchbox/users/maemo/targets/FREMANTLE_ARMEL? autogen.sh is just a script that execute the configure-related programs, and most of the times are tunned for the specific program. So it is required to be executed in the source directory. Anyway, have you tried something like?: myuse...@mymachine:~$ /scratchbox/login $[sbox-FREMANTLE_ARMEL: ~] git clone git://gitorious.org/hildon/hildon.git $[sbox-FREMANTLE_ARMEL: ~] cd hildon $[sbox-FREMANTLE_ARMEL: ~/hildon] dpkg-buildpackage -b -rfakeroot The debian files are included on the repository. debian/rules will call autogen.sh for you. BR === API (apinhe...@igalia.com) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Camera's hardware key.
Hi, guys, I need help. Is anybody know how to handle camera's hardware button? -- Regards, Igor Mironchick, Intervale ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Camera's hardware key.
Dnia poniedziałek, 19 kwietnia 2010 o 14:14:17 Igor Mironchick napisał(a): Is anybody know how to handle camera's hardware button? Press it gently with finger, do not use hammer to push it as it can break. But if you need developer docs then check shortcutd sources maybe? Regards, -- JID: h...@jabber.org Website: http://marcin.juszkiewicz.com.pl/ LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: j2me
On Mon, 2010-04-19 at 11:12 +0200, ext Christopher Intemann wrote: On Sun, Apr 18, 2010 at 7:12 PM, Christopher Intemann intem...@gmail.com wrote: Is there any stupid security mechanism in maemo preventing me to change permissions for files or what am I doing wrong? Its working now. The cvm files were in the MyDocs directory, which is mounted non-executeable. I've moved them somewhere else now. However, it seems to crash (cannot start jvm). I will perform some more testing later. Die anyone else ever try to run phoneme on the N900? Is there any reason for MyDocs beeing mounted noexec? Or, furthermore, any good reason for not remounting it exec? The main reason could be that if you are running a program from MyDocs, you cannot unmount it anymore and use it as USB mass storage. Even with Windows machines, you don't usually run programs from USB sticks if you think about it... -Kimmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Searching rootstrap for maemo5-update4
Hi, ext Cornelius Hald wrote: The rootstrap here: http://repository.maemo.org/stable/5.0/i386 is the latest one. Does anyone know where I can find earlier versions? you can take this [1] rootstrap. This is equivalent to 1.0.1. Every later version is not so trivial to install as it would take anyway the latest packages out of the repository. Hope this will help you. 1. http://repository.maemo.org/stable/fremantle-update2/ Daniel Thanks! Conny [1] https://bugs.maemo.org/show_bug.cgi?id=6263 ___ 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: Hildon status menu plugin source
ext André Hänsel wrote: Hi, source code for hildon-status-bar-usb is not available, is it? Question in general: If there isn't a source package on http://maemo.org/packages/view/hildon-status-bar-usb/, can I assume the package is non-free and file a licensing change request or is there any other place I should check for source before? You are right, the package is source and you would have to file a licensing change request if needed. Daniel Regards, André ___ 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
HAL DBus
Hi. Can anybody explain me where is service name, object path, interface of the DBus here /org/freedesktop/Hal/devices/platform_cam_focus ? Thx. And sorry for the offtopic. -- Regards, Igor Mironchick ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: HAL DBus
Hi, On Mon, Apr 19, 2010 at 3:48 PM, Igor Mironchick imironch...@gmail.comwrote: Hi. Can anybody explain me where is service name, object path, interface of the DBus here /org/freedesktop/Hal/devices/platform_cam_focus ? I think you must use libhal to get informations, take a look here : http://maemo.org/api_refs/5.0/5.0-final/libhal Thx. And sorry for the offtopic. -- Regards, Igor Mironchick ___ 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: Maemo Info Center library service released with first set of official maemo Fremantle 5 documentation
On Mon, 2010-04-19 at 08:28 +0200, jarmo.ti...@nokia.com wrote: Hi again, -Original Message- From: Tikka Jarmo (Nokia-D/Helsinki) Sent: 19 April, 2010 07:45 -Original Message- From: ext Aniello Del Sorbo [mailto:ani...@gmail.com] Sent: 16 April, 2010 21:52 Hi, Thanks about report. This logo link is theme problem and will be fixed as part of next document update to the site. We had some last minute problems with our theme just before publishing the service, and some of those problems are still (unfortunately) visible for users... I could not reproduce Downloads link and moving back with browser problem so I did not write bug report for that. I think I now managed to reproduce this Downloads menu problem and I added bug report also for that. My Info Center theme related bug reports are now these: https://bugs.maemo.org/show_bug.cgi?id=9959 https://bugs.maemo.org/show_bug.cgi?id=9961 https://bugs.maemo.org/show_bug.cgi?id=9960 Cheers, //Jarmo Thanks! I will file reports myself next time! Sorry about that. Aniello ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Info Center library service released with first set of official maemo Fremantle 5 documentation
On Fri, Apr 16, 2010 at 18:40, jarmo.ti...@nokia.com wrote: The Maemo documentation infrastructure project has released new Maemo Info Center documentation service for Maemo platform. Together with Maemo Info Center service we released also the first set of official Maemo Fremantle 5 documentation. More Fremantle 5 documentation will be updated to the Maemo Info Center service end of April. One thing I'd like to see is a *definitive* Maemo reference library. Currently, we have docs spread over Forum Nokia, Info Center, the maemo.org wiki - and then there's the docs that are *duplicated* (with slightly different versions) between the various places. Is it feasible to try and get things like the PyMaemo API reference into the Info Center, and any other popular developer resources (say, Gtkmm is an obvious example)? TIA, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ Maemo Community Council chair ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Help needed: packaging/distributing very small C app
I'm looking for advanced packaging information for a very small C application. While I've learned to build a .deb for a python app using py2deb, I now face another task of packaging where the effort to package could very quickly become exponentially greater than the effort needed to write the application itself. Here's the story: I needed a way to start the playback of a certain playlist in mafw/gstrenderer. Unfortunately, the python-mafw doesn't support this. I also stalled on using ctypes or going through d-bus. However, I found the source code for mafw-renderer-example*, a CLI app that includes the desired functionality. (* http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Multimedia_Components/Media_Application_Framework_(MAFW)#Renderer_example ) I then took that code and made some slight modifications to suit my needs (shuffle the playlist before starting playback, exit the app after starting playback). After building my first C app (hooray!), I now have an ARMEL binary named mafw-play-list that does what I want. Now I face the daunting task to distribute that code/binary, as I will need it in another app of mine (and because I believe others might like it, too). I'ts just one source file (400 lines, 10kB) and it takes two lines to compile. How should I distribute this? (I've already built a binary-only package using py2deb and uploaded it to extras-devel - but I believe this is not the right way to do it). Can someone explain what to do correctly? Or could someone even lend me a hand in packaging this? Thanks! -Tom BTW: strangely, the in-built media player is not aware of any alternatively started playlists in it's renderer. Exists there anything to signal something about a running playlist to the Media player? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help needed: packaging/distributing very small C app
On Mon, Apr 19, 2010 at 2:41 PM, Thomas Waelti twae...@gmail.com wrote: I'm looking for advanced packaging information for a very small C application. While I've learned to build a .deb for a python app using py2deb, I now face another task of packaging where the effort to package could very quickly become exponentially greater than the effort needed to write the application itself. Here's the story: I needed a way to start the playback of a certain playlist in mafw/gstrenderer. Unfortunately, the python-mafw doesn't support this. I also stalled on using ctypes or going through d-bus. However, I found the source code for mafw-renderer-example*, a CLI app that includes the desired functionality. (* http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Multimedia_Components/Media_Application_Framework_(MAFW)#Renderer_example ) I then took that code and made some slight modifications to suit my needs (shuffle the playlist before starting playback, exit the app after starting playback). After building my first C app (hooray!), I now have an ARMEL binary named mafw-play-list that does what I want. Now I face the daunting task to distribute that code/binary, as I will need it in another app of mine (and because I believe others might like it, too). I'ts just one source file (400 lines, 10kB) and it takes two lines to compile. How should I distribute this? (I've already built a binary-only package using py2deb and uploaded it to extras-devel - but I believe this is not the right way to do it). Can someone explain what to do correctly? Or could someone even lend me a hand in packaging this? Thanks! -Tom BTW: strangely, the in-built media player is not aware of any alternatively started playlists in it's renderer. Exists there anything to signal something about a running playlist to the Media player? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers I'm not a packaging specialist, but I'll try to help :) Here is a bare-bones and direct way to do it, inside Scratchbox and using CDBS [1] and GPL2 license: 0. create environment variables for your name and email (they will be useful later for automatic filling of some fields): export DEBEMAIL=your email export DEBFULLNAME=your name 1. Create a directory in the form packagename-version (e.g. mypackage-1.0.0) and put your source files there; 2. Enter the directory and run: $ dh_make -b -c gpl and hit enter; - Obviously, if your package has a different license, you just have to pass a different string to -c parameter of dh_make; run dh_make --help to see available licenses and all other options - or you can just edit debian/copyright directly afterwards; 3. Inside the created ./debian directory, remove all *.ex files (they're all examples); 4. Edit debian/control and fill necessary fields and descriptions; - Build-Depends: dependencies for building your package - Depends: dependencies for installing your package 5. Edit debian/changelog and fill necessary fields; 6. As your have only one source file and assuming you use GNU make, it may be not necessary to edit debian/rules, it should just work. If it does not, however, go to [1] to see detailed instructions for CDBS. 7. Now run dpkg-buildpackage and see what happens: $ dpkg-buildpackage -D -rfakeroot 8. With luck, your package should be built now, and ready to upload to extras-devel! As I said, I'm no specialist, but I have dealt with Debian packaging for some time. My instructions may not be exactly accurate (please correct me as you see fit), but they at least should help you to get started. Also, the package can be further tuned, so this can be an excellent opportunity to learn the ways of the Maemo Debian Packaging :) Well, that's it. Hope it helps! [1] http://cdbs-doc.duckcorp.org/en/cdbs-doc.xhtml Regards, -- __ Bruno Araújo, MSc openBossa Labs - Instituto Nokia de Tecnologia Manaus, Brazil Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help needed: packaging/distributing very small C app
Hi Thomas, Thomas Waelti wrote: I'm looking for advanced packaging information for a very small C application. I documented the packaging of a C app (using autotools for building) a while back in the wiki: http://wiki.maemo.org/Packaging#A_concrete_example_-_rot13 This starts with a tiny C program the minimum autotools stuff to build it (I don't include these - would that be useful?) and guides you through making a .deb. 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
Re: Help needed: packaging/distributing very small C app
Hi, Dave Neary wrote: I documented the packaging of a C app (using autotools for building) a while back in the wiki: http://wiki.maemo.org/Packaging#A_concrete_example_-_rot13 This starts with a tiny C program the minimum autotools stuff to build it (I don't include these - would that be useful?) and guides you through making a .deb. So I included an A to Z for this project, with the 3 files you need to create a .tar.gz using standard autotools. Let me know if it's useful. 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
