views:

40

answers:

2

I am more and more tempted to try jQueryUI. I'm sort of scared, though, that whenever a feature I need is missing, it will be hard to customize the widgets to my needs, so rolling my own widgets as needed may be a ore secure bet.

In particular what I'd like to know is:

  1. How difficult is it to go beyond the basic themes? Say I want to widgets to match the design of my site, can I do this?

  2. What if I need a widget to do a more complex interaction than it is designed for? For instance I created a widget for multiple inputs which works like this. The user writes the input in a text field. If he clicks on a + button, the input is copied in another place, and the input text is emptied, and so on. All the input is then submitted as a multiselect. Now, what if I wanted to use jQueryUI autocomplete on the input field? Can I expect that the other custom interaction will break the widget?

In the end, is it worth the pain to use jQueryUI? I feel like I will lose more time in customizing it than I would in writing the widgets myself. Is this true?

A: 

There are lots of jQuery plugins out there that are very good. They can all interoperate with jQuery UI. I say take from jQuery UI what is useful to you, use other people's plugins where possible, and write your own plugins as necessary.

Robert Harvey
A: 

In general, I would say it is worth it to learn any library if you will be reproducing similar functionality. Even if you end up customizing it, your time spent on fixing bugs will most likely be far less.

softpro_sea
I don't get your point. When one has enough confidence with a library, he may want to use that instead of reproducing its functionality. If you want/need to rewrite it, why learning the library? Ok, in theory you will be wiser when writing your own. But in practice one has limited time, and I think it would be spent better working on your own implementation.
Andrea
I don't get your point. You say, that if I have limited time, I better spend it reimplementing stuff... jQuery UI, ASP.NET MVC, NHibernate, what else. Isn't it crazy? Aren't libraries and frameworks here to save time, which is especially good if it is limited? Why don't you write a C# compiler then, because *maybe* you won't be satisfied with the one that MS provides?
queen3
My only point is I personally would rather use code that has been heavily tested. Unless it is for academic exercise.
softpro_sea