Disqus - Latest Comments for morfunk

Re: Only Grab the Files You Need While Using Bower

David Kaneda — Tue, 24 Mar 2015 14:44:42 -0000

I agree, this would make an awesome flag built into Bower-

Re: WordPress -> Ghost -> Harp (part 1)

David Kaneda — Thu, 02 Oct 2014 19:37:35 -0000

Hey Remy- Loving these posts. Just FYI (and sorry for the plug), but you might want to check out Buckets, a project I'm working on: Some similarities with Ghost, but tailored more to the general "content management" crowd, as well as to web designers specifically. In fact, I'm in the process of building in Harp support for frontend assets. Anyway, check it out if you get a chance! http://buckets.io

Re: How we do it: Backups

David Kaneda — Thu, 04 Sep 2014 14:26:42 -0000

Are there any plans/thoughts around backups that involve both MongoDB and ElasticSearch together? It may be app-specific, but for an app that uses both indexes on the same data set, reverting to a previous point in time (for both, simultaneously) would be tremendously useful...

Re: Your next CMS should be Craft or ExpressionEngine

David Kaneda — Tue, 12 Aug 2014 19:24:25 -0000

I'm a long time fan of ExpressionEngine, and more recently Craft, and I'm also working on a new CMS called Buckets: http://buckets.io. My primary points of focus are noted above (custom fields, editorial permissions, etc.), but it also aims to be much faster than these options (built on Node.js), scalable for apps (can be used as middleware), and also provide a better balance of open source and commercial. It's very early on, but I thought it may hold interest, especially for JS-oriented developers-

Re: http://www.webkitbits.com/post/22327920784

David Kaneda — Wed, 09 May 2012 13:14:05 -0000

Actually I totally agree - I'm not recommending my approach so much as saying it's a viable option to some. Ironically, Financial Times is the perfect example of what I'm talking about: They haven't decided to go "all-responsive," they've simply said they're dropping their wrapped, hybrid apps as a distribution model.

They still have a special version of their site, optimized for touch and mobile WebKit — just visit ft.com from your iPhone/iPad to see. Of course, they use responsive techniques throughout, which is great — but at the end of the day, as far as I know, they're very much using a "multi-web" approach.

Re: http://www.webkitbits.com/post/22459788035

David Kaneda — Sat, 05 May 2012 15:37:52 -0000

Ha, thanks, fixed.

Re: http://www.webkitbits.com/post/22327920784

David Kaneda — Thu, 03 May 2012 18:14:44 -0000

I definitely agree there needs to be more done to push browsers forward — Apple notably held too much out, and Adobe seems to be doing nice work pushing things in now. Either way, though, at a certain level it's about practicality. I won't get _too_ into a flame war, but I'll just say, when compared with making several native apps and a web presence, two web is not "twice the work," by a long shot.

If you think your company has nothing to gain by having native apps, go ahead and pull a Boston Globe. But I strongly believe: if you were to wrap that site in PhoneGap and deploy to the App Store, you'd be blasted with 1-2 star reviews. And the work it would take to make that thing feel like an app and rock on WebKit pales in comparison to the effort it would take to build decent native iOS, Android, and Blackberry companions.

Re: http://www.webkitbits.com/post/22327920784

David Kaneda — Thu, 03 May 2012 17:35:36 -0000

Totes. I did it for my post yesterday and forgot on this one... I'll add it in, though it's probably too late to save dashboards :)

Edit: Lame, it only works on Text posts. Sorry, will keep it in mind for next time.

Re: http://www.webkitbits.com/post/22327920784

David Kaneda — Thu, 03 May 2012 17:33:15 -0000

Christian — Thanks for reading :)

I can see where the comparison comes from, but I just don't think this is comparable to IE6. I think, back in the day, the real problem with these sites was _only_ working in IE6. I realize this will make all the "one-web"-ers cringe, but a two web experience ain't all that bad. Especially when you can take that second web experience and use it as your mobile _software_, that is, wrapped in PhoneGap.

Take a look at Xero: http://www.xero.com/account.... They made a Sencha Touch app which they serve on the web for iOS/Android/Blackberry, then they added some native features (like snapping pics of receipts) to it with PhoneGap, and also distribute in the three separate app stores. The experience they deliver to their customers (over 95% coming from WebKit) would not be possible with "responsive". And at the same time, how long does it take to additionally make this kind of mobile site for everyone else? touch-nontouch-comparison.png — Not long, I would think, and that, of course, could be improved with responsive techniques.

Ideology about the web aside, again, what they're doing is a remarkable example of using web tech to deliver a fantastic UX where possible, reach everyone, and leverage skills to make software more efficiently than the competition. It's a great thing, and to me, should be far more celebrated than something like the Boston Globe, selectively hiding/combining content depending on screen width.

Of course, not everyone uses these techniques as thoroughly and responsibly as they should, and as you said, this could lead to trouble. But that's the web for ya.

Re: Why O, why? Thoughts on Opera’s Implementation of WebKit’s Prefixes

David Kaneda — Thu, 03 May 2012 14:06:06 -0000

I agree, shame on them. But this is far different than IE. The problem with most sites back then was getting a blank page or being told to use another browser.

WebKit's features can be used completely progressively, and are worked on by lots of companies instead of one. Most of those companies also promote their suggestions to the W3C, as opposed to MS a decade ago-

Re: Why O, why? Thoughts on Opera’s Implementation of WebKit’s Prefixes

David Kaneda — Tue, 01 May 2012 19:38:01 -0000

Thanks Peter, and in some ways you're totally right: I'm underplaying the potential issues to a degree. On specifics, I could easily see transform, especially when relying on translate, being an issue -- though transitions, I believe by design, are by and large decorative. It's also important that they're trying to target high profile issues, and I don't see translate used in a potentially blocking way, that often.

I've had your article open in a tab for the entire past day, so definitely appreciate you taking the time, and also linking here :) I think we're actually pretty close to the same page in that it's how the rules are selected, and that "it’s a one-off solution to a problem that would be better off resolved in a different way."

Re: The State Of HTML5 Video

David Kaneda — Mon, 23 Apr 2012 21:39:47 -0000

Yes, the format war is super annoying. One could also say it should be Apple who opens up H264 :)

Re: jQTouch and Sencha Touch: Which is right for you?

David Kaneda — Tue, 03 Apr 2012 14:53:58 -0000

jQuery Mobile has its benefits, but generally suffers by playing to the lowest common denominator. The recent versions of jQTouch have an advantage when it comes to being lightweight and rich. Some more info: http://blog.jqtouch.com/

Re: Goodbye Sencha, Hello World

David Kaneda — Tue, 03 Apr 2012 00:54:12 -0000

Nothing officially, but I hope to spare some time to spend on it over the next week.

Re: Goodbye Sencha, Hello World

David Kaneda — Mon, 02 Apr 2012 18:09:18 -0000

Hoping so! :)

Re: Goodbye Sencha, Hello World

David Kaneda — Mon, 02 Apr 2012 16:07:25 -0000

Ha, soon enough young one. At the least, I'll have a secret version in your inbox this week.

Re: http://9-bits.com/post/18852496252

David Kaneda — Wed, 28 Mar 2012 20:31:39 -0000

We hope to get Android packaging support soon, but it's not currently there. AFAIK, WebWorks makes it pretty easy to wrap a web app.

Re: Google+Facebook

David Kaneda — Wed, 21 Mar 2012 17:17:04 -0000

That's definitely interesting. Another option — and I realize I'm just being crazy here — was for Google to add Facebook/Twitter integration into its platform, meaning just Search, Maps, etc. Could have been less likely to have been blocked, made them relevant, and saved a whole lot of time. Totally not saying this is fact, btw, I just like pondering what could have been :)

Re: Google+Facebook

David Kaneda — Wed, 21 Mar 2012 17:11:39 -0000

I was not! Do you have any links that mention this?

Re: Email Unsubscribe from Hell - South Pole Steve

David Kaneda — Wed, 07 Mar 2012 18:37:48 -0000

It's a common location, clear and easy to find (you found it!), and we're not giving the link ultra-low contrast or anything, like I've seen others do. Not having an underline is also pretty common if you were to look around at a lot of other company emails, including Apple. We're certainly not trying to make it _difficult_ to unsubscribe.

Re: HTML5 Scorecard: Amazon Kindle Fire

David Kaneda — Sun, 19 Feb 2012 19:26:31 -0000

I'm postin' a comment on Facebook yo.

Re: HTML5 Scorecard: Amazon Kindle Fire

David Kaneda — Sun, 19 Feb 2012 19:26:02 -0000

This is super great, hooray.

Re: Sencha Touch: A Cross Platform HTML5 Mobile Application Framework

David Kaneda — Wed, 03 Aug 2011 14:40:55 -0000

Kish- There are some great samples here: http://www.sencha.com/produ...

Re: Custom Styling a Sencha Touch App

David Kaneda — Thu, 16 Dec 2010 13:08:00 -0000

Hi Shea — Glad to see you're getting into the theming in Touch! You have a lot of great tips in here, but just so you know, the only different we recommend making is always creating your own stylesheets, instead of editing the ones provided in the library. We actually have a similar article going up on http://www.sencha.com/blog/ tomorrow-

Best,
Dave

Re: Custom Styling a Sencha Touch App

David Kaneda — Thu, 16 Dec 2010 13:08:00 -0000

Best,
Dave