[magnolia-dev] [JIRA] (MTE-61) Concept for JS/CSS dependent components

2016-04-11 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-61 
 
 
 
  Concept for JS/CSS dependent components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 0.10 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MTE-61) Concept for JS/CSS dependent components

2016-02-29 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-61 
 
 
 
  Concept for JS/CSS dependent components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 0.10 
 
 
 

Fix Version/s:
 
 0.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MTE-61) Concept for JS/CSS dependent components

2016-01-11 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-61 
 
 
 
  Concept for JS/CSS dependent components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 0.9 
 
 
 

Fix Version/s:
 
 0.8 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MTE-61) Concept for JS/CSS dependent components

2015-11-25 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-61 
 
 
 
  Concept for JS/CSS dependent components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Fix Version/s:
 
 0.8 
 
 
 

Fix Version/s:
 
 1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MTE-61) Concept for JS/CSS dependent components

2015-10-29 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-61 
 
 
 
  Concept for JS/CSS dependent components  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Affects Versions:
 

 0.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 29/Oct/15 11:09 AM 
 
 
 

Fix Versions:
 

 1.0 
 
 
 

Labels:
 

 selected-for-backlog to-estimate 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 
To provide a satisfactory basic OOTB set of components to satisfy our customers and evaluators, we require several components which depend on front-end resources (JS/CSS): Video Carousel Columns Social share 
However, including CSS and JS is incompatible with our goals with the MTE to create a future-proof module that is not dependent on the quickly changing trends of front end development. 
How then should we include these components in the product, while keeping a future-proof MTE? 
A related issue is: how can a component provide its unique