Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not sure I like the new 'click on the red stack trace message to show the console' logic #724

Closed
jstrachan opened this issue Nov 5, 2013 · 4 comments

Comments

@jstrachan
Copy link
Contributor

when trying to use hawtio and something goes wrong you get tons of big red warnings; as a user you just wanna get rid of them; but then clicking on them keeps it there, then shows more logs (the console ;).

can we bring back the easy ability to close the big red warning stuff; and make it a little harder to show more console stuff by default?

@gashcrumb
Copy link
Member

Yeah, we can turn that off, though maybe it's worth investigating what the warning is and how we're displaying it? Was kinda thinking generally we could typically log a terse statement at error and then log the full stack trace (if there's one associated) at info/debug so that first off the error/warning popup isn't so large and secondly the user can look in the log for more info and copy/paste it easily into a gist.

@jstrachan
Copy link
Contributor Author

so it seems quite easy to get lots of errors - all of the place - when using fabric ;) I can imagine folks get this when things stop/die/restart too; so wanting to close a big red flashing warning is probably the default requirement; rather than keeping it open and opening another log too for good measure.

Maybe we just need big, clear X button on the notifications?

@gashcrumb
Copy link
Member

Yeah, think at least an x button on all of the notifications would be a good idea...

We're getting more errors these days? :-/

@jstrachan
Copy link
Contributor Author

the errors are more fabric issues than hawtio mind you (and I've just made hawtio deal with the lack of mbeans that were causing all the exceptions in the dozer plugin;)

@ghost ghost assigned gashcrumb Nov 5, 2013
gashcrumb added a commit that referenced this issue Jan 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants