Does it matter if I have a made a website responsive or not. If I show the website on a projector? - responsive-design

So I have to give a presentation of a website I made. So I didn't have time to make it responsive. I have used position:relative and pxunits in margins and all. Will it change layout of website if I use duplicate option in windows 10 project.

If the projector has a resolution similar to a regular computer screen, it won't make a difference.


Universal app wizard mode full screen

I'm working on my first Universal app that is destined to run on a tablet. How would one go about making a wizard flow. Basically it needs to take some input and make a decision on one page and show the results on another page. I see some people collapsing and making grids visible but it seems like there must be a better way. I'd also like the app to scale the UI to fit fill screen. Any thoughts?
Thank You,

Why is Visual Studio altering my Winforms when editing them on another computer?

I am having a rather odd issue that I have been unable to find the answer to. I have 2 PCs that I am doing coding on - one a desktop PC and one a notebook (QuadHD resolution). Each has Windows 8.1 & Visual Studio 2013 Update 5 installed.
I have localized all my Forms and it seems that when I edit the Winform on my notebook, it causes very odd resizing issues to occur. For example, if I simply change the "Language" property from one language to another (that I have already translated), the entire form is skewed and re-sized, completely destroying all the layout of the form in the selected language. On another form, the "ImageScaling" property is erroneously changed from 16x16 to 40x40.
The issue seems to be related to the changing of the 'Language' property. Almost like there's some sort of resizing logic & layout logic being applied when this property is changed.
When I perform the same operation on my desktop PC, I get no such odd modifications (as I'd expect). This obviously renders my notebook completely useless for being able to do any WinForms work!
I initially thought this might be related to some quirk with the QuadHD display (i.e. 3.2k x 1.8k). I have tried to reduce the screen resolution to a regular HD quality, however this doesn't seem to resolve the issue.
Does anyone have any hints about what I could try to fix this problem?
The only workaround I have been able to come across so far is to ensure that your Windows Settings->Display->Scaling is 100% BEFORE making any modifications to the form (including changing any seemingly innocuous properties such as 'Language').
On high-resolution screens, this unfortunately makes the content almost unreadable but at least the forms are not completely ruined/resized when you edit them.
You will unfortunately need to do all your edits in this mode and commit them before reverting your scaling back to its original setting.

Using responsive design within Google Sites

Is there a way to use responsive design principles with Google Sites. Has anyone tried that. Could you direct me to a sample site. I looked at this google help topic but then that is supposedly about exclusively mobile sites.
My main focus is a normal website which is optimized for web rather than primarily a mobile site.
Alternatively would Blogger be a better option in this case as that allows to change CSS.
I think your negative impression is right. It doesn't implement the features you'd expect in responsive design.
The key to your question is that Google Sites don't use a viewport declaration (meta viewport in the head element). If you don't have that, then device browsers treat you as a legacy desktop-only website. They assume you'll break completely below ~830px, and set a page min-width accordingly. That doesn't sound much like responsive design to me.
Google Sites don't let you write your own CSS or HTML HEAD, so you can't implement a more responsive design yourself.
To be fair, you can choose to not set a fixed page width. Also navigations buttons will reflow on relatively narrow windows, if you're using the "horizontal navigation" feature. The latter isn't great design but at least it's degrading gracefully.
There is an option "Automatically adjust site to mobile phones" under Manage site -> General. However many people suggest it's better not to use it :). I tried enabling it on an old site, previewing the page, and selecting "preview in mobile". At least on Firefox on my original netbook (800px width), it was not responsive. It didn't expand to use the 800px screen properly.
As an aside, the line-wrapping (or absence of it) is a pre-existing issue with my site. You could blame this on me for not testing it :). However it illustrates a limitation of the WYSIWYG editor in Google Sites. It doesn't show, check for, or filter out the formatting that causes this problem.
Mobile yes, responsive no.
I was messing with Google Sites today and you can make a site mobile friendly (I had to come here to get started!). I just used the "Blank Template" to mess around with.
You do need to activate (like others that have mentioned):
Options (gear icon) > Manage site > (scroll down to Mobile) Check.. Automatically adjust for mobile phones. Yeah, let's bury that option way down at the bottom!
Considering the whole mobile "push" Google implemented in the spring of 2015 this should be ON by default for any newly created Google Site.
Just selecting that option makes an OK (basic) mobile site. Not a responsive site. So on my iPhone it does scale photos correctly to fit the device and switches the main horizontal menu to the "hamburger" icon/menu. But collapsing the desktop browser window does not produce responsive results.
As a test, I uploaded a way too large photo (2.5mb) to see what would happen. Running the site through Google PageSpeed Insights it did not display any "optimize photos" warning, so seems to serves up an optimized photo for phones and desktops.
I guess the basic theme is actually called "Ski." I tried out the "Legal Pad" theme and it was totally borked on mobile. I think due to the header and content area background images.
To me Google Sites is ideal if you are already heavy into Google's other products... drive, docs, Google+, webmastertools, analytics, etc... As it has links to add those types of items when editing. Or need a quick site for collaborating as you can easily set the site access like YouTube,Drive items.
Also, you are very limited as to what html you can added. Trying to add a script tag gets stripped out when attempting to save. So again depending on the use there are definitely other options out there.
If you create your own custom HTML forms with apps script, you can add the #media viewports etc to the css for those pages/forms,so that helps...
but the google site frame around is still well....not that good........
now a days its possible to make a responsive Google Site. since Google has enhanced this feature "Automatically adjust site to mobile phones" option in the Manage Site option button.
to find the option- go to> Manage Site> General> , in the general settings page's lower portion you can see a radio button named "Automatically adjust site to mobile phones". Just tick the radio button & u have enhanced the feature.
Refer an example site made with responsive Google site

Issue with postbacks on pages viewed from mobile device

I am facing an awkward problem. I am working on a .NET web site for which we are making a mobile version as well. The mobile version seems to be working fine when I am viewing it from the browser on my laptop, but when viewing it from a mobile device (in my case HTC running on Android), there is a problem on button clicks. The postbacks simply freeze the page and after some time "Web page not available" is displayed. Even for simple cancel buttons that only have Response.Redirect associated with them.
Has anyone witnessed similar situation? Any ideas on what can cause this? I am using .NET 3.5.
The postbacks work through inserted JavaScript (__doSubmit). Mobile devices have patchy support for JavaScript. Is it possible to look at the device capabilities for instance by hooking into a WURFL database and look at the device capabilities. I could well imagine that this would be a problem for lower end devices but I am a bit surprised about HTC Andriod devices. Also to help isolate the issue I would test with a normal submit button i.e. one without runat="server" and see what happens then
Also you could try subverting your button and putting in some custom javascript to submit i.e.
This link has some similar problems but with autosubmitting drop down lists
It's also dimly possible that the swollen ViewState is causing issues with the page size on postback. Generally if/when I have been developing for mobile I would turn this off if possible. The resulting page will be larger (a lot larger) than it needs to be. If nothing else you would need to make every effort to keep the pages as small as possible (IMHO)
I'm assuming that you are locked into webforms development at this point -so you could look at ASP.Net mobile controls to see if they behave better - there is a form control in there. But I have never used them or ever seen them used. Some other posters may have had great success with them though? Perhaps?
Not helpful but when we developed for mobile we used MVC which is at least more transparent in these kind of situations

WinForms layouts randomly screwed up

I have written several WinForms apps in my life, and every once in awhile something will go wrong with the layout at run-time. Today, while I was fiddling with the fonts in my application (mainly whether fonts were bold or not), I found that a control (which was anchored to all four sides of a TabPage) was extra-wide at runtime, going beyond the right edge of the page. I fiddled with the fonts again and the problem disappeared. Then I tried to replicate what I thought caused the problem in the first place, but it did not recur.
Another problem I sometimes have is that a Form with no MaximizeBox will randomly start maximized--maybe not on a development machine, but on a user's machine.
Can anyone tell me if they've had one of these problems and found the cause or solution?
Make sure you are familiar with the Anchor and WindowState properties, and set them to the correct values.