I can definitely appreciate the usefulness of realtime here, 'n having led teams in the past I'm all for using tools like Sass/less/blueprint/etc that expedite development time and empower the team. I guess it's the 'Publish' part of this tool that is really irking me, as any environment I've either designed or been a part of has always had a process for sending files to live, and it never included editing and saving files already in a live environment without some intermediary testing platform first.
Instead of publish, I'd rather have a button that says 'commit'.
The problem is you can't use webputty locally, it needs to access the page in order to use it. so anything you're working on needs to be live on the internet
Re:WebPutty: CSS editing goes "boink"
by AndrewHampton on Wednesday July 20, 2011 @03:54PM
(#2787132)
I'm curious if you used this already since you've been working w/ Fog Creek or if this is the first you're seeing it too.
I haven't used it. I will never answer questions about what knowledge I have/had regarding clients' upcoming product releases. You don't have to be Steve Jobs to get touchy about that one, and it's specifically enumerated in most NDAs I sign.
Re:WebPutty: CSS editing goes "boink"
by AndrewHampton on Wednesday July 20, 2011 @04:08PM
(#2787204)
OK, thanks
Doing the same thing with WebPutty would take maybe a dozen lines of code. I'm assuming anyone with multiple environments can make it happen in their language/framework of choice.