Earlier quoted context omitted.
I'm not surprised. Adobe have been pushing Air for years, nobody really likes it, I hate installing it, and the App performance is often sub-par. By contrast Brackets feels very native. For once corporate policy didn't get in the way of building something cool!
>App performance is often sub-par This is typically down to web developers building desktop apps without the same level of experience. There is nothing baked into AIR to make it perform poorly.
Brackets, a code editor
101–110 of 128 posts
Re: Brackets, a code editor
#102There is always a first phase in a project where I only code HTML and CSS. I create the layout, the scaffoldings, the different pages, etc...
And as amazing as emacs and ST3 are, it's a pain in the ass to do that part with them.
I feel like I'm gonna use Brackets a lot.
Re: Brackets, a code editor
#103I downloaded the editor about two weeks ago. It's fun and easy to use. My only criticism is of the live editing feature. That's what drew me to the editor in the first place, but it seems to be very buggy. It stops updating the preview sporadically — and predictably, each time I open the JS Console. As a front-end dev, I can't really count on a preview that doesn't function with developer tools open. Having said all…
Re: Brackets, a code editor
#104Earlier quoted context omitted.
>App performance is often sub-par This is typically down to web developers building desktop apps without the same level of experience. There is nothing baked into AIR to make it perform poorly.
Air is slower than chrome or firefox
Now it's outdated, so I imagine Chrome is faster.
Re: Brackets, a code editor
#105Earlier quoted context omitted.
I've gotta agree with you here. If you are a professional developer and are still writing non-templated html, I'd be surprised. I think it's crazy that all these tools keep coming out for handling vanilla html and css, while the development community is busy shooting miles ahead with far more powerful preprocessing. I'm working very heavily on convenience tools for advanced dev workflows, hopefully these will bring a…
On big projects I work on, front-end developers start from the PSD and do the HTML first (they just do some templates, not the whole site obviously). Then the JS is either made by them (depending if they know JS) or by a JS specialist. Then the programmers integrate the HTML in the "code/templates" (CMS, whatever). We develop in different web technologies and front-end developers don't learn how to code server side c…
If it's a small project, made to be beautiful, they will do the whole design of all the pages. If it's a huge Agile project, they would instead give me a style guide.
Then, I quickly turn everything into reusable HTML blocks and do the CSS (using LESS). If needed, I'll make custom jQuery (or pure Javascript, but that never happens, really) modules for the template. It's very quick. A full page templates takes me about 1 to 2 hours, if it's very, very complex I may take up to 4 hours.
While I'm working on those, the back-end guys are working of making the CMS work correctly. Sometimes, I give them the templates before they program the page, but most of the time I end up attacking the page after them. I then simply use the building blocks they gave me (and turn all the divs they made into the right HTML5 tags).
We use a lot of different CMS and some of the websites have custom backend (no CMS). We develop in both PHP and .Net.
I know PHP, and I'm comfortable developing Drupal websites. However, I don't get a lot of fun making the backend. The only time I would do it if we are working on a one pager or something like that, since it's faster if I do both back and front for project that are not complex.
I prefer working on the front-end. And I do mean front-end development. Not simply mindlessly slicing a PSD into an HTML page or adding content from a Word document.
Re: Brackets, a code editor
#106I tried to get Sublime Text to do the same thing, live updating, and even found a plugin that mostly does the trick. But it required a lot of setup each time I used it, and still wasn't as good as Brackets.
Brackets has issues, it's slower than a "text editor" ought to be, and the general editing tools aren't nearly as developed as Sublime, but for rapidly producing visuals and designing in real-time, it's stellar.
Re: Brackets, a code editor
#107>> Live HTML Development >> As you code, HTML changes are instantly pushed to browser without having to save or reload the page. Who actually writes non-templated HTML any more?
Me.
My martini untemplate engine is a code generator that inputs HTML and outputs Java.
This creates a one-way flow of work. Designer creates the HTML, I create the backend. When the design changes, the backend (e.g. data binding) breaks during the generation and compile steps. Not in the browser.
Martini isn't ready to demo yet. It will be open source. But documentation and examples take more time that I have right now. Sorry.
Re: Brackets, a code editor
#108>> Live HTML Development >> As you code, HTML changes are instantly pushed to browser without having to save or reload the page. Who actually writes non-templated HTML any more?
We use bog standard HTML with custom data- attributes (whose intention is pretty much obvious) and our binding library automagically populates it. So the learning-curve for people joining the project is basically... "do you know HTML?" Want a span to show the live content of foo.bar.baz? .
Re: Brackets, a code editor
#109Earlier quoted context omitted.
Any particular reason for that? It seems like it should come standard, and it's what initially made me switch back to Sublime.
I would expect us to ship code folding, but we just haven't gotten to it yet. Same for themes (for which there are also extensions that fill in the gaps). It would be a great contribution to the project for people to pick up a feature like folding that ideally belongs in core and helps get it to "core quality" (unit tests, comments, etc.) It's possible that some extensions are already that good and we just don't know…
Re: Brackets, a code editor
#110That and the other day I had this xml file I needed to look at and brackets didn't open it on Mac. Right-click open with, Brackets. It failed. Not sure why it wasn't a bad or large file at all. Text-wrangler opened it fine.