search

t-oster / VisiCut

A userfriendly tool to prepare, save and send Jobs to Lasercutters
https://visicut.org
Other
233 stars 114 forks source link

Keeping a lasersettings log #92

Closed peteruithoven closed 11 years ago

peteruithoven commented 11 years ago

In a brainstorm for a lasercut interface specific for Fablab contexts I came up with a logging functionality. We usually ask people to keep a log of the settings they try out when they are experimenting. It might be interesting to have the application keep a log automatically.

We could add a Log / Show log button next to where users edit the profile's lasersettings. This could open up window containing a tekst with every log entry on a line. Each line could contain a time (a full date seems unnecessary) and the properties separated with a tab.

log window

I would love to enable people to add comments like "to dark", "to slow" etc, but I'm not sure how. We could make it editable, but then it might be hard to also keep adding new settings. If it's one file you might get conflicts etc.

I would keep a log per profile for simplicity's sake.

This is a feature request, so give it as much priority as you feel fit.

t-oster commented 11 years ago

Hmm... I think we should not bloat Visicut too much. What about some kind of plugin-system, which gets called e.g. whenever a job is send and can then access such properties and do whatever it likes (e.g. publish on a website)... but I am not sure if that is not too much.

t-oster commented 11 years ago

Who is still interested in a log? Any new suggestions. wich would integrate well in the current UI?

peteruithoven commented 11 years ago

I still like this idea, but currently I think making using the test pattern laserscript as easy as possible solves the underlying goal. That goal being making it easier to find the right settings. See issue #151 for example.