[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-1019:

Fix Version/s: 2.0.11

> 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ò
>Priority: Major
>  Labels: gsoc2018
> Fix For: 2.0.11, 2.1.2, 3.0.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
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-1019:

Fix Version/s: (was: 2.1.1)
   2.1.2

> 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ò
>Priority: Major
>  Labels: gsoc2018
> Fix For: 2.1.2, 3.0.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
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-1019:

Fix Version/s: 3.0.0

> 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ò
>Priority: Major
>  Labels: gsoc2018
> Fix For: 2.1.1, 3.0.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
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-1019:

Fix Version/s: (was: 2.1.0)

> 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ò
>Priority: Major
>  Labels: gsoc2018
> Fix For: 2.1.1
>
>
> 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
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-1019:

Fix Version/s: 2.1.1

> 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ò
>Priority: Major
>  Labels: gsoc2018
> Fix For: 2.1.0, 2.1.1
>
>
> 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
(v7.6.3#76005)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-1019:

Labels: gsoc2018  (was: gsoc2017)

> 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ò
>Priority: Major
>  Labels: gsoc2018
> 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
(v7.6.3#76005)

Re: [jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Menuka Warushavithana]

Hi Andrea,
I have shared my draft proposal for the project "Template mechanism for
End-user UI" on the official GSoC site. Please review it and provide some
comments if you could, so that I can improve it and submit a refined
proposal by April 3rd.

Thank You
Menuka Warushavithana
GitHub: https://github.com/menuka94
LinkedIn: https://www.linkedin.com/in/menukawarushavithana/

On Mon, Mar 27, 2017 at 1:18 PM, Andrea Patricelli (JIRA) 
wrote:

>
>  [ 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
> 

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Menuka Warushavithana (JIRA)]

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

Menuka Warushavithana updated SYNCOPE-1019:
---

Hi Andrea,
I have shared my draft proposal for the project "Template mechanism for
End-user UI" on the official GSoC site. Please review it and provide some
comments if you could, so that I can improve it and submit a refined
proposal by April 3rd.

Thank You
Menuka Warushavithana
GitHub: https://github.com/menuka94
LinkedIn: https://www.linkedin.com/in/menukawarushavithana/

On Mon, Mar 27, 2017 at 1:18 PM, Andrea Patricelli (JIRA) 



> 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)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Andrea Patricelli (JIRA)]

 [ 
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)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Andrea Patricelli (JIRA)]

 [ 
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.
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).

  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 ;)


> 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.
> 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).



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

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Andrea Patricelli (JIRA)]

 [ 
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 ;)

  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


> 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 message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Andrea Patricelli (JIRA)]

 [ 
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

  was:Provide a mechanism for defining templates (in terms of HTML, CSS and 
image files) to simply the appearance customization of the Enduser UI.


> 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



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

[jira] [Updated] (SYNCOPE-1019) Template mechanism for Enduser UI

[Menuka Warushavithana (JIRA)]

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

Menuka Warushavithana updated SYNCOPE-1019:
---

Hi Andrea,
I have read through most of the documentation of Apache Syncope and I
believe I have a base level understanding of it as a provisioning engine. I
would like to start writing a proposal for the project as soon as possible.
Therefore I would like to know the expected deliverables of the project in
a little more detail.

Thanks and Regards
Menuka
LinkedIn: https://www.linkedin.com/in/menukawarushavithana/
GitHub: https://www.github.com/menuka94


On Mon, Mar 6, 2017 at 3:15 PM, Andrea Patricelli (JIRA) 



> 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.



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