|
|
|
|
Want your app on multiple platforms without rewriting all the code? Here’s a summary of some of the tools, libraries and SDKs out there to support building multi-platform apps. Write once, write everywhere... or something to that effect.
|
|
|
|
|
When we pledge to embrace the adaptable nature of the web—to make our websites responsive and even future-ready—we’re typically talking about diversity of devices. But the web’s diversity also comes in the form of different languages and cultures. Translation affects users’ experiences—and our organizations’ success. It’s time we consider translation part of our jobs, too. Je ne suis pas monsieur Lebowski. C’est vous monsieur Lebowski. Moi, je suis le Duc.
|
|
|
|
|
This is the first in a series of posts that will be going over various aspects of using the new Stellaris Launchpad with GCC. This post is going to be a rundown of how the various compiler flags, linker scripts, libraries and drivers work together to give us a working program for our dev board. Deep dive on the compiler toolset for TI's ARM Cortex board. I am intrigued...
|
|
|
|
|
ECMAScript 5 introduced strict mode to JavaScript. The intent is to allow developers to opt-in to a “better” version of JavaScript, where some of the most common and egregious errors are handled differently. For a while, I was skeptical, especially with only one browser (Firefox) initially supporting strict mode. Fast forward to today, every major browser supports strict mode in their latest version, including Internet Explorer 10 and Opera 12. It’s time to start using strict mode. Strict mode will save you from errors you didn’t even know were in your code.
|
|
|
|
|
During a Vermont.NET User Group presentation on single-page applications, Ward Bell, from IdeaBlade, gave us a look at an open source data access API for JavaScript that he and his team were cooking up. I was very interested. From the perspective of my experience with the Entity Framework, what I saw was comparable to using EF for client-side Web development. The API is called Breeze and at the time of this writing is in beta. Building a data-centric web site with BreezeJS.
|
|
|
|
|
Lately I have been considering what a next-level computing experience looks like (an integrated hardware & software solution). I’ve been imagining the role of gestural mapping, holograms & 3d space, all of which I will likely discuss in more depth at some point. But before we get to the fancy stuff, there is one aspect of the “navigation” experience that is ripe for innovation - and that is the computer keyboard. What’s wrong with the current keyboard? And what can we do about it?
|
|
|
|
|
|
If I could vote you would have my 5. I guess saying that is good enough..
John
|
|
|
|
|
i wish i hadak eybord now
------------------------------------------------------------
Sent to you from my iPad
|
|
|
|
|
... miss the point !!!
gestures etc are 'nice to have' .. but you still need a a method of entering text .. else, you foster a mentality of 'programming is copying and pasting' 
'g'
|
|
|
|
|
Garth J Lancaster wrote: else, you foster a mentality of 'programming is copying and pasting'
Most javascipt programming is already like that 
|
|
|
|
|
In a meeting yesterday. The boss said: But you can just copy and paste this bit of code from that little project over there that already does something SIMILAR 
|
|
|
|
|
Deceptive title - I though it was going to be about unreliable keyboards. I feel like reading it was a waste of time.
Beyond that, it's absurd to think they can make the general public accept a change to an almost 150-year old paradigm. The only way to make the keyboard better is to eliminate it completely in deference to something that is undeniably *better* - not just "better in some ways", but a reasonable and viable replacement. Until we can transmit our thoughts wirelessly to the screen, I doubt if anything "better" is in our immediate future.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Transferring my thoughts to the screen would result in a lot of expletives in my code that I'd just have to clean up.
|
|
|
|
|
|
Here's the deal: any talk of touch-screen PCs is just a ruse. It's been tried. It doesn't work, for a number of reasons.
But neither Microsoft nor any of its (former) PC vendors have anything to compete in the fastest-growing segment of computing appliances: touch-screen tablets. They need to compete because traditional PC sales are down significantly. But they have nothing. So they have a touch-screen Surface that's not really a tablet, and not really a laptop. And Windows 8 is supposed to run on touch-screen desktops... if you can find one. But does anyone really want that?
It reminds me of the early days of iPod. There were... "options" if you really, steadfastly refused to go Apple. But, to be honest, the options all sucked. Zune was the only real potential player, and look how Microsoft screwed that up, too.
But I digress... Touch screen PC? Just ask yourself this: would you want to work all day at an ATM? Didn't think so.
Director of Content Development, The Code Project
|
|
|
|
|
|
I didn't suggest touch screens. In fact, touch-screen PCs will probably result in even worse repetitive motion injuries. As a developer, I see not use in anything but a keyboard and a mouse (short of the fore-mentioned mental-link capability).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
The problem is the unnecessary involvement of physical movement just to copy electrical data from one computer to an other. Please perfect the non-invasive brain-computer interface.
|
|
|
|
|
The article isn't consistent, first he acknowledges ergonomic keyboards exist but aren't wide spread, then says ergonomic keyboards would be an innovation. Honestly, I can't stand them, they're so awkward, and the learning curve just isn't worth it to me. The same goes for alternate key layouts, I could swap around the keys on my keyboard, but what's the point? I don't have any issues with QWERTY, and I don't get why people think it's so problematic (I have a co-worker who uses Dvorak, but he's yet to give me a compelling reason to switch, the best I've heard is "you might type faster", but I've never been bottle-necked by my typing speed...).
|
|
|
|
|
lewax00 wrote: they're so awkward
Yes, especially for we who type one-handed.
|
|
|
|
|
As stated in my post, ergonomic keyboards are not. Not only is the qwerty layout flawed, but the position of the keys is flawed. There are some pretty good ergonomic keyboards (realitive to the ones sold by the companies like Microsoft), but they are very expensive. Then there are concepts like using cords to more efficiently type, like a stenograph. On a Dvorak keyboard, your fingers would have to move significanly less than what they do on a Qwerty.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
