|
Just spent some hours today tracking down what I felt was a really odd and unexpected error that turned out to be really simple.
I made a webpage that contained a chart, so far no problem.
But when I moved the code over to the server the chart titles turned out smaller than on my devmachine.
So identical code rendered as images turned out having different size of the text on two machines that I thought had the same settings. 
Well, to the story belong that I got a new devmachine last week. It's a 14" laptop with 1920x1080 resolution (and a ridiculously fast harddrive compared to my old machine), so the clever people at Dell thought that as you obviously don't buy high resolution to get more real estate, had set the default DPI at 120 instead of 96.
So I immediately set it down to 96DPI and thought no more of it. Problem was just that the IIS Worker Process uses a separate account that still had the default 120 DPI setting. And the rendering of text uses that default setting on the Worker Process Account rather than the setting on my account
So whose fault is this?
Mine for not setting the font size in pixels instead of points?
Or Dells for having a stupid default setting?
Perhaps Devexpress for using a local environment setting for something that should have a standard translation in the Control?
Your call. Whose fault is it?
But more important, how should something like DPI be handled on the net? It shouldn't be set at the server, but rather use the setting from the client, or?
/Rant over.
|
|
|
|
|
I always thought web pages should be scaled by using the browser zoom option. So if the user wants it bigger, they hit Ctrl++.
The challenge, then, is to construct a web page that behaves appropriately at 75%, 100%, 150% zoom and everywhere in between.
|
|
|
|
|
I second that opinion. Let me as a old user with bad eyesight control how big the damn thing appears on my device. 
|
|
|
|
|
Bugs are never-ever unnecessary! You only have to know how much to create!
I always say to my group - the bugs you create today are the bread-and-butter of tomorrow! 
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Wally agrees[^]
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
"I'm gonna write me a mini-van this afternoon" classic. 
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
|
|
|
|
|
Please remind me, what's your product?
|
|
|
|
|
ERP for educational institutes including - and our customers are universities and colleges...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
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.
|
|
|
|
|
Most likely Devexpress' fault, if you report this as a bug today it may be fixed in... 3 years if you're lucky... 
|
|
|
|
|
|
Jörgen Andersson wrote: 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.
Details are a scant, but the project includes new ways to stress test large-scale SQL databases and optimizations for certain types of information queries."
http://www.wired.com/wiredenterprise/2014/03/webscalesql/[^]
|
|
|
|
|
But wait! I thought NoSQL was the future!
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
My question exactly. Where does this put NoSQL, esp as I thought NoSQL was starting to include SQL anyhow ?
|
|
|
|
|
Should this be in the News forum?
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
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.
|
|
|
|
|
Hey, do not try and move the interesting posts out of the Lounge, we need quality here.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
From their FAQ:
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?
|
|
|
|
|
CodeProject just highlighted an article whatever happened to reuse[^]
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.
|
|
|
|
|
Our third round of layoffs in a little over two years today, and I'm still here. I know a couple of the folks getting the axe.
'Tis not a happy place today  .
Software Zen: delete this;
|
|
|
|
|
Gary, are you still in an Alpha/VMS environment?
|
|
|
|
|
I worked with VMS back in the late 80's on a MicroVAX-II. At the moment I'm doing C#/WPF user interfaces for commerical ink-jet printing systems.
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
