## 2016-04-08 The "sync" Button

Is introducing the "sync" button into the lively container / browser a good idea? Or should we do it more automatically? 


### Playing around with global error handling

```JS
 
 window.onerror = function onerror(message, source, lineno, colno, error) {
  	window.LastError = error
  	lively.notify("Error: ", message, 20, () => 
  		lively.openWorkspace("Error:" + message + "\nLine:" + lineno + " Col: " + colno+"\nSource:" + source + "\nError:" + error.stack))
 };
 // window.addEventListener('unhandledrejection', 
 
 lively.handleReject = function(evt) {
  window.onerror("Unhandled Promise Reject: " + evt.reason.message,null,null,null,evt.reason)
 }
 window.addEventListener('unhandledrejection', (evt) => lively.handleReject(evt) );
 
```
This can intercept aysnc errors like:
```JS
 setTimeout(() => foo.foo(), 10)
```

But what about errors in Promises?
```JS
 fetch("https:///lively4/").then( () => foo.foo())
 Promise.resolve().delay(500).then(()=>{throw new Error()})
```

### Making sense of native error massages

Maybe the parsing of the error messages may help...

- https://github.com/stacktracejs/stacktrace-gps
- https://github.com/stacktracejs/error-stack-parser


I know, that we will do better by using our own debber infrastructure... and we will, eventually.

## Code Navigation

I would like to have something like:   http://sevin7676.github.io/Ace.Tern/demo.html#javascript

Not for the autocompletion, which is nice, but for navigation between code and all....