On Tue, Feb 26, 2013 at 02:02:44PM -0700, Sebastian Kuzminsky wrote:
>
> I agree that the bulk of our users don't know and don't care where the
> log files are, and that many of our messages need to pop up in the GUI.
> Whatever changes, if any, can't break GUI message popups.
Ideally they would even be improved, especially the case I
mentioned, which is currently pretty horrible, and aside from
generic operator errors ("G1 without feed rate") the VERY most
important error situation.
> Logs are used by integrators and hackers and developers, and
> occasionally by bug reporters. It's one of my primary debugging aids,
Don't get me wrong! I'm all for whatever helps developers and
hackers and list/forum users and irc helpers too. That does
probably involve sending stuff to a file (for attachment to a bug
report)? Many programs can do reporting automatically, attaching
the last N logged messages to a bug report, for instance. I think
that's probably not appropriate for our "can't start because your
hal file or tool table or whatever is bogus" situation, but maybe if
it goes to a pastebin instead of a bugtracker it would be?
I guess I just want us to consider what problem we are solving for
the user before we decide on an architecture. I saw a lot of
"obviously syslog!" and I didn't understand why we were jumping
right to there, because it didn't seem to me that it solves any of
our primary problems. I realize we are coming at this with opposite
approaches - that's good!
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
