templates with declarative event handling, not inside the same file as their component definition add a lot of file shuffling time to my dev
-
-
Replying to @ryanflorence
@ryanflorence I like proximity as well. I have just trained myself to split screen accordingly.2 replies 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner yeah, its less of a big deal when you're working on a specific component, but jumping around the project to add features ...3 replies 0 retweets 0 likes -
Replying to @ryanflorence
@ryanflorence I think my ideal system would support inlining but encourage separate files for big templates@stefanpenner3 replies 1 retweet 1 like -
Replying to @wycats
@wycats The ideal system would be composed out of many small components.@ryanflorence@stefanpenner1 reply 0 retweets 0 likes -
Replying to @BrianDiPalma1
@BrianDiPalma1@ryanflorence@stefanpenner Big templates are usually just static content. I do not want to make l a component per sentence.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Right, I deal with apps not static sites/very little static content in desktop replacement apps@ryanflorence@stefanpenner2 replies 0 retweets 0 likes -
Replying to @BrianDiPalma1
@BrianDiPalma1@ryanflorence@stefanpenner Skylight is a desktop replacement app and the top level still has lots of static.3 replies 0 retweets 1 like -
Replying to @wycats
@wycats We are replacing Bloomberg trading apps, must be highly configurable/flexible.@ryanflorence@stefanpenner1 reply 0 retweets 0 likes
@BrianDiPalma1 @ryanflorence @stefanpenner fair enough. Top level template might be boring then
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.