Active Topics

 



Notices


Poll: What would you think if installing an app opened up the documentation page in Maemo Browser?
Poll Options
What would you think if installing an app opened up the documentation page in Maemo Browser?

Reply
Thread Tools
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#1
There is currently no official way to include documentation with apps in Maemo. I guess the paradigm is supposed to be either so easy to understand that none is needed, or a wiki or thread on maemo.org. The problem with the latter is that a typical user may have no idea of the existence of said thread or wiki page.

One option to resolve this would be to open the browser to the official app page when the app is installed. My question about this is, would such behavior bother/annoy/enrage or otherwise not be a good thing?

One nice thing about that is it would give the maintainer a way to inform the user of any new features or issues, something not possible with App Manager in its current form.

What would you think if installing an app opened up the documentation page in Maemo Browser?
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful

Last edited by Flandry; 2010-01-19 at 14:23.
 

The Following 2 Users Say Thank You to Flandry For This Useful Post:
Posts: 434 | Thanked: 325 times | Joined on Sep 2009
#2
Having a wiki in maemo.org for each app, would certainly make my life easier. All I had to do, is to have a "Help" button/menu that would open the wiki with Maemo Browser. As a developer, I think this would be a great idea!
 
Posts: 434 | Thanked: 325 times | Joined on Sep 2009
#3
Originally Posted by Flandry View Post
One option to resolve this would be to open the browser to the official app page when the app is installed. My question about this is, would such behavior bother/annoy/enrage or otherwise not be a good thing?

What would you think if installing an app opened up the documentation page in Maemo Browser?
As for opening the wiki automatically when installing an app, I don't think I would like that too much. Would it could do instead, is to ask whether it should be opened.
 
Posts: 121 | Thanked: 75 times | Joined on Oct 2009
#4
That would annoy me.

A couple of options you could have are
* Have a link to the wiki page in your about box that the user can click on.
* On first run popup a wizard or dialog which has a link to the help page.

That way the user has an easy way to get to the help page without it being too intrusive.
 

The Following User Says Thank You to matrim For This Useful Post:
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#5
I'm confused. Is this a button I can click to get documentation, or an auto-pop-while-installing or somesuch optionless behavior?

I voted that it would be good but I assumed it would open release notes from a local HTML or have a help menu I can click and choose to see help, home page, vote for the package, etc. Auto-popping stuff without asking would be bad.

Also, including a vote for package link would make our(my?) life WAY easier than digging for the package.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 243 | Thanked: 28 times | Joined on Nov 2009
#6
Originally Posted by Sasler View Post
Having a wiki in maemo.org for each app, would certainly make my life easier. All I had to do, is to have a "Help" button/menu that would open the wiki with Maemo Browser. As a developer, I think this would be a great idea!
Perfect idea. This will help in figuring out the apps that have absolutely no info about what they do and how they can be configured.
 

The Following User Says Thank You to ajamils For This Useful Post:
Posts: 93 | Thanked: 21 times | Joined on Jan 2010 @ The Netherlands
#7
Originally Posted by Sasler View Post
As for opening the wiki automatically when installing an app, I don't think I would like that too much. Would it could do instead, is to ask whether it should be opened.
Same here.
 

The Following User Says Thank You to misterm For This Useful Post:
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#8
Seems that first run is the time for doing this, then. The advantage of doing it on install would have been (1) that an Internet connection can be assumed and (2) that some standard method could have been implemented. I can see it could be annoying, however.

Thanks for your comments and votes.
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful
 
Posts: 1,224 | Thanked: 1,763 times | Joined on Jul 2007
#9
Doing it on first run is just as bad. A program should do what it is supposed to do, not open unnecessary windows. For help there is help menu.
 
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#10
Not a single one of my three apps in Extras has a help menu...

Not all apps need a menu, but all apps have release notes that may be important. Previous versions of App Manager supported a custom control file field that would show upgrade notes, but that is not supported, so i'm trying to find the best alternative.
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful
 
Reply

Tags
app manager, documentation, user interface


 
Forum Jump


All times are GMT. The time now is 23:14.