I've read further down that by 16-bit color they mean 16 bits per channel. But then they should say that. By the strict definition of 16-bit color my post is correct, what I outlined is part of the procedure used to make images compatible with bootloader screens etc. that can only use 16-bit color images.
This is how I have it set up on my work PC (and how I use it on a PDA - with the tiny screen, switching windows is easier than trying to cram everything into the already crowded 4" screen) but on most computers a single-window mode would be preferable.
The problem is that it's used as a loophole to allow companies to use GPLv2 code in their products while effectively not having to give anything back - they can give you the code but with no access to the special hardware needed to run it, it's practically useless. Same deal with Android phones with locked bootloaders (and you could argue, with unavailable closed-source drivers).
Then in 10 years they'll dump it altogether for the next new thing and WP devs will be shocked, SHOCKED that the career they built around developing in a proprietary language for a walled-garden platform is going into the shitter.
If they don't want to get ripped off they can re-license their code, rather than acting surprised when businesses rip off something that is totally legal to rip off. I mean it's not even like Tivoization and the GPLv2 where it's a strong violation of the spirit of the license if not the letter of it, but there's nothing ensuring contributions back to BSD projects apart from the most tenuous of implied gentleman's agreements.
But why would those signatures be needed at all? Android allows sideloading without any keys (and therefore is requiring them in the app store for non-technical reasons), Maemo/MeeGo just uses plain Linux repos...it's not necessary.
I used to download (known good) Windows freeware from them sometimes, but rarely. Probably been to their site less than once per year over the last decade.
That's not sourceforge's fault any more than getting an infected crack from TPB would be TPB's fault. Sourceforge just hosts whatever the hell you upload.
Those who create and support BSD software have no problem with having their software ripped off, if they did, well it wouldn't be BSD licensed would it?
The GPL crowd, that is, the vast majority of the OSS community, has a different definition of openness where being ripped off is frowned up.
Oh I had no idea, since it started with "If Android were GPLv3 licensed" (and Android != Linux kernel) and nobody said anything about a GPLv3 kernel until you brought it up...
Good, then they can stop taking from the OSS community and giving nothing back, and they won't be able to wave the GPL & Linux flags around as part of their openwashing attempts.
Lemme get this straight, you want to allow tivoization? If so just be honest and use the BSD license, that's practically what tivoization turns the GPLv2 into anyways.
Exactly, this is why I support the GPLv3 over the GPLv2. The only things the GPLv2 allows that the GPLv3 doesn't are tivoization and patent timebombs. If a company needs one of those things to offer an open source product, well fuck 'em, we don't need their shit (and yes that goes for the prominent tivoized mobile OS. Better, more open OSes were marginalized due to Android's success, and now Android is practically closed, so in the long run I'd say we would have been better off without it. MeeGo or WebOS could have taken its place).
Slashdot Mirror
Something boring and commercial with no imagination in it, like PhotoShed or PicWorks.
I've read further down that by 16-bit color they mean 16 bits per channel. But then they should say that. By the strict definition of 16-bit color my post is correct, what I outlined is part of the procedure used to make images compatible with bootloader screens etc. that can only use 16-bit color images.
I've never had anyone laugh at GIMP so far IRL, I've gotten way more laughs about Ubuntu, Gnome and SugarCRM.
No GIMP segfaults here, on Ubuntu, Debian, CentOS...or any Windows versions.
This is how I have it set up on my work PC (and how I use it on a PDA - with the tiny screen, switching windows is easier than trying to cram everything into the already crowded 4" screen) but on most computers a single-window mode would be preferable.
For 16-bit color:
Image --> Mode --> Indexed --> Generate optimum palette --> Max colors = 65536, Convert?
For CMYK support, maybe this?
http://www.blackfiveservices.co.uk/separate.shtml
Prozium has no negative side effects.
the robot arm is THIS fast!
you can take that software and use it on any other hardware you want.
Assuming it's not cryptographically tied to any hardware or requires any proprietary parts you can't buy.
The problem is that it's used as a loophole to allow companies to use GPLv2 code in their products while effectively not having to give anything back - they can give you the code but with no access to the special hardware needed to run it, it's practically useless. Same deal with Android phones with locked bootloaders (and you could argue, with unavailable closed-source drivers).
The only fee is for listing in the Ovi store.
And for those who don't know, the Ovi store is an optional, separate, curated store for commercial apps.
Then in 10 years they'll dump it altogether for the next new thing and WP devs will be shocked, SHOCKED that the career they built around developing in a proprietary language for a walled-garden platform is going into the shitter.
That's the topic of the article but not this particular discussion. I can only hope you haven't been following.
If they don't want to get ripped off they can re-license their code, rather than acting surprised when businesses rip off something that is totally legal to rip off. I mean it's not even like Tivoization and the GPLv2 where it's a strong violation of the spirit of the license if not the letter of it, but there's nothing ensuring contributions back to BSD projects apart from the most tenuous of implied gentleman's agreements.
Comin' straight from da playground
But why would those signatures be needed at all? Android allows sideloading without any keys (and therefore is requiring them in the app store for non-technical reasons), Maemo/MeeGo just uses plain Linux repos...it's not necessary.
I used to download (known good) Windows freeware from them sometimes, but rarely. Probably been to their site less than once per year over the last decade.
That's not sourceforge's fault any more than getting an infected crack from TPB would be TPB's fault. Sourceforge just hosts whatever the hell you upload.
Those who create and support BSD software have no problem with having their software ripped off, if they did, well it wouldn't be BSD licensed would it?
The GPL crowd, that is, the vast majority of the OSS community, has a different definition of openness where being ripped off is frowned up.
Oh I had no idea, since it started with "If Android were GPLv3 licensed" (and Android != Linux kernel) and nobody said anything about a GPLv3 kernel until you brought it up...
I assume you're being snarky (open source will never sell hurr durr) because there's nothing in the GPLv3 to prevent that.
Good, then they can stop taking from the OSS community and giving nothing back, and they won't be able to wave the GPL & Linux flags around as part of their openwashing attempts.
There's no GPLv3 Linux kernel as we all know, but the N900 can run MeeGo which is 100% FOSS.
Lemme get this straight, you want to allow tivoization? If so just be honest and use the BSD license, that's practically what tivoization turns the GPLv2 into anyways.
Exactly, this is why I support the GPLv3 over the GPLv2. The only things the GPLv2 allows that the GPLv3 doesn't are tivoization and patent timebombs. If a company needs one of those things to offer an open source product, well fuck 'em, we don't need their shit (and yes that goes for the prominent tivoized mobile OS. Better, more open OSes were marginalized due to Android's success, and now Android is practically closed, so in the long run I'd say we would have been better off without it. MeeGo or WebOS could have taken its place).