To be honest I don't think there's any need to build any specialised UI for
this. Inklecate crashing is supposed to be very rare, and should be
getting more rare all the time! :)

So I'd just present it basically like a runtime error: just some red text
that gets appended to the player view. I definitely wouldn't make it float
or anything - I just don't think there's any reason to add any complexity
there.

It should be really rather simple! Any kind of complexity here just adds
unnecessary bloat to the code base...

Does that make sense?
On Sun, 29 May 2016 at 17:13, Diogo Neves notifications@github.com wrote:

I'm looking into adding a floating ExceptionView that shows exceptions in
the bottom right corner of the editor (as floating boxes that can be
closed).
It similar to the atom error boxes but would be cool to extend them with
actions (e.g. email details, etc)

What do you think? Floating boxes may not be trivial to implement though,
would you be ok using a jquery plugin for this? I'm researching how to
avoid that though.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AA0bV1gAN62c72SXGLi2-v-elX7IagW6ks5qGbsKgaJpZM4IpS5D
.

When inklecate crashes, we should handle it specially #2

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions