syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Patricelli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI
Date Mon, 27 Mar 2017 07:48:41 GMT

     [ https://issues.apache.org/jira/browse/SYNCOPE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrea Patricelli updated SYNCOPE-1019:
---------------------------------------
    Description: 
Provide a mechanism for defining templates (in terms of HTML, CSS and image files) to simply
the appearance customization of the Enduser UI.
The the goal of the issue is to provide a way to:
- avoid HTML code duplication, and define reusable components.
- define an HTML template mechanism which aim is to improve customizability of the enduser
(enduser is meant to be customized and extended, it is not a finite product, but a proposal
from which to start a new implementation).
- exploit as much as possible code re-usability features provided by AngularJS (if possible).
- if needed review actula  CSS implementation, in order to better fit the new template mechanism
- do NOT compromise (or change) enduser functionalities at all! Buttons, selects, wizard and
other components should preserve their role and function; the core logic should remain the
same, though enduser is open to discuss improvements also in that way ;)
[This|https://code.angularjs.org/1.6.3/docs/guide/templates] could be a good starting point
to understand how to use AngularJS tools to implement templating.
BTW If you have proposals that does not involve AngularJS features, they are well accepted
and can be accepted anyway.
Some of the features described there, like directives, have also been used in the Enduser
to define some reusable components (e.g. dynamic-plain-attribute).

  was:
Provide a mechanism for defining templates (in terms of HTML, CSS and image files) to simply
the appearance customization of the Enduser UI.
The the goal of the issue is to provide a way to:
- avoid HTML code duplication, and define reusable components.
- define an HTML template mechanism which aim is to improve customizability of the enduser
(enduser is meant to be customized and extended, it is not a finite product, but a proposal
from which to start a new implementation).
- exploit as much as possible code re-usability features provided by AngularJS (if possible).
- if needed review actula  CSS implementation, in order to better fit the new template mechanism
- do NOT compromise (or change) enduser functionalities at all! Buttons, selects, wizard and
other components should preserve their role and function; the core logic should remain the
same, though enduser is open to discuss improvements also in that way ;)
[This|https://code.angularjs.org/1.6.3/docs/guide/templates] could be a good starting point
to understand how to use AngularJS tools to implement templating.
If you have proposals that does not involve AngularJS features, they are well accepted and
can be discussed.
Some of the features described there, like directives, have also been used in the Enduser
to define some reusable components (e.g. dynamic-plain-attribute).


> Template mechanism for Enduser UI
> ---------------------------------
>
>                 Key: SYNCOPE-1019
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1019
>             Project: Syncope
>          Issue Type: New Feature
>          Components: enduser
>            Reporter: Francesco Chicchiriccò
>              Labels: gsoc2017
>             Fix For: 2.1.0
>
>
> Provide a mechanism for defining templates (in terms of HTML, CSS and image files) to
simply the appearance customization of the Enduser UI.
> The the goal of the issue is to provide a way to:
> - avoid HTML code duplication, and define reusable components.
> - define an HTML template mechanism which aim is to improve customizability of the enduser
(enduser is meant to be customized and extended, it is not a finite product, but a proposal
from which to start a new implementation).
> - exploit as much as possible code re-usability features provided by AngularJS (if possible).
> - if needed review actula  CSS implementation, in order to better fit the new template
mechanism
> - do NOT compromise (or change) enduser functionalities at all! Buttons, selects, wizard
and other components should preserve their role and function; the core logic should remain
the same, though enduser is open to discuss improvements also in that way ;)
> [This|https://code.angularjs.org/1.6.3/docs/guide/templates] could be a good starting
point to understand how to use AngularJS tools to implement templating.
> BTW If you have proposals that does not involve AngularJS features, they are well accepted
and can be accepted anyway.
> Some of the features described there, like directives, have also been used in the Enduser
to define some reusable components (e.g. dynamic-plain-attribute).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message