Depending on your needs you may find RSP's Earth to be a viable solution.
It's cross-platform and has a web interface (though you could build a desktop one easily enough if you wanted to).
skyphyr writes: "Turbosquid mailed its top sellers asking if they'd be interested in entering an exclusivity agreement. Competitors warned their vendors about the risks of going exclusive with Turbosquid. Potential loss of income in the short term, and reduced royalty rates in the long term. Rather than shelve the clumsy attempt at a stealthy cutoff of the competition's air supply Turbosquid instead effectively held their vendors' future income hostage. Royalty rates for vendors who do not go exclusive will be dropping from 55% to 40% on September 1st 2009.
That's a good point, but it didn't bother the ISO when approving OOXML.
Though the W3C haven't scrapped the video tag and Microsoft has made no commitment there. Apple are a smaller player than Mozilla in the browser market. So either way we're looking at inconsistent behaviour.
On the other hand if people feel the standard provides benefits then they'll use the products which support it. So this puts the balance back towards providing a solid spec in the interests of end users. If there aren't benefits the standard will fail if there are benefits then the products which refuse to support it will fail.
That refuses to set a standard because people who should be implement it say they won't?
Simply choose the most appropriate technology, detail the requirements fully in your standard.
It's then a matter for the vendors to decide if they wish to make a standards compliant product
The point of a standards body is to put the interests of the general public first. Failure to do this
is failure to fulfil their purpose. Doing so because of what are effectively bullying tactics is even
worse as you've just decided to put corporate interests ahead of people's.
First ISO corrupts itself into virtual irrelevance now we're seeing W3C fail. Are there any
standards bodies left with the tenacity to get their job done?
Android had a nice half-way option for this. When you type a password in the last character you typed
appears and the rest are bullets. It can be turned off so it's all bullets. This way you have feedback on
what you typed without completely losing security. Some of the dialogs also have a show password
option. So if you really want to you can let other steal your password more easily...
I'd be curious to know what exactly the contracts they had with them stipulate. My guess is it's something along the longs of we own your information once you pass it to us. Ooopppss - guess you really should read those things before signing.
Anyone actually seen it?
skyphyr writes: "A couple of weeks ago I read a review on jroller.com which I felt was inaccurate and glossed over important pieces of information which a developer considering the purchase of a book would want to know. So I added a comment on the site citing these issues to help make the review more useful to others who may be considering purchasing the book. I dropped by today and saw they've changed my comment attempting to make it another gushing complimentary coverage of the book. This is not an accurate reflection of my opinion of the book so I'm counting on Slashdot to set the record straight.
Seeing I'm here my original comments were almost exactly as follows.
-------------------------------- I feel your compliments for this book are a bit excessive here. While it is useful their coding is a little sloppy with inconsistent naming conventions used, creating variables for return values from functions used only once which not only makes the code less readable, but also adds extra memory allocation overhead on a device where this is damaging to performance and battery life. It also includes at least one piece of incorrect information (regarding SQLite databases).
Having said that the book is certainly good enough to get you up and running providing a more application centric overview of android development than the android sdk documentation (which is more API centric) does.
So perfectly written, no, but worth reading if you're a competent coder and just wish to get familiar with the details of android development. --------------------------
To add some additional information about the book for those interested. It contains significant portions which detail APIs that have been removed since the API was finalized for version 1, and in all likelihood will either never return, or been in a significantly modified form in order to ensure sufficient abstraction for the underlying implementation to provide a good base for application development without pushing internal android classes into the SDK.
So to reiterate the book certainly has some value, but I'd be most interested in having a good look at Ed Burnette's Hello, Android and Mark Murphy's Busy Coder's Guide(s) to Android Development. I would recommend that interested developers look at all three before deciding which to purchase."
Organize to have you and these vendors each bring along a system and a hacker. Their hacker tries to compromise your Free Software system, your hacker tries to compromise their windows system.
That should settle it rather efficiently. Just to put a little doubt into anything the "I"SVs may say make sure your client reads this first http://www.linux.com/feature/131059
What the author misses entirely is while he feels it is less likely to happen less likely is still more likely than utterly impossible.
There are other technologies available, such as Qt, where microsoft has no potential for a valid claim over the language. Why, as a developer, would I choose to put my code in a position where this concerns exist instead of taking a path that avoids it entirely?
skyphyr writes: "A storm is brewing on the Adobe forums where members of the VFX industry is requesting that Adobe restore the CS2 handling of OpenEXR files. The OpenEXR format was designed by ILM and has received wide ranging support within the VFX industry. Adobe has taken a disputed interpretation of the EXR specifications which causes data to be destroyed with the files are opened within photoshop.
Adobe's response to user concerns so far has been to tell the professionals for whom the format was designed that they are wrong. As if it wasn't enough to take advantage of their monopoly to turn a blind eye to the industry's concerns, they decided to engage using derisive language their opening response saying "you're still asking for your imagined solution to a problem as you understand it (back the the screwdriver for nails thing). If you want a useful solution, we're going to have to talk about the larger problem, larger workflows, and consider alternative solutions (you know, reach for a hammer)." Soon followed by "Please read some file format documentation." and sinking back to ridiculing metaphors "And even more so when you are clearly ignoring standards or misusing the tools ("But I want my screwdriver to drive nails better").""
skyphyr writes: "The HeliOS project is surging ahead with having just made another two announcements. They've landed sponsorship from a well-known linux company. Those of you who don't follow the HeliOS project may not be aware that Ken tirelessly works to be the change he wants to see and the linux community is better for it. If you've got any spare hardware or a few bucks they are, as always, after hardware to help the community."