Interface brainstorm for Fablab context
At the latest LAOS meeting we discusses the interfaces of the current printer driver and Visicut. I suggested doing some designs from a Fablab perspective. This topic is to brainstorms about better interfaces for in this case Fablab kind of contexts.
So this interface is focused on the average Fablab visitor. 75% of the times this is his/hers first contact with a lasercutter. Visicut is already reasonably userfriendly but features like material presets, custom mappings, loading multiple objects are basically a big distraction.
Multiple Fablab managers believe you shouldn't give these visitor fixed presets because they will skip experiments and get upset when the result aren't to their liking. 
- When the screen is opened your cursor focus should start at the first enable (pressing spacebar wil toggle that enable).
- when you press tab you will go to the mode (up / down keys can be used).
- next tab will bring you to power, the current content is selected so when you type you replace.
- next tab will bring you to speed, the current content is selected so when you type you replace.
- next tab will bring you to the enable of the second row etc.
All comments are welcome. I created these rough designs using Libreoffice Spreadsheet and I've added the .ods file, so you are encouraged to design an alternative.
In Existing lasercut software I've roughly collected existing software.
Replies (3)
RE: Interface brainstorm for Fablab context
-
Added by peteruithoven about 11 years ago
I've also did quite some suggestions for Visicut:
https://github.com/t-oster/VisiCut/issues/68
RE: Interface brainstorm for Fablab context
-
Added by peteruithoven about 11 years ago
At the moment Visicut's user friendliness is already greatly being increased by gradually increasing complexity when necessary.
Interface parts for material presets only show up when you use them, see: https://github.com/t-oster/VisiCut/issues/70.
In the following topic we are brainstorming how to gradually increase the complexity of mapping:
https://github.com/t-oster/VisiCut/issues/87
In the following topic we are brainstorming how to gradually increase the complexity of the file ui:
https://github.com/t-oster/VisiCut/issues/71
But Visicut might still be more complex than necessary for Fablab context. One reason might be that it hides lasercut settings behind presets, which I feel is not that useful for a fablab context.
So I feel this topic is still a good place to brainstorm on how we would design a application because we can start from a blank slate. And yes, if we find ways to incorporate that back into Visicut that would be great.
RE: Interface brainstorm for Fablab context
-
Added by peteruithoven about 11 years ago
Some small improvements and additions.
- Instead of a checkbox for every color a ignore option is added. (Thanks Daid).
- Besides all the found colors a Other option is added for flexibility. (Idea from VisiCut).
- Some users might want to manually alter the min and max power, so a checkbox is added to the expert settings.
- We usually recommend users to keep a log of lasersettings while experimenting, so I'd like to automatically keep a log in the application. Next to each color I've added a log button that open's a simple log window showing the settings tab separated. Of course this adds buttons, but it seems useful enough. I'd like ideas on how to simplify this.