feedhenry/fh-studio — pull request #37 by skalee (2012-02-09 18:10:46+00:00)
Title: Create Configuration section as per current studio

https://github.com/feedhenry/fh-studio/issues/20

Notes:
1. Issue description suggests putting platform tabs to the left. Since this is only a matter of stylization and because of lack of mockup whole stylization of section screen is temporary, I left them on top. And point 1. also applies. BTW I think that uppermost position is better because editor tabs are also on top.
2. Jakefile – me and someone else did the same job – traveling through dust directory. Since my version produces nice output and fixes some very minor bugs, I left my version. Won't be angry if you restore the other content. Both versions should work. I will post pull requests with such minor changes in future to reduce risk of work duplication.
3. Do you use jslint or sth similar? I could check my code against such tool.
4. Updating config could be optimized by doing it concurrently. I am not yet familiar with concurrency in nodejs (I've heard that nodejs utilizes erlang-style message passing which I am familiar with, but haven't digged to it yet).
5. I've introduced new helper for translations (type sth like {#t key="some.translation.key"/} to get nice, translated output. This is better than {lang.key} style for following reasons:
a) it is not prone to context issues, you can switch contexts and still you got {#t} helper (as long as you won't hide it by redefining)
b) writes "missing key" in red when translation is lacking
c) in future (had trouble with chunk.map which should do the job, see source) it may even support constructs like {#t key="some.{key.from.context}"/}

I think that's all.