[jira] Created: (TOBAGO-706) Event list in UIViewRoot changed to request scope (only a test)

Event list in UIViewRoot changed to request scope (only a test) Key: TOBAGO-706 URL: https://issues.apache.org/jira/browse/TOBAGO-706 Project: MyFaces Tobago Issue Type:

Re: [VOTE] Release Tobago 1.0.19

Here is my +1 Regards Bernd Matthias Wessendorf schrieb: +1 On Thu, Oct 2, 2008 at 5:50 PM, Udo Schnurpfeil [EMAIL PROTECTED] wrote: Here is my +1 I've updated the demo on: http://tobago.atanion.net/tobago-example-demo/ Regards Udo Bernd Bohmann schrieb: Hello, I would like

[jira] Created: (TOBAGO-707) Ajax paging of tabGroup should skip disabled tabs

Ajax paging of tabGroup should skip disabled tabs - Key: TOBAGO-707 URL: https://issues.apache.org/jira/browse/TOBAGO-707 Project: MyFaces Tobago Issue Type: Bug Components: Themes

Another approach to the templating problem

Hello everyone I have developed another approach to the templating problem. Most solutions which tried to tackle the approach worked on interepted template level: https://issues.apache.org/jira/browse/TOMAHAWK-1327 I did another approach the last few weeks I made an embedded templating

[jira] Commented: (TOMAHAWK-1327) A proposed solution to separate javascript code from java code in Renderers

[ https://issues.apache.org/jira/browse/TOMAHAWK-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12636804#action_12636804 ] Werner Punz commented on TOMAHAWK-1327: --- Well I dont think an interpreted template

[jira] Issue Comment Edited: (TOMAHAWK-1327) A proposed solution to separate javascript code from java code in Renderers

[ https://issues.apache.org/jira/browse/TOMAHAWK-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12636804#action_12636804 ] werpu edited comment on TOMAHAWK-1327 at 10/4/08 3:20 AM:

[jira] Created: (TRINIDAD-1248) Documentation error

Documentation error --- Key: TRINIDAD-1248 URL: https://issues.apache.org/jira/browse/TRINIDAD-1248 Project: MyFaces Trinidad Issue Type: Improvement Components: Documentation Affects Versions: 1.2.9-core

[jira] Resolved: (TRINIDAD-1248) Documentation error

[ https://issues.apache.org/jira/browse/TRINIDAD-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1248. -- Resolution: Fixed Fix Version/s: 1.0.10-core

Re: Thoughts on Trinidad

Andrew Robinson schrieb: However, as Matthias pointed out, JSF 2.0 standardize Trinidad's principal core features namely PPR and Resource handling and hopefully skinning too. Under such circumstances, I feel that we should wait for 2.0 to be cemented before going through a massive refactoring of

Re: Thoughts on Trinidad

Agree with Werner's assessment on JSF2.0 adoption. The 1.2 adoption curve shouldn't be a benchmark for 2.0 adoption. I think 2.0, when it goes final, is going to have significant uptake. Apple might already be using the Mojarra snapshot for one of its rebate processes:

Re: Thoughts on Trinidad

Simon Lessard schrieb: Hi, The UIX issue is a very valid one indeed and so few link to it remains, it's a shame that we didn't get rid of it already and I'm to blame a lot for that because I started it a long time ago but was never able to finish it. However, as Matthias pointed out, JSF

Re: Thoughts on Trinidad

Hazem Saleh schrieb: I do not think adding another component library to MyFaces will be good as well. I dont think so either, which reminds me I have to drop the code to the dojo stuff asap into the repository. What I mean is following. Trinidad is huge, Oracle is going to donate RCF which