|
Hi all, Scenario: Any idea how I can accomplish step 2? |
|
Anybody?
On Mon, May 14, 2012 at 4:58 PM, Raviteja Lokineni <[hidden email]> wrote:
-- Thanks and regards, Ravi Teja |
|
if you don't need jquery-ui css because you have your own style, i suggest you to look at jquery-ui plugin page, there is an explanation on how to override default theme
2012/5/17 Raviteja Lokineni <[hidden email]> Anybody? |
|
Actually not to override but to exclude.
I have implemented override configuration perfectly. Unfortunately in our project we did not spend enough time customizing it to our needs. So I need to exclude pulling the dependency => 'jquery-theme' on one page. On Thu, May 17, 2012 at 12:44 PM, Luca Farsetti <[hidden email]> wrote: if you don't need jquery-ui css because you have your own style, i suggest you to look at jquery-ui plugin page, there is an explanation on how to override default theme -- Thanks and regards, Ravi Teja |
|
Well, i think that the simple way to do that it's define your custom resource, something like jquery-ui-custom without theme dependencies.
2012/5/17 Raviteja Lokineni <[hidden email]> Actually not to override but to exclude. |
|
I think so. Would be this be a useful addition to resources plugin?
modules = { core{ dependsOn('jquery') excludes('jquery-theme') //new feature } } Can a JIRA improvement be raised for this? Thoughts? On Thu, May 17, 2012 at 1:12 PM, Luca Farsetti <[hidden email]> wrote: Well, i think that the simple way to do that it's define your custom resource, something like jquery-ui-custom without theme dependencies. -- Thanks and regards, Ravi Teja |
|
On 17 May 2012, at 08:55, Raviteja Lokineni wrote: > I think so. Would be this be a useful addition to resources plugin? > > modules = { > core{ > dependsOn('jquery') > excludes('jquery-theme') //new feature > } > } > > Can a JIRA improvement be raised for this? Thoughts? > Hi, I have already got plans to extends dependsOn. In overrides this currently replaces the entire dependency list. However I plan to add support for: modules = { overrides { core { dependsOn remove:'jquery-theme' add:'my-jquery-theme' } } } Would support list values for remove/add too. No ETA though, sorry. Generally speaking removing dependencies is a bad idea. Swapping them for something else is I think a much more valid idea... If the original resource has been declared with a dependency that is not a hard dependency, then this is a mistake and needs to be fixed at source Marc ~ ~ ~ Marc Palmer Freelancer (Grails/Groovy/Java/UX) I offer commercial support for Grails plugins from as low as $50/mo. For details see: http://grailsrocks.com Blog: http://www.anyware.co.uk | Resumé: http://www.anyware.co.uk/marc Contributor @ http://grails.org | Founder @ http://noticelocal.com Developer @ http://weceem.org | Member @ http://spottymushroom.com Twitter: http://twitter.com/wangjammer5 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Yes the problem is at source. Instead of using the same custom jquery-theme the CSS developer wrote a new css.
While pulling in jquery-ui resources plugin pulls the custom jquery-theme and the theme designed for this page. We don't have any CSS developers on board so wondering if there was any such feature(which the answered in the previous posts). On Thu, May 17, 2012 at 3:05 PM, Marc Palmer <[hidden email]> wrote:
-- Thanks and regards, Ravi Teja |
| Powered by Nabble | Edit this page |
