myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Udo Schnurpfeil (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Comment Edited] (TOBAGO-1636) End of theme-dependent resource selection (ResourceManager)
Date Fri, 02 Dec 2016 11:12:59 GMT

    [ https://issues.apache.org/jira/browse/TOBAGO-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714832#comment-15714832
] 

Udo Schnurpfeil edited comment on TOBAGO-1636 at 12/2/16 11:12 AM:
-------------------------------------------------------------------

I've sent the motivation to the mailing list some days ago. It's more or less this:

We don't need the ResourceManager in Tobago 3, because with the CSS / JS technologies we have
these days, we can fulfill the requirements.

On the other side, Bootstrap generates all the CSS stuff, and you can customize a theme and
Bootstrap generates the CSS for the other theme.

This conflicts to the "merge" strategy of Tobago.

The new mechanism has all possibilities, but is more explicit, so much more easier to understand,
and there is no "magic" behind it. So its easier to understand and debug.

This means not, that there is no longer a management of the resources.

When you need to add a resource link CSS or JavaScript you have 2 possibilities:

# Put a <tc:script> or <tc:style> tag with the filename in a single XHTML page
(or a template for more/all pages).
# Put the path inside of the META-INF/tobago-config.xml of your application (or your own theme).
In this case, you may also remove some files from other themes if you want to patch something
(use exclude tag).

So, this mechanism is more flexible, but simple.



was (Author: lofwyr):
I've sent the motivation to the mailing list some days ago. It's more or less this:

We don't need the ResourceManager in Tobago 3, because with the CSS / JS technologies we have
these days, we can fulfill the requirements.

On the other side, Bootstrap generates all the CSS stuff, and you can customize a theme and
Bootstrap generates the CSS for the other theme.

This conflicts to the "merge" strategy of Tobago.

The new mechanism has all possibilities, but is more explicit, so much more easier to understand,
and there is no "magic" behind it. So its easier to understand and debug.

This means not, that there is no longer a management of the resources.

When you need to add a resource link CSS or JavaScript you have 2 possibilities:

# Put a <tc:script> or <tc:style> tag with the filename in a single XHTML page
(or a template for more/all pages).

# Put the path inside of the META-INF/tobago-config.xml of your application (or your own theme).
In this case, you may also remove some files from other themes if you want to patch something
(use exclude tag).

So, this mechanism is more flexible, but simple.


> End of theme-dependent resource selection (ResourceManager)
> -----------------------------------------------------------
>
>                 Key: TOBAGO-1636
>                 URL: https://issues.apache.org/jira/browse/TOBAGO-1636
>             Project: MyFaces Tobago
>          Issue Type: Task
>          Components: Core, Themes
>            Reporter: Udo Schnurpfeil
>            Assignee: Udo Schnurpfeil
>             Fix For: 3.0.0-beta-1, 3.0.0
>
>
> In Tobago 2 and lower the resources will be selected from a theme automatically. This
is a feature on top of JSF.
> In Tobago 3 this is no longer supported, because there is no need (or even rare) to have
different resources for different themes. This is, because these days the features of CSS
and JS are much more advantage.
> Moreover the Bootstrap theme generation will generate a complete theme, so all resources
of the base theme must be excluded.
> Remark: For simplicity, some resources are moved to the core module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message