Hi Christoph
You're completly right. I will see if I get time to implement this, but I think that Form Mailer and plugins using lightbox has higher priority.
jerry
Search found 177 matches
- Wed Jul 06, 2011 11:53 am
- Forum: Open Development
- Topic: Usage of boolean config options
- Replies: 42
- Views: 18441
- Wed Jul 06, 2011 8:15 am
- Forum: Open Development
- Topic: Usage of boolean config options
- Replies: 42
- Views: 18441
Re: Usage of boolean config options
Hi developers I've been out of reach for 1 day and the discussion is over. I agrre there are no hurry to find the solution and there are much more important development that should be done before. It is after all limited in how often people make changes in configutation files. Do you mean that sever...
- Wed Jul 06, 2011 7:58 am
- Forum: Addons and Plugins
- Topic: Newsbox Rotator ver 2.0.0 released
- Replies: 13
- Views: 4349
Newsbox Rotator ver 2.0.0 released
Hi Newsbox Rotator is released in new version based on jQuery. The biggest difference compared to ver. 1 is that it supports many transitions effects beyond fading that was the only option in version 1. Newsbox Rotator 2 is released under Linkware and Commercial license. NB! For all versions of CMSi...
- Mon Jul 04, 2011 8:11 pm
- Forum: Open Development
- Topic: Usage of boolean config options
- Replies: 42
- Views: 18441
Re: Usage of boolean config options
No matter what it will be there is also need for muliple choices.
jerry
jerry
- Mon Jul 04, 2011 2:15 pm
- Forum: Open Development
- Topic: Usage of boolean config options
- Replies: 42
- Views: 18441
Re: Usage of boolean config options
What about a dropdown list like plugin_cf[plugin_name][something]="option1,option2,option3@@@2" That means a list with 3 elements and a selection pointer after @@@. In this example 2 = option3. The pluginloader must check for existence of @@@ to know it is a dropdown and handle it like this. On selc...
- Sat Jul 02, 2011 11:18 pm
- Forum: Open Development
- Topic: Usage of boolean config options
- Replies: 42
- Views: 18441
Re: Usage of boolean config options
Or an extention of configuration file to include possibility of dropdowns, so the end user can choose between hardcoded values. I know it's tricky but it's the most user friendly solution. And it will solve any problems with fields that have even more options. All the plugins I know read the values ...
- Thu Jun 30, 2011 10:53 pm
- Forum: Open Development
- Topic: Coding convention for jQuery4CMSimple
- Replies: 30
- Views: 15439
Re: Coding convention for jQuery4CMSimple
Hi Christoph The older jQuery plugins will usually have a hardcoded call to jquery.js in template. For the same reason I have a hardcoded call to lightbox to avoid several call trough $hjs. Holger had the same solution in Gallery with Lightbox. So it was possible to have several plugins using the sa...
- Thu Jun 30, 2011 7:32 pm
- Forum: Open Development
- Topic: Coding convention for jQuery4CMSimple
- Replies: 30
- Views: 15439
Re: Coding convention for jQuery4CMSimple
Hi Holger
As soon jQuery is loaded before other plugins and $ is not used as variabel in jQuery there are no conflicts with lightbox. Your little trick will do it possible to load other frameworks through $hjs, So yes do it
jerry
As soon jQuery is loaded before other plugins and $ is not used as variabel in jQuery there are no conflicts with lightbox. Your little trick will do it possible to load other frameworks through $hjs, So yes do it
jerry
- Thu Jun 30, 2011 12:25 pm
- Forum: Open Development
- Topic: Coding convention for jQuery4CMSimple
- Replies: 30
- Views: 15439
Re: Coding convention for jQuery4CMSimple
Hi Christoph I don't really know which lightbox features you're using, but if you only use the standard feature (giving a rel="...") the solution might be as simple as including another jQuery based lightbox-clone, e.g. slimbox (that may not be the best choice, but it is the one I know, that works)....
- Wed Jun 29, 2011 9:01 pm
- Forum: Open Development
- Topic: Coding convention for jQuery4CMSimple
- Replies: 30
- Views: 15439
Re: Coding convention for jQuery4CMSimple
I will remove noConflicts before release. Protoype stuff will exist a while until I find out how to convert it to jQuery (and get time to do it) Right now I will just rewrite installation instructions. jerry [EDIT] It seems that (function($) { /* some code that uses $ */ })(jQuery); only works only ...