There's no trick to it. In fact, using UNC paths like you have in your example should "just work".

If it doesn't, the problem is most likely with permissions. Keep in mind that the web server does not run under your user account - it has its own account with completely different permissions. You need to make sure that the account used by the web server has the proper permissions for the network share you're trying to access.

Using "onclick" on a select option isn't universally supported. Instead, try using the onchange event on the select node itself, e.g. <select name="something" id="stuff" onchange="reveal_option()">.

Well, just from a quick look at your page I see you're using an HTML 5 doctype and HTML 5 tags like <nav> and <section>. This is a problem right off because IE8 and lower don't support HTML 5 to any meaningful extent. In other words, don't count on any HTML 5 feature working in IE 8 or less.

If you really want to support old versions of IE, there are several Javascript libraries such as Moderizr that can add some limited support for HTML 5 tags in old versions of IE. They should at least give you the ability to properly style those elements. I've never used such libraries myself, so I can't speak from experience, but the only alternative is to just change all your markup to only use the elements supported by IE < 9.

BenignDesign, on 03 April 2013 - 01:06 PM, said:

I guess I don't understand why you think this is ethically questionable. I mean, it doesn't sound like the intent is to deceive anyone. You'd just be redirecting to a newer version of the same form. What's wrong with that? In fact, if the current version is the only "correct" version for users to download, then that sounds like the opposite of shady to me, i.e. good user experience.

I think you're looking at this the wrong way. You're asking how you can adapt your repository structure to accommodate your existing development environment. You should be changing the configuration of your development environment instead.

All you really need is a single directory for your repository with your different types of files grouped into appropriate subdirectories. So instead of just /www, you might put your public files in /home/you/your_project/www, the private includes in /home/you/your_project/includes, and so forth. To make that work, you would simply set the appropriate file and directory permissions on your checkout dir and configure your server to read the files directly from that location. The exact steps to do that will vary depending on what web server you're using, but in any case it should be pretty easy to configure. Heck, you could probably even cheat and use symlinks if you really wanted to.