|
Given your hardware constraints, would a limited set of named colors be useful [^]
Off-topic: It might interest you to explore Pantone (subtractive) colors: [^], [^]
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
The way C++ works none of the colors are instantiated unless you use them. Strings ... that's not *as* true, so I'm wary of strings. Basically, until I can find a use case for having an actual string in the code for a color name, I'm going to avoid it.
All of the X11 colors I declared are good because like I said, they are only instantiated in the final binary if they are used, and even then they are represented by a single machine word.
The subtractive color models like CYMk? I can support those, I just have nothing that uses them yet so I haven't created a pixel with those channels.
This library will support pretty much any color model, with the possible exception of color models that are dependent on spatial positioning.
Real programmers use butterflies
|
|
|
|
|
|
|
Is that a shaven or an unshaven..
I meant, what is the airspeed of an unshaven European beaver, versus an African unshaven beaver?
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Thats easy - European beavers are pink (close to red) and red always goes faster.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
[...]
Mycroft Holmes wrote: and red always goes faster. The more blood is pumped through it..
So I shut up here. This no Soapbox
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
That's the colour of rock-climbing helmet I asked for
|
|
|
|
|
It was probably done by a modern beaver that wanted internet in his home.
Could happen over here (Netherlands) too as the beaver is returning after a period of absence.
|
|
|
|
|
Codewitch
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
<rant>
Why do vendors insist on launching elephanting web pages at the end of their supposedly enterprise-grade installers when you're installing them under the System account and you used the damn /quiet switch !?!?!?!?!?!?
THERE'S NOBODY LOGGED INTO THE ELEPHANTING MACHINE TO SEE THE ELEPHANTING WEB PAGE!
</rant>
<grumble>
Now I have to get out InstallShield and go hunting for a custom action and rip it out... elephanting vendors...
</grumble>
|
|
|
|
|
Dave Kreskowiak wrote: and you used the damn /quiet switch !?!?!?!?!?!?
THERE'S NOBODY LOGGED INTO THE ELEPHANTING MACHINE TO SEE THE ELEPHANTING WEB PAGE! Because marketing demanded it.
It's not about being reasonable. If we were, marketing had no reason to exist.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
My favorite belongs to the hardware security key we use. Their installer can be run with a UI or "silently". Running it "silently" displays more windows (message boxes mostly) and requires more clicks than the full UI version.
Dumbasses.
Software Zen: delete this;
|
|
|
|
|
Yeah, I got another app that's "enterprise", from a major vendor that shall stay nameless. That thing assumes the users are admins on their own machines, like that's still a thing. When the install completes, it launches Word and a giant "readme.doc", and you can't turn it off! It's an .EXE installer so I can't modify it to remove that function! GRRRRRR!!
The vendors response? "Put in a feature request to remove it and maybe we'll get around to it."
Well, since this was supposed to go on some 3,000 machines, and I can't install it silently as System without it still launching Word, that's a large chunk of money this vendor is now missing out on while we go look for another product.
|
|
|
|
|
Have you considered getting it "repackage" professionally....?
Even if it is (on the surface) an exe it may still contain MSI's... these are (fairly) easily customized using Transforms... if you have to bite the bullet a complete repackaging (capture installation and repackage as an MSI) is an option but be sure that whoever does it is a "Professional" and consider possible updates in the future...
Who the f*** is General Failure, and why is he reading my harddisk?
|
|
|
|
|
More than anything else, I don't think that the customer should have to pay to fix broken software for the vendor.
Not that it doesn't happen all the time but I still, strangely, think the vendor is responsible for this sort of thing.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Oh, don't get me started on broken installers.
Keep in mind that vendor get paid to write software and they spend a ton of time doing that. Installers tend to be afterthoughts that they're not so hot at understanding. You'd be surprise at how many installers I come across that do really stupid things or are just broken and need to be fixed. Sure, they'll install/uninstall the software, but they also end up doing subtle crap that screw things up.
For example, I had a vendor include a custom action in their .MSI installer that indiscriminately killed off all of the WMI provider host processes during uninstall. Those would be the WmiPrvSe.exe processes you see at the bottom of Details in Task Manager. Well, doing that craps out all of WMI on the machine. SCCM (Microsoft's endpoint management and deployment suite) is heavily dependent on WMI. You can guess what chaos ensued when I uninstalled that piece of crap. If you we're running something that was dependent on WMI, you'd never know that happened. Restart the machine and all evidence of it happening is gone.
I cracked open the installer and found the offending (offsensive) custom action. Called the vendor. "Oh, really? It did that? Could you tell us where that is and what to do to fix it. The guy who builds our .MSI's doesn't work here any more..."
I see sh*t like this once or twice a week.
|
|
|
|
|
Dave Kreskowiak wrote:
I see sh*t like this once or twice a week. They shoot horses, don't they?
(make sure other's watch so they don't do the same and get the same "corrective therapy").
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I wish that was an effective deterrent.
|
|
|
|
|
Deployment of *any* software is always last on the list of priorities (a bit like security ) so basically a developer has to use (largely unknown) tools that present a next, next, next installation expecting to be a local admin.... don't talk about unattended... they just don't have the expertise...
Who the f*** is General Failure, and why is he reading my harddisk?
|
|
|
|
|
Unattended is THE main requirement in my house. I'm getting sick of vendors telling me to install it by hand for the users because they assume users can do it themselves when they can't, or won't (it's not in the contract,) or will never pick the correct options if any, even if there's just one! Grrrrr
"Oh yeah? You think I should go install by hand on thousands of machines, do ya?"
"oohhhhhhh We'll get back to you."
|
|
|
|
|
I am the professional. You'd be surprised how hard it is to find a place that can actually repack.
There's no .MSI in the thing and I verified that with the vendor. It's straight up executable. That's also when they told to me to put in a feature request.
Setup captures are a last resort as we try to stay as close to the vendor installer as possible. The captures always pick up garbage, even on a machine stripped down to nothing specifically setup for the purpose. For an installation that runs for 45 minutes on a normal machine, that's a lot of time to pick up a lot of garbage to trim out of the install. Not to mention captures that include drivers are a royal pain in the ass to get perfect.
And then there's dealing with the bugs in the capture software.
|
|
|
|
|
Quote: For an installation that runs for 45 minutes on a normal machine, that's a lot of time to pick up a lot of garbage to trim out of the install.
That's why I said a "Professional".... if they are good that shouldn't be a problem...
Quote: Not to mention captures that include drivers are a royal pain in the ass to get perfect.
Drivers are easy... as long as they are signed
A good packager knows his tools (ergo and it's bugs... )....
Seriously, used to do this all the time in a previous life (10+ years ago)... some of the sh*t that was thrown at us....
Who the f*** is General Failure, and why is he reading my harddisk?
|
|
|
|
|
Phil.Benson wrote: if they are good that shouldn't be a problem...
It's tedious to do when you end up grabbing thousands of keys, and the tooling bugs you deal with won't show you all the keys it grabbed and/or it crashes when building the .MSI project because of certain registry value content, which can show up anywhere in those couple thousand keys. (Good Hunting!) You have to take those out, build the project, then go put them back in in the .MSI.
You were saying something about knowing the tools, and the bugs?
Phil.Benson wrote: Drivers are easy... as long as they are signed
Yeah, about that signing thing. Not everyone does it, especially said nameless vendor, even though MS pushes it and now tries to make it as mandatory as possible. I've run into more than one occasion where vendor signing certs are expired. Yada, yada, yada, ...
Those are fun phone calls when you tell them and they go scrambling to renew it, rebuild, and get you new source, 'cause, you know, deadlines.
|
|
|
|
|
Quote: It's tedious to do when you end up grabbing thousands of keys, and the tooling bugs you deal with won't show you all the keys it grabbed and/or it crashes when building the .MSI
A good packaging pro knows the limits of his tools ,Wise 8(unfortunately dead), AdminStudio, RayPack whatever... also solid exclusion lists and OS knowledge is a *must*...
Quote: Yeah, about that signing thing. Not everyone does it, especially said nameless vendor, even though MS pushes it and now tries to make it as mandatory as possible. I've run into more than one occasion where vendor signing certs are expired.
Internal Signing / Self Signing is the way to go....
Like I said, been there, done that, read the book, seen the film got the T-Shirt... luckily I left that all behind me...
Who the f*** is General Failure, and why is he reading my harddisk?
|
|
|
|