Ideas for Diablo and Elephanta
Now that maemo Chinook approaches is a good time to define the features to implement in the following releases of our SDK and development platform: Diablo and Elephanta. Your suggestions are welcome. You can file enhancement requests at bugs.maemo.org (preferred), send a proposal to be discussed at maemo-developers or post a comment here. We are looking specially for ideas that help improving our developer offer and also coordinating better with Ubuntu Mobile and other projects in the GNOME Mobile space. -- Quim Gil - http://maemo.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: how to tell if files have changed?
Hi, ext Michael Wiktowy wrote: Does maemo have anything like FAM or Gamin that tells us if watched files or dirs have changed? I'm trying to improve Kagu's media scanning capabilities and it seems that the best thing to do would be to get a notification of some sort when a new file arrives, scan it, and act appropriately. Don't both of those tools just tell you which files changed between subsequent scheduled scans? You still have to waste a buch of disk and cpu time on scanning and generating checksums on each file. I think that what you are looking for comes with inotify ... but I am not sure how you hook into that or if it is even available on the N800/770. http://en.wikipedia.org/wiki/Inotify Inotify will be available in the next release having Glibc 2.5. You should be able to test it with the SDK Beta I think. (you can use it also with Glibc 2.3 in earlier releases, but then you need to do syscalls directly instead of using nice Glibc functions.) Could you not just look at the mtime of your monitored music directories on start up and compare it to what it was last time? That should tell you if files were added/removed/changed ... unfortunately you still have to scan to see which ones. BTW ... Kagu is very nice. I have started using it as my default music player. Thanks. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Creating a Debian package - clarifications required
I'm trying to follow the instructions in the How To section of the Maemo website, and I'm finding that there are several questions that don't seem to be addressed. I'm hoping that someone can answer these for me. 1. The application I'm packaging up is not intended to be built from source by users, but to be supplied as-is in binary form on a memory card (specifically for the N800). I am hoping that this means I don't need to supply a Makefile, but the instructions aren't clear on this point. Can I elect not to supply a Makefile if I don't intend to supply sources for the user to build the application? All I want the Application Manager to do, when it reads this package, is copy the binary and other files from the memory card to the right locations and do whatever else is needed to make the application appear in the navigator menu. 2. I originally started off with my source directory containing mixed upper and lower case letters, as well as the version number. However, db_make complained about this and I've now changed the directory name. Do I also need to change the names of the binary, icon file and desktop file to match? Again, this isn't clear from the instructions. 3. Does the application name used for the source directory need to correspond with the name by which the application will be known to OSSO? For example, if my source directory is abc-1.0.0, does this mean that OSSO will have to know the service as abc.nokia.com and that the OSSO application name will have to be abc? 4. Does the name of the icon file have to correspond with the name of the binary file in any way? For example, if it is a 26x26 icon, and the binary name is abc, does the icon have to be called abc_icon_26x26.png? This is kind of suggested in the documentation, but it isn't stated explicitly. 5. Will dh_make automatically uuencode the icon and place it in the control file, or do I have to manually run uuencode and copy the text in? Sorry for so many questions in one go, but my first attempt to follow the instructions didn't really clarify these points. David Hazel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Creating a Debian package - clarifications required
On 21/09/2007, David Hazel [EMAIL PROTECTED] wrote: I'm trying to follow the instructions in the How To section of the Maemo website, and I'm finding that there are several questions that don't seem to be addressed. I'm hoping that someone can answer these for me. 1. The application I'm packaging up is not intended to be built from source by users, but to be supplied as-is in binary form on a memory card (specifically for the N800). I am hoping that this means I don't need to supply a Makefile, but the instructions aren't clear on this point. Can I elect not to supply a Makefile if I don't intend to supply sources for the user to build the application? All I want the Application Manager to do, when it reads this package, is copy the binary and other files from the memory card to the right locations and do whatever else is needed to make the application appear in the navigator menu. When you create debian packaging for your application, you can provide only the binary package to users. Then users don't need to build anything and you don't have to provide sources. You should read Debian New Maintainers' Guide if you'r about to create debian packages. Maemo's packaging howto is just simplification of those instructions and it doesn't explain things very deeply. 2. I originally started off with my source directory containing mixed upper and lower case letters, as well as the version number. However, db_make complained about this and I've now changed the directory name. Do I also need to change the names of the binary, icon file and desktop file to match? Again, this isn't clear from the instructions. 3. Does the application name used for the source directory need to correspond with the name by which the application will be known to OSSO? For example, if my source directory is abc-1.0.0, does this mean that OSSO will have to know the service as abc.nokia.com and that the OSSO application name will have to be abc? 4. Does the name of the icon file have to correspond with the name of the binary file in any way? For example, if it is a 26x26 icon, and the binary name is abc, does the icon have to be called abc_icon_26x26.png? This is kind of suggested in the documentation, but it isn't stated explicitly. 5. Will dh_make automatically uuencode the icon and place it in the control file, or do I have to manually run uuencode and copy the text in? Sorry for so many questions in one go, but my first attempt to follow the instructions didn't really clarify these points. David Hazel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Miko Nieminen [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: installing scratchbox and maemo sdk
hello people, Thanks for all the help on installation . I appreciate all your help. Thanks, Anurag On 9/21/07, leemars [EMAIL PROTECTED] wrote: Date: Wed, 19 Sep 2007 22:01:01 -0400 From: [EMAIL PROTECTED] To: maemo-developers@maemo.org Subject: installing scratchbox and maemo sdk Hi , I have been trying to install scratchbox on my Linux machine. The linux distribution that i have is SUSE I have already downloaded the tar ball for scratchbox and untared it. However when i do ./run_me_first.sh it give me the following error:- Missing /home/anurag/Desktop/scratchbox/host_shared/lib/ld.so Scratchbox-libs not installed? I am not sure how to proceed forward with this. Also after this what would have to do install mameo sdk and start developing. Thanks Anurag Hi Mybe you should untar all scrathbox tar package to root directory (use -C option is important you must install scrathbox in root directory or create a soft link: tar -xvf scratchbox-*.tar.gz -C /). Good Luck mars _ Windows Live Custom Domain，您的免费电子邮局。 https://domains.live.com/default.aspx ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Freescale Licenses AMD Graphics Technologies for use in iMX processors
Jon Smirl wrote: Here's a good reason to switch from OMAP to iMX31 in next gen device Combine this with AMD's decision to open source the specs. Maybe... but there are a couple of things which vote against it: 1) The Hardware used in the N800 is also used in various other Nokia products. The designers of the N770 and N800 had to use parts which will be bought for other products (e.g. N9x series) as well. So there is just a chance to switch, if the developers of the N9x series will also switch... 2) To open the specs for some ATI/AMD graphics architecture does not mean that all specs are open. Even the Xorg programmers said, that the specs opened just covers the 2D part. 3) I have just read the iMX31 product brief. The MPEG-4 _encoder_ is nice, but I don't see a dedicatet DSP on board. I think that there is a lot of TI DSP code running on the N9x series. See 1)... At least, the N800 just _has_ a 3D gfx accelerator. If we just get the specs... -- Klaus Rotter * klaus at rotters dot de * www.rotters.de ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Freescale Licenses AMD Graphics Technologies for use in iMX processors
On 9/21/07, Klaus Rotter [EMAIL PROTECTED] wrote: Jon Smirl wrote: 2) To open the specs for some ATI/AMD graphics architecture does not mean that all specs are open. Even the Xorg programmers said, that the specs opened just covers the 2D part. For now, that's the case. They are promising more once they can work internal legal issues out...and as far as I know they have specifically promised 3D specifications for at least the R3xx and R5/6xx series... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Freescale Licenses AMD Graphics Technologies for use in iMX processors
On Wed, Sep 19, 2007 at 09:22:02PM -0400, ext Jon Smirl wrote: Here's a good reason to switch from OMAP to iMX31 in next gen device Combine this with AMD's decision to open source the specs. AMD today announced Freescale Semiconductor will license its 2D and 3D graphics technology. Freescale Semiconductor will use the AMD graphics technologies to equip its i.MX processors with OpenGL ES 2.0 and OpenVG 1.0 technologies. OpenGL ES 2.0 and OpenVG technologies are designed for mobile applications where battery life is key, including portable gaming, navigation and media player devices. AMD has opened the Radeon graphics specs. Their embedded chipsets (based on work by the Bitboys crew) have nothing to do with the Radeons, and nothing to do with the announcement in the slightest. signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Possible bug in /usr/lib/libglib-2.0.so.0
Hi Fernando, I came closer to the problem. It seems to me, that not the gtkrc.cache file is broken, but the -rw-r--r--1 user users 25 Jun 29 14:30 current-gtk-key-theme -rw-r--r--1 root root 28 Sep 21 21:45 current-gtk-key-theme.cache -rw-r--r--1 user users 50 Jun 29 14:30 current-gtk-theme -rw-r--r--1 root root 52 Sep 21 21:45 current-gtk-theme.cache - cache files in /home/user/.osso are missing. They are not recached by the actual hildon-theme-cacher anymore. (It is disabled in the source // uncommented patch for maetronom, detlef // g_unsetenv (GTK2_RC_FILES); (I reenabled it, so 0.4.1 is working again for me, and added postinst to recache everything including .osso files) I have the files on the project maetronome and the bug report for maetronome in https://garage.maemo.org/tracker/index.php?func=detailaid=1189group_id=152atid=637 This is not a solution up to now. By the way, the hildon-theme-cacher can only be installed in red pill mode. Otherwize the app installer tells me: incompatible package. What is the reason for that. How does the app installer decide, that red pill mode is needed? Am Donnerstag, den 20.09.2007, 15:58 +0300 schrieb Fernando Herrera: Hi, El jue, 20-09-2007 a las 13:53 +0200, ext Detlef Schmicker escribió: Am I right, that the gtkrc.cache is corrupt in the latest image? I had a quite clean N800 installation and only added openssh and xterm before testing! Humm, this sounds very strange to me. What is the clean way to deliver a program which needs calling hildon-theme-cacher. I could not find a trusted source for hildon-theme-cacher and in I could not find the source code. So it is not possible to deliver it with my gpl application?! hildon-theme-cacher is installed in all the images, so you can just invoke it if you really need it from your applications. Usually new themes invokes it in the postinst script, either: hildon-theme-cacher path-to-your-theme or (to update all gtkrc caches): hildon-theme-recache-all The source code for this cacher program it's at stage svn. Latest sources are: https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-theme-cacher/ but those are matching the current development versions of glib and gtk+ present on sardine and won't work with the latest official maemo release, so you probably want to look at: https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-theme-cacher/0.4.1-1/ Hope this helps. Salu2 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Installing xephyr on SUSE 10.2
Hello, I am trying to install xephyr on SUSE, however the tutorial is not very clear on how to install xephyr. Also when I did go the xephyr site, it had debian binaries. I am not sure how to run it on SUSE. I am done with installing scratchbox and maemo rootstrap, I am stuck with xephyr. Also the rootstrap does not have Xephyr as mentioned in the tutorial page. Any help would be appreciated. Thanks, Anurag ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
[ANN] Ruby/Maemo first release.
I'd like to announce the _packaged_ release of my Ruby/Maemo project. The files you need to start developing graphical Maemo apps in Ruby are at: http://maemo.rubyx.co.uk/projects/ruby-maemo Please feel free to contact me about anything concerning the development and usage of these packages. As before with the developer preview release I'm only supplying the Hildon bindings. Please don't fret though, I will be working on the libosso bindings over the next few days and hope to add that package very soon. Hope you enjoy my work as much as I enjoy working on this project. - Tom Swindell [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
