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

Error feedback on the GUI #196

Open
matita opened this issue Apr 14, 2015 · 4 comments
Open

Error feedback on the GUI #196

matita opened this issue Apr 14, 2015 · 4 comments

Comments

@matita
Copy link
Contributor

matita commented Apr 14, 2015

Most of the errors (if not all, I'm just scratching the surface of MediaCenterJS) are logged only on the console and not on the GUI.
One solution (rough but effective) could be to stream logger.error to socket.io to the client and visualize it with a notification in the style of http://ksylvest.github.io/jquery-growl/.
Since the use of winston library it should not be difficult to write a transport or an event listener on 'error' that sends the message to the client via socket.io

@matita
Copy link
Contributor Author

matita commented Apr 14, 2015

There is also an angular library with similar notifications https://github.com/marcorinck/angular-growl

@jansmolders86
Copy link
Owner

Currently the log are written to a file as well in the log folder. I'm using Winston to keep track and write logs to the filesystem. Is that what you meant?

Thanks!

@matita
Copy link
Contributor Author

matita commented Apr 23, 2015

I mean most of the times, if not always, a standard user (not a developer) would probably just see the web app through a browser.
IMHO it could be useful and more usable to have a feedback on the webpage when something is not working on the back end.

@jansmolders86
Copy link
Owner

ow right! Yes, that makes sense! though in the current status of this app I wouldn't be too worried about having users without some technical knowledge but especially if we we are porting this to a node webkit environment we should definitely push messages from the server to the frontend. The websockets already in place would be ideal for that. Backend database loading is already forwarded to the frontend via websockets

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