Talk:FSO

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m
 
(7 intermediate revisions by 6 users not shown)
Line 3: Line 3:
  
 
*[[User:Mickey|Mickey]]: Unified theming is an application level thing, the framework has no idea about UI. To put it to the extreme, the framework services should allow you to write a feature phone UI in ncurses, if you want :) Same goes for web browsing, while being super important nowadays, this is clearly application level framework, not services level.
 
*[[User:Mickey|Mickey]]: Unified theming is an application level thing, the framework has no idea about UI. To put it to the extreme, the framework services should allow you to write a feature phone UI in ncurses, if you want :) Same goes for web browsing, while being super important nowadays, this is clearly application level framework, not services level.
**[[User:Sin|Sin]]: So the framework will be used to make a user environment that could provide a native theme to each of Qt, GTK and EWL/ETK? I'm a bit worried about consistency of the UI since any toolkit can and will be used (which is great btw).
+
**[[User:Sin|Sin]]: So the framework will be used to make a user environment that could provide a native theme as a high level service to each of Qt, GTK and EWL/ETK? I'm a bit worried about consistency of the UI since any toolkit can and will be used (which is great btw).
  
 
[[User:Elektrolott|Elektrolott]]: How about using [http://pim.kde.org/akonadi/ Akonadi]?
 
[[User:Elektrolott|Elektrolott]]: How about using [http://pim.kde.org/akonadi/ Akonadi]?
Line 18: Line 18:
  
 
PolicyKit concerns authorisation of priviledged actions requested by an unprivileged user. This is independant of the actual functionality and APIs. Using PolicyKit may make sense later, when the functionality has been finished.
 
PolicyKit concerns authorisation of priviledged actions requested by an unprivileged user. This is independant of the actual functionality and APIs. Using PolicyKit may make sense later, when the functionality has been finished.
 +
 +
== Highlevel: Network ==
 +
 +
It should be able for a program to determine if network access is free or not (Wifi/USB against GPRS), so a program could have an option like this: Yes/no Only download podcasts when on a free network. Yes/no Check for new episodes even when on paid network. Etc. [[User:EsbenDamgaard|Ebbe]] 10:18, 19 May 2008 (UTC)
 +
 +
== Please clarify sentence ==
 +
 +
The following sentence from the page does not make sense: "The Usage subsystem is coordinating application I/O requirements preventing."
 +
--[[User:Erl|Erl]] 19:18, 18 August 2008 (UTC)
 +
 +
== Using FSO section? ==
 +
 +
I'm very new to wiki editing, but should/could someone create a page about actually *using* the FSO image?  I've done some tweaks that I signed up to edit in the wiki (changing the background edj, for instance), but there's not really a page for that.  I'd love to see a new page called "Using FSO" or something similar.  Thanks!
 +
 +
Hi! See [[FSO UI Tutorial]] [[User:MinhHaDuong|MinhHaDuong]] 14:25, 13 September 2008 (UTC)
 +
 +
== internationalized resource services? ==
 +
 +
is there a plan to make internationalized resources available via dbus in a consistent way? language resource bundles of reusable strings, icons, and images i would be thinking?
 +
[[User:Justo|Justo]] 15:16, 17 September 2008 (UTC)

Latest revision as of 18:09, 3 July 2009

Sin: Would unified theming (something like qtcurve) belong here? How about another high-level service, a web browser element (webkit) that can be used from any application?

  • Mickey: Unified theming is an application level thing, the framework has no idea about UI. To put it to the extreme, the framework services should allow you to write a feature phone UI in ncurses, if you want :) Same goes for web browsing, while being super important nowadays, this is clearly application level framework, not services level.
    • Sin: So the framework will be used to make a user environment that could provide a native theme as a high level service to each of Qt, GTK and EWL/ETK? I'm a bit worried about consistency of the UI since any toolkit can and will be used (which is great btw).

Elektrolott: How about using Akonadi?

Akonadi - The PIM Storage Service
Mission Statement
We intend to design an extensible cross-desktop storage service for PIM data and meta data
providing concurrent read,  write, and query access.
It will provide unique desktop wide object identification and retrieval.
  • Mickey: Akonadi seems huge. It uses kdelibs, tries to integrate a lot (much more than we need) and I don't see any sign of a dbus API.

Contents

[edit] Using PolicyKit for the usage daemon

PolicyKit concerns authorisation of priviledged actions requested by an unprivileged user. This is independant of the actual functionality and APIs. Using PolicyKit may make sense later, when the functionality has been finished.

[edit] Highlevel: Network

It should be able for a program to determine if network access is free or not (Wifi/USB against GPRS), so a program could have an option like this: Yes/no Only download podcasts when on a free network. Yes/no Check for new episodes even when on paid network. Etc. Ebbe 10:18, 19 May 2008 (UTC)

[edit] Please clarify sentence

The following sentence from the page does not make sense: "The Usage subsystem is coordinating application I/O requirements preventing." --Erl 19:18, 18 August 2008 (UTC)

[edit] Using FSO section?

I'm very new to wiki editing, but should/could someone create a page about actually *using* the FSO image? I've done some tweaks that I signed up to edit in the wiki (changing the background edj, for instance), but there's not really a page for that. I'd love to see a new page called "Using FSO" or something similar. Thanks!

Hi! See FSO UI Tutorial MinhHaDuong 14:25, 13 September 2008 (UTC)

[edit] internationalized resource services?

is there a plan to make internationalized resources available via dbus in a consistent way? language resource bundles of reusable strings, icons, and images i would be thinking? Justo 15:16, 17 September 2008 (UTC)

Personal tools

Sin: Would unified theming (something like qtcurve) belong here? How about another high-level service, a web browser element (webkit) that can be used from any application?

  • Mickey: Unified theming is an application level thing, the framework has no idea about UI. To put it to the extreme, the framework services should allow you to write a feature phone UI in ncurses, if you want :) Same goes for web browsing, while being super important nowadays, this is clearly application level framework, not services level.
    • Sin: So the framework will be used to make a user environment that could provide a native theme to each of Qt, GTK and EWL/ETK? I'm a bit worried about consistency of the UI since any toolkit can and will be used (which is great btw).

Elektrolott: How about using Akonadi?

Akonadi - The PIM Storage Service
Mission Statement
We intend to design an extensible cross-desktop storage service for PIM data and meta data
providing concurrent read,  write, and query access.
It will provide unique desktop wide object identification and retrieval.
  • Mickey: Akonadi seems huge. It uses kdelibs, tries to integrate a lot (much more than we need) and I don't see any sign of a dbus API.

Using PolicyKit for the usage daemon

PolicyKit concerns authorisation of priviledged actions requested by an unprivileged user. This is independant of the actual functionality and APIs. Using PolicyKit may make sense later, when the functionality has been finished.