The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
The DPI of the server or the IIS instance should be irrelevant. You should be rendering that chart in a machine-independent way.
I guess the component is designed to be used as an embedded UI control so it kind of makes sense that it picks up your local DPI setting by default. It's mostly your fault I suppose (assuming setting a pixel size makes it work right) but definitely an understandable mistake to make!
I would guess that the root of the problem is that he is using some control that makes an image on the fly. (As opposed to creating a drawing on HTML canvas.) If that is the case, then the image will most likely use the GDI of the server in rendering the image before sending it. Thus, the server settings begin to matter.
Just reading up on CSS and found out that a pixel is not a pixel because it is set to a specific size in the browser. So this setting is a browser setting so that when you define a page in pixels (as we all seem to do) it renders 'consistently' across multiple different resolutions. So the whole thing is not as simple as it sounds.
Problem was just that the IIS Worker Process uses a separate account that still
had the default 120 DPI setting
This isn't really the problem. The problem is that the IIS Worker Process uses a locally sourced DPI value AT ALL. There is no single answer that will be correct for all the platforms that it will render for. Sure, you just fixed it for platforms set to 96 DPI, but that means you just broke it for platforms set to 120 DPI.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
This sounds cool and open source too. I'd like to be a fly on the wall for these meetings.
"That’s why Facebook, LinkedIn, Twitter, and Google have teamed up to create what they call WebScaleSQL, a custom version of MySQL designed just for large scale web companies. Their changes to the database will be open sourced, meaning they’ll be freely shared with the world at large, and the companies plan to contribute their changes back to the original MySQL project. “Our goal in launching WebScaleSQL is to enable the scale-oriented members of the MySQL community to work more closely together in order to prioritize the aspects that are most important to us,” Facebook’s Steaphan Greene wrote in a blog post announcing the project this morning.
News forum is not listed on the Community dropdown. The rules also state "For lazing about and discussing anything in a software developer's life that takes your fancy."
I (and others) have always been posting 'hot topics' in the Lounge and occasionally they will be used in the daily news email, although that is not really my objective. I'm just a geek like the rest of you.
In fact, I prefer to read more hot topics in the lounge than say... Joke of the Day. Videos and other humor links are approved by JoeSox.
[__b__]Q: Will binaries be provided?
A: No. The focus of WebScaleSQL is to provide a common set of code changes that groups can use as a base to apply further changes that are relevant to their use case. For example, Facebook will base the MySQL binaries they use in house on WebScaleSQL code, however, the build used will include some additional Facebook-specific patches, than may not be valuable or useful to others.
So - they don't have anyone on staff old enough to remember how well that went for Unix?
About 16 years ago, my company made a big deal about how good it is to reuse code. The concept was clear, implementation was non-existent. Did I have a central library to pick-up the reusable code others had developed? No. Did I have somewhere to submit a piece of reusable code so the whole company could use it? No.
At the time, I was using a mainframe to post HTML content to an intranet site. That wasn't easy because they didn't like to talk to each other. I built a reusable interface that would allow the web site to tell the interface code the JCL to execute whatever code they were running, where to place the report, put a placeholder site, launch the code, and redirected the user to the placeholder.
The launched code would write the report to the placeholder file and the user could see it on the web.
This company had 50,000 employees, as far as I know one employee reused that code several times. Basically worthless to 49,999 people.
It's always possible to come across good ideas, but if your company tells you to use reusable code, it's BS. Unless they provide a venue to get and re-use code and set up standards to supply and publish searchable, reusable code.
Even our mainframes were specialized, maybe 2-4,000 people could access the mainframes I was using.
Just to be clear, I'm not ranting about reuse itself, it's a rant about a company that said it was a good thing and then did nothing to implement this good thing. I was the only one on my team writing web data, so I couldn't even help my own team build re-usable code. We were doing the same thing several times, but management was forcing us to use new operating systems for each new project so we really couldn't build re-usable code when the OSs wouldn't talk to each other.
I was in a place that axed a 60 person dept down to about 10. I was on call nearly every other week for things I had never even see in my life... not just the software, but entire platforms. The eventually went bankrupt, which was the best thing that happened to me. I moved on to a much quieter, more relaxing job... with new technology, better benefits, and realistic expectations.
Been there, done that. Not fun, but glad to hear you survived. Now I hope you have made plans "just in case".
Actually at a previous employer, I made plans once I heard rumors of the first round of lay-offs, so I was ready when the day came. They didn't get me on the first 2 rounds of lay-offs. but I volunteered and was turned down. They finally got to me on the 3rd round --- and paid me a nice severance to do what I had planned to do anyway: start my own business.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
and paid me a nice severance to do what I had planned to do anyway: start my own business.
That is nice. Where I was, they rebranded the company and required us all to sign new employment acceptance offers (so the old company was gone). Thus, nobody got any severance when they shut the place down 3 months later - some folks had worked there 30+ years.