# New SCB
Keywords: #SCB, #ChangeSets, #ObjectEditor, #Layers
The SCB has become pretty old and despite some face lifting done by Batian and some Bug fixes it was pretty much left alone. I did not like its architecuture because it does not lend itself to be changed with our current tool sets. Further, the file based approach, even though it looks like Smallalk failed to go the last step. You have to first navigate files / modules before you can dive into the classes and methods, or layers or all those other things Lively is build up. This file file centric view makes it also hard to quickly get an overview of the whole system. Searching and navigating it takes ages! This should does not have to be this way! So what would I expect from an alternative tool:
## Core Requirements
☐ browse primarily modules, classes, objects (and not files -- for that the SCB seems ok)
☐ provide fine granular control over changes (Dan's ChangeSets fall out in the form of a real Undo history)
☐ be persistent acrosss world savings....
☐ cooperate with multiple browsers openend in one world
☐ Be as specific and lightweight as possible -> No big general browser framework that will rule them all!
## Nice to have
☐ tight github or alternative SCM (did anybody hear CodeDB?) integration
☐ collaborative editing --> Multiple cursors? Just because we can? As a part bigger syncronous collaborative environment?