From dev-return-15081-archive-asf-public=cust-asf.ponee.io@syncope.apache.org Tue Feb 20 08:53:14 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2ABB1180654 for ; Tue, 20 Feb 2018 08:53:13 +0100 (CET) Received: (qmail 84871 invoked by uid 500); 20 Feb 2018 07:53:12 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 84860 invoked by uid 99); 20 Feb 2018 07:53:12 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Feb 2018 07:53:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 34707180033 for ; Tue, 20 Feb 2018 07:53:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id u_3yUcg5JQk1 for ; Tue, 20 Feb 2018 07:53:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6B12A5F121 for ; Tue, 20 Feb 2018 07:53:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 12CBFE0257 for ; Tue, 20 Feb 2018 07:53:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id BA34A22576 for ; Tue, 20 Feb 2018 07:53:01 +0000 (UTC) Date: Tue, 20 Feb 2018 07:53:01 +0000 (UTC) From: "Andrea Patricelli (JIRA)" To: dev@syncope.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SYNCOPE-1019) Template mechanism for Enduser UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SYNCOPE-1019?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 369791#comment-16369791 ]=20 Andrea Patricelli commented on SYNCOPE-1019: -------------------------------------------- Hi Arun, glad to know about your interest! Your knowledge=C2=A0seems good and don't worry about the skills. Please rea= d carefully description of this issue, learn basic concepts about Syncope a= nd what is its Enduser. You can find useful links in the comments of this i= ssue (docs, AngularJS templating mechanism and more) and you can refer to t= he [mailing lists|https://syncope.apache.org/mailing-lists.html]=C2=A0to ha= ve support on Syncope. A suggestion:=C2=A0do not to focus only on=C2=A0JS (directives, etc), but a= lso on HTML. > 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=C3=B2 > Priority: Major > Labels: gsoc2018 > Fix For: 2.1.0 > > > Provide a mechanism for defining templates (in terms of HTML, CSS and ima= ge 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 customizabili= ty of the enduser (enduser is meant to be customized and extended, it is no= t a finite product, but a proposal from which to start a new implementation= ). > - exploit as much as possible code re-usability features provided by Angu= larJS (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 functio= n; 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 g= ood starting point to understand how to use AngularJS tools to implement te= mplating. > 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 use= d in the Enduser to define some reusable components (e.g. dynamic-plain-att= ribute). -- This message was sent by Atlassian JIRA (v7.6.3#76005)