Re: extras-testing: qt promotion?
My package shows up, though it is not in alphabetical order. - ianaré sévi 2010/5/29 Felipe Crochik fel...@crochik.com: Was the “hold” on qt applications promoted to testing lifted? I have updated two qt packages (macuco2, qtwol) on 2010-05-26 to use the official qt packages on PR1.2 but they still don’t show on the “Repository QA queue”. I assume they would show on: http://maemo.org/packages/repository/qa/fremantle_extras-testing/?org_openpsa_qbpager_packages_in_repo_page=4 among the other packages uploaded around the same time. Did I misunderstand the process? Thanks, Felipe ___ 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: Non-experimental QT versioning in Autobuilder (was: QT Packages, Repositories and PR1.2)
If there was a way we could explicitly tell the autobuilder to build for 4.5 or 4.6 that would be nice. Something in the deb config file for example. I've tried various ways but eventually gave up. As I've stated before my app builds and runs fine on qt 4.5 (madde) and 4.6 (qt creator). I realize not every app is so simple, since mine is more of a learning experience. There would be unforeseen problems in trying to determine this automagically. However the dev should be able to specify what to build for. - ianaré sévi 2010/5/24 Javier S. Pedro ma...@javispedro.com: Attila Csipa wrote: A single #ifdef can break such a setup, and these things might not be apparent at first (as some of the changes involve property names and values, so might even compile with the wrong version, but will simply not work as desired - the most common case exhibiting this problem IMO being finger scrolling, for example). You mean a #define being X in 4.5 and Y in 4.6, with X != Y? This is probably the cause for the missing guarantees in current Maemo Qt versions ABI compatibility. As for runtime stuff (for ex. a flag that does nothing in 4.5 but is implemented in 4.6) packager would need to add forced depedencies on 4.6 if he does not want 4.5 users to install the package (much like the current problem I have with certain hildon-desktop atoms only implemented in PR1.1/PR1.2 but the package being marked as PR1.0 compatible by autobuilder -- because of course atom names are not symbols). Javier. ___ 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: QT Packages, Repositories and PR1.2
Le 22 mai 2010 06:15, Benoît HERVIER kher...@khertan.net a écrit : I'll wait a little longer for this to get resolved, but if it takes too long I just might ebay my n900 and go Android. You can also compile it yourself and create your own repository ... easier to manage, and do the trick ... and switch back to the maemo repository again when everythings will be fixed. I've already made packages available through the garage, but there are several problems with doing this : * No way to promote packages past extras-devel. * Asking non-technical users to start adding repos should be discouraged due to security and stability issues. Having a community reviewed repo is a great thing, if it actually worked as intended. * I don't want users to have to look through the web to install an app, it should be listed in the phone's manager. * Fragmenting apps is a sure way to lose out against iPhone and Android which do have centralized app managers. Granted, deployment is not stopped, but going out of our way as developers to also be package managers is a little silly IMO. Nokia's expertise as a hardware maker but not a software publisher has been showing itself lately ... - ianaré sévi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QT Packages, Repositories and PR1.2
This whole thing has been horrible from the start. I was happily coding, learning to use Qt in a mobile environment, and then the autobuilder got switched to a version NO ONE has on their phone. I can build my app locally and it will run great on my n900, but as soon as I download it from extras-devel, it seg faults. So I thought I would wait until PR 1.2 was released, which was supposed to be '2 weeks' ... now it's not coming until November ?!?! It's obviously not working right (there are several apps that I use that are un-updatable or now crash), is causing a lot of bad press, frustrating developers, and making users confused and angry. Please put up a wiki page detailing EXACTLY what needs to be done for a package to work properly using the new autobuilder, if that is even possible. Otherwise -- please, please please just put it back the way it was. Just make it work. I'll wait a little longer for this to get resolved, but if it takes too long I just might ebay my n900 and go Android. Sorry for the rant but sometimes it feels good to get things off your chest ! Cheers, - ianaré sévi 2010/5/21 Attila Csipa ma...@csipa.in.rs: On Friday 21 May 2010 01:42:43 you wrote: 1. As today what a developer needs to do to get an application that uses qt to the end user? Is there a way to tell the autobuilder to compile against the 4.5 qt and make the package only depend on it? In theory you just depend on the proper version of libqt4-dev, but it's tricky as you might indirectly reference libs that are also newer in the SDK/new PR so end up with a 4.6 dependency (or broken build), see below... 2. What is the point of the (not so few) qt applications on the repository that were compiled against the qt4-core (4.6)? Unless pr1.2 will have a qt that is binary compatible to the libs on the autobuilder right now these packages will be completely useless, right? I thought the point of committing packages using qt4-core (4.6) now was to have them ready for day one when pr 1.2. gets out. Most of the applications got compiled for Qt4.6 'by accident', in terms that they do not really depend on or need 4.6 (nor did the original author WANT that specific version), but with current SDK setup they end up being linked against 4.6 anyway. This is why in my previous post I said this is not strictly a PR1.1 problem, a similar situation might arise with other packages if not managed correctly. 3. The qt applications not using qt4-maemo5 are moved to testing. How are they being tested right now? They can't be tested on the pr1.1, because they are compiled against qt 4.6. Are they not being tested at all (everything is at halt); or they are being tested by people that have pre release pr1.2; or are they being tested using scratchbox environment? AFAIK it's halted. Considering PR1.2 uses a separate repo, it makes no sense to promote them (yet) anyway. I would not consider prerelease 1.2 as a valid platform for community QA purposes. Thanks for taking the time to answer me. It has been very interesting and illuminating Hate to be the bearer of bad news :( What we managed to agree for the PR1.2 release is that development releases starting with PR1.2 will not be called libqt4-maemo5 as it's not that obvious that it's *really* just a version for testing, prone to breakage and not necessarily the exact one that will end up in the next PR. Future releases will sport the 'experimental' moniker (f.e. libqt4-experimental, python-qt4-experimental) so it's more clear that it (and stuff depending on it) are not meant to be promoted to end users. Not ideal, but hopefully will reduce confusion until a better solution is found that is acceptable for both Nokia and the community. 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: Noob question re Qt Application structure
I second that opinion. Subclassing by functionality is definitely good
for a single app, but if you need to have the two parts running at
different times a daemon app and a GUI app is the way to go.
Another option you could use to interact with your two apps is through
dbus itself, ince you will already be using that kind of code.
- ianaré sévi
2010/5/7 Ram Kurvakat rkma...@gmx.com:
just my 2 pence worth.
you should perhaps try to make 2 different apps for it.
1 which runs as a daemon and invoked on startup using an upstart script.
and the other a GUI based app , that can interact with your daemon, via
files, sockets, any which way.
cheers
Ram
- Original Message -
From: Scifi Guy
Sent: 05/07/10 03:26 PM
To: maemo-developers@maemo.org
Subject: Noob question re Qt Application structure
Hi All,
I am developing a Qt4.6 based application that monitors outgoing
international calls (by connecting to relevant DBUS signals) and routes
them via a calling card number. I have developed a configuration UI widget
(QWidget subclass) to enable/disable such routing.
The problem is that the UI widget code and DBUS slots code are all in the
same class. If I launch the application, the UI widget is shown.
This is the code in my main.cpp.
#include QtGui/QApplication
#include eventmonitor.h
#include QDebug
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
EventMonitor w;
w.show();
return a.exec();
}
EventMonitor is a QWidget subclass which also has functions to connect to
DBUS signals. My aim is to separate the functionality into two different
classes. The class with DBus slots should be running as a daemon which is
invoked on startup.
The class with QWidget (config screen) should be invoked when user launches
the app from the applications menu. Think on the lines of AutoDisconnect.
What is the best way to achieve this? Let me know if you want me to post
more code.
Thanks Regards,
Sudheer
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
Get started.
___
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: Maintenance break: updating auto-builder to resolve dependency issues
How will we know if a particular package has been rebuilt ? Also, will all packages be affected, or will there be a list somewhere of which packages are rebuilt. Thanks, - ianaré sévi 2010/4/16 Niels Breet ni...@maemo.org: Hi all, The fremantle autobuilder will be switched to use the debian-squeeze devkit in order to resolve as much SDK backwards compatibility issues as possible. After the swich, rebuilt packages will be imported to fremantle extras-devel and the repository will be reindexed. There will be a maintenance outage for about one hour and will start now. -- Niels Breet maemo.org webmaster ___ 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: Maintenance break: updating auto-builder to resolve dependency issues
Thanks, I wasn't sure if this was the same as list as mentioned in another thread. I can confirm that this has fixed those packages on my 1.1 device. My package (tipqalc) still has broken dependencies, how can I get it rebuilt ? Or will all packages eventually be rebuilt ? Many thanks, - ianaré sévi 2010/4/16 Niels Breet ni...@maemo.org: How will we know if a particular package has been rebuilt ? Also, will all packages be affected, or will there be a list somewhere of which packages are rebuilt. These builds were done: https://garage.maemo.org/builder/.fremantletest/ Those have been rebuilt and imported. Thanks, - ianaré sévi -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: missing dependencies on autobuilder
Autobuilder isn't working right : it's building for Maemo PR 1.2, but our devices are on 1.1. We have no idea when PR 1.2 will be released. You can try explicitly specifying the dependencies in your control file, it might work or might not. I kinda sorta had it working but gave up and simply posted a deb file built on my machine to my project's garage page. - ianaré sévi 2010/4/14 Aapo Rantalainen aapo.rantalai...@gmail.com: Hi, I'm maintainer of this package: http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/jammo/0.5.0/ There are Warning: This package has missing dependencies! And missing are: libgstreamer0.10-0 (= 0.10.25) mp-fremantle-generic-pr (= 3.2010.02-8) My application is heavily using audio processing and it is NOT working on older firmware (from year 2009). I try to be sure, that user has new firmware and new gstreamer (autobuilder has 0.10.23). 1) Is this 'Warning' stopper to promote it to extras-testing (or why I don't see promote button on package page, even I have logged in) ? 2) Why autobuilder is not using new (same) versions of libgstreamer0.10-0 or mp-fremantle-generic-pr than my N900-device? 3) Can I make this dependency check in some other way? (thus they are runtime dependencies, not compile time) -Aapo Rantalainen ___ 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: Squeeze devkit to be installed to autobuilder
First off, a big thanks for this effort. My package (soon to be two ;-) uses Qt, so I'm not sure how much this will help me personally, it is definitely an important step in the right direction. For those packages that are OK, importing them automatically is fine. However for those that do have problems, the developer should be able to control when it gets moved. I think the major lesson learned here is to try hard not to replace a working package with a broken one. It would be unwise to do the same thing again. Scenarios include abandoned packages, long developer response times, etc ... - ianaré sévi 2010/4/14 Niels Breet ni...@maemo.org: Hello all, Hi, As part of the plan to fix the PR1.2 SDK dependency issues in the autobuilder [1], we plan to upgrade the Debian devkit in the Fremantle autobuilder to the Squeeze version [2] (from the current etch one), and start using improved shlibdeps [3] (a.k.a. .symbols files) to version dependencies on a much more granular basis (minimal required version of libraries will be calculated per symbol instead of per library). We plan to ship .symbols files for most of the SDK libraries [4]. This means that packages built in the PR1.2 SDK using no PR1.2-introduced functions will work on a PR1.1 device and even on a 1.0 device. As part of this task we need to decide with the 'broken' or affected packages which have been built on the PR1.2 SDK and have gotten PR1.2 dependencies. We can automatically import all rebuilt packages into extras-devel or we can decide to let developers re-submit their packages after the builder has been switched to the new setup. Thoughts? -- Javier -- Niels Breet maemo.org webmaster ___ 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: Autobuilder - roadrunner don't go extras-devel
I'm having the same problem with a package I uploaded last night. - ianaré sévi 2010/4/10 David Hautbois david.hautb...@free.fr: Hello Yesterday, I'uploaded roadrunnner 0.1.0-18. Today, I'm still waiting for it goes to extras-devel : http://maemo.org/packages/view/roadrunner/ Do I forget something ? Thanks. David. ___ 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: Dependency problems after PR 1.2 update to extras builder
Yes, that's what I ended up doing, since I'm building using MADDE it's
qt 4.5 anyway. Package was built OK by the extras build server and I
was able to install the package on the device. However it is unstable
and seems to crash for no apparent reason. I was able to install the
386 version on scratchbox and that runs OK. Weird.
The other weird thing is that on the device I saw there were some
updates installable through command line that installed the 4.6
packages but this doesn't look like it does anything.
- ianaré sévi
2010/3/30 Marius Vollmer marius.voll...@nokia.com:
ext Marcin Juszkiewicz mar...@juszkiewicz.com.pl writes:
Is there a way of specifiying to use the older packages?
No such option.
The problem are the automatic generated dependencies, if I understand
things right.
I.e., you build against libqt4-core version 4.6.2~git20100224, and the
resulting package ends up having this:
Depends: libqt4-core (= 4.6.2~git20100224)
(Among others, of course.) This originates from this in your source
package:
Depends: ${shlibs:Depends}
The text libqt4-core (= 4.6.2~git20100224) comes from the libqt4-core
package itself that is installed while building. But: You can overwrite
it if you know better what dependency you want to have.
You do this by putting a debian/shlibs.local file into your source
package. It might look like this:
libQtCore 4 libqt4-core (= WHATEVER-YOU-WANT)
ETC...
Of course, this only changes the text in the Depends field of your
package. You must make sure that your program actually runs with the
older version of Qt even when it has been compiled against the newer
version.
___
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: Dependency problems after PR 1.2 update to extras builder
Thanks for the clarifications. I can certainly sympathize with your situation, but in the future it might be better to hold off on updating the autobuilder until you get a firm release date from Nokia. The present situation would be much better if we knew how long we had to wait until our packages are installable again. - ianaré sévi 2010/3/30 Niels Breet ni...@maemo.org: On Tue, March 30, 2010 15:56, Andrew Flegg wrote: On Mon, Mar 29, 2010 at 15:37, ianaré sévi ian...@gmail.com wrote: After making some updates to my package and putting it up on extras-devel, it won't update on the device from the repository. I was able to install it on scratchbox (both prior to and after updating the SDK). So, AIUI (and others did too), the autobuilder would be upgraded to PR1.2's SDK and start publishing to fremantle-1.2 (rather than the current fremantle). It will for Extras, but not for extras-devel and testing. However, yesterday on IRC, there were some complaints that the auto-generated components for things in fremantle extras-devel had incorrect dependencies: It depends on your definition of incorrect ;) They are correct for running on PR1.2. I thought the fremantle extras-devel should now be fixed, so how are things with incorrect dependencies getting in? Niels, could it'd've been a race condition during the switch; or is it a bug; or are we corrupting fremantle extras-devel? Some time ago, when I noticed the issues with upcoming PR1.2 and saw the trouble with PR1.1, I tried to find a solution which could be implemented on a short term. The first priority was to protect the repository which is enabled on every device and is used by end-users. Extras will have a fremantle and a fremantle-1.2 repository, so old device users won't see the new dependencies and PR1.2 users will see the correct dependencies. Then it became clear that the PR1.2 SDK would be available before the firmware release. This is something developers asked for a lot and the idea was to give them the opportunity to get their applications ready for PR1.2 before it actually shipped. By enabling it on the builder, developers can get their updated app in extras-devel and check if everything builds against the PR1.2 SDK. The issue people see is that they are then trying to install the PR1.2 built application on a pre PR1.2 device. This might or might not work, depending on which dependencies are specified. In the short time there was between the time I knew about the PR1.2 consequences and the actual release of the SDK, there was not enough time to develop a cleaner solution for extras-devel and extras-testing. Extras-devel is expected to be running against the latest and greatest and always had the disclaimer about breaking your device. I hate the fact that it now actually does prevent applications from being installed though. Creating a separate fremantle-1.2 -devel and testing QA queue would probably have given more confusion and frustration than it would prevent and would have been hard to do within the available time. So, how to on go from here from my POV: * Hope that PR1.2 will be out soon, so people can test it on their own device. * Update the Packages interface with knowledge about the PR1.2 rootfs, so promotions to testing can happen. * Encourage all people with access to PR1.2 devices to test applications from the testing QA queue on their devices and give feedback to developers, so we can get those applications in fremantle-1.2 as soon as possible. * Look at the possibility of adding a hacked libhildon package in the builder, so it generates 'correct' dependencies and applications can be installed on PR1.1 if they don't use the new livesearch api. (Probably most of them) * Discuss how we can improve this situation for the next SSU. * Make a case for Nokia to convince them to give developers early access to PR1.2 images. Trying to do the right thing, I have the feeling that it backfired. :( Thanks in advance, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is maemo.org web site down?
Same here. Package viewer (http://maemo.org/packages/) appears down too. - ianaré sévi 2010/3/29 Sascha Mäkelä sascha.mak...@gmail.com: Is it only me or is the maemo.org site down? I only get a blank page. Cheers, Sascha ___ 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
Dependency problems after PR 1.2 update to extras builder
Hi all, After making some updates to my package and putting it up on extras-devel, it won't update on the device from the repository. I was able to install it on scratchbox (both prior to and after updating the SDK). Here are the missing dependencies : libqt4-core (= 4.6.2~git20100224) libqt4-dbus (= 4.6.2~git20100224) libqt4-gui (= 4.6.2~git20100224) libqt4-xml (= 4.6.2~git20100224) How do I fix this ? Thank you, - ianaré sévi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
Please tell me you're kidding. Because now my app isn't even available in the catalogue. Is there a way of specifiying to use the older packages ? Or deleting the new build from the server ? - ianaré sévi 2010/3/29 Marcin Juszkiewicz mar...@juszkiewicz.com.pl: Dnia poniedziałek, 29 marca 2010 o 16:37:54 ianaré sévi napisał(a): After making some updates to my package and putting it up on extras-devel, it won't update on the device from the repository. I was able to install it on scratchbox (both prior to and after updating the SDK). How do I fix this ? Wait for November^Wnext firmware drop. When it will be released is unknown but it will fix your problem. I just hope that it will be before developers will start to leave this ship. Regards, -- JID: ...@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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
2010/3/29 Marcin Juszkiewicz mar...@juszkiewicz.com.pl: Dnia poniedziałek, 29 marca 2010 o 16:48:30 ianaré sévi napisał(a): Please tell me you're kidding. No, I am not kidding. It was discussed here on mailing list and announced that Extras autobuilder will be updated to PR 1.2 compatible SDK and that resulting packages will be installable only on devices owned by Nokia employed people (and some from cooperating companies). Other users (and developers) have to wait for next firmware drop (which does not have release date as usual so it can be tomorrow or in next year). I saw that discussion, but I didn't think it would actually break any new build of a previously working package. Because now my app isn't even available in the catalogue. Is there a way of specifiying to use the older packages? No such option. Downgrade SDK on your home machine and do build there. If I build on my machine can I still have it included in extras ? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
OK got it to work, I simply set the Qt dependencies to 4.5 (instead of 4.6) manually instead on relying on the builder scripts ... - ianaré sévi 2010/3/29 Dave Neary dne...@maemo.org: Hi, Marcin Juszkiewicz wrote: No, I am not kidding. It was discussed here on mailing list and announced that Extras autobuilder will be updated to PR 1.2 compatible SDK and that resulting packages will be installable only on devices owned by Nokia employed people (and some from cooperating companies). Other users (and developers) have to wait for next firmware drop (which does not have release date as usual so it can be tomorrow or in next year). Now now Marcin, that's not what was said. what was said was that software built with the PR 1.2 SDK would probably only install on devices with PR 1.2 installed. That's not the same thing. ianaré, normally all you have to do is upgrade the firmware on your N900 to PR 1.2, as I understand it. 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N900 / Media Player / Random play really random?
I haven't seen the code that controls the randomness of songs, but in a truly random sequence of numbers, repetition is to expected. Another way of putting it is that patterns naturally arise out of randomness. There had been similar discussions with the ipod when it came out. I believe that Apple has since made the random generator LESS random, by having it ignore duplicates. - ianaré sévi 2010/3/25 Frédéric Ledain frederic.led...@onmobile.com: Hi, I am using Nokia N900 with something like 1 500 mp3 in it. I am listening to random music, and I can observe that same tracks are often played. I understand this is difficult to spot concrete information, but this feeling is persistent. For instance, in 2 listening sessions (around 1 hour each), I will listen to several same tracks. One more example here: while writing these lines, I can hear a track just listened this morning (session 1 hour). Are there any other N900 users sharing this same feeling? Thanks in advance. Frederic ___ 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: N900 / Media Player / Random play really random?
The original message related to several sessions, so while the same song will not play in the same session, over several sessions there will be repeats, and/or clusters (an artist or style being played more often). Personally, I actually like this, as it gives me the illusion of the computer 'choosing' to play a certain style. But one way to avoid it would be to keep a record of which songs were played _between_ sessions, and not play them again untill all songs are played. A cool thing to do would be weigh by preference, for example a song frequently skipped would be played less often. - ianaré sévi 2010/3/25 Ben Roe b...@dataviz.com: Surely the music player should shuffle the list, not just play random tracks from it? I don't think anyone wants random duplicates in one session. Ben On 25 Mar 2010, at 18:47, ianaré sévi wrote: I haven't seen the code that controls the randomness of songs, but in a truly random sequence of numbers, repetition is to expected. Another way of putting it is that patterns naturally arise out of randomness. There had been similar discussions with the ipod when it came out. I believe that Apple has since made the random generator LESS random, by having it ignore duplicates. - ianaré sévi 2010/3/25 Frédéric Ledain frederic.led...@onmobile.com: Hi, I am using Nokia N900 with something like 1 500 mp3 in it. I am listening to random music, and I can observe that same tracks are often played. I understand this is difficult to spot concrete information, but this feeling is persistent. For instance, in 2 listening sessions (around 1 hour each), I will listen to several same tracks. One more example here: while writing these lines, I can hear a track just listened this morning (session 1 hour). Are there any other N900 users sharing this same feeling? Thanks in advance. Frederic ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Deleting Project PyGTKEditor from Garage
That's the beauty of the n900, you CAN do exactly what you're doing, and the only consequence is some disappointed devs on a mailing list (IOW - none). However, if you want to have your app included in the 'mainline', expect to suffer a little. But this goes for any large open source project. Take a look at getting an app into Debian, Ubuntu, or FreeBSD -- I have, and believe me Maemo is much much easier ! - ianaré sévi Le 24 mars 2010 13:08, Benoît HERVIER kher...@khertan.net a écrit : Why are you saying that i m trying to divide the Maemo Community ? So Maemo is as closed as Apple iThings Store ? We can t provide apps without the approbation of the community ? Uploading things to extras is a pain ... rules changes ... stupid votes ... bug in the interfaces that noone take care... fixing a bug for a package in extras could takes several weeks due to the QA Testing process ... I cannot say to user to set extras-devel repository ... there is too much package that can brick n900 device ... HAM ignore apps that are in other repository if they are already in extras !!! So what ? I m a hobbist developers, i m doing it for free ... and today it s take more time to trying to make packages available in extras than creating new apps and implementing new feature !!! Why ... you should try to found user to test your apps, answer to wrong vote, wait bugs to be fixed in the web interface, and more ! So creating my own repository is the best compromise ... Today i ve already delete my garage account as x-fade is now sure that i ll not publish anything more on extras repository ... what you want ? if you are not happy with that do not use my repository ... BUT STOP WHINNING ! But i got so many complain about creating my repository that now you win ... you know what ? Today i m writing code to create packaged python apps for android, and i ll probably stop all my maemo development ! I know that this n900 will made many damage to the community ... but i was optimist ... i was thinking more users, better for the plateforms ... failed Yes there is discussions, talk, brainstorm ... and other discussions, emails on the mailing list but ZERO actions taken. This was my first experience in an true OSS community ... but probably the last. FELICITATIONS you loose an other dev ! Your so closed mind IS DIVIDING the community ! 2010/3/24, Frank Banul frank.ba...@gmail.com: One person setting up their own repository is hardly dividing the Maemo community, IMHO. Frank On Wed, Mar 24, 2010 at 9:52 AM, Michael Cronenworth m...@cchtml.com wrote: Benoît HERVIER wrote: Once the package will be removed from extras, extras-testing, and extras-devel you will be able to install the new version from my own repository. Why are you attempting to divide the Maemo community? ___ 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 -- Benoît HERVIER, Khertan Softwares - http://khertan.net/ ___ 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: MADDE and Qt4.6
I've been developing using Qt Creator 1.3.1 (based on Qt 4.6) and using MADDE with Qt 4.5 to compile for the phone, using Ubuntu 9.10. Obviously you will need to avoid using any Qt 4.6 specific code until Meamo and MADDE are updated. So far I have not come into any problems with this though. - ianaré sévi 2010/3/12 tero.k...@nokia.com: - Original message - Hi, I know that MADDE is not official supported. I have try to use it with Qt4.6 and Qt Creator, I have used versions 1.3.80 (as in http://wiki.maemo.org/MADDE/QtCreator_integration_for_windows) and 1.3.81 and 2.0.0alpha1. Qt4.6 was taked from http://chaos.troll.no/~harald/MADDE. I have try on Linux and Windows with the same result in QtCreator: The Qt Version has no toolchain. Qt4.5.3 from MADDE works well with QTCreator (any version, any platform). Any sugestions how to make it work? My suggestion would be to wait for the next Maemo 5 update, in which Qt 4.6 will be included. And, sorry no I can't share any details of when that is. It is possible to glue 4.6 on top of the current Madde, but as far as I know it is complicated. You would need to modify the toolchain and the libraries used for cross compiling. Tero Thanks Krzysiek Attachment ATT1..txt ___ 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: N810, GPS and Java
For python there is the python-location module, described here : http://wiki.maemo.org/PyMaemo/Using_Location_API You can see one implementation here : http://maemo.org/packages/source/view/fremantle_extras-devel_free_source/healthcheck/0.5.2-4/ - ianaré sévi 2010/3/5 Demetris demet...@ece.neu.edu: Hi Frank, actually I am able to run PhoneME Java on it but you are right it, I am on my own on that. I did manage to dig out some Python info on accessing the GPS device but not much yet - I will keep at it. Thanks Frank Banul wrote: Hi, Java isn't really supported on the N810, so you'll have to go another route. Frank On Fri, Mar 5, 2010 at 9:26 AM, Demetris demet...@ece.neu.edu wrote: Hi all, is there a Java API available for accessing the GPS device on the N810? I have a feeling asking for a Java API may be a tough one, so in such a case, a C? Any other type? I am pretty much interested on retrieving the appropriate data for my current location that I can feed into Google Maps (or an OS2008 map app) or a distance app for giving me the closest pts of interest to my location. Thanks ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
info on creating widgets using Qt
Can someone point me to some documentation on building widgets using Qt for Maemo 5 (and later) ? I've found some stuff for python, but not much. The docs are not very organized, so I am probably just not looking in the right place. Any help would be appreciated. Thanks ! - ianaré sévi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: info on creating widgets using Qt
Thanks for the help. I've looked through these sites and while they are very helpful, they don't really address widgets specifically. However I now realize my original post was a little confusing, I was referring to _desktop_ widgets, like OMweather, not the general GUI widgets. - ianaré sévi 2010/3/5 Hartti Suomela har...@gmail.com: Have you been here? http://qt.nokia.com/products/platform/maemo http://labs.trolltech.com/blogs/?p=1480 Check also the Qt reference for maemo 5 http://qt.nokia.com/doc/qt-maemo-4.6/ Do these help or are you looking some other kind of documentation? Hartti On Fri, Mar 5, 2010 at 8:37 AM, ianaré sévi ian...@gmail.com wrote: Can someone point me to some documentation on building widgets using Qt for Maemo 5 (and later) ? I've found some stuff for python, but not much. The docs are not very organized, so I am probably just not looking in the right place. Any help would be appreciated. Thanks ! - ianaré sévi ___ 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: info on creating widgets using Qt
Yes, that's exactly what I wanted. I thought this stuff would be on maemo's wiki, not on the Qt site. Thanks much ! - ianaré sévi 2010/3/5 Hartti Suomela har...@gmail.com: Does this then help? http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ On Fri, Mar 5, 2010 at 10:33 AM, ianaré sévi ian...@gmail.com wrote: Thanks for the help. I've looked through these sites and while they are very helpful, they don't really address widgets specifically. However I now realize my original post was a little confusing, I was referring to _desktop_ widgets, like OMweather, not the general GUI widgets. - ianaré sévi 2010/3/5 Hartti Suomela har...@gmail.com: Have you been here? http://qt.nokia.com/products/platform/maemo http://labs.trolltech.com/blogs/?p=1480 Check also the Qt reference for maemo 5 http://qt.nokia.com/doc/qt-maemo-4.6/ Do these help or are you looking some other kind of documentation? Hartti On Fri, Mar 5, 2010 at 8:37 AM, ianaré sévi ian...@gmail.com wrote: Can someone point me to some documentation on building widgets using Qt for Maemo 5 (and later) ? I've found some stuff for python, but not much. The docs are not very organized, so I am probably just not looking in the right place. Any help would be appreciated. Thanks ! - ianaré sévi ___ 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: qmake
Thanks much, that worked !
- ianaré sévi
2010/2/25 daniel wilms daniel.wi...@nokia.com:
ext ianaré sévi wrote:
Thanks for your response.
I'm using the following line in my control file :
Depends: ${shlibs:Depends}, ${misc:Depends}
Should I explicitly add it there ?
No, you have to add it here:
Build-Depends: debhelper (= 5), libqt4-dev
Daniel
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
qmake
I'm having problems building my package using qmake on extra-devels. make[1]: Entering directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/tipqalc-0.3.0/src' make[1]: *** No rule to make target `/usr/share/qt4/mkspecs/linux-g++/qmake.conf', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/tipqalc-0.3.0/src' Any suggestions? Thanks. - ianaré sévi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
