Re: Why touch event go through my window
On Tue, 2010-02-16 at 16:07 +0100, ext Evan JIANG wrote: Yes. I've tried that. But I still have no idea why it crashes on your device. It works well here. I'm not sure, but maybe you can try: 1. rm -rf /home/user/.scim And reboot to check if it works. 2. Reinstall it. Since someone said it works for him before: http://code.google.com/p/scim-for-maemo/issues/detail?id=22can=1 (Comment 8) I'm trying to reproduce and fix it now. I will let you know if I have any progress on it. I tracked down the failure a bit, it seems that PanelAgent::initialize() is failing. So it means that m_socket_server.create() returns false for some reason. -Kimmo Thank you very much! Best regards, Evan JIANG 2010/2/16 Kimmo Hämäläinen kimmo.hamalai...@nokia.com: On Tue, 2010-02-16 at 10:34 +0100, ext Evan JIANG wrote: Hi, Thank you for your reply. Which locale are you using? It's ok to run it under en_US on real device. The application is using by lots of users for 2 monthes. I think it should not have such problem. The source code can be found here: http://code.google.com/p/scim-for-maemo/ Well, I admit the source code is a bit complex. I compiled the mscim package from this Subversion trunk, but it is still crashing after I have installed it. Have you used it in a fresh PR1.1 N900 by just installing those two packages, nothing more? -Kimmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Arabic detection to Enca
Hello, Is there any one knows Arabic charset encodings? We are using Enca [http://freshmeat.net/projects/enca/] to perform encoding detection in N900. It supports detection of Chinese/Cyrillic etc., but not Arabic ones like ISO-8859-6, Windows-1256, IBM-864 and MacArabic. We want to extend Arabic detection to the future products, by adding Arabic to Enca. If anyone can help that would be highly appreciated. Br, Xun ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Free space, Qt and PR1.2
In the light of the latest PR1.1.1 and free space issues I was wondering about the soon to be PR1.2 and Qt update impact on it. Is there a plan/script in place how application developers or people with Qt applications installed should handle the upgrade ? Asking because it seems to me a simple version bump would not quite work due to the space required to install the upgrades (i.e. a new PR containing a new libqt4-core would work for people who do not have Qt apps, but for those who do, it would pull in all the other already installed libqt*, almost certainly ballooning the required free space into the non-available range). As for app developers, due to the existing setup, an automatic recompile spree is not perfect as there is plenty of chance for breakage if libqt4-maemo5 suddenly becomes libqt4. Long story short, is there a PR1.2 migration plan for Qt devs/users, or is it taken care of so the problems outlined above do not apply ? :) Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
Harmattan is going to stay DEB based, despite being the first MeeGo implementation on Nokia devices. This is IMHO good news. Now we only need to convince them to stick to it even after Harmattan... I would _love_ to see that happen. then contribute here: http://wiki.maemo.org/DebForMeeGo Well, I don't have any hope for that MeeGo would switch to .deb. It has been said on several times on the moblin-dev list (even today) that the reasons to choose rpm were technical, but I haven't seen even one technical reason published. So for now I'll believe that it was mostly political decision and as such can not be changed anymore. Anyway, I'll document here my pet peeve about rpm-format. And after that suggest how to limit the damage that this might (will) cause. If you don't like details, just skip to the last chapter at the end of this mail. :) First, lets choose a package that exists in both Moblin and Maemo and that uses few libraries. I'll pick evince, just because I have used it and know what it does. u...@host:~/tmp$ wget http://repo.moblin.org/moblin/releases/2.1/ia32/os/i586/evince-2.26.1-4.12.moblin2.i586.rpm --2010-02-16 12:16:28-- http://repo.moblin.org/moblin/releases/2.1/ia32/os/i586/evince-2.26.1-4.12.moblin2.i586.rpm Resolving repo.moblin.org... 74.86.162.225 Connecting to repo.moblin.org|74.86.162.225|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1462309 (1,4M) [application/x-redhat-package-manager] Saving to: `evince-2.26.1-4.12.moblin2.i586.rpm' 2010-02-16 12:16:30 (943 KB/s) - `evince-2.26.1-4.12.moblin2.i586.rpm' saved [1462309/1462309] u...@host:~/tmp$ wget http://repository.maemo.org/extras/pool/diablo/free/e/evince/evince_2.21.1-1.maemo8_armel.deb --2010-02-16 12:16:32-- http://repository.maemo.org/extras/pool/diablo/free/e/evince/evince_2.21.1-1.maemo8_armel.deb Resolving repository.maemo.org... 217.212.252.193, 217.212.252.161 Connecting to repository.maemo.org|217.212.252.193|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 559882 (547K) [application/x-debian-package] Saving to: `evince_2.21.1-1.maemo8_armel.deb' 2010-02-16 12:16:32 (9,38 MB/s) - `evince_2.21.1-1.maemo8_armel.deb' saved [559882/559882] Then, lets see what dependencies does the rpm package from Moblin has: u...@host:~/tmp$ rpm -qpR evince-2.26.1-4.12.moblin2.i586.rpm rpm: To install rpm packages on Debian systems, use alien. See README.Debian. error: cannot open Packages index using db3 - No such file or directory (2) error: cannot open Packages database in /var/lib/rpm warning: evince-2.26.1-4.12.moblin2.i586.rpm: Header V3 DSA signature: NOKEY, key ID 79fc1f8a /bin/sh /bin/sh /bin/sh /bin/sh GConf2 GConf2 GConf2 GConf2 libICE.so.6 libSM.so.6 libX11.so.6 libatk-1.0.so.0 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.3.4) libc.so.6(GLIBC_2.4) libcairo.so.2 libdbus-glib-1.so.2 libevdocument.so.1 libevview.so.1 libfontconfig.so.1 libfreetype.so.6 libgcc_s.so.1 libgconf-2.so.4 libgdk-x11-2.0.so.0 libgdk_pixbuf-2.0.so.0 libgio-2.0.so.0 libglib-2.0.so.0 libgmodule-2.0.so.0 libgnome-keyring.so.0 libgobject-2.0.so.0 libgthread-2.0.so.0 libgtk-x11-2.0.so.0 libm.so.6 libm.so.6(GLIBC_2.0) libnautilus-extension.so.1 libpango-1.0.so.0 libpangocairo-1.0.so.0 libpangoft2-1.0.so.0 libpoppler-glib.so.4 libpthread.so.0 libpthread.so.0(GLIBC_2.0) librt.so.1 libspectre.so.1 libstdc++.so.6 libstdc++.so.6(CXXABI_1.3) libtiff.so.3 libxml2.so.2 libz.so.1 rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 scrollkeeper scrollkeeper Quite a list. And it seems to include three types of dependencies: 1. File name based. Such as /bin/sh, libgtk-x11-2.0.so.0 and libnautilus-extension.so.1 2. Package name based. Such as GConf2 and scrollkeeper 3. Third one seems to be feature based. For example rpmlib(CompressedFileNames) = 3.0.4-1 Of these, the last two are ok, I can easily see what additional packages I need to get and install to satisfy these. But the first one. What package provides libnautilus-extension.so.1? Or libevview.so.1? And even if I find out what package has these specific files, is there any version dependencies? Now, lets see what the Maemo version depends on. u...@host:~/tmp$ dpkg-deb -f evince_2.21.1-1.maemo8_armel.deb depends | sed 's/,\ /\n/g' libatk1.0-0 (= 1.12.2) libc6 (= 2.5.0-1) libcairo2 (= 1.4.10) libdbus-1-3 (= 0.94) libdbus-glib-1-2 (= 0.74) libdjvulibre15 (= 3.5.20)
Re: MeeGo
Twas brillig at 13:51:52 17.02.2010 UTC+02 when kimju-maemo-...@inside.org did gyre and gimble: KJ But the first one. What package provides libnautilus-extension.so.1? Or KJ libevview.so.1? And even if I find out what package has these specific KJ files, is there any version dependencies? Do you have the slightest idea what SONAMEs are and what they are for? -- http://fossarchy.blogspot.com/ pgp2nbOujVp1B.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
On Wed, Feb 17, 2010 at 12:59:47PM +0100, Mikhail Gusarov wrote: Twas brillig at 13:51:52 17.02.2010 UTC+02 when kimju-maemo-...@inside.org did gyre and gimble: KJ But the first one. What package provides libnautilus-extension.so.1? Or KJ libevview.so.1? And even if I find out what package has these specific KJ files, is there any version dependencies? Do you have the slightest idea what SONAMEs are and what they are for? Yes I do. But they still don't help on picking the correct package. And the sonames are not usually/always incremented for a minor bug fixes etc. At least not the part visible in the file name. For example: Program X uses libfoo, and libfoo had bug that this program triggers. It was fixed in libfoo 1.0.11, but the name of the library is still libfoo.so.1, even if the library itself has more specific version number. So if the program X package still announces requirement for libfoo.so.1, it doesn't say that this really needs = 1.0.11 of the libfoo, -kimju ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
Twas brillig at 14:14:42 17.02.2010 UTC+02 when kimju-maemo-...@inside.org did gyre and gimble: KJ But the first one. What package provides KJ libnautilus-extension.so.1? Or libevview.so.1? And even if I KJ find out what package has these specific files, is there any KJ version dependencies? Do you have the slightest idea what SONAMEs are and what they are for? KJ Yes I do. But they still don't help on picking the correct package. At least for one RPM-based distro (balcanization of RPM-based distros is completely another topic) I know apt-get install libnautilus-extension.so.1 installed the proper package (as well as apt-get install /usr/bin/foobar). KJ And the sonames are not usually/always incremented for a minor bug KJ fixes etc. At least not the part visible in the file name. And they should not to. KJ For example: Program X uses libfoo, and libfoo had bug that this KJ program triggers. It was fixed in libfoo 1.0.11, but the name of KJ the library is still libfoo.so.1, even if the library itself has KJ more specific version number. So if the program X package still KJ announces requirement for libfoo.so.1, it doesn't say that this KJ really needs = 1.0.11 of the libfoo, It's a bug in packaging then. Such dependency won't be picked automatically by dpkg-shlibdeps too, and need to be added manualy by packager. -- http://fossarchy.blogspot.com/ pgpunPaqm9Rwf.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
What to do in order to distribute a proyecto on Maemo (Meego)
I am actually working in a proyect writen in Qt. After the anouncing of MeeGo, what should I do. Should I learn how to create the .deb packages as eplained in Maemo.org or shall I learn how to create .rpm packages in some linux ditribution? Of course If I am developping something new I would like to work for the whole Meego. Some answers? Thanks! This message was sent using IMP, the Internet Messaging Program. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: What to do in order to distribute a proyecto on Maemo (Meego)
On Wed, Feb 17, 2010 at 2:39 PM, ac...@dsic.upv.es wrote: I am actually working in a proyect writen in Qt. After the anouncing of MeeGo, what should I do. Should I learn how to create the .deb packages as eplained in Maemo.org or shall I learn how to create .rpm packages in some linux ditribution? Create the debs. It's going to be a while before anyone can use the rpm format. -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Free space, Qt and PR1.2
I too would like to know the answer for this and preferable before PR1.2 is released. On Wed, Feb 17, 2010 at 11:57, Attila Csipa ma...@csipa.in.rs wrote: In the light of the latest PR1.1.1 and free space issues I was wondering about the soon to be PR1.2 and Qt update impact on it. Is there a plan/script in place how application developers or people with Qt applications installed should handle the upgrade ? Asking because it seems to me a simple version bump would not quite work due to the space required to install the upgrades (i.e. a new PR containing a new libqt4-core would work for people who do not have Qt apps, but for those who do, it would pull in all the other already installed libqt*, almost certainly ballooning the required free space into the non-available range). As for app developers, due to the existing setup, an automatic recompile spree is not perfect as there is plenty of chance for breakage if libqt4-maemo5 suddenly becomes libqt4. Long story short, is there a PR1.2 migration plan for Qt devs/users, or is it taken care of so the problems outlined above do not apply ? :) Regards, Attila ___ 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: What to do in order to distribute a proyecto on Maemo (Meego)
Thanks Ville. I understand that but I see this a little uselees learning to create .debs when they I will not use them anymore in some months. Do not you think so? Regards!!! Quoting Ville M. Vainio vivai...@gmail.com: On Wed, Feb 17, 2010 at 2:39 PM, ac...@dsic.upv.es wrote: I am actually working in a proyect writen in Qt. After the anouncing of MeeGo, what should I do. Should I learn how to create the .deb packages as eplained in Maemo.org or shall I learn how to create .rpm packages in some linux ditribution? Create the debs. It's going to be a while before anyone can use the rpm format. -- Ville M. Vainio http://tinyurl.com/vainio This message was sent using IMP, the Internet Messaging Program. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: What to do in order to distribute a proyecto on Maemo (Meego)
Hi, On 17 February 2010 14:02, ac...@dsic.upv.es wrote: Thanks Ville. I understand that but I see this a little uselees learning to create .debs when they I will not use them anymore in some months. Do not you think so? you will need to create .deb anyway if yoou want to distribute your application to N900 users. -- Andrea Grandi email: a.grandi [AT] gmail [DOT] com website: http://www.andreagrandi.it PGP Key: http://www.andreagrandi.it/pgp_key.asc ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: What to do in order to distribute a proyecto on Maemo (Meego)
ext ac...@dsic.upv.es wrote: I am actually working in a proyect writen in Qt. After the anouncing of MeeGo, what should I do. Should I learn how to create the .deb packages as eplained in Maemo.org or shall I learn how to create .rpm packages in some linux ditribution? At the moment you have only Maemo 5 with Qt and QtMobility (MeeGo API's) it used .deb and only way to distribute is to make .deb packages. Next, first MeeGo, ex Maemo 6 is still using .deb so you still need to use .deb packages. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: What to do in order to distribute a proyecto on Maemo (Meego)
On Wed, Feb 17, 2010 at 3:02 PM, ac...@dsic.upv.es wrote: Thanks Ville. I understand that but I see this a little uselees learning to create .debs when they I will not use them anymore in some months. Do not you think so? You can minimize the effort by using template created by madde as a starting point, or see how it works in a minimal example (apt-get source qt-maemo-example). -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
FatELF Re: rpm vs. deb and universal binaries/packages
Wouldn't it be thrilling to have this implemented in MeeGo? http://icculus.org/fatelf/ Cheers, Chris ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: FatELF Re: rpm vs. deb and universal binaries/packages
On Wed, Feb 17, 2010 at 1:18 PM, Christopher Intemann intem...@gmail.com wrote: Wouldn't it be thrilling to have this implemented in MeeGo? http://icculus.org/fatelf/ What does this actually gain, as opposed to using binaries compiled for the specific platform? The only tangible benefit I can see is the ability to port from one arch to another easily, but that's hardly something that regular users are going to be doing. Cheers, Chris Best, Robin Burchell mob: +447702671419 msn: m...@viroteck.net irc: w00t @ irc.freenode.net twr: http://twitter.com/w00teh ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: FatELF Re: rpm vs. deb and universal binaries/packages
On Wed, Feb 17, 2010 at 2:21 PM, Robin Burchell virot...@viroteck.netwrote: On Wed, Feb 17, 2010 at 1:18 PM, Christopher Intemann intem...@gmail.com wrote: Wouldn't it be thrilling to have this implemented in MeeGo? http://icculus.org/fatelf/ What does this actually gain, as opposed to using binaries compiled for the specific platform? The only tangible benefit I can see is the ability to port from one arch to another easily, but that's hardly something that regular users are going to be doing. Well I just find it nice to download a single software package, e.g. on the Nokia Booklet running MeeGo, and then later copy the same package to the N900 (which is also running MeeGo) and run it there. To make that possible, there either has to be a Booklet based on ARM architecture, an rpm carrying two platform specific versions of the software (e.g. ARM and Intel) or something like fatelf... Cheers, Chris ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: FatELF Re: rpm vs. deb and universal binaries/packages
On Wed, Feb 17, 2010 at 1:34 PM, Christopher Intemann intem...@gmail.com wrote: Well I just find it nice to download a single software package, e.g. on the Nokia Booklet running MeeGo, and then later copy the same package to the N900 (which is also running MeeGo) and run it there. To make that possible, there either has to be a Booklet based on ARM architecture, an rpm carrying two platform specific versions of the software (e.g. ARM and Intel) or something like fatelf... Cheers, Chris The thing is, as the note of FatELF says themselves, that it will require more space (to download store), meaning you're pretty much no better off than having downloaded it twice in the first place. And again, considering that (for the *end user*, not people on this list..) this is probably not going to be such a common use case - that increased size is probably too much cost for little gain. Robin Burchell mob: +447702671419 msn: m...@viroteck.net irc: w00t @ irc.freenode.net twr: http://twitter.com/w00teh ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
En/na Kimmo Jukarainen ha escrit: But the first one. What package provides libnautilus-extension.so.1? $ urpmq --whatprovides libnautilus-extension.so.1 libnautilus1 Or libevview.so.1? $ urpmq --whatprovides libevview.so.1 libevince1 These are examples from mandriva, not from moblin, but it's just to show that the different between both package formats is irrelevant. What makes a difference is the repositories infrastructure and the tools around them to solve dependencies. And even if I find out what package has these specific files, is there any version dependencies? If it's needed it can be specified in the spec file [] I know that rpm allows you to specify the package names as dependencies. It can even be seen on the Moblin package above. But, as this requires some (quite minimal) effort from the packager to do so, most packagers seem to be lazy and use only the automatic dependencies generated from the file names of the used libraries. With deb packages this problem can not occur. Unless you forget a dependency and your package won't work once installed? Bye -- Luca ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: MeeGo
I want to thank everyone for their comments about RPM on the N900. It took a little bit of work, and the version I have running right now is a kludge, but I am now running RPM on my N900. See Maemo, Moblin, MeeGo and running RPMs on the #N900 http://www.orient-lodge.com/node/3970 As I note in the blog post, I'm agnostic about packaging systems and their distribution systems. I like to have multiple options, and if I can install RPMs and DEBs on my N900, great. If I can use both YUM and APT, great. If I can download packages from Nokia, Intel and third parties great. Aldon ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
En/na Aldon Hynes ha escrit: I want to thank everyone for their comments about RPM on the N900. It took a little bit of work, and the version I have running right now is a kludge, but I am now running RPM on my N900. See Maemo, Moblin, MeeGo and running RPMs on the #N900 http://www.orient-lodge.com/node/3970 Beware, though. if you mix'n'match packages from the two systems you're asking for trouble: they don't share the same database of installed packages/files, so it's easy to break the system (say, by installing both a deb and an rpm with the same base library). If you try the fedora image in a chroot there should be no problem. Bye -- Luca ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: FatELF Re: rpm vs. deb and universal binaries/packages
On Wed, Feb 17, 2010 at 9:37 PM, Robin Burchell virot...@viroteck.netwrote: On Wed, Feb 17, 2010 at 1:34 PM, Christopher Intemann intem...@gmail.com wrote: Well I just find it nice to download a single software package, e.g. on the Nokia Booklet running MeeGo, and then later copy the same package to the N900 (which is also running MeeGo) and run it there. To make that possible, there either has to be a Booklet based on ARM architecture, an rpm carrying two platform specific versions of the software (e.g. ARM and Intel) or something like fatelf... Cheers, Chris The thing is, as the note of FatELF says themselves, that it will require more space (to download store), meaning you're pretty much no better off than having downloaded it twice in the first place. And again, considering that (for the *end user*, not people on this list..) this is probably not going to be such a common use case - that increased size is probably too much cost for little gain. that is what apple do in their universal binary format. it benefits for end-user who do not know detail what their device running on arm or x86. for the hacker want to reduce size, they can strip it to normal architecture-dependent binary too. Robin Burchell mob: +447702671419 msn: m...@viroteck.net irc: w00t @ irc.freenode.net twr: http://twitter.com/w00teh ___ 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: FatELF Re: rpm vs. deb and universal binaries/packages
On Wed, Feb 17, 2010 at 16:07, Shuduo Sang sangshu...@gmail.com wrote: that is what apple do in their universal binary format. it benefits for end-user who do not know detail what their device running on arm or x86. for the hacker want to reduce size, they can strip it to normal architecture-dependent binary too. One thing we learnt in the Maemo community many years ago - and are still trying to get across occasionally - is that installing random software from a .deb (or .rpm) file isn't a good way to build a cohesive and reliable platform. FatELF or some new extensions to an existing packaging format would be wonderful if having users install random binaries from random locations on the Internet was a useful requirement. What's the use case? Why can't said user get content from an architecture aware repository/app store? Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: FatELF Re: rpm vs. deb and universal binaries/packages
Andrew Flegg wrote: FatELF or some new extensions to an existing packaging format would be wonderful if having users install random binaries from random locations on the Internet was a useful requirement. ie virus heaven I have to agree wholeheartedly. FatELF is totally inappropriate for Meego/Maemo (and IMHO most Linux distros). I'd say thanks for suggesting it, now let it die :) David -- Don't worry, you'll be fine; I saw it work in a cartoon once... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo-Mailinglist Merge (MMM)
2010/2/16 Yves-Alexis Perez cor...@debian.org On 15/02/2010 18:42, Andre Klapper wrote: Am Montag, den 15.02.2010, 18:25 +0100 schrieb Max: both mailinglists will be disabled, and merged into the megoo mailinglist Right? :-P No? :-P When? ! *If* it happens: When it's time to do so. Maemo and Moblin both coexist right now and there is no need to pollute each project with questions specific to the other platform respectively. There's a Meego list at http://lists.meego.com/listinfo/meego-dev Just unsubcribed it. Very bad SNR at the moment. -Timo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Invoking fremantle symbol menu
Hi, I'm looking for a way to show freemantle sym menu without using hildon text widgets. I'd like to show it in an application that does not use GTK/Hildon as widget toolkit. Is there a way to do this? Regards, Peter Tworek signature.asc Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
Most of the thread about MeeGo seems to be about deb vs rpm and how to install rpms on the N900. This is kind of mind boggling. The real question is, does Nokia have a strategy ? Is it selling the mobiles division to Intel ? Who knows. Nokia had Maemo5 which was 6 months away from being a product worthy system. Nokia promptly killed all interest in maemo5 by announcing it would only be released on an expensive toy (which I bought) and they actually only cared about maemo6 which was going to be ReallyGood. This set them back a good 9 to 12 months. Maemo6 release, in my opinion, was going to be a disaster. The first release would be worse in quality than the first of maemo5. The whole maemoQt vs symbianQt was not going to be pretty, confusing symbian developers and annoying everybody else. Now, Nokia traded promises of a product by promises of another product which is just farther away down the line. What platforms will it run on ? Does Nokia have arm kernel people ? Don't think so, but I dunno intel has loads of x86 kernel people. The whole Qt run everywhere pipe dream is just laughable. This is surely a great deal for Intel. They had a nice product that didn't take on the netbook market and they're bringing Nokia on board with all the mobile expertise. What's in it for Nokia ? Another 16 months of S60v5 or Symbian^3 phones. Honestly, I'll won't even bother with MeeGo 'till I see products and a decent roadmap. Meanwhile Nokia must just change it's mind, buy some GUI toolkit in Java and decide that's the way to go, go back to Symbian or just fold. Nobody knows. -- Carlos Morgado ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: MeeGo
On mer., 2010-02-17 at 22:49 +, Carlos Morgado wrote: Honestly, I'll won't even bother with MeeGo 'till I see products and a decent roadmap. Meanwhile Nokia must just change it's mind, buy some GUI toolkit in Java and decide that's the way to go, go back to Symbian or just fold. Nobody knows. You might have missed the part where the first Meego phone won't be a Nokia. Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
