[Trinidad] The new Casablanca (was: [Trinidad] New Component Showcase Demo and Casablanca Skin)
Hello guys, i followed up on gene...@incubator.a.o and we don't need a software grant for that. Marius and Adonis have already submitted the ICLAs and we are good to go from that point of (legal) view. Now, how to continue. I think we want to have a release (1.2.13) before we add the new skin. So once the release is done, we can integrate the skin; Pretty much after the new skin, I don't mind to have another release as well (- 1.2.14); Once that all is done, I think it is time to merge the stuff also into our Trinidad 2.0 offerings. Catalin, have you guys already checked that ? So let me run a 1.2.13 release, and after that we can integrate the new skin. -Matthias On Thu, Jan 7, 2010 at 11:37 PM, Catalin Kormos catalin.kor...@gmail.com wrote: Hello there, I have the pleasure to inform you about the work we did to develop a new skin for Trinidad and based on this a brand new, Trinidad components showcase application. You can see it all in action at [1]. It is still a working in progress, in advanced state though...i mean there is always something to be improved; nevertheless we would like to donate the new skin and the new demo application to the MyFaces community, in its current state, and continue there if you guys agree. Many thanks go to my collegue Adonis who has put a lot of effort into designing and implementing the new skin called 'Casablanca'. I'm sure he can give you more details as needed about how the process went. A few words about the new demo: first of all, many thanks to another collegue of mine, Cosmin, for his continuos efforts with this. the demo is working only with facelets (there is no jsp version) it uses the latest 1.2.13-SNAPSHOT version of Trinidad we tryied to build it so it can be searched online also, currently tryied with Google Custom Search, but this didn't work out so smoothly so far. In any case, that's the reason for the pretty urls used. (so, no point in trying the search currently as it doesn't work). in general, it replicates the examples available already for Trinidad in the existing demo, in someplaces slightly improved. it tryies to provide a platform on which to build much more demos as required as there can be always new ideas about demoing a meaningfull use case on Trinidad, or some component behaviour. I'm eager to get your reactions, I think these guys did a great job so far and this would bring Trinidad at least a few steps closer to a more appealing and user friendly component set. regards, Catalin [1] http://example.irian.at/trinidad-showcase-casablanca Codebeat www.codebeat.ro -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (TRINIDAD-1445) Lightweight Trinidad dialogs does not move like standard windows pop ups
[ https://issues.apache.org/jira/browse/TRINIDAD-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1445. -- Resolution: Duplicate looks like a duplicated of TRINIDAD-136 Lightweight Trinidad dialogs does not move like standard windows pop ups Key: TRINIDAD-1445 URL: https://issues.apache.org/jira/browse/TRINIDAD-1445 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.0.8-core Environment: Windows XP/ Solaris(in production) Websphere 6.1 Reporter: Anirban Datta When I am using the lightweight trinidad dialogs I cannot move or resize the iframe rendered. Is there any fix for it? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[Vote] Trinidad 1.2.12 release
Hi, I was running the needed tasks to get the 1.2.13 release of the Apache MyFaces Trinidad CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.2.13 artifacts and vote [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/core_1_2_13/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[Vote] Trinidad 1.2.13 release
Hi, I was running the needed tasks to get the 1.2.13 release of the Apache MyFaces Trinidad CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.2.13 artifacts and vote [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/core_1_2_13/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Vote] Trinidad 1.2.12 release --- please ignore
please ignore, I opened another thread. On Sat, Jan 23, 2010 at 3:18 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, I was running the needed tasks to get the 1.2.13 release of the Apache MyFaces Trinidad CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.2.13 artifacts and vote [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/core_1_2_13/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Vote] Trinidad 1.2.13 release
+1 On Sat, Jan 23, 2010 at 3:18 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, I was running the needed tasks to get the 1.2.13 release of the Apache MyFaces Trinidad CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.2.13 artifacts and vote [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/core_1_2_13/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [COMMUNITY] MyFaces += Jakob Korherr
Welcome and congrats Jakob! Regards, Jan-Kees 2010/1/21 Hazem Saleh haz...@apache.org: Congratulations Jakob! On Thu, Jan 21, 2010 at 11:28 AM, Ganesh Jung gan...@j4fry.org wrote: Welcome, Jakob! Am 20.01.2010 00:06, schrieb Leonardo Uribe: Congratulations! regards, Leonardo 2010/1/19 Gerhard Petracek gerhard.petra...@gmail.com mailto:gerhard.petra...@gmail.com welcome! regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/1/19 Matthias Wessendorf mat...@apache.org mailto:mat...@apache.org The Myfaces PMC is proud to announce a new addition to our community. Please welcome Jakob Korherr as the newest MyFaces committer! Jakob is an active member of the myfaces community, especially on the MyFaces 2.0 core efforts. �...@jakob: Please add yourself to the Master-POM at https://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/pom.xml -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Hazem Ahmed Saleh Ahmed Author of (The Definitive Guide to Apache MyFaces and Facelets): http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370 http://www.amazon.com/-/e/B002M052KY Web blog: http://www.jroller.com/page/HazemBlog [Web 2.0] Google Maps Integration with JSF: http://code.google.com/p/gmaps4jsf/ http://www.ibm.com/developerworks/library/wa-aj-gmaps/
Continuum access
Hey, Today I logged into Continuum to see why the build is failing every hour, but my project list was empty. Can someone grant me access rights? Thanks. Regards, Jan-Kees Ps. If you see this message for the second time, it's my mistake. I'm configuring my GMail to use the Apache mail server... ;-)
[jira] Commented: (TRINIDAD-1695) Lightweight dialogs broken with Firefox 3.6
[
https://issues.apache.org/jira/browse/TRINIDAD-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804153#action_12804153
]
Jed Smallwood commented on TRINIDAD-1695:
-
I have seen that the resolution to this issue is in the 1.2.14-SNAPSHOT as of
Jan 23, and the fix works for me at least. My company embeds Trinidad and
would like this fix so that we can operate on Firefox 3.6. That said, it seems
that the 1.2.13 is imminent. Is that the case and will this fix be a part of
1.2.13 and not 1.2.14?
Lightweight dialogs broken with Firefox 3.6
---
Key: TRINIDAD-1695
URL: https://issues.apache.org/jira/browse/TRINIDAD-1695
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.2.12-core
Environment: Trinidad 1.2.12
JSF 1.2_14 majorra
Tomcat 6.0.20
Firefox 3.6
Reporter: Tobias Freier
Assignee: Matthias Weßendorf
Priority: Critical
Fix For: 1.2.13-core
We have a major problem with the lightweight dialogs and the new firefox 3.6.
It's just not working anymore.
In Firebug I get this error:
[object Object]
http://myserver/adf/jsLibs/Common1_2_12.js
Line 7042
[Break on this error] var a11=a10.getBoxObjectFor(a8);\n
TypeError:a10.getBoxObjectFor is not a function {
message=a10.getBoxObjectFor is not a function, more... }
Looks like Firefox killed the function getBoxObjectFor.
a10 is a Document
a8 is body
Code at this place is:
7037 if(_agent.isGecko)
7038 {
7039 TrUIUtils._getElemLoc=function(a8)
7040 {
7041 var a10=a8.ownerDocument;
7042 var a11=a10.getBoxObjectFor(a8);
7043 var a12={x:a11.screenX,y:a11.screenY};
7044 a11=a10.getBoxObjectFor(a10.documentElement);
7045 a12.x-=a11.screenX;
7046 a12.y-=a11.screenY;
7047 return a12;
7048 }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2504) Google App Engine Support
Google App Engine Support - Key: MYFACES-2504 URL: https://issues.apache.org/jira/browse/MYFACES-2504 Project: MyFaces Core Issue Type: Improvement Components: JSR-252, JSR-314 Affects Versions: 2.0.0-alpha, 1.2.8 Environment: Google App Engine 1.3 Reporter: Ali Ok Priority: Minor Support for Google App Engine for MyFaces 1.2 and 2.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2504) Google App Engine Support
[ https://issues.apache.org/jira/browse/MYFACES-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804171#action_12804171 ] Ali Ok commented on MYFACES-2504: - Oops, I forgot something. This patch is for MyFaces 1.2.8 (http://svn.apache.org/repos/asf/myfaces/core/tags/1_2_8). I will work on 2.0 patch after your reviews. Google App Engine Support - Key: MYFACES-2504 URL: https://issues.apache.org/jira/browse/MYFACES-2504 Project: MyFaces Core Issue Type: Improvement Components: JSR-252, JSR-314 Affects Versions: 1.2.8, 2.0.0-alpha Environment: Google App Engine 1.3 Reporter: Ali Ok Priority: Minor Attachments: 2504.diff Support for Google App Engine for MyFaces 1.2 and 2.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2504) Google App Engine Support
[ https://issues.apache.org/jira/browse/MYFACES-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804172#action_12804172 ] Ali Ok commented on MYFACES-2504: - You can see my sample application working at: http://appenginetest.aliok.com.tr/ Complete source code, dependencies and structure of the project (including patched MyFaces 1.2.8, EL, JSTL, Facelets) : http://upload.aliok.com.tr/uploads/myfaces_1_2_8_gae_project.zip Google App Engine Support - Key: MYFACES-2504 URL: https://issues.apache.org/jira/browse/MYFACES-2504 Project: MyFaces Core Issue Type: Improvement Components: JSR-252, JSR-314 Affects Versions: 1.2.8, 2.0.0-alpha Environment: Google App Engine 1.3 Reporter: Ali Ok Priority: Minor Attachments: 2504.diff Support for Google App Engine for MyFaces 1.2 and 2.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2505) ComponentHandler.isNew requires deal with composite components
ComponentHandler.isNew requires deal with composite components -- Key: MYFACES-2505 URL: https://issues.apache.org/jira/browse/MYFACES-2505 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Leonardo Uribe Assignee: Leonardo Uribe Finally it was found a case where it is necessary to take into account the particular structure of a composite component. f:event could be inside next to composite:implementation, and we require this tag be just applied once. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2505) ComponentHandler.isNew requires deal with composite components
[ https://issues.apache.org/jira/browse/MYFACES-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2505. - Resolution: Fixed Fix Version/s: 2.0.0-beta-2 ComponentHandler.isNew requires deal with composite components -- Key: MYFACES-2505 URL: https://issues.apache.org/jira/browse/MYFACES-2505 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.0.0-beta-2 Finally it was found a case where it is necessary to take into account the particular structure of a composite component. f:event could be inside next to composite:implementation, and we require this tag be just applied once. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2502) Component state is lost for composite component childs of facets relocated by composite:insertChildren or composite:insertFacet
[
https://issues.apache.org/jira/browse/MYFACES-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12804198#action_12804198
]
Leonardo Uribe commented on MYFACES-2502:
-
I attached another patch ( MYFACES-2502-3.patch ) that does not have the
problem of c:if inside a composite component. The solution was move the
ordering code to ComponentTagHandlerDelegate and UIInstructionHandler, because
this is the only point where we can keep track of the components that needs to
be added/preserved/removed.
Component state is lost for composite component childs of facets relocated by
composite:insertChildren or composite:insertFacet
---
Key: MYFACES-2502
URL: https://issues.apache.org/jira/browse/MYFACES-2502
Project: MyFaces Core
Issue Type: Task
Components: JSR-314
Affects Versions: 2.0.0-beta
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Attachments: MYFACES-2502-2.patch, MYFACES-2502-3.patch
When partial state saving is not used, component state is lost for composite
component childs of facets relocated by composite:insertChildren or
composite:insertFacet
To understand why this is happening, it is necessary to understand how
facelets works in context and how composite:insertChildren and
composite:insertFacet works, so I'll do a resume for it.
In jsf 1.2, a facelet is applied in two cases:
1. When a page is request for first time, the whole component tree is build.
2. On a postback to update transient components like facelets UIInstruction.
To see it in context, suppose a simple app that ask for a name an it print it
on another component on the same page:
h:form
Name: h:inputText value={bean.name}/
Previous Name: h:outputtext value={bean.name}/
h:commandButton value=submit action=submitToThisSamePage/
/h:form
That is what happened when facelets + jsf 1.2 is used:
First Request:
- There is a call to FaceletViewHandler.buildView from
FaceletViewHandler.renderView that cause the UIViewRoot instance to be filled
for first time calling to f.apply().
- The view is rendered.
- Save the state for all non transient components found on the view. This
include save the tree structure too, so it can be reconstructed later.
Postback (The user send his name and do a submit):
- Restore the tree structure and component state for all saved components.
- All lifecycle phases continues until before renderView
- On FaceletViewHandler.renderView there is a call to buildView, and this
one causes all transient components like facelets UIInstruction to be added
to the tree. ComponentHandler first try to detect if the component is on the
view before create it, and if that is true do not create it, instead it takes
this instance and continue apply the taghandles and it remove and add it from
tree, to give the chance to other transient components to be created and
added correctly.
- The view is rendered.
- Save the state for all non transient components found on the view. This
include save the tree structure too, so it can be reconstructed later.
In jsf 2.0 it happens something similar. ViewDeclarationLanguage and
TagHandlerDelegate abstract classes were created, so some code was
relocated. To be clear, the algorithm in jsf 2.0 without partial state
saving is this:
First Request:
- There is a call to ViewDeclarationLanguage.buildView from
RenderResponseExecutor.execute that cause the UIViewRoot instance to be
filled for first time calling to f.apply().
- The view is rendered.
- Save the state for all non transient components found on the view. This
include save the tree structure too, so it can be reconstructed later.
Postback (The user send his name and do a submit):
- Restore the tree structure and component state for all saved components.
- All lifecycle phases continues until before renderView
- On RenderResponseExecutor.execute there is a call to buildView, and this
one causes all transient components like facelets UIInstructions to be added
to the tree. ComponentHandler first try to detect if the component is on the
view before create it, and if that is true do not create it, instead it takes
this instance and continue apply the taghandles and it remove and add it from
tree, to give the chance to other transient components to be created and
added correctly.
- The view is rendered.
- Save the state for all non transient components found on the view. This
include save the tree structure too, so it can be reconstructed later.
The algorithm in jsf 2.0 with partial state saving is different:
First Request:
- There is a call to ViewDeclarationLanguage.buildView from
