Here’s a brilliant research idea for building GUI of integrated development environments:
http://www.cs.brown.edu/people/acb/codebubbles_site.htm
I hope to be able to work like this with Visual Studio 2012.
Subscribe to:
Post Comments (Atom)
About
- Wiktor Zychla
- I am a software architect and an academic lecturer. I've been awarded Microsoft MVP in C# Architecture between 2005 and 2010. Got a PhD in computer science in 2008. Currently I work mostly with C# and Javascript and love both languages. I consider myself a design/architecture patterns evangelist. In 2003 I wrote first Polish book on C#/Windows programming, "Windows oczami programisty" (Windows through the eyes of a programmer) (the book is out of print)
Search This Blog
Translate
Labels
- ASP.NET (26)
- Puzzle (24)
- WIF (14)
- ADFS (11)
- LINQ (10)
- Other (10)
- WCF (9)
- C# (8)
- IIS (7)
- Entity Framework (6)
- Javascript (6)
- NHibernate (5)
- Silverlight (5)
- Win.Forms (5)
- XPO (5)
- node.js (5)
- X509 (4)
- XMLDsig (4)
- XNA (4)
- ePUAP (4)
- AJAX (3)
- Messaging (3)
- OLAP (3)
- SQL Server (3)
- Testing (3)
- Visual Studio (3)
- log4net (3)
- Async (2)
- CryptoAPI (2)
- ESB (2)
- HTML (2)
- Internet Explorer (2)
- MVC (2)
- Oracle (2)
- RabbitMQ (2)
- SAML2 (2)
- SVN (2)
- WebAPI (2)
- Caching (1)
- Design Patterns (1)
- IoC (1)
- JWT (1)
- MSMQ (1)
- Mass Transit (1)
- PowerShell (1)
- SHA1 (1)
- SHA256 (1)
- SSO (1)
- Unity (1)
- WS-Federation (1)
- WebServices (1)
- WebdriverIO (1)
- Word (1)
Subscribe To
Posts
Comments
Followers
Total Pageviews
Buddhabrot
Beauty of fractals
4 comments:
Really nice - especially on big or multiple screens.
I hope not. It looks really as a counter-productive IDE for me. I would have to check it out to be sure though.
I sure hope so - this is definitely the future of programming.
Some more features I'd like to see on top of that:
* Documentation support. I should not have to look at all the lengthy documentation when browsing through the code, but viewing/editing the documentation for a particular class/method should be very easy and straight-forward.
* Pre/Post-Conditions support. Imagine simply having a list of a method's parameters, and being able to check off which ones should be non-null, or that cost should be > 0. This would automatically generate documentation, and add the appropriate `if(..) throw new ArgumentNullException()` code... or even better, could optionally use CodeContracts!
I used the DebuggerCanvas Extension for Visual Studio for a few weeks and found it to be annoying. By all rights it shouldn't be but I still found the lack of class/code file context to be a detriment. I uninstalled and went back to the file/class based debug context view.
Post a Comment