search

angular / batarang

AngularJS WebInspector Extension for Chrome
MIT License
2.43k stars 338 forks source link

Batarangathon 2 - Models View #110

Open aaronfrost opened 10 years ago

aaronfrost commented 10 years ago

WE AREN'T GOING TO WORK ON THIS RIGHT NOW. We are adding it so that we can begin to think about an alternate view. This view is inherently difficult to use. We need to simplify the UI, without losing the functionality.

btford commented 10 years ago

I have some work on this that you haven't seen yet. Let me dig up a screenshot...

btford commented 10 years ago

screen shot 2013-07-19 at 5 44 29 pm

skiant commented 10 years ago

@btford make sure to check this one out as well: https://github.com/rev087/ng-inspector

aaronfrost commented 10 years ago

Doing it in a panel like this does eliminate the need for the bridge that u have built. However, having it in the dev tools feels cleaner. Thoughts Brian?

btford commented 10 years ago

I think we should perhaps just collaborate on ng-inspector (although I noticed that it seems not to have any tests either)

rev087 commented 10 years ago

ng-inspector author here. Tests are something I feel strongly the project should have had from the start, but I simply lack the experience to implement - it's definitely in the todo list tho.

Tangentially, if Batarang could benefit from any assets/code in ng-inspector, I'd be happy to contribute.

rev087 commented 10 years ago

Just to update the previous comment, I've added Protractor e2e tests to the project, see the issue referenced by @mzgol.

ilanbiala commented 10 years ago

Can we just merge both repos into one that is collaborated on by the developers of ng-inspector, AngularJS, and anyone else in the community who is able to and provides good code? Otherwise the fragmentation will cause people to install both, switch between for little features, and confuse people. It will also probably save time and make the debugging tool better if everyone is working on one specific repo.