Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 9 hrs, 55 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 13 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 2 hrs ago -
n770 youtube video (0)
to General by nmdv - 6 days, 1 hr ago - more...
 |
|
2009-04-28
, 21:43
|
|
Posts: 600 |
Thanked: 742 times |
Joined on Sep 2008
@ England
|
#22
|
From the Hildon Interface Guidelines, I don't think the two-touch has been mentioned before:
Interesting! And it can be done with a resistive touch screen because it's looking for a "jump" in position without a finger being lifted.
Now here's a possible hardware tidbit, although it may just be noise:
I'm trying to imagine which pocket-sized form factor would have an always-present keyboard with an 800x480 screen.
I also enjoyed the suggestion on the last page to design the interface using a thick blunt crayon rather than a sharp pencil. I get a mental image of a roomful of five-year-olds with their crayon sets busy designing Hildon interfaces.
Regards,
Roger
A two-touch happens when the user taps down with a finger and just after that, without lifting the finger, taps another position with another finger. The two-touch can be used to activate context sensitive menu.
Now here's a possible hardware tidbit, although it may just be noise:
Many devices feature a keyboard either always present or a slide-out one.
I also enjoyed the suggestion on the last page to design the interface using a thick blunt crayon rather than a sharp pencil. I get a mental image of a roomful of five-year-olds with their crayon sets busy designing Hildon interfaces.
Regards,
Roger
 |
|
2009-04-28
, 21:48
|
|
Posts: 236 |
Thanked: 149 times |
Joined on Jul 2007
@ Finland
|
#23
|
The two-touch is a nice touch, although only time will tell if it'll end up like the pressure sensitivity of the screen. Anyway, it's great they're trying new things and trying to make the best of the current technologies....
Last edited by Naranek; 2009-04-28 at 21:51.
Originally Posted by eiffel
Maybe a device that folds in two so that you need to open it to use the screen. That way you'd have the keyboard there when ever you can see the screen.
I'm trying to imagine which pocket-sized form factor would have an always-present keyboard with an 800x480 screen.
Last edited by Naranek; 2009-04-28 at 21:51.
| The Following User Says Thank You to Naranek For This Useful Post: | ||
 |
|
2009-04-28
, 22:10
|
|
Posts: 903 |
Thanked: 632 times |
Joined on Apr 2008
|
#24
|
Originally Posted by benny1967
I haven't installed any Alpha or Beta SDK's, but... until we see what is actually involved in porting an application, I wouldn't assume anything.
Mhm... Actually yes, I always thought they were excellent examples of good ports, that's why I mentioned them in this context.
Anyway, forget those two:
My point was that it's getting even more difficult than it is today if you want to do it right. (And I hope developers want to do The Right Thing.)
The menus may be the most evident example: It'll not be enough to transfer them from horizontal to vertical and remove icons, you'll need to re-design the whole UI from scratch if the original application has more than 10 menu items and some sub-menus.
[snip]
Right now it usually takes just a few lines of code to reparent the menu. In fact, most of the time it's like just taking the gtk.Menu() and adding it to the window (.set_menu()) instead of the menubar. I would not be at all surprised if 95% of the hildonization of the menu is automatic in Fremantle.
 |
|
2009-04-28
, 22:26
|
|
Posts: 794 |
Thanked: 784 times |
Joined on Sep 2007
@ /Canada/Ontario/GTA
|
#25
|
Originally Posted by qgil
Thanks for clarifying! It was just wishful thinking on my part.
Hold on. Today we had an SDK beta release, that will be a more solid beta in one month. "Beta SDK" refers to the platform components providing APIs and the SDK tool itself. But if you are talking about 'new devices brought to you' you need to take into account the components tied to the hardware that are not published in the SDK and the applications that are equally missing there.
This beta is out now because we (and you) wanted to give as much time as possible to application developers to have their software ready for the final release.
This beta is also out now because we (and you) wanted to support the Mer project aka Fremantle community edition for N800/N810 giving them as much time as possible to work.
|
|
2009-04-29
, 01:44
|
|
Posts: 1,097 |
Thanked: 650 times |
Joined on Nov 2007
|
#26
|
Originally Posted by Naranek
You mean like a Clamshell (as in the Zaurus style) ?
The two-touch is a nice touch, although only time will tell if it'll end up like the pressure sensitivity of the screen. Anyway, it's great they're trying new things and trying to make the best of the current technologies....
Maybe a device that folds in two so that you need to open it to use the screen. That way you'd have the keyboard there when ever you can see the screen.
|
|
2009-04-29
, 02:56
|
|
Posts: 68 |
Thanked: 63 times |
Joined on Sep 2008
|
#27
|
Originally Posted by eiffel
A plain slate tablet with a split keyboard flanking the display like some of Samsung's and Wibrain's UMPCs. It would be a bit long but it might be possible to make it fit in a pocket.
I'm trying to imagine which pocket-sized form factor would have an always-present keyboard with an 800x480 screen.
 |
|
2009-04-29
, 06:58
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#28
|
Originally Posted by qole
Sorry if that disappointed you. On the other hand, let me remind you that if we would follow your desired schedule probably yourself and surely others would...
[I]pffffffffffffft....
blame us for not thinking about the developers giving them the time and the means to have their apps ready before sales start. And not thinking about the users missing dditional applications to install and expand their usage of the device.
blame us for throwing a release out without giving time to have a Extras community process in place and therefore upsetting users for offering them some apps that have installation problem, crash, drain batteries and so on.
probably also blame us for the quality of the software in the first release. Think that the frozen API is also frozen for ouselves.
Then somebody would go down to the us not-learning, not-getting-it and so on.
You want everything and you want it now. That's fine... but we have our timing and priorities to deliver stuff.
If you want to help to have better products sooner a good way to do it is to come up with great applications and a way to make them move from extras-devel to extras-testing and extras, rwaching good and stable quality at the end exposed to Maemo 5 users.
| The Following 7 Users Say Thank You to qgil For This Useful Post: | ||
 |
|
2009-04-29
, 07:12
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#29
|
Quim, I never blame Nokia for anything, and I never complain. It's always those other guys. I'm all sweetness and light.
And if I ever said anything that sounded like a complaint, I'm so sorry.
I will never complain again.
Can I have my device now?
(An addict will say anything to get a fix.
)
And if I ever said anything that sounded like a complaint, I'm so sorry.
I will never complain again.
Can I have my device now?
(An addict will say anything to get a fix.
)
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2009-04-29
, 11:17
|
|
Posts: 605 |
Thanked: 137 times |
Joined on Nov 2005
@ La Rochelle, France
|
#30
|
Originally Posted by kanishou
It looks like the AboutDialog from gtk is not supported ...
You can still use standard Gtk menus with sub-menus, it is just not recommended.
Applications designed for the new UI guidelines are very slick, but you can still use all traditional Gtk elements to make ports easier. If something behaves in a totally incompatible way, then it has been implemented as a new Hildon widget instead of changing Gtk functionality. Dialogs are probably the biggest case of changed functionality, but they should generally still work ok without changes.
That's the sound of my high hopes being drained of air.
Thanks for the buzzkill. I was looking forward to a very nice Summer Solstice / Father's Day.
fanoush is going to win, isn't he?
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
Last edited by qole; 2009-04-28 at 21:43.