Re: osso, muali , dbus and Qt closeEvent()s
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Greaves wrote: I meant gtk apps need to use osso-initialize() or they just don't work. Since libosso uses glib, I expect that's not really right for Qt apps. In particular I think osso-init.c calls glib setups that seem to hook into the glib context and I think the glib main loop - not used in Qt apps. eg line 503 in osso-init.c calls dbus_connection_setup_with_g_main() which: Sets the watch and timeout functions of a DBusConnection to integrate the connection with the GLib main loop. see: http://dbus.freedesktop.org/doc/api/html/group__DBusGLib.html#ga754eed235cc2b8153bd8f824b687d9e so libosso, as it stands, isn't suitable for Qt apps unless I'm confused :) Actually Qt has supported GLib context stuff since 4.2 (IIRC), so libosso is suitable. That doesn't say that it's practical or nice, but it should work. - -- Santtu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknKghEACgkQX9Rc0+po4p3zUQCgmZLaGy3jTDm3YuCbkuh7OZE4 2J4An3avfLa5Elu8eo94IbW1srViA8aw =ozXP -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Beware Personal launcher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frantisek Dufka wrote: osso-statusbar-cpu does exactly this. With memory reporting turned off it is nice statusbar clock with black background. Once the background turns solid blue you know there is a problem :-) Actually it should have graphs of cpu and/or memory usage, not black background; there's just a bug I haven't fixed that causes it to be black by default. If you change the settings, it should start to work. - -- Santtu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkq3l0ACgkQX9Rc0+po4p1GZwCgpyS/0IlERxAzpEUSTS+RV0HV DskAnj/9VF6ZqZP+KGFHkkS8LBqeU1A1 =9NjT -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to know target in makefile?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mikko Mehtonen wrote: Is there a way to know in Makefile which target we are building (arm or x86)? There seems to be a variable $target in scratchbox, but it isn't exported so it's not visible in Makefile. May I ask why do you need this information. Sbox is meant to be transparent and the target name shouldn't make any difference. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIV5QnX9Rc0+po4p0RAs6fAJ9lK86FfkvpBKO4Wk606ayeSXv+iACgshtH Nshgvpg+6mCAYmaMdGUMTZg= =AboO -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: bootstrapping the sdk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck Robey wrote: Can you give me any idea why sb-menu is finding me no choices for cpu transparency? This is usually because the cputransp devkit hasn't been selected. Even if you don't select it, the method selection dialog is shown, but with no available methods. If you don't have the devkit selection phase, or cputransp isn't listed there, then something is indeed broken. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH2MXyX9Rc0+po4p0RAoq8AJ0bYmuA1YDqxTcwodkQlgp8Sb8mzwCfbHNO KqRcbtBB+panAoVoLwSq6FM= =1KAx -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810: shift+fn+N or M generate two keycodes each
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frantisek Dufka wrote: I tried all other keys on keyboard and no other keys do it when shift and fn are pressed, just 'N' and 'M'. Can anyone with no modifications done on your device press left shift+fn+n and see if two keys are generated too? Shift-fn-n and -m both produce $€, so same b0rkedness can be observed here too. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHsbuxX9Rc0+po4p0RAtMFAJ9GkWZx71L0qPUkSCocuWU+6bdeqQCgoGjE N3yq9nO4I7J00WwZEWaEAc0= =I5Zh -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Two .install file questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony Green wrote: https://stage.maemo.org/svn/maemo/projects/haf/trunk/osso-application-installer/doc/repository.txt (is there something newer? I cant find anything.) gives information about the key names for maemo 2.0 (repo_deb) and 3.0 (rep_deb_3) but not for the latest image. Am I right in guessing that it should be rep_deb_4? The documentation is on hildon-app-mgr's pages in garage[1]. The new format allows you to have multiple repositories defined in one .install file. This has been quite a frequent wish in the past. [1]: http://hildon-app-mgr.garage.maemo.org/install-stable.html - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHqFgmX9Rc0+po4p0RAlCJAJwKMxUR2XwAf9P7jwCadQfwXqadbgCgl3qQ iDrpKPdQp8Xyn2WxiXiCPTQ= =dejG -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging images into deb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 eemeli wrote: I want to create a deb which only contains a bunch of extra images, themes that my application uses. How do i make package for those? The normal dh_make route doesnt work because i dont have makefiles of anything else that all the examples seem to expect. You can create a Makefile that copies the files to the right(tm) places or make debian/rules do it for you. The right place would be debian/packagename/usr/share/ You might want to update some icon caches too in your postinst script if you install your images to the /usr/share/icons/hicolor -path. So, your debian/rules could do something like this (instead of $(MAKE) install): mkdir -p debian/myicons/usr/share/pixmaps cp myimage1.png myimage2.png debian/myicons/usr/share/pixmaps The dpkg -b will also do the thing, but it's harder for others to replicate (and you don't get proper source packages). - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHpyxVX9Rc0+po4p0RAn7lAJ9/AzKaB7XPf0n/564yrEaujtmLHQCghTjv SZdNTDzlCZTP12Dvzn0kEnM= =rcBg -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: desktop/home plugins 2nd round
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 21, 2008 4:59 PM, Collin R. Mulliner [EMAIL PROTECTED] wrote: 1) Are home plugins supposed to work in scratchbox/Xephyr? If yes, is there a trick? I think my load applet (osso-statusbar-cpu[1]) should work with sbox/Xephyr; at least it used to in bora times. 2) Has anybody written a home plugin for Maemo 4.x and has published the source? The source is in the svn[2], it might be a bit messy here and there, as it tries to support all modern maemo releases. [1]: http://maemo-hackers.org/wiki/OssoStatusbarCpu [2]: http://maemo-hackers.org/svn/osso-statusbar-cpu/trunk/ - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHlPuMX9Rc0+po4p0RAvonAKCed7Ky9VikoRLPsDYiYhleRSqlAQCbBKgk qYXfO5hqprJOa6P0mpLVB60= =oix5 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Announcement: OS2008 2.2007.50-2 source repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Graham Cobb wrote: To my mind there are two solutions to this: There is a third option: make the process of upgrading the tablet so easy The fourth option would be to assure the shlibs -files of said libraries always contained at most the version of the first release. To do this, however, it is not enough to keep ABI compatibility, but you cannot introduce any new functions either -- or then you need to create a better shlibs-system. ;) - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFHggWGX9Rc0+po4p0RAiv3AJdiWskVT/zMYPHo6N2KWaDWRZ94AJ9PCLEV FfPEZ7IrC4jRrKCmuq5jqg== =au3U -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Apache + PHP5 + MySQL/SQLite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
On Tue, 18 Dec 2007, Santtu Lakkala wrote:
You can also try these install files: php5-fastcgi[1], nginx[2]. The php
includes sqlite support, so the sqlite functions work out of the box.
There's also a working wordpress package that uses nginx and
php5-fastcgi/sqlite.
Anyone have PHP5 working with Apache? If so, does it use modphp or CGI
modules?
I need Apache because I need mod_rewrite. I also need to get PEAR running
too.
How hard would it be to get all these working?
Nginx actually includes a rewrite module, you could do something like this:
location / {
root /path/to/your/web/app
index index.php
if (!-e $request_filename) {
rewrite ^(.*)$ /index.php?q=$1
break;
}
}
PS. Please use the reply all button in your mail agent, otherwise your
mails aren't sent to the list.
- --
Santtu Lakkala
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQFHaOM0X9Rc0+po4p0RAvGWAJ9OuGtQhiPhHd/YYln/0aK9o9BLcACYqlSo
U7dHRSUjzVE6zDU2vYu4mA==
=4/y5
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Apache + PHP5 + MySQL/SQLite
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joshua Layne wrote: somebody (Santtu Lakkala) has made a host of php5 packages available: php5-cli php5-dev php5-fastcgi php5-fastcgi-dev php5-fastcgi-pear php5-pear Why am I a somebody when the others weren't ;P To the point: the php5-fastcgi is pre-configured to work with the nginx package, both of these can be found from maemo-hackers.org repository: http://maemo-hackers.org/apt chinook main You can also try these install files: php5-fastcgi[1], nginx[2]. The php includes sqlite support, so the sqlite functions work out of the box. There's also a working wordpress package that uses nginx and php5-fastcgi/sqlite. [1]: http://maemo-hackers.org/php5-fastcgi.install [2]: http://maemo-hackers.org/nginx.install - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHaBe0X9Rc0+po4p0RAkq9AJ99G7/Xx1XE2u5yJ9EmJzUWgcElHQCgi1E/ HK5TReBnIy8vceAlLiatEs0= =OKJZ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: cannot resolve repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aleksandr Koltsoff wrote: This way sbox name resolution will use the dnsmasq that is running on your real host, and you'll never have to touch your sbox resolv.conf again. Very useful when using the machine in dhcp environments and/or traveling around. Another way (which I use) is to have a pre-up.d -script that copies /etc/resolv.conf to /scratchbox/etc. I also have sb-conf in -e in .bashrc in scratchbox so the file gets copied to rootstrap too. This way I can use the short names for the boxen in my LAN. ;) - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHQyHBX9Rc0+po4p0RAqt8AKCvk8kN8uFSnjuGTSu5eNe52kunwgCfSypV wtyeM0trGLkGIOrZuGg3UhI= =M9fW -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Any problem with chinhook beta repo?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Juha Kallioinen wrote: ext Luca Donaggio wrote: Any clue about how to fix it? I followed these instructions to set up my sbox environment: http://inz.fi/blog/2007/10/22/multi-target-development-for-maemo/ My current parameters for chinhook-armel target (via sb-menu - show) are: Hi Luca, it looks like your target setup is not quite correct. Inz's blog entry is quite new but the information for a chinook target is incorrect. Here's a target setup that works for me: sb-conf st maemo4-arm -c cs2005q3.2-glibc2.5-arm -d cputransp:perl:debian-etch -t qemu-arm-0.8.2-sb2 The most notable differences are that you should use debian-etch devkit (not debian or debian-sarge) and that the qemu version is wrong. Please do note that I use the old debian devkit on purpose, because the goal in my blog post is to be able to compile the same source for different targets, so there cannot anyway be anything using the new features of the newer devkit. Also, I have tested each of the commands and they produce a working target, with no arm/armel mismatch. Unfortunately I don't know why is there a problam for Luca. My instructions do use the qemu-0.8.2-sb2 and use the maemo3-debian. It might be that debian-sarge without maemo3-debian breaks things. The package versions may indeed be the ones to blame, apt-get upgrade (outside scratchbox) might help. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHNJhBX9Rc0+po4p0RAvVVAJ9EOc22HTL9gIVkj+ifuXOanMDn4gCgsciH kqd2nnTlgzQeJF7fDcDqCt0= =QiEY -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Developing for all IT platforms
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Gedminas wrote: Missing footnote: [1] http://inz.fi/blog/2007/10/21/leetle-hildon-1chinook-migration-things/ Thanks for filling in, wonder how I managed to leave that out. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHHd7zX9Rc0+po4p0RAiSoAJ9KCHa+q2ZvRGY63zDbUV3POKIaBwCeM5vg QsSoE9/XIytUET4bNKIp82M= =TzLZ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Developing for all IT platforms
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Morrison wrote: I have a similar question on the same topic. How are people setting up their automake/autoconf projects? Is it possible to set up the automake/autoconf scripts in such a way that running ./configure will detect which SDK (gregale, bora, chinook) is installed and configure the project accordingly? You shouldn't do stuff depending on the rootstrap version, but on individual package availibility/versions. I wrote a leetle blog post[1] over matter of supporting both chinook and mistral/bora, hildon-wise. The same method can obviously be transferred to other libraries as well. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHHYuSX9Rc0+po4p0RApzvAJ0XnZVawjEU9DJneHYD7enIc7pwFQCfeEYX HPQ/Z2baBRDe5x6IG3qGLHE= =te+5 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Developing for all IT platforms
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Gedminas wrote: On Thu, Oct 18, 2007 at 10:12:29PM +0100, Neil Jerram wrote: Is there a recommended procedure for setting up Scratchbox so that one can easily compile an application and build its package for all of the IT platforms (i.e. ideally: 770 with latest 2006 OS, 770 with HE, N800 with latest 2007 OS, and N810 with whatever its OS is). I had Maemo 2.1 and 3.0 targets side-by-side in my Scratchbox once. I haven't tried installing 4.0, 3.2 and 2.2 yet (actually I haven't gotten up to installing scratchbox on my new laptop yet, it's just too tedious. I want 'apt-get install maemo-sdk-4.0 maemo-sdk-3.2 maemo-sdk-2.2'!) I have targets for mistral/2.0 (to support mistral, scirocco and gregale), bora/3.0 (to support bora 3.0, 3.1, 3.2) and now chinook-beta to support the upcoming N810. I then compile packages first on mistral and see if they work on bora -- if they don't, rebuild with bora... and/or providing .install files, so that an IT user will easily be able to get the version of the package that is right for them? The Extras repository will generate several .install files for you, which is a bit silly, because you want only one that works for all OS versions. Merging them into a single .install isn't too difficult, and the format is pretty obvious. It is documented here: https://stage.maemo.org/svn/maemo/projects/haf/trunk/osso-application-installer/doc/repository.txt Hm, it only speaks of OS2006 (where .install files are not officially supported, but work fine nevertheless) and OS2007. I didn't find documentation for chinook .install files, but reading the source, I got the following: - 888 [install] package = package to be installed catalogues = comma separated list of repositories for the package [repository1] name = repository name uri = base uri dist = dist name components = components - 888 Of course the .install file can still include the repo_name, repo_deb and repo_deb_3. For example, mh-shot-tool install file currently looks like this: - 888 [install] repo_name = maemo-hackers catalogues = maemo-hackers-chinook repo_deb = deb http://maemo-hackers.org/apt mistral main repo_deb_3 = deb http://maemo-hackers.org/apt bora main package = mh-shot-tool [maemo-hackers-chinook] name=Maemo Hackers for chinook uri=http://maemo-hackers.org/apt dist=chinook components=main - 888 - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHGho3X9Rc0+po4p0RAtFRAJ0QbwwI920qeM5SrgiirGH5/owdswCgqRdB +wowp0L0ng6DeyQFhmPjCFU= =/0Aa -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: osso-xterm and osso-xterm advanced
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 28 Sep 2007, Daniel M German wrote: I debugged today osso-xterm and found the reason that ctrl of special characters did not work, and I have a patch for it. I downloaded it from http://maemo-hackers.org/browser, but it source is for version 0.12. and the latest debian package is version 0.13 so where is the source for version 0.13? That's weird -- maemo-hackers svn doesn't have any versions older than 0.13mh13. Where did you check the version number from. At least both configure.ac and debian/changelog say 0.13mh13-24. That aside, the osso-xterm garage-project is the one you should use. Bugs should also be reported to its bug tracker instead of the maemo-hackers trac. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHAMekX9Rc0+po4p0RAgU0AKCd5/YfkEMkU6TVEmnkMZU/JGKEHwCfdfRX C04OpdUAZ9T+F5NqT8qKd9Q= =vy1l -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Missing Hildon include files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Hazel wrote: I appear to be missing some Hildon include files, and presumably the libraries that go with them. In particular, I can't find osso-manager.h in my development environment under Scratchbox, and I haven't been able to find out where to get it from. Can anyone advise me where to find it? I need to use the is_service_running function within my application, and the include file for it isn't there. It is meant for maemo-af-desktop internal use. Use dbus_bus_name_has_owner[1] instead. [1]: http://dbus.freedesktop.org/doc/api/html/group__DBusBus.html#g9cf4ff79453e2e11eab5b1d33395679b - -- Santtu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFG8mDlX9Rc0+po4p0RArZFAJ49mMGzWuOqyOR1w9y6CohcpOu3eQCfb7lU FUwa6DBK4GLP82upvm0UaII= =bFrt -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: conflicts between row-activated and button-press-event signal on GtkTreeView
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zhu, Peter J wrote: I'm having problems with mouse click processing of GtkTreeView. I would like to have different callback to single click and double click. But once I connect singal to button-press-event, no row-activated signal is received. I would guess your button-press-event-handler returns TRUE. For most Gdk/Gtk+ signals, returning TRUE means that the event has been handled, and it's emission is stopped -- thus it never reaches the handler in GtkTreeView. Try returning FALSE. ;) - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFG6jQEX9Rc0+po4p0RAtAMAJsEuNd8k7X/gbioT3XOgjScJqFUJQCfc2Eq 782EgwHiuTHQbX8pfgfJucE= =O2Gv -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Possible libosso bug?
Eero Tamminen wrote: The messages are answered by the co. processes, not D-BUS itself. If the message is sent with auto-activation flag, the co. process is started. Otherwise the message is lost (I think). If you pass something as retval, you will get error code and something like No such service in the retval s-field. I think all these libosso functions use the D-BUS auto-activation flag. True for osso_* -- muali -functions seem not to. I would say that it's a bug in the Browser. I agree. You might also use the co. D-BUS message directly _without_ auto-activation. That should do it (or you could ask dbus if the service is running or not). OTOH telling the browser to exit is not nice, the user might be using it for something else too. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Alarm API: Recurrence
Murray Cumming wrote: So I think that the (wrongly formatted) documentation is wrong when it says that it is the Number of minutes between each recurrence here: http://maemo.org/api_refs/3.0/alarm-api/structalarm__event__t.html The documentation is indeed wrongly formatted (the source has gtk-doc comments, not doxygen comments). The howto[1] is more accurate, please use that instead. [1]: http://maemo.org/development/documentation/how-tos/3-x/howto_alarm_interface_bora.html ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: hildon-1: Deprecated/removed widgets?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Murray Cumming wrote: These widgets/headers seem to have been removed from hildon-libs https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-libs/ as it was changed to hildon-1 (in sardine, for Maemo Chinook) https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-1/ There's some info in the wiki[1], according to it: hildon-add-home-dialog.h hildon-grid.h hildon-grid-item.h hildon-telephone-editor.h were dropped, hildon-name-password-dialog.h was renamed as hildon-login-dialog.h hildon-dialoghelp.h was moved to a more appropriate place (hildon-help), hildon-scroll-area.h will be replaced with more widely useful solution. About the rest: hildon-color-popup.h hildon-color-selector.h hildon-input-mode-hint.h it doesn't mention. [1]: http://maemo.org/community/wiki/haf/apicleanup/ - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFGm07NX9Rc0+po4p0RAlhmAJ0Rc0tAEoywBnXcqHCYu/PGoUX7AgCgl0iw UgY/pynlJY1LcK0vePjtL9g= =II1P -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo emails classified as spam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frank W. Kooistra wrote: The gmail account has a spam directory tag the erroneously spemmed messeges as This is not spam and they will be taken off spam lists if every body does that they will be cleared I have done this actively -- a couple of times a day since I noticed that the mails were being spammed. It doesn't help the fact that there's a mail server with no reverse, which is considered as a mark of spam by some mail servers. If google has such check, it's getting less effective on every not spam operation. - -- Santtu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeMoMX9Rc0+po4p0RAmv9AJ92fi16Dl/6J9xsH+fmpNfHmaMhxQCfS7OQ MbvDyiljleioAI0vpcjd0hM= =drSX -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Osso rpc complex return types
Christian Kellner wrote: with osso rpc so I was wondering if somebody have had that problem before and found some nice way around that (maybe using raw dbus in addition to osso rpc?). Indeed libosso doesn't support any complex types (or multiple return values for that matter), so you need to do raw dbus. You can get the dbus connection libosso uses with osso_get_dbus_connection, add a filter there and you should be good to go. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: CIA.vc tracking broken
Ferenc Szekely wrote: Well, sometimes you just can't go to sleep with unresolved problems in your head, right? I changed our cia bot to use email instead of XML-RPC and voila, the latest commit message from Johan has arrived there: Yay, #maemo-commits @ freenode is flooded again! Thanks for fixing it! -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: libconic.so.0 missing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mike t wrote: error while loading shared libraries: libconic.so.0: cannot open shared object file: No such file or directory libconic was introduced in bora/IT2007, and thus is not found on scirocco/IT(1.)2006. In IT2006 the library was osso-ic-lib, which has totally different API. All in all, you should use maemo 2.x when writing programs for IT2006 and maemo 3.x when for IT2007. It might be possible to build libconic for IT2006, you can get the sources with apt-get. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFGCnSkX9Rc0+po4p0RAnqaAJ92LeLYDgunEWyeMyWudkN6D7irCACeJbJk 891J2JgB+HYXugLc/Dn1p0w= =A5oz -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Developping C application on maemo without scratchbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: 5. Go to x-terminal and cd e.g. /media/mmc2/ (depending on which memory card you did put your file, is it in the internal slot or on the external slot) 6. Then you can execute your hello by typing ./hello And surely it works and it doesn't say Permission Denied. It can say this if you haven't Given that the mmcs use (v)fat (by default), chmod +x is a noop, and as they're mounted noexec, Permission Denied is exactly what you get. So in order to test the program, one needs to copy it to rootfs, then chmod +x and then run-standalone ./foobar. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFGAV03X9Rc0+po4p0RAnaoAJwM0sboqSgeFZtlfIAwhR04Ll8B1QCfcRc6 CiHMSY9LPzb7zdWj6YOsUp8= =WUfw -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] debhelper
Andrew Barr wrote: It seems a lot of Debian source packages now require debhelper = 5. This is a PITA because Scratchbox only has 4.2.32 and as far as I can tell building it is going to be no small task...I am failing to build the dependency libmodule-build-perl. Most of the packages I've run into only use debhelper = 5 to get 5 to debian/compat, I've successfully built many packages just by lowering the dependency and echo 4 debian/compat. Maybe one failed to build because of that, not quite sure -- it's still worth a try. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: gethostbyname() ?? Unable to become root
andrew gatt wrote: Looks like you just have to launch it from the menu, you can't just ./example_libosso to execute it. You can also use the run-standalone.sh -script to launch it. Without it (or launching from the menu) some environment variables will not be set (most importantly the DBus bus addresses) and osso_initialize will fail. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] automatic cache erase at update in RSS reader
Erick Lavoie wrote: I'm new to the list. I would like to add an option to prevent caching for some entries or erase the cache during an update in the default RSS reader. Do I have access to the source code and where should I contribute? The sources for all (L)GPL software on the device are available at maemo.org[1], and Koen has made them available[2] separately, so you don't need to download them all at once. There's no (at least public) project for the rss reader, but as the code is GPL, you can start your own as long as you keep the source available. [1]: http://maemo.org/downloads/IT_source.php [2]: http://linuxtogo.org/~koen/maemo/unpacked/ -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] gconf notifications?
Manuel Roman wrote:
I just wrote a very simple application that uses gconf notifications.
Unfortunately, the callback is never called. I have used gconf from a
graphical hildon app and notifications worked fine, however, when I try
from
a console application it does not seem to work. I include the two simple
files I wrote: gconf_test, which registers the callback and gconf_test_set,
which sets a value. If you can pinpoint the problem I would really
appreciate it. Although there is no error checking for gconf_init, I tested
it and always returned TRUE.
GConf needs GMainLoop to be running to work. In normal hildon
applications Gtk+ takes care of this, as gtk_main() runs a GMainLoop.
You can alter your main() to use GMainLoop:
int main(int argc, char **argv)
{
GMainLoop *loop;
g_type_init();
config_init();
loop = g_main_loop_new(NULL, FALSE);
g_main_loop_run(loop);
return 0;
}
Do note, that unlike with Gtk+'s gtk_main_quit(), with GMainLoops, you
need to pass the loop object to g_main_loop_quit, so you'll need to
store the loop pointer and pass it everywhere it is needed. Also note
that gconf_init() is deprecated and needs not be called.
--
Santtu Lakkala
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] upgrading base packages from third party repositories
Jussi Kukkonen wrote: If I upload a gstreamer package with version number larger than the Nokia-provided-gstreamer has into the extras repository, the users of that repo would then install it on the next upgrade even if they hadn't installed a package that requires the new version of gstreamer, right? That does not sound like something I'd like -- Should I use another package name and a Conflicts-field? Normal users quite rarely do an upgrade. I.e. the package won't be installed unless one does apt-get upgrade or installs a package via application manager that needs it. Having a newer version of a package in extras sounds a bit weird. Whatever you do, you shouldn't use only the Conflicts field, but instead some kind of combination of Conflicts, Replaces and Provides. Otherwise the new package would most likely be uninstallable (or would uninstall many other packages). -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] upgrading base packages from third party repositories
Marius Vollmer wrote: That way lays madness. :) You shouldn't turn a real package into a virtual package willy-nilly. For example, Provides can't talk about versions. I think it is not really possible to have one package masquerade as another package cleanly. Well yes, that way does lay madness or that way there be monsters, and yes it will probably break. But so will having only Conflicts too. Should've started with *** DON'T DO THIS *** If you choose to ignore the warning =) -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] keyboard simulator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Moore wrote: I am interested in writing a script or program (or obtaining from elsewhere an open source one) that can simulate hardware keypresses of a keyboard, in particular those of the hardware keys on the nokia. XTest is probably what you want, XTestFakeKeyEvent to be more precise. See for example: http://homepage3.nifty.com/tsato/xvkbd/events.html, google is your friend too. =) - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbBx2OjErIbnoFXIRAh3PAJ0b8pm7D4qjg/dXblFJNkh9vI9R1wCeL6Vj oKR213GHP/w+v6uScAb1d/M= =vCIw -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Java on 770
Michael Dominic Kostrzewa wrote: I find it more reasonable to port a Java widget toolkit to hildon, than to create a wholly new toolkit. SWT can already use Gtk, so I guess it'd mostly be porting the backend to use hildon widgets where applicable. Hmm, I'm not sure what you mean. There is, indeed, no sense in creating a new toolkit (for what?). What we prolly need is hildon-* bindings for Java and gtk bindings (I assume they exists somewhere). Afaik there are no Gtk bindings per se. But there is IBM's swt toolkit, that can use Gtk as a backend. If we just make Gtk bindings, we lose quite a lot of the reasons to use Java in the first place. If we have our own, product specific, library for widgets, then there is a need for porting software. Instead there should be a backend for swt (or awt/swing) that uses hildon widgets where appropriate. This way the program will run and look native in multitude of environments. All this without need for modifying source or even recompiling. Also, it's not only about GUI toolkit but also about other API's. Ie. you most likely want to use gnome-vfs, dbus, gstreamer, etc. Using plain SWT (even with Gtk drawing) will result in a lot of inconsistencies. Ie. the input methods will not work as expected. Why will the input methods not work? I may be wrong on this, but I really think they would work. But anyway, having gnome-vfs available would be nice, but once again, if it is only used on maemo there is no real gain from using java. For gnome-vfs, I'd say the best way is to replace FileInputStreams with gnome-vfs implementations. Sure, then you'd be forced to use gnome-vfs, but at least you would not need code changes. GStreamer is a harder one, this would probably be a nice-to-have one. And without DBus I guess there's no way to get total integration with rest of the system. With mono, the bindings exist for most of the components we use, although they might need some tweaking. For some custom components (ie. hildon-libs) we want to generate the bindings with the gapi-parser. This way the mono apps on 770 will have a 100% native look, feel and behaviour. Call me idealist, but in my opinion for Java (and mono) to be really useful, the same code -- even the same binaries, should run everywhere and look native -- without a mess of checks on what the system we're on supports. Oops, forgot (once again) reply-to-all and thus we were out of the list for a couple of messages. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Livejournal client for 770
Santtu Lakkala wrote: Andrew Barr wrote: Is anyone aware of a Livejournal client for Maemo, or, failing that, a small and simple GTK+ client that could be ported? I've been writing this little application called maemo-blog; however it currently only supports Blogger and MetaWeblog APIs: no LiveJournal yet (and AFAIK LiveJournal doesn't support any other APIs than their own). I'll have to take that back; LiveJournal _does_ support blogger API. So if you want to try maemo-blog, insert: http://www.livejournal.com/interface/blogger as the Blog RPC url. Did a quick test and it seemed to work. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] re-evaluating the handwriting input method - butthere's a problem
[EMAIL PROTECTED] wrote: You can always switch the case of already written character with the arrow button located left second from bottom. It works both ways and is a better solution for normal typing, not necessarily for entering commands in xterm ;-) Xterm and HWR don't work too well together anyways. The HWR uses delete-surrounding quite a lot, and this doesn't really work for terminal applications, especially when using interactive programs. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: rebooting constantly after upgrading packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Álvaro J. Iradier wrote: Yes, basically you'll need to disable lifeguard flag, and then complete the apt-get upgrade using ssh (when updating maemo-launcher xterm will be killed). This actually depends on which version of osso-xterm is used, the one from maemo[1] repositories does not use maemo-launcher, so it is safe to use; however, the one from maemo-hackers[2] does use, and will be killed. (thanks btw, just noticed that the maemo-hackers version does not depend on maemo-launcher -- need to fix) [1]: http://repository.maemo.org/pool/mistral/free/o/osso-xterm/ [2]: http://maemo-hackers.org/wiki/OssoXterm - -- Santtu Lakkala [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFE9bZDX9Rc0+po4p0RAih3AKCMpkt1cwxTi6AM38E9gnWNck8fdgCgrFb1 nxAsPewbsIqfEyWm5qhxJ8g= =awyL -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] osso-xterm
Fred Lefévère-Laaoide wrote: I installed the latest version (0.13.mh12) and ... it still didn't work ! I executed killall osso-xterm then it worked ! Yeah, sorry 'bout that, the mh11 version process did not stop, if you used exit or logout to close the last terminal. It is now fixed in mh12. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: [maemo-users] Using osso_iap_cb example
Brad Burleson wrote: My only problem is that gtk_main() transfers control away from my daemon. Is it possible to attach to the GLib main loop and return back to my own code from time to time (the project I'm working on has it's own internal scheduler and I'm not up for a big rewrite now)? You can do: g_timeout_add(milliseconds, function, user_data); or g_idle_add(function, user_data); to get regularily back to your code. Note that function should return TRUE to get called again (and again). But neither of these is really a good solution. When working with glib, you should use it's scheduler for things to go smooth. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Missing libgmodule-2.0.la
Murray Cumming wrote: Actually, I may have mistyped that. I'll try do a rootstrap install. You can also remove all .la files, then libtool will not bug you about missing ones. (It only bugs about them, if there is a .la file referencing to a missing one.) -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Application catalog from repositories
Tommi Komulainen wrote: I hacked together a small script which reads the Packages.gz files from a configured set of repositories and generates a catalog page showing all packages, grouped by sections. Maybe someone finds this useful. Here's a little patch (sorry for the low quality, don't really use python) that gets the list of repositories from maemowiki/ApplicationRepositores instead of hardcoded values: http://inz.fi/generate-catalog-maemowiki.patch -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] cannot compile example_libosso.c
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dionisis Petromanolakis wrote: hi Laszlo and all, what do you mean with makefile?I just downloaded the file from the maemo.org. I didnt find a makefile. Instead im trying to compile it from the command prompt. but the compilation always fails. The command i use is gcc -o example_libosso example_libosso.c 'pkg-config --cflags gtk+-2.0 hildon-libs' -ansi -Wall 'pkg-config --libs gtk+-2.0 hildon-libs', is something wrong with the command? Do i need to specify the libosso library from path /usr/lib directory. I assume that the program may cannot see this library. I tried to include /usr/lib/libosso.so in the compilation but it didnt find the file. Do i need to download another file? Do i need to use another command option? libosso has pkgconfig file, so you can simply add libosso to pkg-config packages. i.e. pkg-config libosso gtk+-2.0 hildon-libs --cflags and obviously the same for --libs. Or you can also just grab the makefile and all the examples from stage[1]. There is also newer example, that no longer uses gtk_infoprint, but the successor HildonBanner. [1]: https://stage.maemo.org/svn/maemo/projects/tools/trunk/maemo_testing/maemo-examples/ - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFErkJCOjErIbnoFXIRArHOAJ0dZIce5bw48o1IBdvPJh5YUj5RlACffrD3 e8T0Uy+4qK0xvaqQjegM0wI= =tY2s -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Playing WAV files on nokia
Vladislav Grinchenko wrote: Someone mentioned calling hildon_play_system_sound(soundfile.wav) in a prior post, but I can't seem to find the header file for it in my scratchbox. Am I missing a library? And if so, what's its name? It should be in /usr/include/hildon-widgets/hildon-system-sound.h, which belongs to hildon-libs-dev (= 0.9.52), older versions don't have this. You can also use esd_play_file(myprogname, soundfile.wav, 0); if play_system_sound is not available. This however does not respect the system sound level setting and blocks until the sound has been played. If you want nonblocking audio that's not a system sound, combination of: int esd = esd_open_sound(NULL); int sample = esd_file_cache(esd, myprogname, soundfile.wav); esd_sample_play(esd, sample); esd_sample_free(esd, sample); esd_close(esd); should do the trick. -- Santtu ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
