[
https://issues.apache.org/jira/browse/TOMAHAWK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545353
]
Bogdan Sava commented on TOMAHAWK-1032:
---
the patch cannot be used with Sun JSF RI 1.2 implementation
[
https://issues.apache.org/jira/browse/TOBAGO-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-538.
--
Resolution: Fixed
Avoid 'This page contains both secure and nonsecure items' messages in IE
[
https://issues.apache.org/jira/browse/TOBAGO-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-541.
--
Resolution: Fixed
ActionListener signature is restricted to SortActionEvent in
[
https://issues.apache.org/jira/browse/TOBAGO-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-542.
--
Resolution: Fixed
FileUpload doesn't work in Facelets
---
[
https://issues.apache.org/jira/browse/TOBAGO-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-544.
--
Resolution: Fixed
tip and label attribute of TobagoLabelExtensionHandler (tx) in facelets
[
https://issues.apache.org/jira/browse/TOMAHAWK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545430
]
Bogdan Sava commented on TOMAHAWK-1032:
---
patch is working with Sun JSF RI 1.2 implementation!
:)
sorry for
Ok, 14th 15th.
regards,
Martin
On 11/23/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Which day should we take?
-14th ?
-15th ?
-14th 15th ?
(to ensure we can have feedback, in case of a bad patch...)
I'd vote for option three, if this were a vote ;-)
-M
On Nov 23, 2007 3:13
[
https://issues.apache.org/jira/browse/TOBAGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545440
]
Tobias Glensk commented on TOBAGO-552:
--
A tc:panel with an included tc:label and tc:selectOneRadio is not
[
https://issues.apache.org/jira/browse/TRINIDAD-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhijit S Ghosh updated TRINIDAD-781:
-
Status: Patch Available (was: Open)
NavigationPane should support non-command
[
https://issues.apache.org/jira/browse/TRINIDAD-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhijit S Ghosh updated TRINIDAD-781:
-
Status: Open (was: Patch Available)
NavigationPane should support non-command
currently (the vote is done) it looks like, there is no interest in 1.2.4.1
Not to bad... since I fixed another bug in Trinidad plugins, which is needed to
get rid of a MyFaces CORE bug.
I tend to not release 1.2.4.1, but re-run this vote for a 1.2.5
what do you think ?
On Nov 22, 2007 5:18
Thanks for voting.
We got eight votes and all were +1.
Votes from:
-Matthias Wessendorf
-Manfred Geiler
-Bern Bohmann
-Simon Lessard
-Paul Spencer
-Cagatay Civici
-Bruno Aranda
-Grant Smith
I'll work on getting this process managed.
On Nov 23, 2007 10:28 PM, Grant Smith [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/TRINIDAD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brunette updated TRINIDAD-840:
---
Status: Patch Available (was: Open)
New attribute on tr:table to hide Select All/Select
I'd like to go for a 1.2.5 release.
I can provide the bits by tomorrow morning.
-M
On Nov 26, 2007 4:07 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
currently (the vote is done) it looks like, there is no interest in 1.2.4.1
Not to bad... since I fixed another bug in Trinidad plugins,
[
https://issues.apache.org/jira/browse/TRINIDAD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545481
]
Simon Lessard commented on TRINIDAD-840:
I don't know if this should be on component level or a skin
[
https://issues.apache.org/jira/browse/TRINIDAD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545486
]
Matthias Weßendorf commented on TRINIDAD-840:
-
ya, move this please to ML.
Jira discussion are odd
[
https://issues.apache.org/jira/browse/TRINIDAD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545489
]
Dave Brunette commented on TRINIDAD-840:
Yes, tr:table rowSelection=multiple / works just like it does
[
https://issues.apache.org/jira/browse/TOBAGO-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545490
]
Guido Dubois commented on TOBAGO-515:
-
Have you already looked after this? I am waiting for this...
tx:in in
[
https://issues.apache.org/jira/browse/TOBAGO-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545495
]
Guido Dubois commented on TOBAGO-348:
-
Have you already a target date for this behavior? It sounds good, and I
I think that this should probably be a skinning key instead of an
attribute, anyone else with that opinion? (I see that comment was
already made in the bug once)
On Nov 26, 2007 8:12 AM, Dave Brunette (JIRA) dev@myfaces.apache.org wrote:
New attribute on tr:table to hide Select All/Select None
Hi Jeanne,
The any-* types are for users that do not require specific
consideration. It is useful because then someone could define some
styles without worry of negatively impacting users with special needs.
In particular, it is most useful for people that extend skins. If
you are making a
Moving my response to this thread...
+1 on a skinning key instead of an attribute
-A
On Nov 26, 2007 9:12 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Thanks for filing https://issues.apache.org/jira/browse/TRINIDAD-840
and providing a patch.
Simon had a valid point, that this could be
[
https://issues.apache.org/jira/browse/TOBAGO-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545499
]
Bernd Bohmann commented on TOBAGO-515:
--
The binding attribute for the tx variant in facelets has a different
I'm expecting that as of JSR-286 though, we should even be able to
support popups in a wsrp environemnt. :)
Anyway, think of it this way. WSRP is a web-services layer. JSR-168 is
the container. Typically Portlets are run under WSRP though the JSR-168
container. The only difference is
Yeah, this patch was reversed because we had some issues. It works
under a bear-bones environment but when some other state-managers are
introduced, this patch blows up. I'll reassign it to 1.2.5 since it
primarily only impacts the portal environment which is still
experimental anyway.
Skinning property would prevent rendering as well, we're not talking about
using visibility: hidden here, but rather having something like
-tr-showSelectAllLink: false set on af|table selector.
Regards,
~ Simon
On Nov 26, 2007 11:41 AM, Dave Brunette [EMAIL PROTECTED] wrote:
Yeah, I
NullPointerException in AbstractSpringOrchestraScope when BeanPostProcessor is
configured
-
Key: ORCHESTRA-9
URL: https://issues.apache.org/jira/browse/ORCHESTRA-9
Oh... I didn't know the skin could prevent rendering. OK, that would seem
fine to me. I'll have to read up on that stuff, but I can re-work the patch
and submit a new one using a skinning property instead.
Date: Mon, 26 Nov 2007 11:58:50 -0500
From: [EMAIL PROTECTED]
To:
You can check train or breadcrumb renderers for usage examples. The former
use an integer property to determine how many visible station at a time it
should render while the latter use a boolean property to determine if the
current location should be rendered or not.
Regards,
~ Simon
On Nov
Thanks Simon. I had found the breadcrumb renderer and it was a good
example of how to use this. Cool stuff.
While looking around, I came across a skin property that already
existed called SkinProperties.AF_TABLE_SELECTION_BAR_IN_TABLE... but it
didn't seem to be used by
If it's appropriate, then use it, otherwise remove it. Whatever you decide,
the skin property will need to be added to the skinning reference doc.
Thanks,
D.
On Nov 26, 2007 12:48 PM, Dave Brunette [EMAIL PROTECTED] wrote:
Thanks Simon. I had found the breadcrumb renderer and it was a
What I was asking was if it's appropriate to use it. It seems right to
me, but I just wanted to make sure I wasn't stepping on somebody else's
property. I'll move on with using it until I hear otherwise.
No doubt, it's important to keep the the documentation updated. Any tips
on
Hi Dave,
src/site/xdoc/skin-selectors.xml from Trinidad project root (not
trinidad-api nor trinidad-impl).
Regards,
~ Simon
On Nov 26, 2007 2:15 PM, Dave Brunette [EMAIL PROTECTED] wrote:
What I was asking was if it's appropriate to use it. It seems right
to me, but I just wanted to
Great, thanks for the help guys. The latest patch attached to the issue
should have the doc updates included.
Date: Mon, 26 Nov 2007 14:18:18 -0500
From: [EMAIL PROTECTED]
To: dev@myfaces.apache.org
Subject: Re: [Trinidad] Enhancement to hide Select All/Select None on table?
Hi Dave,
Hello.
I noticed in the SVN repository that there are no tags for the 1.2.0 release of
the Core or the 1.1.6 release of Tomahawk. The branches are available, but no
tags. Since these are released, should there be tags?
Also, is there anyone willing and able to update the compatibility matrix
35 matches
Mail list logo
