Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 7 hrs, 45 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 20 hrs ago - more...
| The Following User Says Thank You to lcuk For This Useful Post: | ||
 |
|
2009-04-11
, 01:12
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#52
|
Originally Posted by lcuk
Nokia's plan is less for tablet/desktop compatibility than it is for tablet/S60 compatibility.
the ONLY problem ive got with qt and cross platform is that on the whole GUI apps from desktop software simply does not fit on the tablet.
__________________
Ryan Abel
Ryan Abel
| The Following 3 Users Say Thank You to GeneralAntilles For This Useful Post: | ||
 |
|
2009-04-11
, 03:53
|
|
Posts: 2,869 |
Thanked: 1,784 times |
Joined on Feb 2007
@ Po' Bo'. PA
|
#53
|
Originally Posted by GeneralAntilles
Not exactly on this topic but what I have been thinking lately is...
Nokia's plan is less for tablet/desktop compatibility than it is for tablet/S60 compatibility.
A way to attract new users of the new device directly to maemo.org would be to have a desktop app like TightVNC tested, polished, and available from close to day one that would allow Windows and the newer Linux flavors to easily interact with the new device.
|
|
2009-04-11
, 04:41
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#54
|
Originally Posted by YoDude
Just one? That thing's going up in flames.
A way to attract new users of the new device directly to maemo.org would be to have a desktop app like TightVNC tested, polished, and available from close to day one that would allow Windows and the newer Linux flavors to easily interact with the new device.
Seriously, though, VNC is pretty bandwidth heavy which is a weight you really don't want to have when people are unboxing new tablets and trying to download software. I don't see us being able to get the 100s of tablets that'd be needed to run live demos for everybody on the internet.
A good, easy to use, lightweight SDK would be a better option.
__________________
Ryan Abel
Ryan Abel
Last edited by GeneralAntilles; 2009-04-11 at 04:44.
 |
|
2009-04-11
, 06:09
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#55
|
Bandwidth heavy AND slow 
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
|
|
2009-04-11
, 06:25
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#56
|
Originally Posted by GeneralAntilles
What happened to http://sdk-ami.garage.maemo.org/ ? EC2 sure does seem a reasonable choice for an on-demand horde of emulated devices over the net, and it's not going to bankrupt Nokia either.
Seriously, though, VNC is pretty bandwidth heavy which is a weight you really don't want to have when people are unboxing new tablets and trying to download software. I don't see us being able to get the 100s of tablets that'd be needed to run live demos for everybody on the internet.
A good, easy to use, lightweight SDK would be a better option.
| The Following User Says Thank You to attila77 For This Useful Post: | ||
|
|
2009-04-11
, 06:29
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#57
|
Originally Posted by lcuk
Qt has been focusing on tablets through Qtopia previously, that's why no 'direct' support for Qt on tablets. Not sure about the future roadmap as Qtopia/QtEmbedded is no longer an option, but if you did your app the 'proper' way, Model-View-Controller style, the only thing you need to redo are the dialogs and almost none of the functionality itself - which *is* a major gain.
the ONLY problem ive got with qt and cross platform is that on the whole GUI apps from desktop software simply does not fit on the tablet.
I'm not talking about scalable lists and things, i mean in the amount of information a desktop app typically tries to display.
so if you need to write the app again anyway, so it doesnt really matter what you use
| The Following 2 Users Say Thank You to attila77 For This Useful Post: | ||
 |
|
2009-04-11
, 07:45
|
|
Posts: 1,635 |
Thanked: 1,816 times |
Joined on Apr 2008
@ Manchester, England
|
#58
|
Originally Posted by attila77
of course, and thats the same no matter which toolkit you choose.
Qt has been focusing on tablets through Qtopia previously, that's why no 'direct' support for Qt on tablets. Not sure about the future roadmap as Qtopia/QtEmbedded is no longer an option, but if you did your app the 'proper' way, Model-View-Controller style, the only thing you need to redo are the dialogs and almost none of the functionality itself - which *is* a major gain.
I think the General hit the nail on the head though:
Originally Posted by GeneralAntilles
thats a pretty damned good reason in my book
Nokia's plan is less for tablet/desktop compatibility than it is for tablet/S60 compatibility.
__________________
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk
|
|
2009-04-11
, 08:50
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#59
|
Originally Posted by lcuk
One tiny note - Qt has the history going a long way to make itself not only platform agnostic, but how should I put it, platform friendly. Regardless of what you do, Qt will try to do it in a way that is native for that particular platform, not only try to 'get away with it'. Others try this as well, of course, but IMHO Qt does this to a much greater extent than any other toolkit/framework I had tried (GTK, wxWidgets), so your programs not only run (and look decent) on different platforms, but they actually *behave* like native applications without too much effort. YMMV, of course. This is also the reason why I think (or at least hope
of course, and thats the same no matter which toolkit you choose.
) it has good chances making a real impact on S60.
| The Following 2 Users Say Thank You to attila77 For This Useful Post: | ||
 |
|
2009-04-11
, 17:59
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#60
|
To chime in on the finger-vs-stylus debate.
For the majority of use cases, I believe that the finger is more than suitable for mobile use with an appropriately designed UI. Even in the case of apps that require precision at times (ie. web browser/text-editor/etc with small text), a properly designed UI can compensate and doesn't *need* a stylus (eg. iPhone/Pre/Android/etc). In fact, I'd say that the consequences of including a stylus far outweigh its rather limited benefits.
I've noticed that there are very few use cases that require the precision of a stylus for their operation when a finger just wont do. Of these are drawing apps, and handwriting recognition -- a tiny fraction of overall use cases (who uses handwriting recognition anyway?).
That said, I hope the stylus is eliminated from the next Tablet, available only in add-on form.
There are some advantages to eliminating with the stylus:
1) Capacitive touch is an option - Higher durability, brighter screen, with higher finger accuracy -- potential for multi-touch (novel, but useful in certain cases)
2) Smaller device form factor (no internal housing for stylus)
3) Incentive for much-more finger-friendly apps
4) One less thing to lose
Having the stylus attached leads to apps that require one more step that I should not have to contend with while on the go.
YARR!
}:^)~
Bonjour, Corrupt
For the majority of use cases, I believe that the finger is more than suitable for mobile use with an appropriately designed UI. Even in the case of apps that require precision at times (ie. web browser/text-editor/etc with small text), a properly designed UI can compensate and doesn't *need* a stylus (eg. iPhone/Pre/Android/etc). In fact, I'd say that the consequences of including a stylus far outweigh its rather limited benefits.
I've noticed that there are very few use cases that require the precision of a stylus for their operation when a finger just wont do. Of these are drawing apps, and handwriting recognition -- a tiny fraction of overall use cases (who uses handwriting recognition anyway?).
That said, I hope the stylus is eliminated from the next Tablet, available only in add-on form.
There are some advantages to eliminating with the stylus:
1) Capacitive touch is an option - Higher durability, brighter screen, with higher finger accuracy -- potential for multi-touch (novel, but useful in certain cases)
2) Smaller device form factor (no internal housing for stylus)
3) Incentive for much-more finger-friendly apps
4) One less thing to lose
Having the stylus attached leads to apps that require one more step that I should not have to contend with while on the go.
YARR!
}:^)~
Bonjour, Corrupt
| The Following 2 Users Say Thank You to Capt'n Corrupt For This Useful Post: | ||
 |
| Tags |
| dismantle, fremantle, fremantle summary, kate alhola, kool-aid, no soup for you, presentation, to sylus or not to stylus |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 01:27.
I'm not talking about scalable lists and things, i mean in the amount of information a desktop app typically tries to display.
it means that qt works really well across the similar platforms - basically a desktop setting, but as soon as it gets down to this size the paradigm breaks down.
so if you need to write the app again anyway, so it doesnt really matter what you use
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk