User talk:WikiSysop

Microsoft .NET Framework, ASP.NET, Visual C# (CSharp, C Sharp, C-Sharp) Developer Training, Visual Studio

-I cannot use your forums ///It won't let my name/password in

- User:JimSharp

Unfortunately, the forums require a seperate user id, which means you must register for the forums seperately using the Register option on the main forum page.

--Midnight Programmer 04:35, 3 November 2008 (EST)

Study Guide Categories and Templates

What are your thoughts about the organization of the Study Guide using Categories and Templates?

There is a problem with the sub menu templates that float on the side of the screen:

1. They overlap the content of CSO_Source boxes and other items sometimes
2. They use an inline style, which will be hard to maintain and might conflict with some skins
3. The way it is now, each Sub Category has its own template, which could result in redundancy and lack of consistency (For example, there are 2 menus on Value types with different widths)

I like the side menu for navigational purposes within a section, but I think it will become difficult to manage if not better designed.

I like the navbox template on wikipedia, but I was not able to get one to work on this site: Navbox

CoderForChrist 09:46, 23 May 2006 (CDT)

As a follow up, I was able to make a side menu template with all the style and layout inside it. I made Microsoft Exam 70-356 Study Guide 1 and 2 use that template (Study menu). In addition, I made another template for each sub section (Study section).

Also, I discovered that putting a category in a template added any pages that use the template to the category. Which is great. By putting the Study Guide Templates in the specific study guide template (see the bottom of Template:Use_generic_collections), now all that is needed is to add that template to the page that uses it. By doing so, it will add both side menus and add the page to the categories.

However, the floating side menus are still a problem with CSO_Source and probably Pre tags. CSO_Source apparently does not wrap the text under any circumstance, I understand that behavior, but it causes the text to overlap the side menu. (I am using Firefox and have not tested to see what happens in IE 6). It also forces the edit links on document sections to move unpredictably.

I am not sure how to fix the problem. Do you have any ideas?

I know limiting the amount of information in the menu would help, but it does not really solve the problem.

--CoderForChrist 08:16, 24 May 2006 (CDT)

Problem solved:

I was able to make the two side menus match in width by making them fixed width = 150px. I think it looks much better.

Also, I was examining the CSO_Source and I discovered that it is just a pre class=".csharp". I was able to experiment with the css and found a way to make the text wrap so that it does not run onto the menu:

/* Browser specific (not valid) styles to make preformatted text wrap */	

pre {
 white-space: pre-wrap;       /* css-3 */
 white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
 white-space: -pre-wrap;      /* Opera 4-6 */
 white-space: -o-pre-wrap;    /* Opera 7 */
 word-wrap: break-word;       /* Internet Explorer 5.5+ */
}

Alternatively, this could be applied to .csharp instead of all pre tags.

I could only test the solution in Firefox because I was using a Firefox css editor extension (Web Developer)

Hope this helps make the site better --CoderForChrist 09:15, 24 May 2006 (CDT)

One more issue: The document section edit links are still moving down to the top of the side menu below it.

A fix:

.editsection
{
position: absolute; 
padding: 15px 0px 0px 0px;
right: 170px;
}

However, this should only appear on pages with the side menu.

I do not know if there is a way to add to the pages style sheet from within the wiki. I have only seen controlling inline styles.

If there were a way to change the page style. Then putting this css style and the pre style would fix the problems.

--CoderForChrist 09:39, 24 May 2006 (CDT)

Ok, I was able to fix the edit links by putting both side menus in one table and floating the table on the right side.

The only problem remaining is the lack of wrapping for CSO_Source, but that could be easily fixed by editing main.css with the pre or .csharp css block I mentioned above. If you think it should be done that is...

Thanks -- CoderForChrist 13:38, 24 May 2006 (CDT)

thanks!

Osias 14:31, 24 July 2007 (EDT)