Le 01/10/2013 22:23, Jim Donegan a écrit :
Hi all.
Yes indeed - totally agree. I've not contributed here thus far as I know you
guys are busy working to a deadline but I have followed your progress and have
to say it's looking really good.
Power to yer collective elbows!
Thank you Jim and N
The options qmlscene used are passed onto Qt itself, so the solution
for Python is the same. You need to become the phablet user as
indicated, and provide the respective file and option to Qt, in
whatever way PyQt does it.
On Mon, Sep 30, 2013 at 1:43 AM, Roberto Colistete Jr.
wrote:
> I have
Hi all.
Yes indeed - totally agree. I've not contributed here thus far as I know you
guys are busy working to a deadline but I have followed your progress and have
to say it's looking really good.
Power to yer collective elbows!
Jim Donegan
Sent from my iPhone
> On 1 Oct 2013, at 21:20, Nath
On 10/01/2013 09:43 AM, Didier Roche wrote:
Part 2 on the exciting image release plan of the day!
Didier,
Frankly, these kinds of updates are absolutely the most valuable I've
ever seen as per tracking the progress and health of the project. It's
extremely valuable to have an overhead view
FYI, I've attached a simple script to add "datapart=/dev/mmcblk0p10" to the
"cmdline" for tilipia.
On Tue, Oct 1, 2013 at 12:34 PM, Darren Paxton wrote:
> Brilliant News, Ken.
>
> charging my Tilapia as we speak to get it up and running.
>
> Darren Paxton
> Staticwave
>
>
>
>
> On Tue, Oct 1, 20
Brilliant News, Ken.
charging my Tilapia as we speak to get it up and running.
Darren Paxton
Staticwave
On Tue, Oct 1, 2013 at 8:31 PM, Ken Harris wrote:
>
>
> I got tilipia to boot! Ubuntu Touch looks great!
>
> I added "datapart=/dev/mmcblk0p10" to the "cmdline". This is a
> workaround,
I got tilipia to boot! Ubuntu Touch looks great!
I added "datapart=/dev/mmcblk0p10" to the "cmdline". This is a workaround,
but indicates that the problem is in the /dev partition.
In "initrd" , /scripts/touch , in "mountroot", it searches /dev for
""userdata UDA DATAFS USERDATA" , when it does
Hey everyone.
Part 2 on the exciting image release plan of the day!
Some good news:
* the regressions on mediaplayer-app and camera-app were tracked down
(It was as deep as in the initramfs!). We are waiting on an android
rebuild to get everything we need in. Then only we can start rebuilding
It is now possible to build android emulator, and launch it from the
phablet checkout.
It is using goldfish kernel as packaged in the Ubuntu Archive, and
builds everything else from scratch.
It's not packaged at the moment, but you can build & run it locally:
(in the phablet-dev-bootstrap setted u
Hi guys, just a heads-up about this interesting article
http://dot.kde.org/2013/09/25/frameworks-5 about how the KDE guys are
splitting the old kdelibs into bits and pieces that are easier to reuse.
This means using some small part of KDE Frameworks does not involve pulling
tons of dependencies
Hey all.
Here are the latest image on the touch image front side
* We got multiple builds overnight to handle and test image upgrade (71,
72, 73, 74). We got as planned the new media running on hardware landed
\o/. system-images is in as well (but from our testing, it seems that we
don't have
On 01.10.2013 10:35, Sam Bull wrote:
> When running our app on the phone, it uses the size specified in the
> QML, and the app is displayed too small or too big for the phone screen.
>
> We are running this through C++, so my first thought is that qmlscene
> overrides the sizes (as we are using th
I have the same problem, but the other way around: In qmlviewer the size is
incorrect (uses the size specified in QML), but when run from C++ it's OK (fits
the screen). I used the QML2 example from QtCreator, maybe you want to look
into that. It has some strange wrapper class included.
Still pu
When running our app on the phone, it uses the size specified in the
QML, and the app is displayed too small or too big for the phone screen.
We are running this through C++, so my first thought is that qmlscene
overrides the sizes (as we are using the same size as clock-app). If
that's correct, i
On Mon, 2013-09-30 at 19:10 -0500, Israel wrote:
> You could shrink the image(if you mean too large in dimensions), and
> export it as a PNG.
Dimensions don't matter, it's set to the correct size for an icon. Qt's
renderer just makes it look awful at small sizes. It looks fine at the
same size in
15 matches
Mail list logo