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

More Search Options

RSS Available

• New release of popular Watermark plugin for jQuery (3.0.2)

  Last night I released the latest version of the Watermark plugin for jQuery (version 3.0.2 ). The new release fixes a couple of bugs reported, and adds a potential performance boost when a page is submitted or unloaded. For ASP.NET developers, the previous version had a bug that occurred when a validator was placed on a text box that also had a watermark in place. If a postback occurred without changing the contents of the text box, the watermark would end up being posted instead of a blank entry

  Posted to Announcements (Forum) by speednet on 11/12/2009
  Filed under: plugin, javascript, jquery, watermark, textbox

• Online YUI JavaScript Compressor now available

  For several years I have hosted an online CSS Compressor and made it available to anyone who wants to quickly compress their CSS code. Now I am announcing availablility of an interactive, online version of the YUI JavaScript Compressor. The YUI Compressor is known for it's unmatched ability to shrink a piece of JavaScript code to its smallest size possible, while never (or almost never) corrupting the code it compresses. This is accomplished through its use of the RHINO engine, which is a real

  Posted to Announcements (Forum) by speednet on 9/22/2009
  Filed under: javascript, Compressor, YUI, minify, utility

• New version 2.0.1 of the TinyAutoSave plugin for TinyMCE released

  Version 2.0.1 of the free, open-source TinyAutoSave plugin for TinyMCE has been released. The major new feature of the plugin is its ability to maintain multiple independent autosave storages and settings. Individual editors on the same page can have their own unique autosave abilities and behavior. There have been some other great enhancements, such as refined toolbar graphics that better fit TinyMCE's optimum 20x20 image size. Practically every aspect of the auto-save operation can be extended

  Posted to Announcements (Forum) by speednet on 9/21/2009
  Filed under: editor, plugin, TinyMCE, javascript, TinyAutoSave, Speednet

• Re: Tip for those who put ScriptManager on the Master page

  Just to be clear: Even though I have been using this approach since the days of Atlas, all the tests I ran with the current release of ASP.NET AJAX. I compared using the Master Page property outlined in my first post in this thread to the static ScriptManager.GetCurrent(Page) method. As I mentioned previously, my Master Page property ran 40% quicker. Honestly, I would not recommend switching to this method purely for performance purposes, even though it is technically faster. As I mentioned, you

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by speednet on 2/26/2009

• Re: Tip for those who put ScriptManager on the Master page

  Oh my gosh, I think I said a half-dozen times that I ran time-trials. Plus, we're discussing a very simple property vs. one static call. Unless you're going to execute that 20,000 times per page, I don't think performance will be an issue for you. Look at what the property does. It determines if the page is in a partial-page postback. Are you actually concerned about performance, or are you dwelling in the land of the ivory towers?

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by speednet on 2/25/2009

• Re: Tip for those who put ScriptManager on the Master page

  @Pawan_Mishra: I ran real-world performance tests, isolating both approaches, and my Master Page property approach ran 40% quicker in all tests. Sorry if your book didn't cover my approach, but that was the freaking point to writing the original post in this thread. So not only is performance much better, but it also simplifies a great many things -- as I've said numerous times. Also, I finding the negativity epxressed here jaw-dropping. It seems the majority of developers see a new idea

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by speednet on 2/25/2009

• Re: Tip for those who put ScriptManager on the Master page

  Thanks Seed, I appreciate the note.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by speednet on 2/25/2009

• Re: Tip for those who put ScriptManager on the Master page

  I[quote user="stmarti"]If you don't want to use the static GetCurrent( ), the best way - I think - is to move the ScriptManager declaration to a base class. That way you don't need to repeat any property definition, you can refer to your scriptmanager: base.YourScripManagerID.SomeProperty. This is the object oriented way to do this. What do you think?[/quote] That doesn't really address the issue at hand. The issue is a ScriptManager on a Master page, and giving pages access

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by speednet on 2/25/2009

• Re: Tip for those who put ScriptManager on the Master page

  Or, users can do exactly what I specified, and they do not have to wreck the maintainability of their web site by repeating the same property definition on every page of their site. The ability to think beyond one's own pre-conceptions appears to be a dying concept.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by speednet on 2/24/2009

• Re: HtmlTextWriter2 0.1

  It looks like the icon used on the Copy button is actually the Paste icon. Copy typically has two identical documents on the icon, and Paste has a clipboard with a doc in front of it.

  Posted to Announcements (Forum) by speednet on 2/2/2009