Click a filter below to apply it to results
If you've hung on to your BlackBerry smartphone in the hopes that you'll one day see an open source version of it's code, you're in for a long wait.
Speaking at the BlackBerry Developer Conference hosted by Research In Motion (RIM), RIM Senior Software Developer Cassidy Gentle said, I would expect some of our Eclipse or Mobile Tools for Java could be made available on an open source basis, but as for our APIs or other softwareﾗthat's a pretty big leap.
Earlier this week, the Qt Labs at Nokia announced a new project, QtMobility. QtMobility's primary goal is to offer a new set of Qt API development tools for mobile device applications.
While this will certainly make life easier for developers working with the Qt framework on specific Nokia devices, one of the best (and intentional) fringe benefits is that the new API tools are cross-platform. A single application, then, can be built and maintained for any supported Qt platform -- regardless of the mobile device model or manufacturer.
How do you know when a proposed software contract principle is really broken? When the Linux Foundation and Microsoft have their respective legal departments sit down and pen a joint letter asking it be reconsidered. ZDNet's Mary-Jo Foley has written a nice, legalese-free summation of the story.
In short, the American Law Institute (ALI) has proposed some guiding principles for judges, lawyers and other legal professionals working with software-related cases to aid in settling software licensing issues. Given how quickly everything about software delivery and production changes, this in and of itself is a decent enough idea. The problem is one particular principle, a policy calling for a non-disclaimable implied warranty of no material hidden defects. Both the Linux Foundation and Microsoft say this is a disadvantage all around -- discriminating and subtlely changing between various licensing, business, and distribution models.
