Re: Maemo documentation - feedback time is now

2007-04-01 Thread Quim Gil
Hi Ian,

The Documentation Big Plans will take effectively place as soon as we
hire the (hopefully) brilliant documentation manager we are (still)
looking for. In the meatime the broad plans are:

1. Make a clear distinction between official and not-official docs in
the new maemo site.

2. Structure properly the official documentation so it's easy to see
what is there and what is still lacking.

3. Introduce more and better quality checks in order to keep the
official documentation in a good and better shape. Keep the call for
documentation needs open and be fast responding to your needs.

Although the first focus is on the official documentation, we have high
expectations in the community documentation work. The idea is to help
providing:

a) A basic content structure to ease the publishing and retrieval of
docs.

b) Tools to differentiate "good" docs from the rest. As you know 'good'
is a quite subjective value, these tools should put this subjectivity
into efficient work.

c) Proper links between official and community documentation, making
possible to move/listing of docs from one category to another.


In the meantime we will work in two parallel areas: 

1. Nice & useful packaging of documentation in i.e. PDF sets with decent
look&feel, consistent style, professional proofreading.

2. Orientation of documentation towards training for entry and mid
levels.


And just to make this explicit, "documentation" should include graphics,
screenshots and even screencasts and videos wherever useful.

One additional challenge will be to make all this with a certain/proper
coordination with upstream projects, since it is obvious that a lot of
maemo depends on components originated out of maemo.


These are more or less the pre-plans. Seriously. They are open to
improvement. In fact we expect this new doc manager to push these plans
to a level we can't hardly imagine now.  :)


On Thu, 2007-03-29 at 16:42 -0500, ext Ian wrote:
> Ola, My question is about the wiki and the idea that was discussed to
>  use as staging area for experimental documentation. Like this docs
>  which are not well tested for spelling errors/bugs/version
>  incompatibilties and so on do not make it up into the official docs
>  until they *are* well tested. []'s Ian
> 
-- 
Quim Gil - http://maemo.org

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-29 Thread Mike Morrison

Here are a few things I've been struggling with lately:

The porting guide, the 'writing a new application' document, and the
tutorial (and probably others) have a lot of overlap. Maybe they could be
merged or the redundant bits of information could be in one place and these
docs could link to it?

The documentation on .desktop/.service files needs improvement as the
examples in the docs do not work. I wasted several hours figuring out how to
set it up properly (later I saw a bug in bugzilla about this,
https://maemo.org/bugzilla/show_bug.cgi?id=602).

I couldn't find any documentation about mime types / file associations. Is
it even possible to associate a mime type with a different application or
does the file manager always just use the default? And how does the file
manager pass arguments  (the files to load) through to the associated
application (if the associated app has a .service file)?

Documentation on icons is lacking. Why isn't the libossomime in the api
docs? I would also like to use some of the "stock" hildon icons in my app
but there is no HILDON_STOCK #defines (like in gtk+). Why not?

There is no document about thumbnail caching, but I see that
~/.thumbnails/osso has 80x80 thumbnails. Should that be in a document
somewhere?

I have probably had other issues with the docs, but that's all I can
remember right now.

Mike


On 3/28/07, [EMAIL PROTECTED] < [EMAIL PROTECTED]>
wrote:


 Hi,

Maemo tutorial and how-to documention are in 
http://maemo.org/platform/docs/how-to.html
. There exists API documentation as well on 
http://maemo.org/platform/docs/api-index.html
. So the question is are they good enough, what could be improved, any
bugs, two few examples or specs, wrong format, or other things that are on
your way to block hacking on some area or on a particular topic? Thanks,
already in advance!

Regards,
JP

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-29 Thread Ian

Ola,
My question is about the wiki and the idea that was discussed to use as staging 
area for
experimental documentation.
Like this docs which are not well tested for spelling errors/bugs/version 
incompatibilties and so
on do not make it up into the official docs until they *are* well tested.
[]'s
Ian

-- 
.''`.
   : :'  :
   `. `'`
 `- Orgulhoso ser MetaRecicleiro

http://ianlawrence.info
http://manaus.metareciclagem.org/

Jabber: [EMAIL PROTECTED]

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-29 Thread Laurent GUERBY
Hi,

I'm trying to do what the battery applet does when clicked but
from a simple python program, mixing information from various places:

http://maemo.org/platform/docs/pymaemo/pyosso_context.html
http://maemo.org/platform/docs/python-bora/python_maemo_howto.html
http://maemo.org/pipermail/maemo-developers/2007-March/009300.html

Looks like the documented system_bus is not available for rpc_run:

$ python
Python 2.5 (r25:10194M, Feb 23 2007, 15:35:52) 
[GCC 3.4.4 (release) (CodeSourcery ARM 2005q3-2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import osso
>>> osso_c = osso.Context("osso_test_sender", "0.0.1", False)
>>> osso_rpc = osso.Rpc(osso_c)
>>>
osso_rpc.rpc_run("com.nokia.bme.request","/com/nokia/bme/request","com.nokia.bme.request","timeleft_info_req",wait_reply=True,system_bus=True)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: 'system_bus' is an invalid keyword argument for this function

(I've no knowledge of dbus and osso it may show :).

Thanks in advance,

Laurent

On Wed, 2007-03-28 at 13:05 +0300, [EMAIL PROTECTED] wrote:
> Hi,
> 
> Maemo tutorial and how-to documention are in
> http://maemo.org/platform/docs/how-to.html. There exists API
> documentation as well on
> http://maemo.org/platform/docs/api-index.html. So the question is are
> they good enough, what could be improved, any bugs, two few examples
> or specs, wrong format, or other things that are on your way to block
> hacking on some area or on a particular topic? Thanks, already in
> advance!
> 
> Regards, 
> JP
> 
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-28 Thread Daniel Stone
On Wed, Mar 28, 2007 at 05:16:36PM +0300, ext Marius Gedminas wrote:
> On Wed, Mar 28, 2007 at 03:52:18PM +0300, Daniel Stone wrote:
> > Enable extended events in your GTK application, and ensure that axis 2
> > (i.e. the third axis) is set as PRESSURE (set_axis_use) or something,
> > and now the PRESSURE field of every event will be valid.  OTOH, I think
> > GTK might already do this for you.
> 
> Thanks.  Here's some source code for that as well:
> http://groups.google.com/group/fbreader/msg/86fceebf61e5e358
> 
> It's from FBReader.  That method distinguishes stylus taps from thumb
> presses in all Maemo versions that do i tin three different ways.
> 
> There is one bit of guesswork there.  What's the pressure value
> threshold used to detect thumb presses in the system by such controls as
> the thumb-aware menus?

Hi,
As Tuomas posted, there's a Hildon finger API which will tell you
whether or not it's a finger press, hiding all the voodoo from you.  If
you just want a pure pressure value, then check the pressure field.

Cheers,
Daniel


signature.asc
Description: Digital signature
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-28 Thread Marius Gedminas
On Wed, Mar 28, 2007 at 03:52:18PM +0300, Daniel Stone wrote:
> On Wed, Mar 28, 2007 at 03:24:42PM +0300, ext Marius Gedminas wrote:
> > On Wed, Mar 28, 2007 at 01:05:01PM +0300, [EMAIL PROTECTED] wrote:
> > > Maemo tutorial and how-to documention are in
> > > http://maemo.org/platform/docs/how-to.html. There exists API
> > > documentation as well on
> > > http://maemo.org/platform/docs/api-index.html. So the question is are
> > > they good enough, what could be improved, any bugs, two few examples
> > > or specs, wrong format, or other things that are on your way to block
> > > hacking on some area or on a particular topic? Thanks, already in
> > > advance!
> > 
> > A week ago I was unable to find documentation how to detect thumb
> > presses in Maemo 3.0.
> 
> Enable extended events in your GTK application, and ensure that axis 2
> (i.e. the third axis) is set as PRESSURE (set_axis_use) or something,
> and now the PRESSURE field of every event will be valid.  OTOH, I think
> GTK might already do this for you.

Thanks.  Here's some source code for that as well:
http://groups.google.com/group/fbreader/msg/86fceebf61e5e358

It's from FBReader.  That method distinguishes stylus taps from thumb
presses in all Maemo versions that do i tin three different ways.

There is one bit of guesswork there.  What's the pressure value
threshold used to detect thumb presses in the system by such controls as
the thumb-aware menus?

Marius Gedminas
-- 
This host is a black hole at HTTP wavelengths. GETs go in, and nothing
comes out, not even Hawking radiation.
-- Graaagh the Mighty on rec.games.roguelike.angband


signature.asc
Description: Digital signature
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-28 Thread Tomas Junnonen
ext Daniel Stone wrote:
> On Wed, Mar 28, 2007 at 03:24:42PM +0300, ext Marius Gedminas wrote:
>> On Wed, Mar 28, 2007 at 01:05:01PM +0300, [EMAIL PROTECTED] wrote:
>>> Maemo tutorial and how-to documention are in
>>> http://maemo.org/platform/docs/how-to.html. There exists API
>>> documentation as well on
>>> http://maemo.org/platform/docs/api-index.html. So the question is are
>>> they good enough, what could be improved, any bugs, two few examples
>>> or specs, wrong format, or other things that are on your way to block
>>> hacking on some area or on a particular topic? Thanks, already in
>>> advance!
>> A week ago I was unable to find documentation how to detect thumb
>> presses in Maemo 3.0.
> 
> Enable extended events in your GTK application, and ensure that axis 2
> (i.e. the third axis) is set as PRESSURE (set_axis_use) or something,
> and now the PRESSURE field of every event will be valid.  OTOH, I think
> GTK might already do this for you.

I don't know why it's not part of the docs, but there's a convenience
API for the applications to use. Here's the gist of it:

#include 

gtk_widget_set_extension_events(widget, GDK_EXTENSION_EVENTS_ALL);
g_signal_connect(G_OBJECT(widget), "button-press-event",
 G_CALLBACK(button_press_cb), NULL);

button_press_cb(GtkWidget *widget, GdkEventButton *event, gpointer data)
{
  if (hildon_button_event_is_finger(event))
 ...

Regards,
Tomas

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-28 Thread Daniel Stone
On Wed, Mar 28, 2007 at 03:24:42PM +0300, ext Marius Gedminas wrote:
> On Wed, Mar 28, 2007 at 01:05:01PM +0300, [EMAIL PROTECTED] wrote:
> > Maemo tutorial and how-to documention are in
> > http://maemo.org/platform/docs/how-to.html. There exists API
> > documentation as well on
> > http://maemo.org/platform/docs/api-index.html. So the question is are
> > they good enough, what could be improved, any bugs, two few examples
> > or specs, wrong format, or other things that are on your way to block
> > hacking on some area or on a particular topic? Thanks, already in
> > advance!
> 
> A week ago I was unable to find documentation how to detect thumb
> presses in Maemo 3.0.

Enable extended events in your GTK application, and ensure that axis 2
(i.e. the third axis) is set as PRESSURE (set_axis_use) or something,
and now the PRESSURE field of every event will be valid.  OTOH, I think
GTK might already do this for you.

Cheers,
Daniel


signature.asc
Description: Digital signature
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: Maemo documentation - feedback time is now

2007-03-28 Thread Marius Gedminas
On Wed, Mar 28, 2007 at 01:05:01PM +0300, [EMAIL PROTECTED] wrote:
> Maemo tutorial and how-to documention are in
> http://maemo.org/platform/docs/how-to.html. There exists API
> documentation as well on
> http://maemo.org/platform/docs/api-index.html. So the question is are
> they good enough, what could be improved, any bugs, two few examples
> or specs, wrong format, or other things that are on your way to block
> hacking on some area or on a particular topic? Thanks, already in
> advance!

A week ago I was unable to find documentation how to detect thumb
presses in Maemo 3.0.

Marius Gedminas
-- 
What goes up, must come down. Ask any system administrator.


signature.asc
Description: Digital signature
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Maemo documentation - feedback time is now

2007-03-28 Thread Jukka-Pekka.Iivonen
Hi,

Maemo tutorial and how-to documention are in 
http://maemo.org/platform/docs/how-to.html. There exists API documentation as 
well on http://maemo.org/platform/docs/api-index.html. So the question is are 
they good enough, what could be improved, any bugs, two few examples or specs, 
wrong format, or other things that are on your way to block hacking on some 
area or on a particular topic? Thanks, already in advance!

Regards,
JP
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers