@Leo Oh, I didn’t mean to struggle throughout the project with this :). Just create a very simple target UI to have when doing HEAVY debugging (complex, hard to find issues that may arise and especially now when architecting the project and need to adapt to an ever-changing architecture).
The UI is not where most work will happen yet, so I can afford a very cheap & simple Flash prototype, mocking the main functionality. My game is almost 90% logic with little UI and having the power of an IDE when debugging the beast will be very handy compared to the time spent mocking some UI in Flash (which I already did).
Maintaining 2 targets is far from what I was thinking . So, thanks for the suggestion. That’ll come in handy when I focus on the final UI. Then, Visual Studio will come in really handy (hoping they support debugging in VS Community, since I already have that installed).
As per your question, here are some of the MAJOR things I’m missing in Chrome developer tools:
- ctrl+click navigation to types
- speed - an IDE is much, much faster and convenient when doing any sort of navigation; by comparison the windows of the developer tools are sluggish to say the least.
- a proper, large screen, tabbed environment to switch between those files
- hotkeys (not as reliable and easy to use as a full-fledged IDE)
- syntax coloring & type hinting
This is just the major stuff that comes to mind