ShadowMage

I don't think a shadow like that is possible with CSS. Or at least not without a lot of "sneaky" code. You'll probably have to use an image (or two).

You'll need to use either JavaScript or PHP, but yes it's possible. JavaScript: http://w3schools.com/jsref/met_loc_assign.aspPHP: http://us.php.net/manual/en/function.header.php

There are a couple different ways to do it involving either display or float. If you post your code (HTML and CSS) we could take a look at what you have and see if there are any immediate issues that stand out.

Yes, frames are deprecated in HTML 4 (Strict) and HTML 5 and should no longer be used.

I understand the concepts of the trunk and what tags and branches are for. I was asking about naming conventions for the branches themselves. Like all the examples I've seen in the TortoiseSVN documentation name the branches something like "V 1.2.x" but to me that doesn't make much sense. I don't know what "V 1.2.x" means in terms of what feature/fix the branch is implementing. To me, it would make more sense to name it something that reflects the feature/fix it is implementing, which I think is what boen was referring to regarding the modules. I was just wondering what the commonly accepted conventions were. Thanks for the tip! I'll have to try to remember that.

Well, just thought I'd pop in and let everyone know how it went. I just installed TortoiseSVN on my local workstation and I wrote a simple batch script as a backup system. The batch runs daily via Scheduled Tasks in Windows, and dumps the repository to our network, where it gets backed up by our regular nightly backups. Tortoise itself is actually far simpler to use than I expected. It fits my requirements perfectly, too. (Thanks boen, for the recommendation! ) I am able to create repositories and do all the branching/merging/modifying/tagging right on my local workstation. Since I am (currently) the only developer, this solution works perfectly. Now the question: :PWhat is the common naming convention for creating branches?

I think I understand. So for now, I'll just use Tortoise and maybe in the future, if things work out, we can install Subversion Edge (or some other VCS) on an actual server. Thanks for all the help guys.

Ok, I'm a little confused. Why do I not need a server? Isn't the VCS server what tracks changes and controls the branching/merging? EDIT: Actually, I think I just answered my own question. I reread your post, and I see you are referring to "server" as something that allows other users to check out the code. Which Tortoise won't do. But, Tortoise is a VCS server in the sense that it still tracks history and does branching and merging. Is this correct?

If I set it up on my local machine, I would still have the history and branching functionality, would I not? I'd still have the VCS server and a VCS client, they'd just be on the same machine. TortoiseSVN is just a client, isn't it? Subversion Edge has the whole package (including server and client) if I understand correctly.

This is actually more what I'm worried about. Like you said, if someone deletes all the files, no big deal, I have a copy. The project's source could be considered confidential (at least in the minds of the execs ) and so I'd like to keep it under lock and key as much as possible. So from what you've just said, I probably want to go with an on-site solution rather than a hosted solution. That said,I spoke to my immediate supervisor about setting up a VCS and he suggested installing Subversion Edge on my workstation and set up a backup schedule to push the repository to our network (in case my workstation fails). He had never heard of VCS before and was not sure if such a solution would be feasible/advisable. What do you guys think?

I thought about a hosted service, but I worry about security. My worries are probably unfounded, but anytime I do anything over the internet I worry... Anyway, this would be mainly just for me to use. I am really the only developer/programmer here at work, but I am working on a very large project and I'm finding that my old way of creating copies of the project directory (ie, Project_bak, Project_rev1, etc.) isn't working so well. Especially since I have been making several "branches" of my code doing a few different tasks at a time. Merging changes is a hassle at best, so I thought version control might help me.

It isn't really all that important, I guess. I was just curious. Our intranet server is running W2K. So I guess I'm actually more concerned with the OS being supported...

The Subversion Edge stack doesn't seem too hard to set up. My only concern is system requirements (hardware/OS). The server I was planning on installing the VCS server on is quite old and I'm afraid it won't be able to efficiently run the Subversion server. JSG, what type of system do you run the server on?

I'll look it over and see if anything makes sense. I'm not going to go installing anything yet, I'm still in the research phase. That's not entirely convincing...

I have been thinking, and I think a version control implementation would be a great thing to implement here at work. One problem: I have no idea where to start. Based on what reading I've done, I've concluded that there are two pieces to the puzzle: a server for the code repository, and the client which will access the repository.I'd like to set up the server on our intranet server and the client (obviously) on my workstation. My questions are: - What is a good server/client setup?- Any tutorials you can recommend on getting things set up?- Can I migrate an existing project into a VCS? Any advice/feedback/pointers you have to offer will be much appreciated. TIA.

You realize that Notepad++ is an editor, right? .... :)In fact it's quite powerful. Certainly not the most powerful, but it holds its own. Especially once you add plugins like the FTP client.

History is bound to repeat itself... :)It seems FireFox is the real gladiator in this fight.

FireBug 1.7 seems to be a little bit laggy in comparison to its predecessor. Especially on the script tab. As I'm scrolling through my (couple thousand) lines of code it takes about a half second for it to refresh and display the code. With the older version it was smooth scrolling.As far as FF4, I am impressed with the improvements in load time (for the browser, not web pages). I too have FireFox loaded with plugins (no less than 14 extensions and 3 themes) and it loads a lot faster than 3.6 did. I think it actually compares decently with the other browsers.

Old habits.....learned it from a bad/outdated source....There are a number of reasons one might create a table based layout, but regardless of the reasons, tables should not be used to layout a page. And trust me, you can achieve a lot richer, more manageable effects without them.

:)Did I miss something....

Yep, just encountered one of those yesterday.

So, when is this thing going down? Is there a plan? I'd very much like to help with whatever I can, whenever I can.

Gotta say I am loving this editor! :)Thank you!The "minimap" is the coolest thing I've ever seen. It makes it so much easier to navigate files that are several thousand lines long... :)Also really dig the syntax highlighting. It's fantastic!Just not sure how long I'll be able to use the trial version. It says on their web site that there is "no enforced time limit for the evaluation" but I'm not exactly sure what that means... (Though I think it's worth the $60 to buy a license)