Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 17 hrs, 34 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 18 hrs, 48 mins ago -
Maemo repository (3)
to Community by torsen - 1 day, 10 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 7 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 14 hrs ago - more...
| The Following 2 Users Say Thank You to timsamoff For This Useful Post: | ||
 |
|
2008-08-27
, 17:04
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#142
|
Originally Posted by Texrat
Yeah, I've been told I look like QT before. If only he was known for his good looks and not for his writing.
I swear you look like Quentin Tarantino in that avatar pic.
Just to gasp speak on topic for a moment here....
I really think the whole idea of Hildonization is absurd. Why should we have to modify the interface of each and every app to run on the tablet? There should be a way to "skin" or "theme" the interface of every single GTK app completely and utterly, so that it runs as a tablet app on a tablet and it runs as desktop app on a desktop. And, for that matter, it will run as a media-box app on my remote-controlled media box (usable from the remote control). If the tablet environment has kinetic scrolling, all of the apps that use the toolkit will automatically get kinetic scrolling. If the user finds that annoying, they can turn it off system-wide. One dropdown box will make the entire system "finger friendly" or "stylus friendly" or "keyboard friendly" or "joystick friendly". All GTK apps should just automatically invoke the pop-up keyboard, if that's what you like using....
What am I doing?! Must get off topic again!
I thought "Grindhouse" sucked, but for different reasons than most people did. It was painfully pretentious, and I got sick of the broad winks they kept giving the audience.
__________________
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!
| The Following 4 Users Say Thank You to qole For This Useful Post: | ||
|
|
2008-08-27
, 17:19
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#143
|
Originally Posted by qole
While I like the idea I believe it to be near impossible. You are talking about a completely seamless integration for all apps to inter-cooperate... which means that everything from your Tablet, to your Laptop, to your TV, Microwave and VCR would all be based on one specific environment.. and then all apps written for that code-base. Apple and Windows do this.. they have 1 interface/kernel and then everything they release works great with itself (well; Apple is good as working with itself.. microsoft is well.. microsoft) - but none of them hardly cooperate at all with anything NOT made by them.
I really think the whole idea of Hildonization is absurd. Why should we have to modify the interface of each and every app to run on the tablet? There should be a way to "skin" or "theme" the interface of every single GTK app completely and utterly, so that it runs as a tablet app on a tablet and it runs as desktop app on a desktop. And, for that matter, it will run as a media-box app on my remote-controlled media box (usable from the remote control). If the tablet environment has kinetic scrolling, all of the apps that use the toolkit will automatically get kinetic scrolling. If the user finds that annoying, they can turn it off system-wide. One dropdown box will make the entire system "finger friendly" or "stylus friendly" or "keyboard friendly" or "joystick friendly". All GTK apps should just automatically invoke the pop-up keyboard, if that's what you like using....
It takes away the options of say.. KDE vs Gnome. Or.. Gnome would have to support all calls that KDE apps might make and vice versa to get a complete seamless environment working. And the sheer amount of coding this would require is monumental...
Still; good idea though. Hopefully someone much smarter than me figures it out soon.
|
|
2008-08-27
, 17:21
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#144
|
I was specifically talking about apps that use the GTK toolkit, not every single Linux app. Most of the core Gnome stuff uses this now. Why can't the GTK apps be auto-hildonized, I'd like to know?! Why is theming so shallow, so skin-deep?
__________________
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!
|
|
2008-08-27
, 17:26
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#145
|
Originally Posted by qole
Yeah this is true.. the "hildonizing" code should have been written in a way that a normal app that was written for normal GTK would make the same function/library calls and would just receive the different "hildonized" environment...
I was specifically talking about apps that use the GTK toolkit, not every single Linux app. Most of the core Gnome stuff uses this now. Why can't the GTK apps be auto-hildonized, I'd like to know?! Why is theming so shallow, so skin-deep?
but I think (haven't ported anything myself yet) some calls are missing in the Hildonized GTK.. meaning they needed to add some form of seamless 0 return or something to the missing functions so that the app doesn't completely die out.. but it may not work at it's 100%.
 |
|
2008-08-27
, 17:35
|
|
Posts: 475 |
Thanked: 771 times |
Joined on Dec 2007
@ Hamilton, Ontario, Canada
|
#146
|
Qole, I think part of the problem auto-hildonizing would be restricting all GTK programs to a small set of features. For example, Hildon applications can only have one menu, while GTK applications can have as many menus as they want. Hildon applications, while able to have more than one toolbar, would look pretty silly with 8 toolbars stacked along the bottom - not to mention there would be very little usable real estate.
That is not to say that some things could not be auto-hildonized, like hildon input method. I have no idea why all editable text areas do not have this automatically, other than the fact that code would have to be moved into GTK.
I am by no means an expert on this, but I can see why Hildon is a layer on top of GTK. Having small-screen support built into GTK would be another option, but would certainly be much more complicated and I think many applications (Xournal, Abiword, Gnumeric, etc) would not be quite as nice as their Hildonized counterparts.
That is not to say that some things could not be auto-hildonized, like hildon input method. I have no idea why all editable text areas do not have this automatically, other than the fact that code would have to be moved into GTK.
I am by no means an expert on this, but I can see why Hildon is a layer on top of GTK. Having small-screen support built into GTK would be another option, but would certainly be much more complicated and I think many applications (Xournal, Abiword, Gnumeric, etc) would not be quite as nice as their Hildonized counterparts.
__________________
Check out:
Large Statusbar Clock (https://garage.maemo.org/projects/statusbarclock/)
Personal Menu (https://garage.maemo.org/projects/personal-menu/)
Countdown Home (https://garage.maemo.org/projects/countdown-home/)
Personal Launcher (https://garage.maemo.org/projects/personal-launch/)
Check out:
Large Statusbar Clock (https://garage.maemo.org/projects/statusbarclock/)
Personal Menu (https://garage.maemo.org/projects/personal-menu/)
Countdown Home (https://garage.maemo.org/projects/countdown-home/)
Personal Launcher (https://garage.maemo.org/projects/personal-launch/)
|
|
2008-08-27
, 17:45
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#147
|
I think the one-menu limit of Hildon is a problem with the current Hildon spec. There needs to be a way to shoe-horn full functionality into a small form-factor. Toolbars also need to be more configurable; the whole toolbar-across-the-top (or bottom) concept makes some problematic assumptions about the screen size. I like the way gThumb auto-hides the toolbar in fullscreen mode (it can be recovered by tapping the top of the screen); I've found that this works well on the tablet...
__________________
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!
 |
|
2008-08-27
, 17:49
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#148
|
Originally Posted by TA-t3
But discussion is always good.
We can never agree on the "best" user interface, that was clear to me a long time ago already.
Discussing user interfaces and consistency issues is good.
Discussing what's the "best" way and "how it should be" is _useless_.
There is only one answer to that: Bring in the same flexibility as there's on the (X11) desktop: The GUI should either be as configurable as the KDE window manager or e.g. FVWM, or the Hildon stuff should be opened/loosened up enough so that it's easy to replace the actual window manager. Thus, the long-click folks will get their thing, the context-menu folks likewise, ditto fat vs. small menus and icons. And so on.
User choice is the only thing that works for the desktop, it will be the only thing that works for the NIT.
At any rate, I agree that EVERY feature is a good feature so long as it's optional so I can turn it off or choose another.
| The Following 2 Users Say Thank You to danramos For This Useful Post: | ||
 |
|
2008-08-27
, 18:44
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#149
|
Originally Posted by timsamoff
Then you aren't paying very close attention.
I beg to differ here... Kinetic scrolling is highly useful (and usable) in apps like Canola, Mauku, etc... I wish microB had it too. If kinetic scrolling was the only improvement in the next OS, I would be ecstatic. Unfortunately, I don't think it's even in the plan.
It's popped up in one or two commit logs (can't be bothered to dig them up, I know MicroB had one), and I've had several Nokia engineers mention it directly. Kinetic scrolling is likely to be a big part of Fremantle.
| The Following User Says Thank You to GeneralAntilles For This Useful Post: | ||
|
|
2008-08-27
, 18:53
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#150
|
Originally Posted by GeneralAntilles
I'm not sure if it's been answered elsewhere, but will Fremantle suddenly arrive magically and flash over the Intarwebs... or will we be using the same ol' SHUT'R DOWN, WE'ER FLASHING THE WHOLE THING! method of the past?
Then you aren't paying very close attention.
 |
| Tags |
| stuff nokia should read, user interface, whining |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 04:02.
-T.
http://samoff.com