Response title
This is preview!
- Screen name: christoph.herold
christoph.herold's Profile
4 Posts
7 Responses
0
Followers
Activity Trend
Last 30 days
- Last 30 days
- Date Interval
From Date : To Date :
Loading Chart...
Show:
- Expanded view
- List view
Private Message
- What is the best practice for initializing widgets? In the demos, the document.ready event is used, but wouldn't it be better to use inline script blocks directly after the corresponding html structure? If you have a large page or a slow connection, and you use the document.ready event, you will see the basic html structure (e.g. ul-li for tabs) until the whole document is loaded. Instead, placing a script block directly after the required html structure would immediately initialize the widget. Is there a known drawback to using an inline script block, or is this considered this a valid alternative? I would imagine that dialogs and the datepicker will cause problems, as they create some parts of their UI at the end of the document, which would then not be ready. Any recommendations?
- Did I miss an option, or is it currently not possible to have autocomplete in one box with multiple values separated by some sort of character? I'm thinking of the following use case:
enter 'J' -> select suggestion 'javascript' -> enter '; C' -> select suggestion 'C#' -> enter '; P' -> select suggestion 'PHP'
This would lead to a final value in the textbox of 'javascript; C#; PHP'. I believe I would currently have to try to implement this myself using the various events of the autocomplete widget. Please tell me, I am mistaken :-)
Kind regards and keep up the great work,
Christoph- 23-Apr-2009 11:01 PM
- Forum: Developing jQuery UI
Hi everyone!
As I'm working on the integration of jQuery UI in DNN, I come across
an issue concerning the theming of the Dialog and Datepicker widgets.
I was very impressed, when I saw that you even added support for
multiple themes on one page by simply prefixing the styles. The
problem is, that the popup controls are added at the bottom of the
page, therefore being only themeable by adding the class name to the
body. But this disables the use of multiple themes.
I was able to work around this issue by using the open/close and
beforeShow/onClose events respectively and using jQuery().wrap to
create a <div> with the given theme's class name, and jQuery().replace
to remove it when closing. In the case of the Datepicker I was able to
use jQuery(inst.dpDiv) to access the element for wrapping. For Dialog
I had to use jQuery(this).parent().parent(), which, to me, looks kind
of ugly, and I fear this is bound to break in future releases. Also,
the close events are called at the start of the closing animation, so
the wrapping div and therefore the theming is removed before the
animation completes.
Shouldn't the popup widgets include a theme name option so this
handling can be included with the widget? I'd be willing to supply a
patch for this feature, if it is decided to include this option.
Best regards,
Christoph
Hi all!
I recently started work on a jQuery UI DotNetNuke integration, to make
it easier for module developers like me to use jQuery UI from an
ASP.NET context. So far I have rudimentary support for Tabs and
DatePicker, including theme support, since those were the components I
required first. I was thinking of making the code available
publically, perhaps on CodePlex, as this is one of the preferred
ASP.NET project platforms. Can anyone give me guidance on whether or
not this is allowed, and how I would go about with this. Developers
would of course be welcome to work with me on the project ;-)
Best regards,
Christoph- «Prev
- Next »
Moderate user : christoph.herold
© 2012 jQuery Foundation
Sponsored by 
and others.
