by Peter Seibel
-- A fantastic collection of interviews with 15 famous programmers. Contains some great history and insights on the field of "computer science."
-- Geeks, drugs, and deception. An entertaining look into the (fictional) lives of techno con artists, and how a recently-fired comic book artist get pulled into their inner circle.
"
-- Particularly useful reference when trying to eek out a few extra milliseconds of load times in older browsers.
-- Interesting tech, and somewhat engaging, but disappointing ending (or lack thereof.)
, by Neil Strauss
-- An engaging, first-person account on transforming from an urban writer into "Jason Bourne."
, by Cory Doctrow
-- A high school hacker fights the 'Department of Homeland Security' to reclaim American civil liberties after anti-terror tactics are taken to a new level.
-- Techniques-for, and the value-of sketching interactivity before developing products. Good ideas. OK book.
" -- About finding untapped opportunities in your market and repositioning yourself to capitalize on them. Easy to grasp; Longer then it needed to be.
" -- A thin book with some good best-practices, but a little disappointing. Perhaps it's JavaScript's fault, not the author's ;-)
" -- Good overview of usability issues in designing HTML forms, backed by examples and eye-tracking research. I bought the 
" by Marshall Goldsmith
-- Discusses interpersonal skills (and how to identify and fix them) that most commonly hold executives back in their career advancement.
"
-- Lesson: Cut the corporate B.S. and stop wasting your time. Focus only on what matters most.
"
-- Lessons on handling tough conversations: firing people, relationship problems, hostage negotiations (well, maybe not that last one.) Wasn't an exciting read, but I've been paying more attention to "turning points" in conversations since reading it.
"
-- Lessons in building reusable ("pluggable") Django applications. Assumes you know the basics of Django and Python.
"
-- I really enjoyed this one. Lots of suggestions and strategies for negotiating.
You’ve heard about Nokia’s open source web browser for S60 based on Apple’s WebCore/JavaScriptCore right? I’m sure you have… but did you know that you can try it out right now? I didn’t either.
The odds are pretty good that you (like me) don’t have an S60 3rd Edition phone that can run the new browser; Fortunately, there’s a build included in the new S60 3rd Edition SDK. What you need is the final build of the SDK, which can be found here: http://www.forum.nokia.com/main/0,6566,034-4,00.html. (If you get totally lost on Forum Nokia, don’t forget about the Google Mini powered search: http://search.forum.nokia.com/!)
The download page defaults to the Japanese version, so make sure you change the drop-down menu to “SDK for 3rd Edition” if you want English. (Note: the “beta” version doesn’t seem to have the new browser.)
Once you install the SDK (and sadly, you’ll need a Windows machine for this), launch the SDK, wait awhile, and once the phone menu screen comes up, navigate to the “Installed” folder. In there you will find an application called “Web”. That’s the new browser!
I did some quick browsing from the emulator and took screen shots to give an idea what this new software is capable of:
–
[Update: 2006-05-24]
The OpenDarwin Wiki now contains a page with instructions on running the new S60 browsing within the emulator. Thanks for the tip Franklin!
Artem 12:15 am on March 28, 2006 Permalink |
Errgh, I hate the horizontal scrolling. Whatever good the rendering is, while there is Opera with its “small screen rendering” Nokia browser is out of competition… Well, it would be out of competition if there was a competition :)
erik 3:08 pm on March 31, 2006 Permalink |
Yeah, two different approaches. Opera adapts the page to fit on a small screen. The Nokia browser squeezes where possible, but obeys coded widths and positioning, making it conform as best as possible to the intended page design. I like both approaches depending on the need. The Opera approach works really well for sites that have put some thought into page-flow for small screens. The Nokia approach works better for capturing the desktop experience with sites that don’t render well when the browser chooses to layout the screen in a manner other then how the designer specified. And as site interactions become more rich (ex., touch screens and AJAX), the need to render as declared in the HTML becomes somewhat more critical for the customer experience.
The lines begin to blur when you use larger screen though. On the Nokia 770, for example, even sites such as Google Mail work perfectly with Opera.