The example site - One for each big release?
Fri, 07/23/2010 - 11:16
I think this has been discussed before but I did not find the post.
How does it sound to have one example site for every big release (1.1, 2.0 etc)? Then it's easy to explore and test new features as soon as the examples are available and also compare the difference between releases.
Any thoughts/comments?
Brynjar
I really don't see the point in offering a 1.0 or 1.1 based example site any longer. We strongly encourage everyone to upgrade to 2.0, and most certainly don't want to have new users think that older versions offer any benefits over the newer versions (they don't).
Should a user already be running an older version, they also have the code to run their own examples site for it.
I'd like an "upcoming" (SVN head) version of the examples as well as a "release" version of the examples, for marketing reasons, but that's as far as I'd ever want to go.
There seems to be a lot of very new and cool features in 2.0.1. Actually, 2.0.1 seems to be a completely different version from 2.0. It would be extremely helpful to have a lot more examples, covering those new features. For example, I believe vakopian created integrated api's for most of the jQuery plugins. It would be really great to have examples for them. A couple of examples are the QAutocomplete and QSortable plugins. They are particularly useful and complex plugins. It would be nice to have exmples.
Actually, 2.0.1 does include an example for these new controls. They're all lumped together on one page though. :)
So it does. I was searching, before I installed the plugin. Thanks.
However, the server side Autocomplete doesn't seem to work. The client side works though.
Thanks again,
LaCeja
LaCeja
I'm not sure what you mean by the "server side" not working. Do you have an example code?
Also, 2.0.2 will include a pretty big patch for these controls (see ticket #604), so many more features will be available for these controls with the upcoming release. The examples page is also more complete in 2.0.2.
If there is a bug in there, I would really like to fix it before 2.0.2 is released.
-Vartan
Sorry, I should have been more specific. The QCubed Autocomplete plugin includes to types, the Ajax server side (QAjaxAutoCompleteTextBox), which uses an Ajax call to get the array of data to choose from, and the client side (QJavaScriptAutoCompleteTextBox), where a static list is provided. It's the QAjaxAutoCompleteTextBox that doesn't work.
So have you tried to use the new core controls instead of the old plugin?
We'd love to hear if it meets your needs, and/or how it could be improved.
Please see my comment in the other thread: http://qcu.be/content/new-autocomplete-qcubed-201#comment-5235