You searched for the word(s): userid:45204

More Search Options

RSS Available

• Re: RE: Quick General Question on Namespaces for Module Development

  As a general rule, be frugal about the namespaces you reference in any .Net project, limiting references to only those being used. By only referencing namespaces you are actually using, your code's dependencies are clear, the compiler has to do a little less work and you make your code impervious to changes in an assembly that you have referenced, but don't actually use for anything in your code, especially if the assembly is strong-named. My personal preference is to only import Microsoft.VisualBasic

  Posted to DotNetNuke (Forum) by cniknet on 2/28/2006

• Re: a free host for testing site for non profit org

  There is adequate language in the DotNetNuke Trademark Policy and DotNetNuke Logo Guidelines that is clearly being violated by the site in question. Before citing the specific text, I do want to point out that over and above everything, DotNetNuke is a volunteer effort of a team consisting primarily of developers. Our job is to continue to enhance DotNetNuke and provide value to the community, not delve into legalese. When we publish guidelines and policies, it is with a fairly reasonable expectation

  Posted to Resources (Forum) by cniknet on 2/4/2006

• Re: Why does 100% Css Design Fail in Dnn? (No Tables)

  Lee, Most of the report is misleading because the validator is parsing the code within the JS block as code within the page. This is why there are attribute flags raised. This can be fixed as follows: - Change the script tag to <script language="Javascript" type="text/javascript"> - Mark the script as #PCDATA content as follows: <script language="Javascript" type="text/javascript"> <![CDATA[ ... script ... ]]> </script> - Add a closing slash for the link element that is rendered

  Posted to DotNetNuke (Forum) by cniknet on 2/3/2006

• Re: Why does 100% Css Design Fail in Dnn? (No Tables)

  Glad it worked! One word of caution about the SkinPath variable... <%= SkinPath %>/something.css <= will work but will produce a double slash <%= SkinPath %>something.css <= will work and will produce only a single slash Some browsers may choke on the former, so it's best to use the latter. Nik

  Posted to DotNetNuke (Forum) by cniknet on 2/1/2006

• Re: Why does 100% Css Design Fail in Dnn? (No Tables)

  The results you see are expected since the script does not define any print stylesheet for IE. I created a JS object called styleSheetPicker() to make this easier. Now, the code for setting the stylesheets can be: var picker = new styleSheetPicker(); // IE stylesheets picker.ieScreen = "ie.css"; picker.iePrint = "other.css"; // Other browser stylesheets picker.otherScreen = "default.css"; picker.otherPrint = "other.css"; picker.render(); You can grab the complete script including the code for the

  Posted to DotNetNuke (Forum) by cniknet on 2/1/2006

• Re: Why does 100% Css Design Fail in Dnn? (No Tables)

  dnncreative wrote: Thanks for the updated script, appreciated. - I've tried it out, but it still doesn't pick up the print.css styles for some reason. The cross-browser part turned out to be trickier than I had imagined, but I have it working. FireFox seems to choke when the "media" property is used, which is why the script was not working. As a workaround, instead of using a DOM-based approach, I just appended the requisite <LINK> element into the flow. My test case consists of four docs:

  Posted to DotNetNuke (Forum) by cniknet on 2/1/2006

• Re: Why does 100% Css Design Fail in Dnn? (No Tables)

  I'll check it out later today and post back here. I posted the link for the CSS layout generator, but be sure to also check out the parent site Position Is Everything ...it's a fantastic resource for CSS, especially if you want to see working examples of cross-browser designs and learn about CSS bugs. While CSS Zen Garden is good for design concepts, PIE is a better resource, IMO for CSS layouts with dynamic content (a.k.a. DotNetNuke skins). Nik

  Posted to DotNetNuke (Forum) by cniknet on 1/31/2006

• Re: Why does 100% Css Design Fail in Dnn? (No Tables)

  Lee, Looks like @import is only supported at the beginning of a stylesheet on Mozilla browsers (AFAIK), so here's the amended script: <script type="text/javascript"> if (document.createStyleSheet) document.createStyleSheet("<%= SkinPath %>iehacks.css"); else { var newStyleSheet=document.createElement("link"); newStyleSheet.rel="stylesheet"; newStylesheet.media="print"; newStyleSheet.href="<%= SkinPath %>print.css"; document.getElementsByTagName("head")[0].appendChild(newStyleSheet

  Posted to DotNetNuke (Forum) by cniknet on 1/31/2006

• Re: My skin with a flash header calls a second flash movie... help

  When the page is executing the "current folder" is the root of the portal. So, if the first Flash movie is looking for the second movie relative to its current folder (usually assumed to be the skin folder, but not so), it will not find it. The solution is have the first movie reference a Javascript variable to obtain the path to the second movie. The path can be initialized using code in the skin like this: <script language="Javascript"> var moviePath = "<%= SkinPath %>/movies/SecondMovie

  Posted to DotNetNuke (Forum) by cniknet on 1/17/2006

• Re: Easy JS Question

  No. The document.getElementById() method requires a parameter which is the ID of an element on the page. Nik

  Posted to Custom Modules (Forum) by cniknet on 1/17/2006