Re: browserd (aka tablet-browser-daemon) is now open source
On Friday, November 04, 2011 06:52:45 PM Jonathan Wilson wrote: I have taken the old browserd source code at http://vcs.maemo.org/svn/browser/client-server/trunk/server/ and come up with a set of code that is functionally identical to the N900 browserd. ... Wow! Thank you! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using a library package in Maemo sysroot
[Replying to both Christian Kandeler and Tomi Ollila in this message.] On Wednesday, August 31, 2011 05:28:56 AM Tomi Ollila wrote: On Wed, 31 Aug 2011 10:00:48 +0200, Christian Kandeler christian.kande...@nokia.com wrote: On Tue, 2011-08-30 at 16:07 -0400, ext David Talmage wrote: I'm having trouble deploying an application to my N900. When QtCreator builds the application package, dpkg-shlibdeps claims that it cannot find the dependency information for one library. This is what I need help fixing. The error message is dpkg-shlibdeps: failure: no dependency information found for /home/talmage/QtSDK-1.1/Maemo/4.6.2/sysroots/fremantle-arm-sysroot-20. 2010.36-2-slim/opt/usr/lib/libqcontactchooserdialog.so.1 (used by debian/panicbutton/opt/usr/bin/panicbutton). I made the library myself. It is on the phone and in my Maemo sysroot. QtCreator put it in the sysroot for me using this additional deployment step: mad-admin xdpkg --install libqcontactchooserdialog_1_0_0_armel.deb I copied the libqcontactchooserdialog.shlibs file from my phone into var/lib/dpkg/info in the sysroot. That changed nothing. Are you saying that mad-admin xdpkg does not install the shlibs file into the sysroot? That sounds like a bug to me. Anyway, could it be that the shlibs file is somehow not containing the correct information? Have you checked its contents and compared with what the man page for deb-shlibs says? Yes, the version of mad-admin I had did not install the shlibs file into the sysroot. According to the deb-shlibs man page, libqcontactchooserdialog.shlibs should look like this: libqcontactchooserdialog 1 libqcontactchooserdialog (= 1.0-0) Instead, mine looks like this: libqcontactchooserdialog 1 libqcontactchooserdialog In other words, it's missing the version number in the dependencies field. After I followed Tomi's directions, I have $SYSROOT/madde_xpkgs/libqcontactchooserdialog.shlibs. This is new, I think. There isn't one in $SYSROOT/var/lib/dpkg/info. The reason is that that such an old MADDE does not support checking those dependencies in xdpkg -installed packages: ... Tomi, the new dpkg-shlibdeps and xdpkg files didn't fix the problem. I get the same output as before when deploying my application. Could this be related to the location of my library? It's in $SYSROOT/opt/usr/lib instead of $SYSROOT/usr/lib. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtCreator, libraries, and multiple platforms
On Wednesday, August 03, 2011 03:03:11 PM David Talmage wrote: I need help making QtCreator build an application and a library for Maemo, Symbian (using the remote compiler), and the simulator. I've been all over the documentation, the forum on Qt Developer Network, and Google. I can't find an example that does what I need. I have a library (lib) and an application (app). Each one is a QtCreator project. I can build them individually but I can't link app with liblib.so. Whatever I use has to work with maemo.org's autobuilder and Nokia's remote compiler for Symbian. ... Thanks to the help I've received from Cristian Kandeler, Ville M Vainio, Daniil Ivanov, and Roman Morawek, I have a library project and an application project. The application project depends on the library project. I can deploy both of them to my N900 phone. I did not use a subdirs project as suggested. I created a library project and an app project. I manually copied the library and its header files to my Maemo sysroot. In order to make the loader look for the library in /opt/usr/lib, I added some linker flags to the qmake variable QMAKE_LFLAGS in the maemo5 section of the app project file: QMAKE_LFLAGS += '-Wl,-rpath,/opt/usr/lib' I think that's everything I did. Then I went and broke things. That's a story for another thread. Thank you all for helping me. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Using a library package in Maemo sysroot
I'm having trouble deploying an application to my N900. When QtCreator builds the application package, dpkg-shlibdeps claims that it cannot find the dependency information for one library. This is what I need help fixing. The error message is dpkg-shlibdeps: failure: no dependency information found for /home/talmage/QtSDK-1.1/Maemo/4.6.2/sysroots/fremantle-arm- sysroot-20.2010.36-2-slim/opt/usr/lib/libqcontactchooserdialog.so.1 (used by debian/panicbutton/opt/usr/bin/panicbutton). I made the library myself. It is on the phone and in my Maemo sysroot. QtCreator put it in the sysroot for me using this additional deployment step: mad-admin xdpkg --install libqcontactchooserdialog_1_0_0_armel.deb I copied the libqcontactchooserdialog.shlibs file from my phone into var/lib/dpkg/info in the sysroot. That changed nothing. I don't know what else I can do. I've looked hard for a definitive answer and have found nothing. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtCreator, libraries, and multiple platforms
Thanks to Danil, Ville, and Christian for taking the time to answer my call for help. On Thursday, August 04, 2011 06:16:16 AM Daniil Ivanov wrote: I agree that three project files are the way to go: ... This is how you declare your library for your application http://doc.qt.nokia.com/latest/qmake-project-files.html#declaring-other-li braries I got about that far. More below. To answer Ville's question about the need for a separate library: I refactored my application into a library that other applications can use and an application that uses the library. I have at least one more application in mind that will use this library. For the curious, it's a home-grown dialog for choosing contacts. I wrote it last year because the native Maemo contacts dialog didn't support pre-selecting some contacts. (The documentation said it did but I couldn't make it work at all.) To answer Christian's question about linking: By can't link I mean that the linker can't find my library, so it complains about undefined symbols. I have a directory structure like this: N900/app N900/app-uberproject N900/lib The contain, respectively, the app, the subdirs project, and the library. I'm building for Maemo, Harmattan, Simulator, and Remote Compiler. In short, everything but Desktop. When I build for Simulator, I get directories N900/app-build-simulator N900/app-uberproject-build-simulator N900/lib-build-simulator The next challenge is to teach app.pro how to find the library for the build platform, simulator in the example above. It looks like some hackery-pokery with replace() will do the job. I was hoping that QMake would Do The Right Thing for me. After that, my challenge is to install liblib.so in the simulator so that app can load it. That's just the usual packaging task, right? Dave On Thu, Aug 4, 2011 at 12:48 PM, Ville M. Vainio vivai...@gmail.com wrote: Do you have a particular reason for the requirement (like license) to have a separate library, instead of just having one monolithic application? On Wed, Aug 3, 2011 at 10:03 PM, David Talmage talm...@acm.org wrote: I need help making QtCreator build an application and a library for Maemo, Symbian (using the remote compiler), and the simulator. I've been all over the documentation, the forum on Qt Developer Network, and Google. I can't find an example that does what I need. I have a library (lib) and an application (app). Each one is a QtCreator project. I can build them individually but I can't link app with liblib.so. Whatever I use has to work with maemo.org's autobuilder and Nokia's remote compiler for Symbian. As a first pass, it would help if there is an environment variable I can reference in app.pro like $$OUT_PWD that contains the name of the build directory for lib. Then linking might work. I can hack something together with qmake's replace(), like replace($$OUT_PWD, app, lib) and that might work as long as app/ and lib/ were in the same directory. I don't know how well it would port or whether it would continue to work when I install app and liblib.so on the phones. Dave ... ... ... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtCreator, libraries, and multiple platforms
On Friday, August 05, 2011 05:38:40 PM Ville M. Vainio wrote: So I guessed correctly; your rationale for using a library is wrong ;-). You are introducing a bunch of deployment headaches for the sake You're right, Ville, I am introducing deployment headaches. Those headaches shouldn't be there in this day and age. I have no idea if or how this will build on maemo.org's autobuilder or Nokia's remote compiler for Symbian. of having a reusable unit, which is not in fact reused by other applications. In general, libraries should only be introduced when I am writing another application that will link with the library. At least one other developer was interested in using my library last year. I failed to release the code. I don't know if he's still interested. ... You should just link all the code statically with your main application to keep things simple. I agree that static linking would make this simple. However, I'm targeting devices with limited memory (e.g. N900, N8, N9). Dynamic linking is better in this context. David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtCreator, libraries, and multiple platforms
Thanks, Daniil! This is nearly working. I structured my directories as you advised. Everything builds and the app links with lib. There is an executable, oh-my/app/app. Then some task called copydeploymentfolders is invoked and it fails. The output is: Copying application data... cp: cannot overwrite non-directory `/home/talmage/N900/oh-my-build- simulator/app/app' with directory `/home/talmage/N900/oh-my/app/' make[1]: *** [copydeploymentfolders] Error 1 I can't imagine qmake thinks it's doing. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
QtCreator, libraries, and multiple platforms
I need help making QtCreator build an application and a library for Maemo, Symbian (using the remote compiler), and the simulator. I've been all over the documentation, the forum on Qt Developer Network, and Google. I can't find an example that does what I need. I have a library (lib) and an application (app). Each one is a QtCreator project. I can build them individually but I can't link app with liblib.so. Whatever I use has to work with maemo.org's autobuilder and Nokia's remote compiler for Symbian. As a first pass, it would help if there is an environment variable I can reference in app.pro like $$OUT_PWD that contains the name of the build directory for lib. Then linking might work. I can hack something together with qmake's replace(), like replace($$OUT_PWD, app, lib) and that might work as long as app/ and lib/ were in the same directory. I don't know how well it would port or whether it would continue to work when I install app and liblib.so on the phones. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
modest/tinymail imap idle test available
I've put together a set of tinymail/modest patches to support imap idle mode. That's where the server can notify the client of mail changes in the currently selected mailbox (this also selects the inbox if you aren't in another folder). See bug 3888 for more history. IMAP-IDLE https://bugs.maemo.org/show_bug.cgi?id=3888 In short tinymail supports idle, but turns it into a polling operation where a thread would wake up every second or two and check for more data. Nokia has it disabled as shipped in the N900, due to the battery drain. This rather large set of changes adds proper blocking to idle based on a three year old patch, and hooks up the notifications for when idle has new mail. With this change, idle only makes four system calls every time the server sends an idle keep alive. For me that's 4.5 minutes and is set that way because of T-Mobile IPv4 NAT's 5 minute timeout before it kills the connection. I don't think you can take any less power and still get e-mail. That said it's a large set of patches and could use some more testing. To give it a try, compile and run both tinymail and modest, then try e-mailing yourself. Tinymail doesn't expose an idle enable or disable, so it's either compiled in and enabled or disabled at compile time, so there isn't any configuration changes to start using it. https://gitorious.org/~dfries/community-ssu/dfriess-tinymail/commits/force_online https://gitorious.org/~dfries/community-ssu/dfriess-community_ssu_modest/commits/idle_work Unfortunately tinymail's current multithreaded lock system is prone to deadlocks, and while I've found and fixed a bunch it's likely there are more lurking, if you find any, patches are welcome. I'll only try to debug reports which include a set of reproducible steps. The majority of the deadlocks are related to connecting and getting disconnected and being online but having the server down. They result is the account being stuck in refreshing and requires killing the modest executables. -- David Fries da...@fries.netPGP pub CB1EE8F0 http://fries.net/~david/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Details on the information required to replace the tklock (touchscreen/key lock) systemui plugin
On 5 July 2011 13:18, Jonathan Wilson jfwf...@tpgi.com.au wrote: [snip] The SYSTEMUI_TKLOCK_OPEN_REQ handler gets passed a uint argument for the lockscreen mode, can be TKLOCK_ENABLE, TKLOCK_ONEINPUT or TKLOCK_ENABLE_VISUAL. TKLOCK_ONEINPUT is for the blank screen lock mode (called event eater mode in the code) and TKLOCK_ENABLE_VISUAL is for the slide to unlock screen. Not sure what TKLOCK_ENABLE is for exactly. TKLOCK_ENABLE was used for the tklock in earlier versions of Maemo (where you'd press the power button followed by center button to unlock). The second parameter is a boolean argument labeled silent by the code. The code says true = disable infoprints, false = enable infoprints. The third parameter is a flag that seems to indicate if there is a flicker key (whatever that is). Both the second and third parameters seem to be ignored by the stock tklock plugin. The flicker key is the lock key available on the N810 and N900; the 770 and N800 doesn't have one. Called flicker because it's not a slider key -- it flickers back. And indeed these parameters are ignored. Regards: David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Using Qt Creator to make qml modules and package them for deployment
Would someone please post or point me to instructions for creating and packaging a QML module with Qt Creator? I'm embarrassed to say that I can't find any guidelines for doing this with or without Qt Creator. None of the choices offered by Qt Creator seem right: Qt Quick Application builds an executable I don't need, Qt Quick UI isn't deployable, and Custom QML Extension Plugin gets me into C++ land. The motovation for this is an application I'm making with Colibri (https://projects.developer.nokia.com/colibri), Digia's library of QML components. I want to turn Colibri into its own Qt Creator project and to deploy it separately from my application. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
P1 bug in QtMobility Contacts module
I've encountered a bug in QtMobility's Contacts module. It's in the Symbian^3 implementation. I'm reporting it to maemo-developers because I encountered it while porting a Maemo application to Symbian^3. Nokia recently classified it as priority P1: Critical. The Symbian^3 implementation of QContactManager doesn't work well with QContacts that contain avatars in PNG form. If there are any such avatars in your contacts, QContactManger returns an empty QListQContact in response to contacts() or a QContactFetchRequest. The Symbian^3 Contacts application displays PNG avatars as expected, so the bug is definitely in the QtMobility Contacts module. http://bugreports.qt.nokia.com/browse/QTMOBILITY-1647 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Installing HTML help files in Maemo and Symbian^3
Thanks, Timur. On Monday, May 16, 2011 03:33:07 AM Timur Kristóf wrote: ... I'd recommend you to put those files into your app's resources, then Qt will embed them into your app's executable. ... Read more about this at http://doc.qt.nokia.com/latest/resources.html ... I considered that. I don't think that's the right solution. It's my intention to translate the help files into a number of languages. Embedding each one in my application will make my application much bigger. There has to be another way. When I find it, I will share it here. On 05/16/2011 04:56 AM, David Talmage wrote: I'm sure some of you develop for both Maemo and Symbian^3. I need some advice about deployment on those platforms. I'm looking for a place to put support files, such as help files, that can't be made into resource files. In Maemo, I'm putting them in /opt/usr/share/doc/myapp/. Where does Symbian^3 keep such files? ... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Canonical list of fremantle sections
Is this still the canonical list of sections for debian/control in fremantle: http://wiki.maemo.org/Packaging#Sections There used to be a section named user/communication. Is that now obsolete? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Adding additional files to deb with QtSDK-1.1
On Friday, May 06, 2011 11:43:55 AM Daniil Ivanov wrote: It's enough if you add to your project file: data.path = /usr/share/doc/panicbutton/ data.files += panicbutton.html INSTALLS += data ... Thanks, Daniil. That's what I was missing. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Installing HTML help files in Maemo and Symbian^3
I'm sure some of you develop for both Maemo and Symbian^3. I need some advice about deployment on those platforms. I'm looking for a place to put support files, such as help files, that can't be made into resource files. In Maemo, I'm putting them in /opt/usr/share/doc/myapp/. Where does Symbian^3 keep such files? In my perfect world, each platform has a standard place for support files. My application would learn the platform's name for a support file using a library call like QString aSupportFile = QSupportSystem.openSupportFile(relative/path/to/the/file.html); Thus far, I can't find what I'm looking for. I expect to resort to using cpp: #if defined(SYMBIAN) QString aSupportFile = /special/symbian/place/for/file.html; #elseif defined(MAEMO) QString aSupportFile = /opt/usr/share/doc/myapp/file.html; #else SYNTAX ERROR: FIND A PLACE FOR file.html ON THIS PLATFORM #endif As always, I will receive with gratitude any clues you care to share with me. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Nokia developer discount on phones?
I applied for Nokia Launchpad yesterday. While I'm waiting for Nokia to respond, I'm curious about the discounts it offers on phones. Is this something we can talk about on maemo-developers ? I found a new, green N8-00 at Amazon.com for $349. I'm tempted to buy it. That's the lowest price I've found in two weeks of looking on EBay and my local Craig's List. If the developer discount isn't substantial, I'm sorely tempted to buy it now so that I can get on with testing my QtMobility apps on Symbian. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
How to display progress while fetching contacts?
I'm looking for a platform-independent way to display the progress of a QContactFetchRequest. Can any of you suggest a solution? I've found a couple of partial solutions but nothing completely satisfactory. QProgressBar would be perfect if I knew how many contacts to expect. I don't know that. I only know when the QContactFetchRequest begins, when some results arrive, and when it ends. QMaemo5InformationBox::information() with a timeout value of QMaemo5InformationBox::NoTimeout is informative but the user can (or must?) dismiss it by tapping on the screen. I don't want that. In addition, with a name like QMaemo5InformationBox, I don't expect that I will be able to use it on Symbian devices or whatever else I port my application to. I'm going to look into QStatusBar. I welcome other ideas from all of you. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtMobility app shows, hides, shows again at startup
On Saturday, April 09, 2011 04:11:08 am Thomas Perl wrote: 2011/4/8 David Talmage talm...@acm.org: My newly released PanicButton application [1] behaves strangely at startup. When I start the application, it displays its window, then immediately hides the window. In a few but significant number of seconds, it displays its window again. It should display its window ... Is the first window that you see a black one that animates from the application icon to fill the screen and has the sound effect of an opening window attached to it? If so, it's just a fake window ... You can fix this by doing all the time-consuming operations *after* you have created and shown your window. You can usually populate your window with contents even after it has been shown, so that would be a good idea to do in that case. You can do this using single-shot QTimer, so that the main loop gets enough time to really show and draw the initial window. This is good advice, Thomas. Thank you. Your solution worked perfectly. My application now behaves as I want it to. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
QtMobility app shows, hides, shows again at startup
My newly released PanicButton application [1] behaves strangely at startup. When I start the application, it displays its window, then immediately hides the window. In a few but significant number of seconds, it displays its window again. It should display its window only once. Perhaps one of you can help me make it behave the right way. I can't be the only one who has ever encountered this application behavior. I've searched for a solution but haven't found the right way to describe it to Google or developer.qt.nokia.com. This is what PanicButton does at startup in order: 1. Changes the style sheet of its single, large button, so that the text color is green. 2. Creates but does not display a dialog for choosing contacts. 3. Reads settings from a file. 4. Creates a QMenuBar, populates it with QActions, and displays it. Each QAction has some of its signals connected to slots in PanicButton. 5. Creates a QMessageService and connects one of its signals to one of the PanicButton slots. 6. Creates a QGeoPositionInfoSource, connects one of its signals to one of the PanicButton slots, and asks it to begin getting updates. 7. Connects some of the contact chooser dialog's signals to PanicButton's slots. 8. Connects some of the signals of two QContactFetchRequests to some of PanicButton's slots. 9. Starts one of the QContactFetchRequests. Dave [1] http://talk.maemo.org/showthread.php?p=982605 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
QtCreator 2.1.0-rc1
QtCreator puts underscores instead of dashes in the names of the packages it creates for me. Have I misconfigured it or have I bound a bug? For example, when I build my soon-to-be-released PanicButton application, QtCreator makes panicbutton_0.3.0_armel.deb instead of panicbutton-0.3.0-armel.deb. Then it complains: :-1: warning: Your project name contains characters not allowed in Debian packages. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtCreator 2.1.0-rc1
On 12/01/2010 09:15 PM, Felipe Crochik wrote: Hi David, I think they are separate issues (especially because -1 is not even part of the file name you described). The panicbutton_0.3.0_armel.deb is a valid package name. You may also have something like panicbutton_0.3.0-1_armel.deb. It is complaining about the project name. I don't think it has anything to do with the package name. ... Thanks for pointing that out, Felipe. Is it complaining about PanicButton.pro? Should that be panicbutton.pro? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtCreator 2.1.0-rc1
On 12/01/2010 09:45 PM, Felipe Crochik wrote: I don't think the upper/lower case especially on windows but I may be wrong. Anyway does not sound like the cause for the message. Have you checked the actual contents of the panicbutton.pro file? It could be the TARGET=-1 but it is hard for me to guess w/o the code and/or more of the output. For what it's worth, I'm using Linux. Here's the definition of TARGET in PanicButton.pro: TARGET = panicbutton ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Position of the icon in QListWidgetItem
On 10/19/2010 08:40 AM, Felipe Crochik wrote: I haven't tried with a list item but with buttons you can reposition the image using just style sheets. Be aware that you (can) have two images: the ... I am sure you found this already but: http://doc.trolltech.com/4.6/stylesheet-examples.html#customizing-qlistview Thanks for the example and the URL. I had read that page already. What's there doesn't tell me enough about QListView and its style sheet items. I found a solution overnight. While reading about models and delegates in the Qt book, I took a guess that the item index of the icon is strictly less than the item index of the text. With that and a hint I found elsewhere, I tried setting the QListWidget's layout direction to Qt::RightToLeft. That fixed my ordering problem. To make the text flush left, I set each QListWidgetItem's text alignment to Qt::AlignLeft|Qt::AlignVCenter|Qt::AlignAbsolute. The Qt::AlignAbsolute is the key. According to the online documentation, when the layout direction is Qt:RightToLeft, the meanings of Qt::AlignLeft and Qt::AlignRight are reversed. Qt::AlignAbsolute restores them to their default meanings, the ones they have when layout direction is Qt::LeftToRight. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
listenning for orientation changes using dbus
Hello I'm looking for a way to listen for orientation changes using dbus. the subscription to the mce dbus service sig_device_orientation_ind works fine, but only when the device is unlocked. I'm using this to avoid battery draining. I also tried Qmobility, but this uses 10% of CPU. I don't think that an infinite loop querying the orientation is the good trick How to enable this signal when the device is locked ? Is there another way ? Thanks. David. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Position of the icon in QListWidgetItem
I need help placing an icon in a QListWidgetItem. I want the icon to appear on the far right instead of the far left. Can I do this with a style sheet? Do I need to write a delegate instead? This is for a contact chooser for Qt4.7 that behaves like the OssoABookContactChooser. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
A QContactDetailFilter that matches only non-empty details
Is it possible to make a QContactDetailFilter that matches non-empty details? For example, I want a QContactManager to return only Contacts with telephone numbers. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Crash reporting (was: Package promoting)
There's been a Crash reporter available for several years Maemo releases, it's even open sourced: http://wiki.maemo.org/Documentation/devtools/maemo5/crash-reporter http://repository.maemo.org/pool/maemo5.0/free/c/crash-reporter/ I have never been able to get this to work: Every time I have a crash report and try to submit it, I get a Nitro: Failed to connect error. I've tried having the network up, but looking at the tcpdump's it looks like all I am getting it errors from the server. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qt Dev Days San Francisco/Meego Conference - Are you going to?
On 10/07/2010 04:25 PM, Felipe Crochik wrote: I am going to attend both events and would like to meet other maemo developers, anybody else? I'm going. I'll have my first Maemo app to show off. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
maemo.org Bugzilla 3.4 update
The migration of bugs.maemo.org from Bugzilla 2.22 to Bugzilla 3.4 is almost complete. Thanks to the efforts of Karsten Bräckelmann: http://blogs.gnome.org/kbrae/2010/09/23/bugzilla-3-4-for-maemo-org/ the new version is skinned to fit in with the rest of maemo.org. The changes from a stock Bugzilla installation are as minor as possible, to make future security upgrades easier. Bugzilla 3.4 also brings some new features and customisations, such as a template for licensing change requests: https://bugs.maemo.org/show_bug.cgi?id=9068 As this will be a large change for users of bugs.maemo.org, public testing of the test server is encouraged. A testing instance of the latest Bugzilla 3.4 for maemo.org is available at: https://test.maemo.org/testzilla/ The Bugzilla database is a snapshot from mid-August and mail sending has been disabled. Please test and report any bugs that you find at bugs.maemo.org (please include screenshots if the issue is with page layout). https://bugs.maemo.org/enter_bug.cgi?product=maemo.org%20Websitecomponent=Bugzillaversion=5.0short_desc=[3.4] For those interested in the details, the source is available on Garage in a Subversion repository: https://garage.maemo.org/scm/?group_id=675 -- http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems during packaging
On 2010-08-02 19:33, Kamilla Bremeraunet kami...@bremeraunet.com wrote: Hi, I'm trying to package FaceBrick, which is using libqfacebook in MADDE (instead of scratchbox, which I have heard works) and have run into some problems: At first when doing mad dpkg-buildpackage -us -uc it was complaining about not being able to find the file libqfacebookconnect.so.1 - I solved this by copying the file over to /home/kamilla/.madde/0.6.72/sysroots/fremantle-arm-sysroot-10.2010.19-1-slim/usr/lib/, but now I'm running into a different error: dh_makeshlibs dh_installdeb dh_shlibdeps dpkg-shlibdeps: failure: no dependency information found for /home/kamilla/.madde/0.6.72/sysroots/fremantle-arm-sysroot-10.2010.19-1-slim/usr/lib/libqfacebookconnect.so.1 (used by debian/facebrick/opt/facebrick/facebrick). dh_shlibdeps: command returned error code 512 make: *** [binary-arch] Error 1 dpkg-buildpackage: failure: debian/rules binary gave error exit status 2 Does anyone know what I need to do to fix this? If using third-party libraries with MADDE, you may wish to read the following talk thread: http://talk.maemo.org/showthread.php?t=48536 especially the last post, which mentions how to resolve your dh_shlibdeps problem, by copying /var/lib/dpkg/info/package.* of an installed package to the corresponding location in the MADDE sysroot. There was some discussion in June about these problems: http://lists.maemo.org/pipermail/maemo-developers/2010-June/026807.html -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [MeeGo-community] Open Letter/Proposal to allow Maemo on the MeeGo Community OBS
This issue has recently received some attention from this post onwards: http://bugs.meego.com/show_bug.cgi?id=615#c26 so I felt it worth re-posting this to remind people of the original request. Summary : We would like to support the Maemo community in migrating to MeeGo by allowing them to build open-source applications that link against a mix of open _and closed_ libraries on the MeeGo _Community_ OBS. Cross-posted again... please discuss on meego-community. Thanks. David PS as an aside we have almost finished the OSU deployment thanks to a long weekend. Details here: http://wiki.meego.com/Build_Infrastructure/Community_Builder/Installation On 15/06/10 18:16, David Greaves wrote: This is an open letter to the whole MeeGo community and on behalf of the Maemo development community. The purpose of this letter is to ask the MeeGo community for their permission to bring Maemo build targets (currently Fremantle eventually Harmattan, Diablo, Chinook?) to the MeeGo Community OBS and to ask the Maemo development community for their support in this project. *Please discuss on meego-community mailing list* I would like to emphasise that this is a Maemo Community initiative and is not being pushed by Nokia. At this point we are not aware of any similar initiatives related to the Moblin community but we would fully support any that arise. The Maemo community has built up around Nokia devices which, in many ways, are amongst the most open devices available in their class. There is a passion for openness in the Maemo community and we know that the future for this family of devices lies with MeeGo. Many of us are looking forward to MeeGo and are keen to transition as smoothly as possible. However our devices are not fully open and developing for them has dependencies on vendor proprietary binaries which would need to be available on the build service. This would mean putting closed binaries on the MeeGo OBS and having a part of the MeeGo Community OBS functionality being 'restricted' to Maemo developers. Naturally we recognise and respect that MeeGo is an open source project and there may be ideological issues in allowing closed binaries into the ecosystem (even though they're just for build/linking). We also recognise the risk of opening the door to closed binaries and suggest that this arrangement could be agreed as a one-time grandfathering in (http://en.wikipedia.org/wiki/Grandfather_clause) situation for the Maemo community. However we also feel that the benefits of supporting a smooth transition for the vibrant Maemo development community would be worthwhile both for MeeGo and Maemo: * developers would be able to use the OBS' natural ability to target Fremantle, Harmattan and MeeGo from a single location. This would bring more developers and their applications to MeeGo sooner. * many of the same people in the Maemo and MeeGo community teams look after the Maemo Autobuilder and the MeeGo application OBS. Our limited volunteer time would be used more effectively on a single platform instance. * resources earmarked for Maemo could be added to the MeeGo estate and would naturally be used at peak efficiency as Maemo demand decreases and MeeGo demand rises. * new Maemo community Quality Assurance processes would evolve around the shared OBS and could assist the development of MeeGo QA processes. and perhaps most important of all: * users of existing devices could expect a significantly longer maintainable life from products built on a consolidated build service and could look forward to their applications being available on MeeGo as soon as devices become available. The maemo.org buildservice already has a 'proof of concept' instance of the OBS which allows the Fremantle target to co-exist with a MeeGo target and we already intend to use this as a basis for the MeeGo community OBS. The proposed solution *must* allow MeeGo community users to use the MeeGo Community OBS without any reference to Nokia closed binaries; this facet of the service should be entirely optional. Equally the legal issues around the closed binaries require an EULA related to demonstrated possession of a relevant device. This can be handled in a similar manner to the Maemo Autobuilder service; ie registration of a serial# to a developer account. The proposal therefore is: * To provide the closed binaries as a build-target repository (probably DoD for those who know and care) on the community OBS. * To grant ACL based access to this repository based on acceptance of an EULA * To *not* require any such EULA for 'MeeGo-only' accounts on the service I've run this by Tero Kejo in Nokia and he's very supportive of the idea. From: David Greaves / lbt Community Member and build systems guy. Niels Breet / X-Fade maemo.org webmaster and autobuild owner Carsten Munk / Stskeeps maemo.org distmaster Andrew Flegg / Jaffa on behalf of the Maemo Community Council ___ MeeGo
Re: Attach an icon to an application does not work
On 2010-07-15 14:45, Pierre CLARENC pierre@gmail.com wrote: Hello, I have developed a small program using ESbox. It works well when I execute it on my N900. I want to attach a specific icon to this program. I use a 48*48 px image (PNG format) that I have resized with the GIMP. I use the following command to generate a base64 coded image: uuencode -m icon.png icon.png icon_64.base64 But when I install my deb package on the device, the icon does not work. I only have the blue square instead. The instructions at: http://wiki.maemo.org/Packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package (that you apparently followed) refer to an icon in the application manager only. If you wish to have an icon shown in the application menu, then you should install it to the correct location (usually /usr/share/icons/hicolor/size where size is one of a range of possible values, e.g. 16x16, 32x32, scalable). Then, you must refer to that icon in the desktop file, see: http://wiki.maemo.org/Packaging#Desktop_files and the links in that section for some more details. -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: OBS for Freemantle (really Chinook)
On Thu, 2010-06-17 at 11:25 +0200, Bas Vermeulen wrote: On 15.06.10 17:35, David Greaves wrote: On 15/06/10 14:34, Bas Vermeulen wrote: Hello David, I'm trying to set up a private OBS to be able to automatically build/rebuild Chinook instead of Freemantle. I'm getting stuck on the first few steps in your description, specifically where to get the maemo_sdk_5 /maemo_sdk_4 stuff you refer to in the Stable part. Where can I get those? Thanks for any help you can give, Sure... you may want to take this onto the maemo-dev list too? What pages are you using? http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup ? Yup, that's the one. I've set up OBS on a private server, and that's working so far. I've created a Maemo:4.1 project on the OBS web interface, including a repository there. My question is how to populate that so I can build and/or rebuild any packages in the base distribution (and what other repositories I'd need). I've copied the configuration from build.opensuse.org's Maemo 4.1 project, but I believe it doesn't have anything else there. I suggest you document the steps you're taking (following the same overall process as Fremantle). Do that in http://wiki.maemo.org/OpenSuse_Build_Service/Chinook_Setup Then I'll have a much clearer idea of what the problems are. This is a complex and iterative process BTW... don't expect it to be simple ... David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Open Letter/Proposal to allow Maemo on the MeeGo Community OBS
On 15/06/10 18:16, David Greaves wrote: This is an open letter to the whole MeeGo community and on behalf of the Maemo development community. The purpose of this letter is to ask the MeeGo community for their permission to bring Maemo build targets (currently Fremantle eventually Harmattan, Diablo, Chinook?) to the MeeGo Community OBS and to ask the Maemo development community for their support in this project. *Please discuss on meego-community mailing list* DocScrutinizer on irc pointed out that a url might be useful but was too shy to post himself ;) http://lists.meego.com/listinfo/meego-community David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtSql and Debian package probelm
On 2010-06-10 15:01, Sascha Mäkelä sascha.mak...@gmail.com wrote: Hi, I just made a Debian package of my app. I'm using QtSql in it. But for some reason when I install the package, all the SQL things don't work. My guess is that I'm missing something in the Build-Depends line in the control file. How can I check what libs I need to add there and what are their correct names? Cheers, Sascha PS. Currently it's like this: Build-Depends: dephelper (5), libqt4-dev, libqt4-network You need to add the relevant Qt SQL provider packages to the ‘Depends:’ line, not the ‘Build-Depends:’ line, as the SQL providers are plugins that are not required at build time, but at runtime. You probably want libqt4-sql-mysql or libqt4-sql-sqlite in Depends, depending on which database provider you are using. -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QtSql and Debian package probelm
On 2010-06-10 15:47, Sascha Mäkelä sascha.mak...@gmail.com wrote:
This how it looks now:
Depends: ${shlibs:Depends}, ${misc:Depends}, libqt4-network, libqt4-sql,
libqt4-sql-sqlite
But still it doesn't work. Am I missing something? The app works fine when I
run it in N900 from Qt Creator.
Which database provider do you use, I guess SQLite? If so, your Depends:
line looks correct. When you say that the SQL parts of the application
do not work, what is the problem? You could try starting your program
from the terminal to check for clues in the output. Either that, or
report any error messages that the application gives you.
Thanks for all your help,
Sascha
On Thu, Jun 10, 2010 at 15:12, David King dav...@openismus.com wrote:
On 2010-06-10 15:01, Sascha Mäkelä sascha.mak...@gmail.com wrote:
Hi,
I just made a Debian package of my app. I'm using QtSql in it. But for
some
reason when I install the package, all the SQL things don't work. My guess
is that I'm missing something in the Build-Depends line in the control
file.
How can I check what libs I need to add there and what are their correct
names?
Cheers,
Sascha
PS. Currently it's like this: Build-Depends: dephelper (5), libqt4-dev,
libqt4-network
You need to add the relevant Qt SQL provider packages to the ‘Depends:’
line, not the ‘Build-Depends:’ line, as the SQL providers are plugins that
are not required at build time, but at runtime. You probably want
libqt4-sql-mysql or libqt4-sql-sqlite in Depends, depending on which
database provider you are using.
--
David King | http://amigadave.com/
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: EDS groupware plugin development
On Fri, 2010-06-04 at 11:48 +0200, Nils Faerber wrote: Hello! We are currently evaluating the possibilities to attach the N900/Maemo5 to a groupware server for synchronising PIM data - primarily contacts and calendar events. Maemo5 quite obviously uses EDS EDS? Electronic Data Sync ? http://en.wikipedia.org/wiki/EDS Not a term I'm familiar with :) in some form to handle some PIM data but by quick searching I was not yet able to verify how EDS is used in Maemo5. E.g. it is not fully obvious to me if EDS is used for all PIM data or just for the address since I only see this /usr/lib/evolution-data-server/e-addressbook-factory in my process list. Try: http://syncevolution.org/ http://wiki.maemo.org/Sync syncevolution is also part of MeeGo and has an active mailing list. And since the calendar and addressbook applications seem to be non-open-source I cannot check in them either. The intention is to create something, like an EDS plugin, that will allow the standard Maemo5 applications to transparently use another groupware server, like e.g. Kolab. So SyncML is the likely answer AIUI. - For the other non EDS type(s) what would be the best way to create alternate source connectors? HTH David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Q_WS_MAEMO_5 directive
On 2010-06-02 09:53, Ram Kurvakat rkma...@gmx.com wrote: Hi, what preprocessor directives need to be used for Maemo5 specific QT code ? is it still Q_WS_MAEMO_5 or has it changed in PR1.2 QT4.6 release ? I remember in QT4.5 it was Q_WS_HILDON. Correct, for the 4.6 in PR1.2 the define is Q_WS_MAEMO_5: http://wiki.maemo.org/Qt4_Hildon#Adding_Maemo_changes_to_a_Qt_Application -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
QA Proposals (was Re: Quality assurance of stable software: my battery drained in few hours)
On 29/05/10 17:52, Sivan Greenberg wrote: Yes, I am working on this :) Real life and bills paying can sometimes get in the way but I'm slowly going back to being fully active with MeeGo. I will send a notification to go over and review [0] once it is finished, as so far I outlined the tools that will enable us better QA but have not expanded them and elaborated. Then I would ask the TSG to approve the team creation, which would also attempt to engage users in QA and specific niche testing of the software we deliver. Hi Sivan Just checking : [0]: http://wiki.meego.com/Proposal_for_a_Quality_Assurance_working_group and maemo-developers mailing list So we should really take (or at least cc) the QAWG to meego-dev (but see later) However could you look at: http://wiki.meego.com/Proposal_for_a_Repository_working_group Having spent quite a lot of time pushing for *something* to be done in this area I'd like to suggest that the successor to the RWG encompases this kind of QA activity. Personally, I'd also suggest that you forget about Working Groups the powers that be don't seem interested in setting up WGs for much other than product direction at the moment; certainly they won't (AFAIUI) set one up for just QA; it would be expected to fall under a larger umbrella. See the various TSG logs for the past few months for my (lbt) attempts and more useful URLs. Of course there's also the Meeting call for Community application support that you responded to on the -community ml. Lets follow up in that meeting. Right... now the see later: I actually don't think there's much point in doing MeeGo QA policy right now anyway; I think we'd be *far* better off working on Maemo QA for Fremantle ... and Harmattan. We have an established community and real devices to work with. We're also working on moving the build and QA infrastructure in Maemo towards the same basic shape that I think we'll see in MeeGo (ie an OBS driven approach). FYI I'm also working on workflow automation and integration with image and test systems internally for Nokia and we expect those solutions to be OSS and deployed on maemo.org meego.com(munity) So if we work on a decent solution for Maemo and ensure it's suitable for MeeGo then we solve a lot of real-world issues. 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: Using libosso-abook getting package requirement error
On 2010-05-19 10:30, Faheem Pervez tripp...@gmail.com wrote: Just to clear, you are doing: AC_SUBST([LIBOSSO_CFLAGS]) AC_SUBST([LIBOSSO_LIBS]), right? This is unnecessary as PKG_CHECK_MODULES already does the substitution. On Tue, May 18, 2010 at 12:37 PM, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: I want to display all contacts from phone. For that I am using libosso-abook. I am adding following lines to configure.ac PKG_CHECK_MODULES(libosso, osso-addressbook-1.0) Thanks. -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using libosso-abook getting package requirement error
On 2010-05-19 01:48, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: Hi David, I again tried re-doing the entire procedure and the output is as follows: [sbox-FREMANTLE_X86: ~] fakeroot apt-get install libosso-abook-dev Reading package lists... Done Building dependency tree... Done libosso-abook-dev is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Good, so you have the right package installed. [sbox-FREMANTLE_X86: ~] --- Now in my project if I add foll lines to Makefile.am myproj_LDADD = \ $(LIBOSSO_LIBS) As is mentioned in all the documentation that I linked to the last time that you had a pkg-config query, you must also use the relevant preprocessor flags, to ensure that the headers can be found. So, you would add: myproj_CPPFLAGS = $(LIBOSSO_CFLAGS) Of course, this will only work if you use PKG_CHECK_MODULES in configure.ac to check for libosso-abook-1.0. the output is as follows: Description Resource Path Location Type 'book' undeclared (first use in this function) main.c ContactList/src line 45 C/C++ Problem 'EBook' undeclared (first use in this function) main.c ContactList/src line 45 C/C++ Problem 'EBookQuery' undeclared (first use in this function) main.c ContactList/src line 47 C/C++ Problem 'osso_context' undeclared (first use in this function) main.c ContactList/src line 111 C/C++ Problem 'query' undeclared (first use in this function) main.c ContactList/src line 47 C/C++ Problem libebook/e-book.h: No such file or directory main.c ContactList/src line 12 C/C++ Problem libosso-abook/osso-abook.h: No such file or directory main.c ContactList/src line 13 C/C++ Problem make: *** [all] Error 2 ContactList line 0 C/C++ Problem make[1]: *** [all-recursive] Error 1 ContactList line 0 C/C++ Problem make[2]: *** [main.o] Error 1 ContactList line 0 C/C++ Problem --- And if i add below line to configure.ac (making no changes to Makefile.am) PKG_CHECK_MODULES(libosso, osso-addressbook-1.0) You should use the same capitalisation for libosso as you do in Makefile.am, so the libosso above should be LIBOSSO. Output is: Package requirements (osso-addressbook-1.0) were not met: configure.ac Are there any other libraries to be included in Makefile? or any changes to configure.ac? As Dave Neary mentioned, the pkg-config file is libosso-abook-1.0, so you should use that and not osso-addressbook-1.0. -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using libosso-abook getting package requirement error
On 2010-05-18 04:37, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: I want to display all contacts from phone. For that I am using libosso-abook. I am adding following lines to configure.ac PKG_CHECK_MODULES(libosso, osso-addressbook-1.0) and to Makefile.am : myproj_LDADD = \ $(LIBOSSO_LIBS) But i get foll error: Package requirements (osso-addressbook-1.0) were not met: configure.ac Pls do help me in this matter Do you have libosso-abook-dev installed, for the development headers, pkg-config file, etc.? http://maemo.org/packages/view/libosso-abook-dev/ -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using libosso-abook getting package requirement error
On 2010-05-18 04:47, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: No i dont have it installed. I had a look at this site: http://62.61.85.167/platform/docs/howtos/howto_using_abook.html#basics and they said to follow this link : Using Nokia binaries in rootstrap But this link is not working. Pls can u guide me regarding how to install the required things? Sure. You must install the nokia-binaries package, from the Nokia binaries repository. Accept the license agreement at: http://tablets-dev.nokia.com/eula/index.php Add the URL that you get from that page to the /etc/apt/source.list file inside Scratchbox. Inside Scratchbox, you must then execute: apt-get update fakeroot apt-get install libosso-abook-dev You can install all the other Nokia binaries and application with: fakeroot apt-get install nokia-binaries nokia-apps This information is in the wiki article regarding Maemo SDK installation, but not very well organised, so I will fix this up soon: http://wiki.maemo.org/Documentation/Maemo_5_Final_SDK_Installation#Manual_Installation -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using libosso-abook getting package requirement error
On 2010-05-18 05:35, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: All these steps we had done at the time of installation. When i give foll command at prompt the output is as follows: pall...@pallavi-desktop:/scratchbox$ apt-get update E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied) E: Unable to lock the list directory pall...@pallavi-desktop:/scratchbox$ fakeroot apt-get install libosso-abook-dev The program 'fakeroot' can be found in the following packages: * fakeroot * fakeroot-ng Try: sudo apt-get install selected package fakeroot: command not found pall...@pallavi-desktop:/scratchbox$ Are there any PKG_CHECK_MODULES and libraries to be added in the code? Are you sure that you are executing the commands _inside_ Scratchbox? That is, have you executed: /scratchbox/login before trying any of the commands above? I ask because your prompt does not look like a regular scratchbox prompt, which includes the target name. -- David King | http://amigadave.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Finding path of file / folder present on emulator
On 2010-05-16 22:10, Pallavi Kandhare pallavi.kandh...@yahoo.com wrote: I write my appliccation using ESbox. Then build the application and run it on Xephyr. This we call as emulator. In the emulator I want to find the path of File Manager folder. Pls do tell me how can i do this. Do you mean that you want to show a file chooser dialog, like: http://maemomm.garage.maemo.org/docs/tutorial/figures/filechooser.png so that you can select a file? If so, you would use hildonfm: http://maemo.org/api_refs/5.0/5.0-final/hildonfm/HildonFileChooserDialog.html You will need to use the ‘hildon-fm-2’ module with pkg-config so that you can compile and link against the hildonfm headers and libraries. As HildonFileChooserDialog implements the GtkFileChooser interface, you will also want to read the API reference for that: http://library.gnome.org/devel/gtk/stable/GtkFileChooser.html Also, the GtkFileChooserDialog documentation has some useful examples: http://library.gnome.org/devel/gtk/stable/GtkFileChooserDialog.html I am not quite sure if this was what you wanted, so let me know if this solves your problem. -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
OBS and Fremantle .... 193 Extras apps built...
A couple of posts on Planet Maemo[0] that may be interesting * Community Building for Maemo and MeeGo - What does the OBS *Do*? [1] and * OBS and Fremantle ... huge success and HELP [2] Essentially work has been proceeding on the OBS and we now need experienced maemo build system people to help get it working properly. I also realise I didn't post about the startup of the OBS work [3]. I've also tried to put everything on a wiki [4] so it can be maintained Talk to Neils or I for more details. For when they've scrolled off into the the planet's crust: [0]http://maemo.org/news/planet-maemo/ [1]http://mer-l-in.blogspot.com/2010/05/community-building-for-maemo-and-meego.html [2]http://mer-l-in.blogspot.com/2010/05/obs-and-fremantle-huge-success-and-help.html [3]http://mer-l-in.blogspot.com/2010/05/it-was-dawn-of-3rd-age.html [4]http://wiki.maemo.org/OpenSuse_Build_Service 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
IO schedules other than noop?
I run my N800 with root on an SDHC card (to get a bit more room on root), and I've notices quite a few cases where the system becomes unresponsive due to mmcq blocking for a long time. I'd guess that when a lot of writes get flushed to the card, the system can backlog while the card writes the data. Has anybody played with IO schedulers other than the NOOP scheduler? It seems to me that perhaps using deadline, with writes having a large deadline and read a small deadline might help address this. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: OBS and Fremantle .... 193 Extras apps built...
Ville M. Vainio wrote: On Sun, May 16, 2010 at 4:59 PM, David Greaves da...@dgreaves.com wrote: A couple of posts on Planet Maemo[0] that may be interesting Not sure I understood correctly, but does this mean that we'll have a PPA-like thingie for Fremantle soon? Yes, that's likely to be one of the side-effects of an OBS - but it's certainly not the main objective :) 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: Keeping backlight on
On Tue, 2010-05-11 at 12:45 +0200, ext saurabh aggarwal wrote: Our application on Maemo requires that the backlight be kept on for the entire time we do a process. How do we achieve that? I have already tried calling the command below (every 10 seconds), but that didn't work. usr/bin/dbus-send --system --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:unlocked That's because this isn't the correct method... Try: dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.req_display_blanking_pause instead (every 30s should be enough). An (undocumented) alternative is: gconftool -s --type int /system/osso/dsm/display/inhibit_blank_mode 3 Replace the 3 for whatever inhibit mode you want: 0 -- No display blanking inhibit 1 -- Inhibit dimming/blanking if charger is connected 2 -- Allow dimming, but inhibit blanking if charger is connected 3 -- Inhibit dimming/blanking 4 -- Allow dimming, but inhibit blanking Regards: David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help needed: packaging/distributing very small C app
On 2010-04-27 23:30, Thomas Waelti twae...@gmail.com wrote: Hell, frozen over. It took me four evenings, one hour each evening, to tinker and try and fail and try again. But now it loooks good: http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/mafw-play-list/0.1.0-5/ (To test it, you need to have one or more saved playlists on your N900. Then open X-Term and enter mafw-play-list NameOfYourPlayList and it should start the playback of this playlist.) Thanks for all the help and support - it's been a positive (community) but still frustrating (technology) experience :-) I guess once you're spoiled by something like the Compact Framework and Visual Studio, a casual hoppy developer finds the current state of Maemo development quite difficult to accept... Mainly, there was a major pitfall that I fell into: - In configure.ac, pkg_check_modules, I had to put mafw and mafw-shared as dependencies - But in the Build-Depends of the control file, I had to write libmafw0-dev and libmafw-shared0-dev Yes, perhaps I could make this a bit clearer in the wiki. Maybe a bit of dpkg magic to determine which package owns a particular pkg-config file would be helpful? In addition, once something fails, it's still a bit unclear from the current docs about where to continue/repeat which steps. Yes, this is hard to solve in such a compact tutorial, as there are lots of steps where something could fail, and it is difficult to find the right balance between proding too much and too little information. Contributions welcome ;) -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help needed: packaging/distributing very small C app
On 2010-04-28 13:20, Dave Neary dne...@maemo.org wrote: David King wrote: In addition, once something fails, it's still a bit unclear from the current docs about where to continue/repeat which steps. Yes, this is hard to solve in such a compact tutorial, as there are lots of steps where something could fail, and it is difficult to find the right balance between proding too much and too little information. Contributions welcome ;) Sounds like there's a sufficient amount of material for a packaging troubleshooting page? It would certainly be possible, but much of what it might say is already documented in the Debian packaging documentation, and other links from the Packaging article. A general recommendation to ask on maemo-developers would probably be better than trying to make presumptions about possible errors. A troubleshooting page could then be added if some common questions and answers arose. A packaging tutorial really should only cover the most simple things, and point people to canonical references where they can get more information. The Packaging page has already gotten too long for my liking, it seems like most people will only need about half of it at this stage, and the other half is likely to be more confusing than useful. I split off the section on porting a Debian package to Maemo, which shortens the article somewhat. The majority of what remains is focussed on Maemo packaging specifics, with several links to reference documentation. The information in the new packaging guidelines page: http://wiki.maemo.org/Packaging/Guidelines could simplify the Packaging article further, but it is quite a long and dry read, so leaving the summaries as they are might be preferable. -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help needed: packaging/distributing very small C app
On 2010-04-20 18:01, Chitti Babu chitti_ma...@yahoo.com wrote: Hi Dave, Cool documentation ! It helped me in revising all my basics. I am sure, it will serve a great purpose for a maemo newbie developer. Few suggestions :- 1. Adding a GTK based example with dependencies specified in configure.ac (PKG_CHECK_MODULES for gtk flags), debian/control (Depends,Build-depends) would be useful I will find a place to add this, as the information is currently scattered in several places, such as: http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_a_new_maemo_application http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/GNU_Build_System#Integration_with_Pkg-Config http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Porting_Software/Porting_MaemoPad It might make sense to split this off into a seperate autotools article, as there is not a direct relation to packaging, and the article is already very long. 2. What changes are required for deb packaging a QT program. An article on Qt packaging is linked from the Packaging article. The direct link is: http://wiki.maemo.org/Packaging_a_Qt_application and could probably do with some improvement. Contributions or suggestions very welcome! P.S : I have suggested this as you also mentioned about desktop files. Well, this is mentioned as something Maemo-specific, as the desktop file installation location is different from the usual /usr/share/applications. Dave Neary wrote: I documented the packaging of a C app (using autotools for building) a while back in the wiki: http://wiki.maemo.org/Packaging#A_concrete_example_-_rot13 This starts with a tiny C program the minimum autotools stuff to build it (I don't include these - would that be useful?) and guides you through making a .deb. So I included an A to Z for this project, with the 3 files you need to create a .tar.gz using standard autotools. Let me know if it's useful. -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help needed: packaging/distributing very small C app
On 2010-04-19 16:50, Dave Neary dne...@maemo.org wrote: Hi, Dave Neary wrote: I documented the packaging of a C app (using autotools for building) a while back in the wiki: http://wiki.maemo.org/Packaging#A_concrete_example_-_rot13 This starts with a tiny C program the minimum autotools stuff to build it (I don't include these - would that be useful?) and guides you through making a .deb. So I included an A to Z for this project, with the 3 files you need to create a .tar.gz using standard autotools. Let me know if it's useful. I updated this with some newer syntax and a link to some (very detailed) documentation in the wiki. I second autotools as a way to make packaging easier (once you understand them). -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Info Center library service released with first set of official maemo Fremantle 5 documentation
On 2010-04-19 17:21, Andrew Flegg and...@bleb.org wrote: On Fri, Apr 16, 2010 at 18:40, jarmo.ti...@nokia.com wrote: The Maemo documentation infrastructure project has released new Maemo Info Center documentation service for Maemo platform. Together with Maemo Info Center service we released also the first set of official Maemo Fremantle 5 documentation. More Fremantle 5 documentation will be updated to the Maemo Info Center service end of April. One thing I'd like to see is a *definitive* Maemo reference library. Currently, we have docs spread over Forum Nokia, Info Center, the maemo.org wiki - and then there's the docs that are *duplicated* (with slightly different versions) between the various places. Is it feasible to try and get things like the PyMaemo API reference into the Info Center, and any other popular developer resources (say, Gtkmm is an obvious example)? There is already API references for hildonmm and hildon-fmmm, and a tutorial for the C++ bindings in general included in Info Center. If you mean that the gtkmm API reference should be included, then that should be relatively easy. The API reference is generated by Doxygen, and the index is created with a custom XSLT script that is included in hildonmm and hildon-fmmm: https://garage.maemo.org/plugins/ggit/browse.php/?p=maemomm;a=blob;f=hildonmm/docs/reference/tagfile-to-eclipse-toc.xsl The tutorial documentation is Docbook XML, which makes use of the Docbook XSL stylesheets to generate an Eclipse table of contents: https://garage.maemo.org/plugins/ggit/browse.php/?p=maemomm;a=blob;f=maemomm-documentation/docs/tutorial/eclipse.xsl We added some paramaters to this file to make things easier: https://garage.maemo.org/plugins/ggit/browse.php/?p=maemomm;a=blob;f=maemomm-documentation/docs/tutorial/docbook2eclipse-toc.xsl -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Inhibiting device auto-lock on N900
Hello. To unlock the device : http://wiki.maemo.org/User:Jebba/DBUS#dbus-send-unlock To keep the display on and device unlocked : http://maemo.org/api_refs/4.0/libosso/group__Devstate.html#g93fe32aeb992e128c94b890d6f801bfd David. Per von Zweigbergk wrote: I'm writing a talking clock application. The purpose of this application is to answer the ever-so-frequent question mghhnm, what time is it in the morning, just before you've been able to open your eyes properly much less put on your glasses. I've already written the application itself, it was a fairly simple project that took a couple of hours. In testing, however, I discovered a slight drawback to my planned approach of start the program before falling asleep, mash the screen in the morning and it'll tell me the time. 1. The screen itself will stop accepting taps when the device is turned off. It seems this particular feature can be inhibited by leaving the phone slided open (with the qwerty keyboard exposed) or by setting the gconf setting /system/osso/dsm/locks/touchscreen_keypad_autolock_enabled to false. This requires you to slide the lock button on the side of the phone to unlock the screen. Annoying, but still doable even in a half-awake stupor. And besides, you can always leave the phone activated in its opened mode. 2. The device will automatically lock itself after 5 minutes, for security purposes. Now, remembering and correctly entering the device lock code in a half-awake stupor is considerably more difficult. This can be disabled by setting the gconf setting /system/osso/dsm/locks/devicelock_autolock_enabled. However - I don't really like this approach of changing gconf user settings to inhibit device locks. The last thing I want is for the phone or my application to crash (or more likely, to run out of battery) while the program is running and leaving the device unlocked, requiring the user to set the automatic lock option on again (if he even notices it's been disabled). Whoever coded the built-in media player agrees with this. He's found some way to tell the system not to automatically lock itself without changing the gconf settings. I have not yet figured out how. One other option worth considering is the fact that some applications, such as the phone (for an incoming call) and the alarm application (to silence the infernal bleeping of an alarm) will allow you to throw up a screen to the user that'll be accessible even if the lock code has not been entered. This would also solve the potential security issue of somebody stealing your phone while you're sleeping to get to it while it's unlocked. :-) So, does anybody have any ideas as to how I might acheive this in some way? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Packages interface - Warning: This package seems to be a library in a user/* section!
Hi Could someone explain what the packages interface considers my application as a library ? http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/libellule/0.0.1-3/ I uploaded 2 anothers apps without problem... Thanks. David. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packages interface - Warning: This package seems to be a library in a user/* section!
Thanks Niels Breet wrote: Hi Hi, Could someone explain what the packages interface considers my application as a library ? http://maemo.org/packages/package_instance/view/fremantle_extras-devel_fr ee_armel/libellule/0.0.1-3/ This is a rather lame check I added to prevent people submitting obvious libs as user applications. Starts with lib ;) I added an exception for libellule. I uploaded 2 anothers apps without problem... Thanks. David. -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Autobuilder - roadrunner don't go extras-devel
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
Re: proper icon path
On 2010-04-06 15:35, Stefanos Harhalakis v...@v13.gr wrote: On Tuesday 06 of April 2010, daniel wilms wrote: ext Stefanos Harhalakis wrote: I'm currently using /usr/share/icons/hicolor/64x64/apps/, but I see other applications using /usr/share/icons/hicolor/64x64/hildon, or even /usr/share/icons/hicolor/scalable/apps and /usr/share/icons/hicolor/scalable/hildon. Is there a proper location or is everything acceptable? The proper location for the icons is in: /usr/share/icons/hicolor/scalable/hildon/ Thank you for clarifying that. Is there a reason why scalable was chosen? AFAIK for desktop systems this is supposed to hold scalable graphics like SVGs while bitmaps icons are supposed to go under /usr/share/icons/hicolor/AxB/ (AxB being the dimension) (or perhaps I know wrong). I would also like to know this, as I was going to edit a few wiki pages that mention install locations for icons. However, all the locations above seem to work just fine (I tested with a few applications), and the freedesktop.org icon naming specification suggests that ‘apps’ is the correct subdirectory to use: http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html#context Daniel, is /usr/share/icons/hicolor/scalable/hildon/ the canonical location for all application icons on Fremantle, and if so, where is this documented? -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to include glib-object.h
On 2010-03-29 15:25, Murray Cumming murr...@murrayc.com wrote: On Mon, 2010-03-29 at 11:24 +0200, Alberto Garcia wrote: Actually you should include `pkg-config --cflags glib-2.0` Well, actually, the location library apparently provides a pkg-config file that he should check for instead, so he doesn't have to worry about checking for its glib dependency. However, this example suggests that the liblocation pkg-config file is broken, because it suggests checking for glib too. Well, that whole pkg-config call is very strange. http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Connectivity_Components/Using_Location_API#Using_Location_API CCing David so he can investigate. I fixed the pkg-config invocation to be less misleading: pkg-config --cflags --libs liblocation and as the liblocation pkg-config file correctly depends on glib-2.0, that is included automatically in the compiler and linker flags. -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Deleting Project PyGTKEditor from Garage
Very sad to read this Good luck Le mardi 23 mars 2010 à 18:17 +0100, Benoît HERVIER a écrit : Hi, As a dumb, i ve forgot to delete project PyGTKEditor before deleting garage account. Someone can do it ? Thanks. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Ask for removal of some packages from Extras Fremantle repository
Hello And please remove qypy too. David. Benoît HERVIER wrote: Hi, Please, can you remove all version of the following packages from the extras fremantle, extras-testing fremantle, and extras-devel fremantle repository : - pygtkeditor - pypackager - py2deb - pylint - vectormine - mcalendar - mtodos - mnotes - python-logilab-astng - python-logilab-common - pychecker Thanks. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Ask for removal of some packages from Extras Fremantle repository
I'm not allowed to use this name (based on qype name) The application will come back soon with another name and some improvements Jeremiah Foster wrote: Do these packages have other packages that depend on them? Why are you guys interested in removing so many packages? Jeremiah On Mar 22, 2010, at 11:16 AM, David Hautbois wrote: Hello And please remove qypy too. David. Benoît HERVIER wrote: Hi, Please, can you remove all version of the following packages from the extras fremantle, extras-testing fremantle, and extras-devel fremantle repository : - pygtkeditor - pypackager - py2deb - pylint - vectormine - mcalendar - mtodos - mnotes - python-logilab-astng - python-logilab-common - pychecker 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
How to remove a package from repositories
Hello I'm the maintainer of qypy : http://maemo.org/packages/view/qypy/ I'm not allowed to use this name. How to remove a package from devel and extras-testing repositories ? Thanks. David. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to remove a package from repositories
David Hautbois wrote: Hello I'm the maintainer of qypy : http://maemo.org/packages/view/qypy/ I'm not allowed to use this name. Interesting. Says who? How to remove a package from devel and extras-testing repositories ? Talk to Neils, cc'ed 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: Extras-testing improvements
Graham Cobb wrote: On Monday 08 March 2010 23:04:36 Attila Csipa wrote: I invite everyone who has not alredy done so to take a good look at http://wiki.maemo.org/Extras-testing/QA_Checklist/QA_Improvements Scary. Well, trying to solve a bigger problem than the process originally intended to address. I think what's being proposed (Atilla: BUG: I can't easily tell what's new and what exists) is that the functionality of the software is assessed and then the tester makes a call as to whether that functional bug warrants blocking promotion. I think this should be permitted *if the developer agrees* - maybe we'd need to note applications that want the QA team to do application QA too. 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: Maemo 5 PR1.2 and Extras
Marius Vollmer wrote: ext David Greaves da...@dgreaves.com writes: My wife must have done an 'ignore' on a Maemo5 update sometime in oct/nov. The device never reminded her again. She only got pr1.1.1 because she noticed my device made a sound on account connections and hers didn't... I did 2 upgrades in succession. Normal users wouldn't have even noticed. That's a bug in the ignore machinery: I think we only store which packages have been ignored, but not which versions. This means that if you ignore a OS update, you will never be notified again about OS updates ever. Has a fairly big impact on the assumptions being made including those who will never see the update that fixes the bug... 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: Maemo 5 PR1.2 and Extras
Graham Cobb wrote: My personal view is that there will be a lot of people running earlier software for quite a long time. How long do Nokia believe it will be before 80% of new devices being sold in retail stores have PR1.2 pre-installed? FYI My wife must have done an 'ignore' on a Maemo5 update sometime in oct/nov. The device never reminded her again. She only got pr1.1.1 because she noticed my device made a sound on account connections and hers didn't... I did 2 upgrades in succession. Normal users wouldn't have even noticed. I've filed a bug but if this is normal behaviour then I guess a *lot* of devices will never be upgraded. 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: 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: rpm vs. deb and universal binaries/packages
On Tue, 2010-02-16 at 12:17 +0100, Christopher Intemann wrote: On Tue, Feb 16, 2010 at 11:56 AM, Andrew Flegg and...@bleb.org wrote: Sure, but is there a recent i386 port of Maemo at all? :-) No one is running Maemo on i386, not even Nokia on their Booklet 3G. Mer is - I run Mer/Maemo on the O2 Joggler which is Atom iirc. David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: About legacy Maemo 5 documentation on the wiki
On 2010-02-11 21:50, Anderson Lizardo anderson.liza...@openbossa.org wrote: While fixing a few bugs on the supposedly official developer documentation on the wiki, I just noticed I made a mistake and was actually editing this one: http://wiki.maemo.org/Legacy_Maemo_5_Documentation The problem is that it is often getting high results while searching for documentation (at least for me). I will add a ‘Legacy’ template to all legacy pages today, to place a banner at the top of each page with links to the non-legacy documentation, which should make the status of these pages more obvious. Can it be moved to a different place, archived, or even removed completely (as it has been superseded by other documentation as mentioned on the link above)? I think it is too easy to not notice the Legacy on the title. In the long term, archival or removal seems the best option. Thanks for pointing this out. -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [New Developer]: Questions - Python Packaging / Free or Non-Free / Software Licensing
Sanjeev (EIPI) wrote: Thank you for the reply. To clarify this particular situation a bit more... The API key is available only on a paid basis. For some novel or new devices, a limited use (read: non-commercial) key is given to developers that apply for one. So, a casual user is not able to obtain their own API key. I have obtained one of these limited use keys for use in my application. This is the reason why I was inquiring about how to protect the API key within the application. (nb try not to top-post) This is not a licensing issue, it's a security issue. (Well, actually, you may contravene the api publisher's license since you probably can't avoid publishing your personal credentials to the world). In general if you distribute a binary containing credentials then the credentials can be extracted. You need a fairly complex security system to avoid this (eg Harmattan's upcoming DRM management which is the problem you're attempting to solve - and look how well that worked out so far). You have several obvious problems: * python is distributed as source - it's hard to obfuscate * the api key will almost certainly be clear in the source * if you encrypt the credentials then the decryption routine will be clear * if you obfuscate it (eg compile) then it has to be capable of being read by the CPU - or by a debugger. One solution is to use a proxy. Provide an 'open' service that your app calls and which then passes the request on to the paid service using credentials kept on the proxy. This is likely a breach of the terms-of-use license. As the problem is outlined I think you're out of luck - sorry. 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: sensing change in System Clock using Qt
ibrahim wrote: remi.denis-courm...@nokia.com wrote: Hello, - Message d'origine - But the problem that can face me is the case when the user changes his clock settings (i.e adjust phone's time to a different time). in this case, the timer that has been set to some fixed duration can go wrong. As a general rule, delay measurements should be done with the monotonic clock, not the wall clock (the real-time clock). As far as I know, Qt timers already do so internally. But of course, your own code should never request and use the wall clock for time measurements. I don't think I follow you! What do you mean by monotonic clock ? If I don't depend on the system's clock to get current time, where else can I get it from ? Let me explain my problem again briefly, I want to know the current time, calculate some future durations depending on it. Then I figure out the time left to the upcoming duration and set it as interval to a QTimer Object. But I'm afraid that user may change the system clock (adjust the clock) So that my preset time will be invalid. Just so you know... you're describing an implementation and asking if it does what you want without describing what you want. Example: At 4am the user wants to play a sound at 8am (in 4hrs). At 6am the user changes timezone and it becomes 7am. The alarm should sound at 8am in the new timezone. My guess is that you know about interval timers but you should be using a wall-clock. Since you haven't specified what you want it's hard to know. 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: Build Server Configuration
On Tue, 2010-01-26 at 12:52 +0100, Ove Kaaven wrote: Mer builds packages on OBS - why can't we do that for Maemo? I thought you wanted to use Debian tools? Besides, I believe OBS is based on a standard Debian install, which Mer probably aims to be compatible with, but Maemo isn't. (For those who don't know, I'm the build guy for Mer) I don't think it would be hard to build Fremantle in OBS. There may be some policy issues using the public OBS server (they don't like closed binaries) but Mer may be setting up a 'private' OBS anyhow to handle the opengl dev binaries - In general OBS is certainly a good approach IMHO. I spent a few minutes on this for fun last year and made good progress. My approach was to fake out scratchboxisms and it worked pretty damned well. Mer already uses a sophisticated (ie clever hack) debian derived cross-compiler with qemu - more info on the Mer Build pages. Actually there's a *lot* there :) Answering a later thread: OBS is working on linking to VCS too David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Backwards compatibility broken PR1.1 SDK
Graham Cobb wrote: I do think there may be an option 1.5: create multiple autobuilder queues which feed the same repository but build against different SDK releases. For example, a fremantle queue which builds against the base release (for ever), and a fremantle-pr1.1 queue which builds against the new SDK (for ever), but both populate the same repository (extras-devel fremantle). That would allow the applciation developer to decide which users they are willing to support. If the application supports all fremantle users it submits to the fremantle queue. But if it uses a new feature (or even an important bug fix) from the pr1.1 release the maintainer could submit it to the fremantle-pr1.1 queue. If we did this, I wouldn't object to automatically adding a dependency on the device software version, as long as it is worked out from which queue you submit to. I like - but as someone mentioned to me in a similar situation: testing. We'd need testers for each queue and that may be tricky. 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: How to destroy your community
On tis, 2010-01-19 at 12:10 +0100, ext Jeff Moe wrote: On Tuesday 19 January 2010 07:13:30 Jeremiah Foster wrote: 10) Silence. Don't answer queries, don't say anything. A company which masters this technique may not need any of the others; it is the most effective community destroyer of them all. Ooops! No silence here! I guess that disproves point 10. :-) (http://jaaksi.blogspot.com/ -- More non-silence.) Actually, when I cut and pasted that article snippit I was thinking about his blog *specifically*. AFAICT he has the highest position in Nokia with respect to the Maemo project (correct me if I'm wrong plz). He has a whopping 5 blog posts since the device has been out. His karma in maemo.org is 100% based on his blog posts. He gets asked lots of questions in the blog comments, but rarely answers. Since the N900 has been out, I see he only answered two comments, one of which was mine. ;) The other comment he replied to starts like this: Is there any reason why all my contact attempts with you, Mr. Makkinen and other Maemo people at Nokia are being ignored? ... Excuse me for posting it this way, but what else am I supposed to do if all I get in exchange for my emails is delivery confirmations? I wonder if he ever got a response. Blogs are often used as two way communication tools, he uses it for the occasional edict or a marketing promotion tool. So, what you're saying is that you acknowledge that Ari is the highest ranking person within Maemo. Then you are surprised that he doesn't have time to answer random comments made on his blog... Regards: David Weinehall ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Command to turn on the screen led (Maemo N810)
maybe : dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:unlocked Faheem Pervez wrote: Hiya, You're looking for this function: http://maemo.org/api_refs/4.0/libosso/group__Devstate.html#g93fe32aeb992e128c94b890d6f801bfd libosso's source is available, too, so if you don't like using it and would prefer to see the D-Bus behind it... Best Regards, Faheem On 1/6/10, dc101 dc1...@gmail.com wrote: Hi all, I am just wondering if it is possible to use a command (most probably dbus or something) to tell the screen to light up once it has turned off. I know it can be turned on by a simple tap, but I need to automate this when the device has received some notifications. Also, if it's not too much to ask, is it possible to disable software updates notification at the status bar? Cheers, dc101 ___ 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: Mirrors
Jeff Moe wrote: As far as I can tell, there are no mirrors of the repositories. Pretty sure Nokia/maemo.org went with a CDN which satisfies all the points you raised. The maemo.org infrastructure problems are more to do with dynamic content and build services and are being addressed AFAIUI. 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: Proposal: Karma-Whores protection mailing list
Mustali Dalal wrote: Till, It is obvious that your angst is against my thumbs-down to your app due to my perceived understanding of optification which is at odds with yours. I take testing seriously and do this as a way of giving back to the open-source community. Thanks I am a developer too; but still on the maemo-developer learning curve. The experience with rating your app is not something I would consider a high-point of maemo. So long as you take it as an outlier :) 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: SyncEvolution in Fremantle
Eugene Agafonov wrote: Update: I've built a far better .deb based on SyncEvolution 0.9.1, and put it up at http://people.debian.org/~ovek/maemo/ It can't yet be built with a buildbot, primarily because not all of its build-dependencies exist in maemo-devel, cppunit in particular. I tried to build fro source package you provided but build fails because of boostlib. How did you solve it? I couldn't find boost packages for Maemo5 so I have to build boost from source. Any other options? It's named oddly http://repository.maemo.org/extras-devel/pool/fremantle/free/source/b/boost1.38/ 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: [SyncEvolution] SyncEvolution in Fremantle
Ove Kaaven wrote: David Greaves skrev: Ove, Patrick I'll volunteer to do the packaging for maemo for this if you like? Well, there's already packaging (last updated for OS2008 I think) and the .debs were built from it. Only thing that remains, apart from submitting patches upstream, is maybe clean up debian/rules a bit, update the build-deps, and select the final configure options to use, and maybe other nitpicks like that. I could probably manage that. OK then. I've sent libxmltok-1.2 to the autobuilder already. boostlib1.38 is in extras-devel but it looks like I'll need to package synthesis from git://git.moblin.org/libsynthesis.git - which branch? master? You won't have to. The syncevolution build system can build synthesis on its own as part of the syncevolution build tree, so it's just a matter of putting synthesis into the same source package as syncevolution, no need for a separate package (unless you really want it). That's what I did for now, anyway. I thought that in general shipping a library's source inside another package is a bad idea. If libsynthesis was a part of syncevolution then it would make sense but in this case (and given that Debian already has a package and a debian/ dir for it) I'd keep it separate. We do need to downgrade debhelper from 7 to 5 though as Maemo is a bit behind there. I also made http://gitorious.org/mer-extras/libsynthesis to manage the tweaks to that libraries package. What branch to use was answered elsewhere in this thread - best to use the tag that corresponds to whatever syncevolution version we want to build. Sounds reasonable - I didn't spot that. Nb personally I use eGroupware and I'm getting some success (especially now I have this stuff in: http://k.noc.de/index.php?option=com_contentview=articleid=6Itemid=8 but there are still some issues) Anything in particular? like this: http://www.mail-archive.com/syncevolution-iss...@syncevolution.org/msg00412.html Most of my contact and calendar data goes from the device to egw but nothing comes back. I upgraded egw to the nightly release with the new syncml patches and enabled the syncml option in the prefs but no change. I thought I'd get the packages built and get a little more familiar with the code first; right now I get the session messages but egw isn't putting a log where it's supposed to. 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: [SyncEvolution] SyncEvolution in Fremantle
Ove, Patrick I'll volunteer to do the packaging for maemo for this if you like? I'd put them on gitorious.org/mer-extras (until we get some kind of community area at maemo.gitorious.org). I'll use the packaging approach I use for Mer and create suitable branches cppunit is ready (I won't push it to the builder until I can get a clean build locally) and I'm looking at syncevolution and dependencies now. I notice that syncevolution should build-depend on boostlib and synthesis too. boostlib1.38 is in extras-devel but it looks like I'll need to package synthesis from git://git.moblin.org/libsynthesis.git - which branch? master? Nb personally I use eGroupware and I'm getting some success (especially now I have this stuff in: http://k.noc.de/index.php?option=com_contentview=articleid=6Itemid=8 but there are still some issues) David/lbt -- 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: SyncEvolution in Fremantle
Ove Kaaven wrote: Update: I've built a far better .deb based on SyncEvolution 0.9.1, and put it up at http://people.debian.org/~ovek/maemo/ Thanks Ove, got it, installed it. It'd be great if anyone would try to put cppunit into extras-devel (the debian package of cppunit can't be ported directly since it depends on qt3, I'll take a look at cppunit and see if I can produce a non-qt maemo variant. However, the binary package is probably fairly ready for testing. It is compiled with optimization, optified, and stuff. It will synchronize your addressbook via the Evolution backend, as well as your calendar (including tasks and notes), via the Maemo-Calendar backend which I've spent the last two days writing, and which now seems to work fine for me. OK, I'd love to help get this moved forwards but I'm not familiar with linux syncing (I run IMAP/LDAP at home and used to use eGroupWare/iCal so I've not needed to be up to now). Could you help me get it working and I'll put some wiki docs up? Wasn't sure what URI scheme to use to let the user configure which calendar to sync, for now I've settled on id:calendar ID, and defaulting to the same calendar that Nokia PC Suite would sync to. So I have no idea what you mean here... I'll start digging ut if yo could expand that'd be great. I'll be around on #maemo on freenode over the holidays. Anyway, everything I've got on ScheduleWorld is now also available on the N900's builtin contacts and calendar apps... rockin', Sounds brilliant. Lets start with a simple howto... assuming this allows syncing against evolution on the desktop and also assuming a linux only setup (no PC-Suite) how do I find out what values to put in what fields in what desktop apps? Then what do I type where to do a sync? (meaning do I ssh into the N900 and push, or pull from the desktop cli?) There's still no GUI. For fun I tried to run the gtk+ ui (and again stumbled across missing build-deps when building it - the 0.9.1 version can't be built because of missing gnome-keyring, the git head version is slightly easier to build), but it was totally worthless on the N900. Guess it'd be necessary for someone to build a new GUI for this. Or maybe a control panel applet or something. Hmm. Still, it seems to work fine from the command line, if you really need to sync your stuff. That's all I need, at least... It's a great start :) David/lbt -- 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: Auto builder - Maemo-Optify
Ed Bartosh wrote: It's just ridiculous to have bug against autobuilder about maemo-optify is not taking care of build dependency to pymaemo-optify considering the fact that at the moment maemo-optify doesn't even try to do anything unless it founds debian/optify file with the line 'auto' inside it. Of course it's invalid and confusing. What is bugzilla policy for misfiled bugs? I suspect that, whilst satisfying, closing them as invalid until the reporter eventually gets the right package is not the best policy :) Ed... 2 questions: 1. are you happy that /usr/sbin/dpkg-preconfigure: No such file or directory is a bug (as you said a couple of emails back)? 2. what section do you think the bug should be against? Cheers 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: SyncEvolution in Fremantle
Ove Kaaven wrote: Hi, Patrick. I'm new to Maemo, but I've been a Debian Developer for a long time. I recently got a N900, and decided I really want to sync my stuff. Hi Ove, welcome to maemo-dev :) Just breaking lurker status on this thread and saying that I'm really pleased that someone's making an effort - if you could push your git tree to gitorious.org (maemo's de-facto git-sharing service) that would be really nice even though I realise it is likely to be ugly atm. Also maybe start scribbling on the maemo.org wiki too? Cheers David/lbt -- 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: Commands for adjusting screen brightness for N810
On ons, 2009-12-16 at 07:13 +0100, ext Jey Han Lau wrote: Hi all, I know there's an built-in application for managing the display (brightness, etc), although I am curious if there are any commands (I am guessing it'll be D-BUS commands if there's any) to manipulate the screen brightness directly, or commands to manipulate all the display settings for that matter. If there's none, are there any ways run the built-in display program (at Control panel) via commands? The display brightness control panel uses GConf for its brightness setting. You can simply change the relevant GConf key and have the brightness change immediately. The relevant GConf key in question is: /system/osso/dsm/display/display_brightness and valid values are 1-5. Regards: David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build-Depends for several Maemo versions
On Fri, 2009-12-11 at 14:34 +0100, Cornelius Hald wrote: What am I missing? In the general sense: A way to specify per-build-target .dsc files (for pre-calculation of the build-deps setup of the chroot) and easy access to per-build-target source variations in debian/ (either through patches or tag-based pulls from a vcs). I say this because that's an area the OBS we use for Mer is pretty good at. I'm sorry I don't know how to work around it for Garage. I would have done exactly what you're doing. David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dbus on Mer
Jeffrey Barish wrote: I am trying to activate the display on an N800 using dbus. On maemo, my code works fine. On Mer, I get osso.OssoException: Cannot initialize context. I have fiddled with the X-Osso-Service entry in my .desktop file in /usr/share/applications and with the Name entry in my .service file in /usr/share/dbus-1/services. Everything that I have tried produces the same error message. Has anyone had any luck using osso.Context on Mer? Hmm, I've done this at a low level from python-dbus and hal iirc. I can't get at that code at the moment but it may well change in the near future anyhow; see below. BTW, is Mer still alive? Yes, very much so however I see that there has been some occasional chat about it, but the release schedule for version 0.17 hasn't been updated for a long time. Nor, I believe, has the hardware support table. ...as you've noticed we've slipped when it comes to releases. One key reason is that we're integrating the Fremantle packages into Mer and this is hard work; another is that both Carsten and I have been tied up on other work too. However this should pay dividends over the hols and into the new year :) We've had a lot of new interest in Mer recently so we're hoping this will improve moving the fremantle code back to the N8x0 devices; and now we have sniffs of the 3D drivers that could be rather good. David/lbt (Ignoring the followup to news... I'm on maemo-developers) -- 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: Maemo Best Practices
Edward Page wrote: Hi All, I was talking to texrat recently who had the idea of organizing best practices for app development. Currently I really only have a couple of categories with limited ideas for each. I'm curious what you all think before running off and creating the wiki page. Out of laziness, I did some wiki syntax but not all of it is. Just snipping the content and responding to the concept... The documentation stream at the Barcelona weekend proposed just such an idea. We're looking to make this pervasive; to include best practices with examples as a part of each area in the docs rather than an area in itself. A challenge is to find a way to introduce these things and structure them into the overall set of docs. 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: Double checking free/nonfree packages
On Mon, 2009-11-30 at 22:16 -0600, Christopher Allan Webber wrote: Hello, I'm compiling a list on the Libre Planet wiki to determine what packages are nonfree, and what steps would need to be taken to make the n900 a fully free phone: http://groups.fsf.org/wiki/FreeMaemo Hi Christopher As another Mer person I'm also very interested in this work. Mer on any Nokia device out today is not (and realistically has zero chance of ever being) 100% fsf-free. However every step the community takes in the right direction moves us towards that milestone and I personally feel that Nokia are doing freedom in a better way than most (which is one reason I'm here!) If this is a reasonable compromise then it would be great to see this work integrated with the maemo community efforts - IIRC there have been other initiatives to investigate this kind of data so maybe they could be dug up? David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Command line apps Extras
Andrew Flegg wrote: On Sat, Nov 28, 2009 at 15:57, Valerio Valerio vdv...@gmail.com wrote: Based in your feedback, here are the best solutions in my opinion, let's try to reach a good solution that can make both sides happy: 1 - Modify the HAM code in order to add some kind of switcher for the CLI apps - Very good solution IMO, but very hard to accomplish in the short term. Should we introduce an `XSBC-Maemo-Type' header which can have the following values: Or we could use debtags... interface::text-mode interface::shell interface::daemon http://debtags.alioth.debian.org/ [snipped the rest which is fine] 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: Debhelper 7
Do you have a URL for the .dsc and tarball David Teemu Ikonen wrote: Hi, I'm trying to compile / port some C libraries from Debian to Maemo 5. The actual compilation goes without problems, but the packaging scripts use the (very nice) command sequencer functionality of debhelper v. 7, while the SDK has only debhelper 5. There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, but trying to compile it in the SDK fails miserably. The problem seems to be related to perl, which is also of similar vintage (i.e. obsolete) in the SDK. Has anyone else tried or managed to get debhelper 7 running on maemo 5? Having to rewrite the packaging on every library I need would be a major suck. Teemu ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- 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: Updating the info for Extras-devel non-free
On Wed, 2009-11-25 at 12:04 +0100, Jeremiah Foster wrote: We are seeing more questions about this and actually the current information is misleading since it suggests that non-free packages can bypass the Extras-testing QA process, which is not true. I am hesitant here, some of the testing process may require source packages, either now or in the future. I am not certain that non-free packages deserve to get all the free quality assurance that the community provides. I think they should be grateful that they are included at all and if they want to go through testing, they need to at least provide a source package. Does the community really have so much spare resource that we can QA non-free (and presumably non-community) apps? I suppose one way to look at it is that these are no-cost apps that the community can't have unless it QA's them; from that PoV I think providing a place for the app's userbase to QA the apps is fine but I feel that they should be separate to a community queue. David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Updating the info for Extras-devel non-free
On Wed, 2009-11-25 at 15:07 +, Andrew Flegg wrote: On Wed, Nov 25, 2009 at 14:55, David Greaves da...@dgreaves.com wrote: Does the community really have so much spare resource that we can QA non-free (and presumably non-community) apps? fms/RST38h's emulators are non-free. However much I'd prefer to have the source and not special case them, they are useful packages and the author's intention should be respected. Yep - my 2nd para was about the balance. Whether they get highlighted in a different queue is an interesting question; but will probably push non-Ovi, non-free apps away into their own repositories. Why? It's a different queue, not a different community. The point of community QA is to make sure only good apps get to users: we're doing it because we're selfish. Yes. It's not free bug finding for commercial software teams; Agreed, the non-free apps you identified are non-commercial. Do you see non-free apps which are commercial (eg crippleware needing an email supplied EIN-keyed password or adware) going through the same process? Would that fail the Extras QA? Why? Would it fail a non-free queue's QA? How do testers QA such (IMHO perfectly reasonable) applications? Should the test process require a password for testers? and so saying we're only go to QA it for you if you give us the source would seem to be a change in the purpose and intent of the QA process. Fair, but some of us (and note that I've spent time testing RST38h's Master Gear emulator) do and will continue to care about free rather than no-cost. Are you as a community member happy to QA a binary app from a polite and well spoken community noobie without even having the *option* of reviewing the source? What if I'm not? Will it be obvious that there's no source for that app (ie marked non-free) in the testing queue? /me sees quite a bit of grey. David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging a bookmark?
confession: I was all set to rant about 'web apps' in HAM :) However, I apologise : it's a nice app. I can see why you'd want it packaged and visible; I've added it to my desktop. (Nb, map needs to be scrollable - but you knew that) I think it would make sense for you to get karma for it and for it to be published via the Extras process; it truly is an N900 web application (heck, it even has a dependency on maemo-geolocation). I also think it makes sense for HAM to allow web-apps to be published but I personally don't think it's there yet - maybe packaging this up as a desktop/app mgr launch icon is the way to go. Nokia led the way with the 'ovi store' link. Eventually maybe we'll see better presentation... but the issue may need forcing. I do worry about a proliferation of packaged web links though - I thin I'd like some kind of bar to be set here. David Till Harbaum / Lists wrote: Hi, as long as the app manager is a flat list of things i'd oppose to this. It's already a problem to finger scroll to the list of gcompris-packages. Having to also scroll though a list of bookmarks would make things worse. Till Am Freitag 20 November 2009 schrieb Thomas Waelti: Hello list Some of you might have seen my Google Maps webapplication called maeMaps (http://tomch.com/maemaps.html) As it is a always online app anyway, I would like to distribute through Extras not an offline version, but just a bookmark to the online version. This would have the advantage for endusers that people can easily find it through the Application Catalog and for me as a developer greater freedom in updaating and integration with other services. Is that allowed and acceptable? Does it make sense in my case? What would you do in such a case? Best regards and a happy weekend -Tom -- 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: how build a package?
http://maemo.org/maemo_release_documentation/maemo4.1.x/Maemo_Diablo_Reference_Manual_for_maemo_4.1.pdf p466 mohamed ismael wrote: hi, i built an executable file using the following command gcc `pkg-config --cflags --libs profile hildon-1` main.c -o main i want now to build a package to deploy it on N900 device can any body help? thaks ___ 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: debhelper-maemo-package-icons
On 2009-11-10 14:30, Gabriel Schulhof n...@go-nix.ca wrote: On Tue, November 10, 2009 13:49, Aniello Del Sorbo wrote: Where does it expect the package_name.png file to be? If you have an icon debian/package-name.png, then package-name_version_arch.deb will have the icon. the helper assumes that debian/package-name.png is a 26x26 PNG file. You mean 48x48 pixels, right? http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging%2C_Deploying_and_Distributing#Icons -- David King | http://amigadave.blogspot.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DBus service name
On 2009-11-09 09:08, Aniello Del Sorbo ani...@gmail.com wrote: I got it now. I initialize osso with a call like: osso_initialize (PACKAGE, VERSION, 0, NULL); where PACKAGE is the Debian name xournal. I think com.nokia is then automatically added. Correct: http://maemo.org/api_refs/5.0/5.0-final/libosso/group__Init.html#g05d45d1e72c2cd74f665086225141431 -- David King | http://amigadave.blogspot.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
On Mon, 2009-11-09 at 12:16 +0200, Gabriel Schulhof wrote: Hey, all! I added a package to the extras(-devel)? repositories called maemo-release. It has version 1.0.0 in gregale, 2.0.0 in bora, 3.0.0 in Chinook, etc. ... Cool... what values did you pick for Mer? David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
