Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 1 day, 23 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 3 days, 20 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 4 days, 17 hrs ago - more...
|
2011-02-07
, 11:04
|
|
Posts: 35 |
Thanked: 246 times |
Joined on Feb 2009
|
#2
|
Originally Posted by davidmaxwaterman
May be we should get first out for MeeGo style Maemo5 version
I wonder if anyone is developing a qt-components style for maemo5.
Max.
that does not depend on MeeGoTouch themeing engine.
I feel that it is best starting point to take MeeGo style and then
make Maemo5 style based on that.
More challenging would be making themebridge that extracts
Hildon themes directly.
Kate
 |
|
2011-02-07
, 15:37
|
|
Posts: 52 |
Thanked: 45 times |
Joined on Dec 2009
|
#3
|
Other than maybe games an app should not have to worry about "style". All it should need to know is how to collect the data it needs to process and how to return results to the user. It should be the concern of the OS only on how the data is obtained and the results presented.
In other words programming an app should be as simple as:
Far too much developer time is wasted on how to collect and display data instead of processing the data itself.
Last edited by EzInKy; 2011-02-07 at 15:40.
In other words programming an app should be as simple as:
Code:
os_collect_data(&my_data_struct); my_app_process_data(data_struct); os_dispaly_data(&my_data_struct);
Last edited by EzInKy; 2011-02-07 at 15:40.
|
|
2011-02-07
, 17:39
|
|
Posts: 724 |
Thanked: 1,255 times |
Joined on Nov 2007
@ Cambridge, UK
|
#4
|
Originally Posted by EzInKy
I guess you're not a developer then. Or you're a semweb junky :P
Other than maybe games an app should not have to worry about "style". All it should need to know is how to collect the data it needs to process and how to return results to the user. It should be the concern of the OS only on how the data is obtained and the results presented.
In other words programming an app should be as simple as:
Far too much developer time is wasted on how to collect and display data instead of processing the data itself.Code:os_collect_data(&my_data_struct); my_app_process_data(data_struct); os_dispaly_data(&my_data_struct);
|
|
2011-02-07
, 21:43
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#5
|
Originally Posted by kate
Hmm qt-componets looks very promising but AFAIK qt-components for Maemo5 hasnt been updated for months? or has I missed this ?
May be we should get first out for MeeGo style Maemo5 version
that does not depend on MeeGoTouch themeing engine.
I feel that it is best starting point to take MeeGo style and then
make Maemo5 style based on that.
More challenging would be making themebridge that extracts
Hildon themes directly.
Kate
|
|
2011-02-08
, 11:04
|
|
Posts: 52 |
Thanked: 45 times |
Joined on Dec 2009
|
#6
|
Originally Posted by tswindell
I had to search to find out what you even meant by "semweb" B-)
I guess you're not a developer then. Or you're a semweb junky :P
No, that is not what I meant at all. Interface design should be left to, well, interface designers so that developers can concentrate on improving algorithms. As nice as QtCreator is, deciding on where to place widgets is still a waste of time. The important things are the work performed when those widgets are clicked.
 |
|
2011-02-08
, 11:15
|
|
Posts: 1,391 |
Thanked: 4,272 times |
Joined on Sep 2007
@ Vienna, Austria
|
#7
|
Originally Posted by EzInKy
UI design is at least as important as "algorithms", if not more important for UI-driven apps (and basically all mobile apps are UI-driven). That said, it's not as easy as "gather, process, display" - that only works in batch processing. There is much more going on in an interactive application.
No, that is not what I meant at all. Interface design should be left to, well, interface designers so that developers can concentrate on improving algorithms. As nice as QtCreator is, deciding on where to place widgets is still a waste of time. The important things are the work performed when those widgets are clicked.
QML does help split the "backend" from the "frontend", though, and I spend less time (compared to GTK or QWidget) writing code to juggle around pure UI stuff. There's the UI "code" (in QML/JavaScript) where I just define the looks, layout and where the data comes from, and then there's the backend code (in my case Python, but in general C++), where data is brought into a form that can be displayed by the UI. And then there's glue code in there, and things get more complicated
If we can get the default MeeGo theme on Maemo 5 working for Qt Components, that should be ok at first. If people really want to, they can probably design a Maemo 5-style MeeGo theme.
| The Following User Says Thank You to thp For This Useful Post: | ||
|
|
2011-05-27
, 09:16
|
|
Posts: 123 |
Thanked: 21 times |
Joined on Sep 2009
|
#8
|
Originally Posted by kate
I wonder if anyone has done any work on this. I'm looking around to see if there's anything, but no joy so far.
May be we should get first out for MeeGo style Maemo5 version
that does not depend on MeeGoTouch themeing engine.
I feel that it is best starting point to take MeeGo style and then
make Maemo5 style based on that.
More challenging would be making themebridge that extracts
Hildon themes directly.
Kate
Anyone?
Max.