On Fri, Jun 1, 2012 at 1:21 PM, Matt Wilkie <[email protected]> wrote:
> There's a video demo of light table + python at > http://www.chris-granger.com/2012/05/21/the-future-is-specific/ > (3rd example) I don't see any video. Just screen shots. QQQ In traditional web-MVC, the code necessary to serve a single route is spread across many files in many different folders. In a normal editor this means you need to do a lot of context switching to get a sense for everything going on. Instead, this mode replaces the file picker with a route picker, as routes seem like the best logical unit for a website. When you click on one of these, you're given boxes with all of the code related to serving that route - even going so far as to figure out what templates you referenced and getting the subtemplates out of those. This means you have a single context in which you are able to understand the entirety of the code necessary to serve that page. QQQ This is exactly why I use clones to create views. QQQ It occurred to me the other day that what we're talking about is something like a macro system for tools...Imagine being able to create these sorts of experiences on a whim instead of needing hundreds of hours to even get something simple working. If you couple that with the generalized editing capabilities I showed last time, you have what we believe to be the future of tools: an environment that you are able to mold to the exact shape of your problem. QQQ That's why I have always been excited about @button & @command. It's just so easy to put together great tools quickly. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
