Re: Any early QtWRT adopters flying with us?
On Thu, 12 Aug 2010, Dawid Lorenz wrote: > > I have created a widget which uses sysinfo API and all relevant API calls > > are stored in separate js file, so I include it into main html with: > > > > > > Script itself uses plain old document.getElementById(�element�).innerHTML > > calls to update corresponding html placeholders and it generally works > > nicely together. Now, the problem I have is that as soon as I include jQuery > > to the JS stack: > > > > > > > > suddenly all my API calls just stop working and I don�t get responses from > > sysinfo API. I don�t modify anything within hellowrt.js, just adding > > jquery-1.4.2.js file renders hellowrt.js non-functional. > > > > Perhaps there�s some sort of conflict between jQuery and sysinfo API? > > Additionally, is there any way to debug QtWRT apps, ie. see JS errors as > > they happen? http://docs.jquery.com/Using_jQuery_with_Other_Libraries -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: /etc/init.d/ssh stop does not stop ssh on the N900
On Wed, 24 Mar 2010, Sivan Greenberg wrote: > I'd say supporting > /etc/init.d/ssh stop is important for users that are coming from the > pre-upstart time. Better get used to it - upstart has been standard on several distros for a few years now (Ubuntu, Fedora and maybe the next Debian release). -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSOC Project: eBook Reader
On Tue, 23 Mar 2010, Oliver Haag wrote: > Okular should be a pretty good base, it supports many formats and is Qt-based > (Hope there aren't too many KDE-dependencies...). I'll take a closer look at > the source the next days. > > There's another eBook-Software in the repos called FBReader, maybe that is > already known but wanted to write it here anyway in case it wasn't seen. I've > tried it out and it doesn't seem to be touch-friendly but it looks like it > supports more eBook-only-formats, maybe these could be ported (When the other > things are running fine :D). You've been reading my mind haven't you? :-) It has to be said, Evince is pretty good for PDF (but I dont know if that build includes DJVU support?). The other two major formats that I would love to see supported are CHM and ePub. For CHM, have a look at ChmSee (thought it uses GTK+). kchmviewer uses Qt but might have too many dependencies on KDE libs. I was hoping to look at some of these packages myself but Ive not had much spare time. -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: A proper home page in maemo.org with help wiki for each app in Extras
On Fri, 12 Feb 2010, Sascha Mäkelä wrote: > While writing help files for my current project, I came to a conclusion that > it would be easier to have the app simply point to a wiki page. This way a > new version of the app would not be needed for changes/corrections in the > documentation. What about providing the help as a separate package? That way, you can distribute help updates any time you like. You could also make it a dependency of your app to ensure it always gets installed alongside your app. -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging questions
On Tue, 9 Feb 2010, Dave Neary wrote: > Which docs were you following, and how did you get there? we're trying > to make http://wiki.maemo.org/Packaging the standard "quick start" page, > and > http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging%2C_Deploying_and_Distributing FYI, the URL above is what I was reading. -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging questions
On Tue, 9 Feb 2010, Jeremiah Foster wrote: > Exactly. Thanks for pointing this out Marius. Unless I am mistaken Ajai, > you were referring to building multiple *package* binaries, correct? > (Not multiple application/runtime binaries.) Just to clarify with an example: when installing say, ruby, there is a main binary but also additional binaries in the package (irb, etc) - those should all be in the same package. Things like MySQL or openssh have separate client and server tool so those should be separate package. Am I correct? -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging questions
On Mon, 8 Feb 2010, Jeremiah Foster wrote: > This means you do not have an original tarball of your package that has the > suffix orig.tar.gz. > > Take a look at the debian documentation here which should help: > http://www.debian.org/doc/maint-guide/ch-first.en.html#s-dh_make Hmmm.. the docs says: "After this execution of dh_make, a copy of the upstream tarball is created as gentoo_0.9.12.orig.tar.gz in the parent directory to accommodate the creation of the non-native Debian source package with the diff.gz." Which seems to imply that dh_make creates the orig tarball... UPDATE: I used the -f flag to point to the original tarball "outside" the build directory and it seems to have worked. -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging questions
On Mon, 8 Feb 2010, Jeremiah Foster wrote: > > Im trying to create my first Maemo package > > Awesome! :) Yes, Maemo needs more developers and more software! :-) > That depends, but for the current situation, I would say no. Firstly, > creating multiple binary packages is harder than a single binary, though > not by much. I recommend you start out with just a single binary if you > can. OK, but Im curious: what would be an example of a package with multiple binaries? > > 2) I got an error saying it could not find package.orig.tar.gz - what does > > that mean? > > This means you do not have an original tarball of your package that has the > suffix orig.tar.gz. > > Take a look at the debian documentation here which should help: > http://www.debian.org/doc/maint-guide/ch-first.en.html#s-dh_make So, to clarify, I need to have a tarball of the original source inside the untarred tarball build directory? :-) > You have to specify the license the software is under yourself. From the man > page for dh_make: > > "OPTIONS >-c, --copyright > Usetype in copyright file. can be > gpl, lgpl, artistic or bsd. If this field is not specified the copyright > file has a space to fill in which sort of license is > used. The field is case-insensitive so -c GPL works as well as > -c gpl." I was following the Maemo docs which dont mention anything about licenses. Maybe there ought to be a link to the dh_make man page from there? > You may want to review this document: http://www.debian.org/doc/maint-guide/ Thanks for this and the other links. -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Packaging questions
Im trying to create my first Maemo package and I had a few questions: 1) This package has a main binary, but also has additional binaries/scripts and library files, so do I select 'Multiple binaries' when running dh_make ? 2) I got an error saying it could not find package.orig.tar.gz - what does that mean? 3) The summary dh_make printed said the license was 'blank' ? -- Aj. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
