Numbered sections in wiki (was: Re: Packaging guidelines)
Hi, Graham Cobb wrote: 0) I have a meta-comment: to facilitate discussion, the sections of the document should be numbered. This is a user-preference in Mediawiki: in My preferences, in the Misc tab, check Auto-number headings to have sections in all pages numbered. Sections are numbered in the table of contents in any case, so there is no problem with referring to section 4.1 (Package relationships) - I'd like to see people include the names in any case, because section numbers can change in a wiki after edits. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Meaning of Phone.Net.get_current_cell_info return values
On 27 April 2010 20:04, chantra chan...@debuntu.org wrote: Actually, the fields you mentioned are the ones returned by get_registration_status get_current_cell_info fields are slightly different. I did not find anything yet on those 2 last fields :s. Have you been looking into sources of NetMon application I've suggested earlier? -- Dawid 'evad' Lorenz * http://adl.pl null://google 'no evil' mail has taken away my random signatures ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Meaning of Phone.Net.get_current_cell_info return values
Hi Dawid, Yes I did a while back, and that sorted me out with get_registration_status reply. Did read over http://mxr.maemo.org/fremantle/source/bluez/audio/telephony-maemo.c I also searched http://mxr.maemo.org to no avail This page https://garage.maemo.org/plugins/wiki/index.php?Toolsid=1106type=g wrongly interprets the replies in my opinion. I have been googling/yahooing (not yet binging) for hours, tried to understand what those fields could mean by myself and yet just hit a wall. IRC also. All I need really is the API doc :) /me banging his head tks, chantra Have you been looking into sources of NetMon application I've suggested earlier? !DSPAM:4bd952a861678079316340! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
PyQt ForegroundRole
Hello, I've been struggling getting
ForegroundRolehttp://doc.trolltech.com/4.6/qt.htmlto work properly
so I can change the text color of certain cells in
QTableView.
I took an example from http://www.daniweb.com/forums/thread191210-7.html and
added the following in the data(...) method:
elif role == Qt.ForegroundRole:
return QBrush(QColor(255, 0, 0))
When I run it on my Windows PC, the font color is set to red for all the
cells but does not seem to have an effect on my N900.
Is there any Maemo-specific calls that I am missing here?
# http://www.daniweb.com/forums/thread191210-7.html
import operator
from PyQt4.QtCore import *
from PyQt4.QtGui import *
class MyWindow(QWidget):
def __init__(self, data_list, header, *args):
QWidget.__init__(self, *args)
# setGeometry(x_pos, y_pos, width, height)
self.setGeometry(300, 200, 420, 250)
self.setWindowTitle(Exploring PyQT's QTableView)
table_model = MyTableModel(self, data_list, header)
table_view = QTableView()
table_view.setModel(table_model)
# enable sorting
table_view.setSortingEnabled(True)
layout = QVBoxLayout(self)
layout.addWidget(table_view)
self.setLayout(layout)
class MyTableModel(QAbstractTableModel):
def __init__(self, parent, mylist, header, *args):
QAbstractTableModel.__init__(self, parent, *args)
self.mylist = mylist
self.header = header
def rowCount(self, parent):
return len(self.mylist)
def columnCount(self, parent):
return len(self.mylist[0])
def data(self, index, role):
if not index.isValid():
return QVariant()
# -
# Works on Windows PC but not on N900
# -
elif role == Qt.ForegroundRole:
return QBrush(QColor(255, 0, 0))
elif role != Qt.DisplayRole:
return QVariant()
return QVariant(self.mylist[index.row()][index.column()])
def headerData(self, col, orientation, role):
if orientation == Qt.Horizontal and role == Qt.DisplayRole:
return QVariant(self.header[col])
return QVariant()
def sort(self, col, order):
sort table by given column number col
self.emit(SIGNAL(layoutAboutToBeChanged()))
self.mylist = sorted(self.mylist,
key=operator.itemgetter(col))
if order == Qt.DescendingOrder:
self.mylist.reverse()
self.emit(SIGNAL(layoutChanged()))
header = ['First Name', 'Last Name', 'Age', 'Weight']
# a list of (name, age, weight) tuples
data_list = [
('Heidi', 'Kalumpa', '36', '127'),
('Frank', 'Maruco', '27', '234'),
('Larry', 'Pestraus', '19', '315'),
('Serge', 'Romanowski', '59', '147'),
('Carolus', 'Arm', '94', '102'),
('Michel', 'Sargnagel', '21', '175')
]
app = QApplication([])
win = MyWindow(data_list, header)
win.show()
app.exec_()
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packaging guidelines
Hi, ext Graham Cobb wrote: 1) These feel like rules, not guidelines, and some of them are much too strict. If we adopt unnecessary rules then what will happen is that people will set up alternative repositories which do not have any rules (or any QA process), and many developers will just migrate to the alternative repository. Much better to have the minimum necessary rules, simple and quick process, and human judgement to assess the risk of violation of the guidelines. By all means create guidelines which are recommendations, but keep the number of actual rules to the absolute minimum necessary. I agree, and this was the reason for not calling it policy. The guidelines mention special requirements, which you should consider, packaging for Maemo. I think these guidelines help to give a bit more detailed overview, of what you should look at if packaging an application or testing it for extras. The human judgement is still necessary, if you consider something as a blocker or not to vote up or down. Further this is a start. As I wrote in my blog, the discussion is open and appreciated, and in my opinion it is easier to start a discussion, having some basis to discuss about. 2) It is not clearly specified what is the scope of these guidelines. I assume that the plan is that packages for Maemo Extras (free or not free) will not be accepted if they do not conform to these rules, with no exceptions. If that is the case, then the rules need to say so. Note that there are several other possible interpretations: - The rules could apply to all packages which are to be listed in Maemo Downloads, even if they are from external repositories. - The rules could apply to all packages submitted to the autobuilder. - The rules could be intended to apply to all packages which can ever be installed on a Maemo system (this is currently unenforceable but that could be the intent). - The rules could only apply to user-visible packages, not all packages in the repository. - The rules could really be guidelines: in other words they should normally be followed but exceptions will be allowed if some people (who?) can be convinced there is a valid reason. If this is not the case, the document should be renamed to Requirements instead of Guidelines. Some kind of packaging policy was requested by the community since a long time already. I share your opinion that we have to be careful, that it won't get too restricted. But these questions are exactly, what I'm glad to see being discussed here. The packaging policy before was maintained by Nokia, but in my opinion it is most valuable for the community. So let's find some solution in a discussion on this list. I would go for your last point and the intend were guidelines and not to create requirements . But I think partially there is a little misunderstanding: I didn't set the guidelines, as it was mentioned in some other mails, I just had the task to push that forward that the discussion can be started. 3) Differences between corresponding Maemo and Debian packages . This requirement should be deleted. There are many very reasonable reasons for incompatible differences between package X in Maemo and in Debian. Some examples: - Libraries compiled with different options because different features or dependencies are available in Maemo - Libraries with capabilities disabled because the porter is not using those features and hence cannot test them - Applications with features disabled because the porter has not got around to porting them - Applications with features disabled because they aren't relevant use cases on a Maemo device or cannot work effectively on a Maemo device Note that not even Nokia-supplied system libraries comply with this requirement! But in those cases it says, that you can set the bug as a WONTFIX for obvious reasons. So I see it more as a description of the common practice. 4) Maemo packages that are not yet in Debian. This is not a requirement Maemo should or can impose and should be deleted. There are no requirements on what is made available in any VCS, only that the source package is uploaded for free packages. Note that in GPE, I do choose to include the Maemo packaging in the /debian directories in SVN, but that the Debian packager explicitly insists that they be removed before tar files are exported, as he has his own packaging directories and does not want /debian directories from upstream interfering with the real debian packaging! 5) Separating files into binary packages. This should say: If this requires packaging the sources differently from the upstream distribution (Debian), the packaging changes MAY be propagated back to upstream. Maemo packaging should not require any changes to upstream packaging -- it is entirely up to the Maemo package maintainer, and nothing to do with the Maemo community, if the maintainer wishes to try to
Re: PyQt ForegroundRole
Not a 100% sure, but I think this is due to the QMaemo5 style implementation
you are not able to do it.
Think Ive faced the issue before.
Is there a chance you could try with a delegate for your columns, thats worked
for me.
Implementing the paint().
P.S. i dont use python, I use C++, hence I didnt paste the example.
cheers,
Ram
- Original Message -
From: SC
Sent: 04/29/10 11:16 AM
To: maemo-developers@maemo.org
Subject: PyQt ForegroundRole
Hello, I've been struggling getting ForegroundRole
http://doc.trolltech.com/4.6/qt.html to work properly so I can change the text
color of certain cells in QTableView.
I took an example from http://www.daniweb.com/forums/thread191210-7.html
http://www.daniweb.com/forums/thread191210-7.html and added the following in
the data(...) method:
elif role == Qt.ForegroundRole:
return QBrush(QColor(255, 0, 0))
When I run it on my Windows PC, the font color is set to red for all the cells
but does not seem to have an effect on my N900.
Is there any Maemo-specific calls that I am missing here?
# http://www.daniweb.com/forums/thread191210-7.html
http://www.daniweb.com/forums/thread191210-7.html
import operator
from PyQt4.QtCore import *
from PyQt4.QtGui import *
class MyWindow(QWidget):
def __init__(self, data_list, header, *args):
QWidget.__init__(self, *args)
# setGeometry(x_pos, y_pos, width, height)
self.setGeometry(300, 200, 420, 250)
self.setWindowTitle(Exploring PyQT's QTableView)
table_model = MyTableModel(self, data_list, header)
table_view = QTableView()
table_view.setModel(table_model)
# enable sorting
table_view.setSortingEnabled(True)
layout = QVBoxLayout(self)
layout.addWidget(table_view)
self.setLayout(layout)
class MyTableModel(QAbstractTableModel):
def __init__(self, parent, mylist, header, *args):
QAbstractTableModel.__init__(self, parent, *args)
self.mylist = mylist
self.header = header
def rowCount(self, parent):
return len(self.mylist)
def columnCount(self, parent):
return len(self.mylist[0])
def data(self, index, role):
if not index.isValid():
return QVariant()
# -
# Works on Windows PC but not on N900
# -
elif role == Qt.ForegroundRole:
return QBrush(QColor(255, 0, 0))
elif role != Qt.DisplayRole:
return QVariant()
return QVariant(self.mylist[index.row()][index.column()])
def headerData(self, col, orientation, role):
if orientation == Qt.Horizontal and role == Qt.DisplayRole:
return QVariant(self.header[col])
return QVariant()
def sort(self, col, order):
sort table by given column number col
self.emit(SIGNAL(layoutAboutToBeChanged()))
self.mylist = sorted(self.mylist,
key=operator.itemgetter(col))
if order == Qt.DescendingOrder:
self.mylist.reverse()
self.emit(SIGNAL(layoutChanged()))
header = ['First Name', 'Last Name', 'Age', 'Weight']
# a list of (name, age, weight) tuples
data_list = [
('Heidi', 'Kalumpa', '36', '127'),
('Frank', 'Maruco', '27', '234'),
('Larry', 'Pestraus', '19', '315'),
('Serge', 'Romanowski', '59', '147'),
('Carolus', 'Arm', '94', '102'),
('Michel', 'Sargnagel', '21', '175')
]
app = QApplication([])
win = MyWindow(data_list, header)
win.show()
app.exec_()
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Meaning of Phone.Net.get_current_cell_info return values
On 29 April 2010 10:34, chantra chan...@debuntu.org wrote: Hi Dawid, Yes I did a while back, and that sorted me out with get_registration_status reply. I've just looked into it as well and you're right. For some reason get_current_cell_info method call returns different value for that field. :-o Perhaps it has different meaning, or perhaps it's some kind of bug in the method itself? Hard to tell when there's not much documentation about this around... I've asked NetMon's app author about it, maybe he will have some clues. -- Dawid 'evad' Lorenz * http://adl.pl null://google 'no evil' mail has taken away my random signatures ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
osso-abook
Hi I am having troubles when I am trying to fetch sms -field from addressbook. My code is straight from there: http://wiki.maemo.org/PyMaemo/Accessing_APIs_without_Python_bindings and I don't have a clue how I can do anything except fetch the name. Does someone have a good tip for me? There seems to be multiple possibilities in the api but I haven't succeeded with couple I tried. Thanks in advantage! Ossipena/TimoP ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo Extas Builder / QT
I have ported Paulo Cesar's Macuco to the N900 and I am having the hardest time submitting it to the autobuilder. It is the first time I try this so please don't mind if I am missing something obvious. I think some of my problems may be related to the transition to PR1.2 but once I got it working on my n900 I imagine I should be able to get it out to the autobuilder. To make it work on my n900 I have to use the libqt4-maemo5 packages. I assume to make it work on the PR1.2 I should use the libqt4-dev packages. Should I just wait for the PR1.2 to be out before? Regardless I can't make the autobuilder compile it (using qmake from either set). It always fails like this: make[1]: Entering directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/usr/share/qt4/mkspecs/linux-g++-maemo5/qmake.conf' , needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' or make[1]: Entering directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/opt/qt4-maemo5/mkspecs/linux-g++-maemo5/qmake.conf ', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' References: https://garage.maemo.org/builder/fremantle/macuco2_0.0.2-1/ https://garage.maemo.org/builder/fremantle/macuco2_0.0.5-1/ I can only imagine I am missing something but can't find what. Any help will be greatly appreciated. Thanks, Felipe ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
GSoC 2010, eBook reader. Looking for feedback and ideas.
Hello, I've been lucky enough to get accepted to Google Summer of Code 2010 and my project is to develop an eBook reader for Maemo 5 with Qt 4.6. Coding starts May 24 and before that we have a Community Bonding period so I'm looking for ideas and feature requests. Would be nice to also get comments from people who have worked on eBook readers themselves. Anyway the purpose of this post is just to get some conversation started so I can start planning ahead. My original proposal can now be found at http://durriken.org/gsoc/. Juhana Jauhiainen ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Extas Builder / QT
Hi 2010/4/29 Felipe Crochik fel...@crochik.com I have “ported” Paulo Cesar’s Macuco to the N900 and I am having the hardest time submitting it to the autobuilder. It is the first time I try this so please don’t mind if I am missing something obvious… Have you defined build dependencies in your debian/control file? Something like this Build-Depends: debhelper (= 5), libqt4-dev (= 4.6.0) -Timo I think some of my problems may be related to the transition to PR1.2 but once I got it working on my n900 I imagine I should be able to get it out to the autobuilder. To make it work on my n900 I have to use the libqt4-maemo5 packages. I assume to make it work on the PR1.2 I should use the libqt4-dev packages. Should I just wait for the PR1.2 to be out before? Regardless I can’t make the autobuilder compile it (using qmake from either set). It always fails like this: make[1]: Entering directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/usr/share/qt4/mkspecs/linux-g++-maemo5/qmake.conf', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' or make[1]: Entering directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/opt/qt4-maemo5/mkspecs/linux-g++-maemo5/qmake.conf', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' References: https://garage.maemo.org/builder/fremantle/macuco2_0.0.2-1/ https://garage.maemo.org/builder/fremantle/macuco2_0.0.5-1/ I can only imagine I am missing something but can’t find what. Any help will be greatly appreciated. Thanks, Felipe ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Extas Builder / QT
Hi Yes, I did. On one of them like this: Build-Depends: debhelper (= 5), libqt4-maemo5-dev, libqt4-maemo5-webkit, libqt4-maemo5-xmlpatterns And on the other one like this: Build-Depends: debhelper (= 5), libqt4-dev Thanks, Felipe _ From: Timo Härkönen [mailto:timop.harko...@gmail.com] Sent: Thursday, April 29, 2010 12:27 PM To: Felipe Crochik Cc: maemo-developers@maemo.org Subject: Re: Maemo Extas Builder / QT Hi 2010/4/29 Felipe Crochik fel...@crochik.com I have ported Paulo Cesars Macuco to the N900 and I am having the hardest time submitting it to the autobuilder. It is the first time I try this so please dont mind if I am missing something obvious Have you defined build dependencies in your debian/control file? Something like this Build-Depends: debhelper (= 5), libqt4-dev (= 4.6.0) -Timo I think some of my problems may be related to the transition to PR1.2 but once I got it working on my n900 I imagine I should be able to get it out to the autobuilder. To make it work on my n900 I have to use the libqt4-maemo5 packages. I assume to make it work on the PR1.2 I should use the libqt4-dev packages. Should I just wait for the PR1.2 to be out before? Regardless I cant make the autobuilder compile it (using qmake from either set). It always fails like this: make[1]: Entering directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/usr/share/qt4/mkspecs/linux-g++-maemo5/qmake.conf' , needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' or make[1]: Entering directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/opt/qt4-maemo5/mkspecs/linux-g++-maemo5/qmake.conf ', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' References: https://garage.maemo.org/builder/fremantle/macuco2_0.0.2-1/ https://garage.maemo.org/builder/fremantle/macuco2_0.0.5-1/ I can only imagine I am missing something but cant find what. Any help will be greatly appreciated. Thanks, Felipe ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSoC 2010, eBook reader. Looking for feedback and ideas.
On 29 April 2010 09:24, Juhana Jauhiainen juhana.jauhiai...@gmail.com wrote: Hello, I've been lucky enough to get accepted to Google Summer of Code 2010 and my project is to develop an eBook reader for Maemo 5 with Qt 4.6. Coding starts May 24 and before that we have a Community Bonding period so I'm looking for ideas and feature requests. Would be nice to also get comments from people who have worked on eBook readers themselves. Anyway the purpose of this post is just to get some conversation started so I can start planning ahead. My original proposal can now be found at http://durriken.org/gsoc/. Juhana Jauhiainen Yup, I've noticed you got accepted and I really like the idea of an eBook reader for the N900. FBReader is there, but it's quite rough. Anyway... I am about to get an eBook reader next week and I've been reading about Ebook readers quite a lot lately. What seems to be important is the font. The default font has to be really nice on the N900 screen and look gorgeous and easy to read on the chosen background. Of course, one has to be able to choose, but the default one has to be the one most people will use. So please, take particular care on choosing it. Second, I don't know (I'll read the proposal later today) if you've already had a thought about this, but will you be using regular text (i.e. normal font rendering by Pango) or will you be looking at handling the fonts yourself? I know the font topic is a huge one and handling them properly from scratch is quite though, but a graphic reader with nice rendered font, will sure make the reading experience awesome and pleasant. Last, how do you plan to swipe through pages? Gestures, overlay buttons (a la PDF reader) or continuous read? -- anidel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSoC 2010, eBook reader. Looking for feedback and ideas.
On Thu, Apr 29, 2010 at 10:00 PM, Aniello Del Sorbo ani...@gmail.com wrote: Second, I don't know (I'll read the proposal later today) if you've already had a thought about this, but will you be using regular text (i.e. normal font rendering by Pango) or will you be looking at handling the fonts yourself? To make the schedule realistic (and future maintainability reasons), I think letting Qt handle all of this is the way to go. It doesn't hurt that the app can be easily ported to other platforms either. -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: git over ssh access for garage projects - calling for brave testers
Ferenc Szekely wrote: If you had a few minutes to spare please check it out and let me know your findings. We may have some bugs here and there, so let's find and fix them together. I get this: ma...@portatie:/tmp$ git clone ssh://drop.maemo.org/git/maemo-mapper Initialized empty Git repository in /tmp/maemo-mapper/.git/ fatal: ''/git/maemo-mapper'': unable to chdir or not a git archive fatal: The remote end hung up unexpectedly Ciao, Alberto -- http://blog.mardy.it - geek in un lingua international! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSoC 2010, eBook reader. Looking for feedback and ideas.
On Apr 29, 2010, at 12:24 PM, Juhana Jauhiainen wrote: Hello, Howdy! I've been using FBReader on Maemo since the earliest days of the 770, and I've read hundreds of books on my Maemo devices over the past 5 years. So book reading is something rather near to my heart. ;) First and foremost you need two things: good format handling and good formatting options. Implementing format handling from-scratch is going to be a herculean undertaking, so I wonder if you could've borrow FBReader's handling (as their format support is strong and fairly extensive). As that not only gives you a lot of quality format support, but also a long-term solution to format handling (assuming you don't have to deviate overly far from their code to implement it). As for formatting, having easily configurable formatting options is important to ensuring that all of your users can get their optimal experience. This is one area where devices like Kindle and iPad fall flat on their faces (setting the default margin to 1 always seemed rather insane to me). Again, this is another area where I would mostly just borrow from FBReader (options, not code ;)), but see if it can't be implemented in a more mobile-friendly manner. Having a number of useful default profiles will help here. FBReader's greatest strength is also its greatest weakness, so having a native book reader would be a very welcome change! -- Ryan Abel Maemo Community Council member ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Extas Builder / QT
I have some progress to report but still can use some help: The problem seems to start when I run qmake on scratchbox it adds the full path to the qt headers on the Makefile and I end up with: . INCPATH = -I/targets/FREMANTLE_ARMEL/opt/qt4-maemo5/mkspecs/linux-g++-maemo5 -I. -I/targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore By manually removing /targets/FREMANTLE_ARMEL from the Makefile I can get it to compile on my machine and also on the autobuilder. How should I proceed to create the Makefile from the .pro file? Are there any arguments that I should pass to qmake to avoid it including /targets/FREMANTLE_ARMEL to the paths? What did I miss? Thanks again, Felipe _ From: Timo Härkönen [mailto:timop.harko...@gmail.com] Sent: Thursday, April 29, 2010 12:27 PM To: Felipe Crochik Cc: maemo-developers@maemo.org Subject: Re: Maemo Extas Builder / QT Hi 2010/4/29 Felipe Crochik fel...@crochik.com I have ported Paulo Cesars Macuco to the N900 and I am having the hardest time submitting it to the autobuilder. It is the first time I try this so please dont mind if I am missing something obvious Have you defined build dependencies in your debian/control file? Something like this Build-Depends: debhelper (= 5), libqt4-dev (= 4.6.0) -Timo I think some of my problems may be related to the transition to PR1.2 but once I got it working on my n900 I imagine I should be able to get it out to the autobuilder. To make it work on my n900 I have to use the libqt4-maemo5 packages. I assume to make it work on the PR1.2 I should use the libqt4-dev packages. Should I just wait for the PR1.2 to be out before? Regardless I cant make the autobuilder compile it (using qmake from either set). It always fails like this: make[1]: Entering directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/usr/share/qt4/mkspecs/linux-g++-maemo5/qmake.conf' , needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder2/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.5' or make[1]: Entering directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' make[1]: *** No rule to make target `/targets/FREMANTLE_ARMEL/opt/qt4-maemo5/mkspecs/linux-g++-maemo5/qmake.conf ', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/macuco2-0.0.2' References: https://garage.maemo.org/builder/fremantle/macuco2_0.0.2-1/ https://garage.maemo.org/builder/fremantle/macuco2_0.0.5-1/ I can only imagine I am missing something but cant find what. Any help will be greatly appreciated. Thanks, Felipe ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSoC 2010, eBook reader. Looking for feedback and ideas.
On Apr 29, 2010, at 6:23 PM, Aniello Del Sorbo wrote: Ryan, how often do you read e-book in portrait mode on the tablets? 99% of the time I use it in portrait mode, except for a short stretch after Maemo 5 was first released when the volume keys wouldn't scroll. ;) The volume rocker is just to useful for paging not to use it in portrait. Also: less wasted screen space in portrait. -- Ryan Abel Maemo Community Council member ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSoC 2010, eBook reader. Looking for feedback and ideas.
On Fri, Apr 30, 2010 at 1:09 AM, Ryan Abel rabe...@gmail.com wrote: Implementing format handling from-scratch is going to be a herculean undertaking, so I wonder if you could've borrow FBReader's handling Okular (that happens to be a Qt program) also has format handling code, including support for epub. I don't think format support is hugely important in the end, as you can convert between formats with a program like calibre. -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
