Sunday, July 20, 2008
Saturday, July 12, 2008
Wednesday, July 09, 2008
Maemo Summit 2008: going to berlin!
Today I have noticed that the Maemo team accepted my sponsorship application for the Maemo Summit 2008 in Berlin, September 19-20!
I was not expecting it. I am very glad about this.
I am still trying to figure out what to actually do there.
My idea was to talk (but not a real talk where you listen and I speak,but rather a session where we both speak, ask and listen) about issues in porting desktop applications to the Maemo platform.
I would like to also underline the importance of evaluating the platform potential before even planning to port the application.
This should lead to a better integration of the application with the Maemo platform.
Porting an application is not only a matter of redefining the UI (even tho this is another extremely important aspect of the porting procedures).
Usually we think about the mobile devices as a cut down version of our desktops.
Even tho it's always true, it is also true that the mobile devices, often, provide more new features that the desktop doesn't or cannot provide at all.
Taking the key aspects of the target platform into the right account when planning a port, is fundamental for the success of the port.
I will refine these ideas during the following weeks.
Looks like it'll be an interesting summer (job hunting in London, Maemo Summit in Berlin and a few conferences/workshops/meeting related to my research).
I was not expecting it. I am very glad about this.
I am still trying to figure out what to actually do there.
My idea was to talk (but not a real talk where you listen and I speak,but rather a session where we both speak, ask and listen) about issues in porting desktop applications to the Maemo platform.
I would like to also underline the importance of evaluating the platform potential before even planning to port the application.
This should lead to a better integration of the application with the Maemo platform.
Porting an application is not only a matter of redefining the UI (even tho this is another extremely important aspect of the porting procedures).
Usually we think about the mobile devices as a cut down version of our desktops.
Even tho it's always true, it is also true that the mobile devices, often, provide more new features that the desktop doesn't or cannot provide at all.
Taking the key aspects of the target platform into the right account when planning a port, is fundamental for the success of the port.
I will refine these ideas during the following weeks.
Looks like it'll be an interesting summer (job hunting in London, Maemo Summit in Berlin and a few conferences/workshops/meeting related to my research).
Wednesday, July 02, 2008
Back on Xournal
UPDATE:
Looks like too many people have the maemo extras-devel repository installed.
They should not. Or at least, they should know what the extras-devel repo is.
The maemo extras-devel repository is intended as a tool for the developer to test out its code before promoting it to the real maemo Extras repository (the one that's pre-configured in your tablet when you buy it, disable).
Today I've uploaded an alpha version of Xournal (packaged for diablo) on the maemo extras-devel repository. Thus, those people got the notification of an update available and went straight to the Application Manager in order to update.
I see here two mistakes:
1) they should have not installed the -devel repository (unless they knew what they were doing)
2) the Application Manager should TELL from WHERE the package is coming from
However, the next release of Xournal HAS NOT YET been released.
And I strongly suggest, whoever has the maemo extras-devel repo installed, to NOT update to the Diablo version yet.
Check out this ITt forum thread for more info.
My post #198 on that thread explain how to solve the issue.
Thank you.
Original post:
Today I noticed that Xournal has been selected as "The Pearl" in the Maemo Downloads section.
Right on time, I would say as this morning I woke up and decided that it's time to upgrade my Maemo SDK to Diablo and re-package Xournal in order to make it appear in the Diablo extras repository.
So, thank you Maemo team for choosing Xournal as the current pearl!
Stay tuned, it shouldn't take too much time.
Looks like too many people have the maemo extras-devel repository installed.
They should not. Or at least, they should know what the extras-devel repo is.
The maemo extras-devel repository is intended as a tool for the developer to test out its code before promoting it to the real maemo Extras repository (the one that's pre-configured in your tablet when you buy it, disable).
Today I've uploaded an alpha version of Xournal (packaged for diablo) on the maemo extras-devel repository. Thus, those people got the notification of an update available and went straight to the Application Manager in order to update.
I see here two mistakes:
1) they should have not installed the -devel repository (unless they knew what they were doing)
2) the Application Manager should TELL from WHERE the package is coming from
However, the next release of Xournal HAS NOT YET been released.
And I strongly suggest, whoever has the maemo extras-devel repo installed, to NOT update to the Diablo version yet.
Check out this ITt forum thread for more info.
My post #198 on that thread explain how to solve the issue.
Thank you.
Original post:
Today I noticed that Xournal has been selected as "The Pearl" in the Maemo Downloads section.
Right on time, I would say as this morning I woke up and decided that it's time to upgrade my Maemo SDK to Diablo and re-package Xournal in order to make it appear in the Diablo extras repository.
So, thank you Maemo team for choosing Xournal as the current pearl!
Stay tuned, it shouldn't take too much time.
Tuesday, June 24, 2008
Diablo has been released!!!
Cool finally they released it!
Going to update.
You can find it the usual place for the n810 and n800.
Here you can find the announcement.
Going to update.
You can find it the usual place for the n810 and n800.
Here you can find the announcement.
Thursday, June 19, 2008
[UPDATED] Maemo: No Java and OpenGL ES support. Official.
UPDATE: Daniel Stone and Quim Gil further explained the status of the OpenGL ES and Java support in the comments to this post.
As they've pointed out, the title of my post is misleading in the sense that FOR NOW there is no support and no plan for it.
The "WONTFIX" part is, thus, temporary.
Daniel also went further and added a new comment to bug #1028
I will leave the original post below unedited.
-- ORIGINAL WRONG POST
This morning, during my usual e-mail check, I had a quick look at Maemo Bug Jar #9 and discovered this list of two bugs marked as RESOLVED: WONTFIX.
[This part is just plain wrong]
Thus, it's official: we won't get either Java and OpenGL ES support on the Nokia's Internet Tablets.
I was expecting it, but it's anyway sad to read that it's confirmed.
As they've pointed out, the title of my post is misleading in the sense that FOR NOW there is no support and no plan for it.
The "WONTFIX" part is, thus, temporary.
Daniel also went further and added a new comment to bug #1028
I will leave the original post below unedited.
-- ORIGINAL WRONG POST
This morning, during my usual e-mail check, I had a quick look at Maemo Bug Jar #9 and discovered this list of two bugs marked as RESOLVED: WONTFIX.
[This part is just plain wrong]
Thus, it's official: we won't get either Java and OpenGL ES support on the Nokia's Internet Tablets.
I was expecting it, but it's anyway sad to read that it's confirmed.
Thursday, May 29, 2008
A-GPS support on the N8x0 is coming with Diablo
Looks like we will finally get really fast fix times, with our tablets, when Diablo will eventually come out.
ITT's forum user "qwerty12" noticed a nice "agps-ui" application to control AGPS on the tablet.
He went on and installed it and it works!
Other (lucky) Diablo (pre-release) users are reporting time to fix in the order of SECONDS!
Can't wait for the release of this new firmware.
ITT's forum user "qwerty12" noticed a nice "agps-ui" application to control AGPS on the tablet.
He went on and installed it and it works!
Other (lucky) Diablo (pre-release) users are reporting time to fix in the order of SECONDS!
Can't wait for the release of this new firmware.
Subscribe to:
Posts (Atom)


