With the new ravel feature, especially given it has so many new features which might be difficult for a new user to understand, I was wondering if it might be helpful to have a mouse-over tooltip information box to explain what a particular segment is doing or can do. For example, a ravel box with no CSV file loaded could tell the user that they still need to load a CSV file. Or ravel axes could be explained in a tooltip? It doesn't have to be a tooltip necessarily but this could be quite helpful for the front-end user.
Anonymous
On Thu, May 31, 2018 at 06:44:49AM -0000, Hal Crichton-Standish wrote:
It seems like a good idea. Could you flesh out a user story along the
lines of:
State: eg Nothing loaded or connected to input
Action: What to show on tooltip, context menu, F1 press
There is a ravel manual (of sorts) that can be linked to at
http://ravelation.hpcoders.com.au/using.html. Obviously that will need
updating in light of ongoing development. How much of that material
should be put into the Minsky manual is also up for debate, given that
Ravel is an optional add-on product for Minsky.
--
Dr Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Senior Research Fellow hpcoder@hpcoders.com.au
Economics, Kingston University http://www.hpcoders.com.au
Related
Bugs:
#830https://sourceforge.net/p/minsky/tickets/867/