As I mentioned in "Collecting anonymous statistical data" thread, seeing
what features of the program are not used by the users could help us
display a proper Tip of The Day to make sure the user will learn something
new, not read how to save files, if he does it 20 times a week.

We'd need a list of features that would both be accesed by the statistic
gathering system as well as the tips.

If every feature has a unique ID umber, we could then add a
reportUse(featureID) function that would add a log about what was launched
when.
We could have a simple text (CSV) file with:
featureID; featureName; featureTipTitle; featureTipContent;<newline>

Example file contents:

*000001;* "File > Open..."; "Loading project using main program menu"; "You
can load an existing project using the main menu. Select "File" and then
"Open..." in the new submenut that appears. Then use the file browser to
pick the project file you want to load. Press <enter> or click <Open>
button. Wait until the project loading is complete and you're ready to
continue previous work!";<newline>
*000002;* "Main Toolbar > Open"; "Loading project using main toolbar
button"; "You can load an existing project using the main toolbar. Use the
Open File button. Then with the file browser - pick the project file you
want to load. Press <enter> or click <Open> button. Wait until the project
loading is complete and you're ready to continue previous work!";<newline>

<...>

*000213*; "Drag+Ctrl in Sequencer"; "Dragging Sequencer clips  overriding
the bar grid"; "You can move (or resize) a clip in the Sequencer by
fraction of a bar. First click on a clip with Left Mouse Button and hold
it, then start dragging the clip and finally - press and hold Ctrl key. The
same can be done for changing the clip's length - just click on the right
edge of a clip instead of it's body.";


The Tip of The Day function should sort the features by usage. Then make a
list of top X less used features in the last time frame (say: 90 days) and
randomly pick one from there. It should log that a tip was displayed at a
given date to not repeat itself until all other possibilities are already
exploited - showing a tip and getting user's "I got this" click in it's
window should be counted as a use of the feature to make it go lower in
sorting.

Also users should be able to click "Useful (+1)" or "Useless (-1)" for each
tip - and developers will then see the feedback for tips. The tips which
have "top useless" score should be revisited and changed.

I can offer my help in writing the tips and start the feature list, however
I'll need some help with this and we should design this with the Reporting
Anonymous Statistical Data system in mind.

Also designing the feedback system and how developers see it's input form
users is out of my scope now - if anyone has ideas how it can be done,
please rise you hand.

-- 
Tobiasz *unfa*

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT/MU/P d->-- s+:-(--)> a? C++(+++)>$ ULC+(++)>$ !P? L+++>++++$ E? W++>$
!N-? !o--? K-? !w-- O? !M-- V? PS++ PE++ !Y+ !PGP+? !t(+) 5? !X !R+ tv
b+>+++ DI>+ D+ G e h-->- !r y--()
------END GEEK CODE BLOCK------
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to