sjs/samhuri.net
1
0
Fork 0
mirror of https://github.com/samsonjs/samhuri.net.git synced 2026-04-27 14:57:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

update post 'My kind of feature checklist'

Browse source
This commit is contained in:
Sami Samhuri 2015-05-14 18:46:38 +00:00
parent fd879e9b1a
commit 23ab7a52ad
2 changed files with 40 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
public/posts/2011/12/_data.json
View file

@ -34,14 +34,16 @@
"link": "http://calendar.perfplanet.com/2011/i-see-http/" "link": "http://calendar.perfplanet.com/2011/i-see-http/"
}, },
"my-kind-of-feature-checklist": { "my-kind-of-feature-checklist": {
"id": "my-kind-of-feature-checklist",
"author": "Sami Samhuri",
"title": "My kind of feature checklist", "title": "My kind of feature checklist",
"date": "19th December, 2011", "date": "19th December, 2011",
"timestamp": 1324354805, "timestamp": 1324354805,
"link": "http://www.marco.org/2011/12/19/amazon-kindle-vs-ipad",
"url": "/posts/2011/12/my-kind-of-feature-checklist",
"tags": [ "tags": [
], ]
"url": "/posts/2011/12/my-kind-of-feature-checklist",
"link": "http://www.marco.org/2011/12/19/amazon-kindle-vs-ipad"
}, },
"new-release-of-firefox-for-android-optimized-for-tablets": { "new-release-of-firefox-for-android-optimized-for-tablets": {
"title": "New Release of Firefox for Android, Optimized for Tablets", "title": "New Release of Firefox for Android, Optimized for Tablets",
@ -63,4 +65,4 @@
"url": "/posts/2011/12/the-broken-pixel-theory", "url": "/posts/2011/12/the-broken-pixel-theory",
"link": "http://jtaby.com/2011/12/25/the-broken-pixel-theory.html" "link": "http://jtaby.com/2011/12/25/the-broken-pixel-theory.html"
} }
} }

41
public/posts/2011/12/my-kind-of-feature-checklist.md
View file

@ -1,8 +1,35 @@
Marco's feature checklist in favour of the iPad illustrates how easy it is The latest technology I've been learning is Palm's SDK for webOS,
to rig these things. Combined with Amazon's checklist favouring the Kindle Mojo. My first impression is that it's a great platform and
Fire this would be mildly useful, half as long as a modest review, and with Palm could do a great job of 2.0 if they cut down on some of the
more or less the same conclusions. verbosity of gluing together the UI. I have learned to like
JavaScript over the years as I learned that despite its
warts [there are good parts](http://ca.video.yahoo.com/watch/630959/2974197)
too. If you squint just right you can see that it's scheme with
Algol syntax. HTML and CSS are what they are, but with WebKit running
the show and only a single engine to target it's not that bad. I've
gone from Eclipse to Emacs for the coding itself and highly recommend
Emacs for Mojo development. There is nothing that I miss from the
Eclipse or Komodo Edit thanks to the fact that Mojo uses open
languages and standards.
Seriously though some of the items on Marco's list are pretty important to
most people but would never make anyone's feature checklist. Goes to show As far as actual development goes the Mojo documentation steers you
that most feature checklists are bullshit. towards a combination of Eclipse, Palm's Mojo plugin for Eclipse,
and the Aptana Studio plugin. My editor of choice is Emacs but
I decided to give it a spin just to get started quickly, how bad
could it be? I'm not going to get into details but I will say that I
don't think I'll ever use Eclipse for anything; it's far too
sluggish and provides no compelling features for the languages
that I use. I tried Komodo Edit and it was significantly
better but still not for me. Emacs is great for editing HTML,
JavaScript, and CSS so all I really missed from the IDEs were the
shortcuts to package, install, and launch apps in the
emulator. I headed over to
the [Emacs Wiki](http://www.emacswiki.org/) and
downloaded Jonathan
Arkell's [Mojo
support for Emacs](http://www.emacswiki.org/emacs/MojoSdk)
which provided a great base to get
started with. There are wrappers around (all?) of the Palm SDK
commands but it needed a bit of work to make it just do what I
wanted with as little input and thought as possible.