[
https://issues.apache.org/jira/browse/ORCHESTRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching resolved ORCHESTRA-23.
-
Resolution: Fixed
Patch applied. Thanks very much Dan.
Incorrect initialization of
Hi Lenonardo,
[EMAIL PROTECTED] schrieb:
Author: lu4242
Date: Fri Apr 18 00:00:16 2008
New Revision: 649387
URL: http://svn.apache.org/viewvc?rev=649387view=rev
Log:
Generation of .tld
I just wanted to say I really appreciate all the work you're putting
into this.
I'm back from
On Wed, Apr 16, 2008 at 12:33 PM, Mike Kienenberger [EMAIL PROTECTED]
wrote:
Another alternative to option 1 is to #parse($fileName) or
#include($fileName).
You can specify filename externally. This is probably the best
solution so long as the contents of the file included can be included
SelectMany Shuttle javascripted links not properly rendered if url parameter is
set
---
Key: TRINIDAD-1051
URL: https://issues.apache.org/jira/browse/TRINIDAD-1051
Leonardo Uribe schrieb:
On Wed, Apr 16, 2008 at 12:33 PM, Mike Kienenberger
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Another alternative to option 1 is to #parse($fileName) or
#include($fileName).
You can specify filename externally. This is probably the best
Using dynamic pattern in f:convertDateTime
Key: TRINIDAD-1052
URL: https://issues.apache.org/jira/browse/TRINIDAD-1052
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.7-core
[
https://issues.apache.org/jira/browse/TRINIDAD-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590323#action_12590323
]
Matthias Weßendorf commented on TRINIDAD-1051:
--
if(href != null
[
https://issues.apache.org/jira/browse/TRINIDAD-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590326#action_12590326
]
Simon Kitching commented on TRINIDAD-1052:
--
I don't think this is a bug.
The
[
https://issues.apache.org/jira/browse/TRINIDAD-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590328#action_12590328
]
Werner Punz commented on TRINIDAD-1051:
---
I am still not entirely convinced if we
[
https://issues.apache.org/jira/browse/TRINIDAD-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590331#action_12590331
]
Matthias Weßendorf commented on TRINIDAD-1052:
--
yes. simon is right
Using
[
https://issues.apache.org/jira/browse/TRINIDAD-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590374#action_12590374
]
Paul van Rossem commented on TRINIDAD-1052:
---
Simon and Matthias, thanks for
[
https://issues.apache.org/jira/browse/TOMAHAWK-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590399#action_12590399
]
Simon Kitching commented on TOMAHAWK-1234:
--
People, *please* do not reformat
Simon Kitching commented on TOMAHAWK-1234:
--
People, *please* do not reformat code at the same time that you modify it.
+1
I wanted to review this patch for correctness, as I have done a lot of work
on the calendar component. But it's really
[
https://issues.apache.org/jira/browse/MYFACES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann reopened MYFACES-1825:
duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds()
[
https://issues.apache.org/jira/browse/MYFACES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590417#action_12590417
]
Bernd Bohmann commented on MYFACES-1825:
I think it should be:
Iterator it =
[
https://issues.apache.org/jira/browse/TOMAHAWK-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590420#action_12590420
]
Simon Kitching commented on TOMAHAWK-1234:
--
After wading through the 239-line
Avoid possible NullPointerException and NumberFormatException in
JspStateManagerImpl.getServerStateId
-
Key: MYFACES-1866
URL:
[
https://issues.apache.org/jira/browse/MYFACES-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved MYFACES-1866.
Resolution: Fixed
Avoid possible NullPointerException and NumberFormatException in
[
https://issues.apache.org/jira/browse/TOMAHAWK-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590466#action_12590466
]
Simon Kitching commented on TOMAHAWK-1234:
--
Within class HtmlCalendarRendere,
[
https://issues.apache.org/jira/browse/TOMAHAWK-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590461#action_12590461
]
Zdenek Sochor commented on TOMAHAWK-1234:
-
Hi,
wouldn't it be better to check
Hi,
i think, that there is a problem with the markup rendered for navigationPane
(hint=bar). The component is embedded in one div. A table is rendered
for each child - commandNavigationItems. These tables are containing a
tbody with style=display:inline. This causes strange behaviour and i
think
[
https://issues.apache.org/jira/browse/TOMAHAWK-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590479#action_12590479
]
Richard J. Barbalace commented on TOMAHAWK-1231:
It sounds as if this
Hi Team,
Generated file is now depending on the mime type :) .
Here is an example of usage)
s:exporter for=your dataTable id fileType=XLS or PDF
h:commandButton action= value=Export/
/s:exporter
Thanks all for your suggestions.
On Fri, Apr 18, 2008 at 5:45 AM, Hazem Saleh [EMAIL PROTECTED]
Refactoring Calendar component
--
Key: TOMAHAWK-1235
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1235
Project: MyFaces Tomahawk
Issue Type: Improvement
Components: Calendar
Affects Versions:
Hi Matzew,
What is the problem with the previous syntax :-
s:exporter for=your dataTable id fileType=EXCEL or PDF
h:commandButton action= value=Export/
/s:exporter
On Fri, Apr 18, 2008 at 6:57 PM, Matthias Wessendorf [EMAIL PROTECTED]
wrote:
Hi,
I would instead of:
s:exporter for=your
Hi,
I would instead of:
s:exporter for=your dataTable id fileType=EXCEL or PDF
h:commandButton action= value=Export/
/s:exporter
expect something like:
commandButton...
s:exporter/
/commandButton
On Fri, Apr 18, 2008 at 6:49 PM, Hazem Saleh [EMAIL PROTECTED] wrote:
Hi Team,
Own Renderer for cell
-
Key: TOBAGO-651
URL: https://issues.apache.org/jira/browse/TOBAGO-651
Project: MyFaces Tobago
Issue Type: Improvement
Components: Themes
Reporter: Bernd Bohmann
Hello Mark,
I found no issues with 1.0-alpha-2-SNAPSHOT and the tobago build.
When you will release the 1.0-alpha-2-SNAPSHOT version?
Regards
Bernd
Bernd Bohmann schrieb:
Hello Mark,
I changed a local tobago version to use the apt-maven-plugin.
I think everything is fine with the new
[
https://issues.apache.org/jira/browse/ORCHESTRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590527#action_12590527
]
Dan Tran commented on ORCHESTRA-23:
---
any chance we are going into have 1.1.1 release?
On Fri, Apr 18, 2008 at 7:02 PM, Hazem Saleh [EMAIL PROTECTED] wrote:
Hi Matzew,
What is the problem with the previous syntax :-
s:exporter for=your dataTable id fileType=EXCEL or PDF
h:commandButton action= value=Export/
/s:exporter
I thought that the exporter would be an
[
https://issues.apache.org/jira/browse/TOBAGO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-621.
--
Resolution: Fixed
Avoid empty class in option element of tc:selectXXX
Move tobago-menu.css and tobago-sheet.css content to style.css
--
Key: TOBAGO-652
URL: https://issues.apache.org/jira/browse/TOBAGO-652
Project: MyFaces Tobago
Issue Type:
On Thu, Apr 17, 2008 at 9:21 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I'll be happy either way, but I think I now bend to the below
explanation of 5 == 5.0 from Jeanne's reasoning
FWIW, I actually agree with Jeanne's first opinion. :-)
That is, I think of 5 as 5.*. 5.0 as 5.0.*, etc.
Well that is difficult isn't it? Perhaps what I suggested a long time
back in my bug is best and allow regexp:
@agent blah and (matches-version: /someRegExp/)
example to match 6.x through 7.x:
@agent ie and (matches-version: /[67](\.\d)*/)
yeah it is harder to write, but then we can write it
[
https://issues.apache.org/jira/browse/TOBAGO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590550#action_12590550
]
Volker Weber commented on TOBAGO-652:
-
I don't like this one BIG file. It is not easy
[
https://issues.apache.org/jira/browse/TOBAGO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-652.
--
Resolution: Fixed
Move tobago-menu.css and tobago-sheet.css content to style.css
[
https://issues.apache.org/jira/browse/TOBAGO-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-419.
--
Resolution: Fixed
Sheets disappear on a tab in IE
---
Hi all,
The regex would be powerful though I'm afraid that it would not as
obvious or easy to use for non-technical designers/skinners.
I think something like this would be clearer:
@agent ie and (min-major-version: 6) and (min-minor-version: 1) and
(max-major-version: 6) {
/* styles for IE
[
https://issues.apache.org/jira/browse/TOBAGO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590556#action_12590556
]
Bernd Bohmann commented on TOBAGO-652:
--
This would be the next possible step, but I
Perhaps matching the full agent string is a bad idea. I'd hate to have
to parse many variations of things like:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b5)
Gecko/2008032620 Firefox/3.0b5
-Andrew
On Fri, Apr 18, 2008 at 12:46 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
The
I agree, full agent version matching is troublesome. With this approach:
@agent ie and (min-major-version: 6) and (min-minor-version: 1) and
(max-major-version: 6) {
/* styles for IE agent version 6.1 through 6.x (inclusive) */
}
We could go up to as many decimal tokens as we wish, e.g.
Could we leverage maven version parsing algorithms? Maven seems to be
able to parse a lot of crap :)
-Andrew
On Fri, Apr 18, 2008 at 1:09 PM, Matt Cooper [EMAIL PROTECTED] wrote:
I agree, full agent version matching is troublesome. With this approach:
@agent ie and (min-major-version: 6)
@agent id (version: 8-SNAPSHOT).. :)
Andrew Robinson wrote:
Could we leverage maven version parsing algorithms? Maven seems to be
able to parse a lot of crap :)
-Andrew
On Fri, Apr 18, 2008 at 1:09 PM, Matt Cooper [EMAIL PROTECTED] wrote:
I agree, full agent version matching is
That's fine with me. At this time, I'm really only concerned that we
have a flexible-enough API which has a CSS-like syntax to it.
Regards,
Matt
On Fri, Apr 18, 2008 at 1:30 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
Could we leverage maven version parsing algorithms? Maven seems to be
Hi team
I am planning to recommend JSF and MyFaces for the development of the
application.
like Navigation Tree on the left side, header, footer and body ..
1) Can any one share a piece of code to develop Dynamic Navigation Tree(like
ServerSideToggling ..I will get the data from backend based
[
https://issues.apache.org/jira/browse/ORCHESTRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590607#action_12590607
]
Mario Ivankovits commented on ORCHESTRA-23:
---
*shocked* Really?! All due to this
@agent ie (versions: 4 5. 6)
where 4 = 4
and 5. = 5, 5.5, 5.6, 5.6.2 ...
and 5.5 = 5.5
and 5.5. = 5.5, 5.5.3 ...
Glauco P. Gomes
Scott O'Bryan escreveu:
@agent id (version: 8-SNAPSHOT).. :)
Andrew Robinson wrote:
Could we leverage maven version parsing algorithms? Maven seems to be
able to
Sorry this should have gone to dev@, not users@:
While looking at the Trinidad demo, I was thinking that it is odd that
the skins are shipped inside the demo project as opposed to jars that
can be added to user's applications.
I was thinking this layout would make more sense:
Hmm, that's an interresting format.
Glauco P. Gomes wrote:
@agent ie (versions: 4 5. 6)
where 4 = 4
and 5. = 5, 5.5, 5.6, 5.6.2 ...
and 5.5 = 5.5
and 5.5. = 5.5, 5.5.3 ...
Glauco P. Gomes
Scott O'Bryan escreveu:
@agent id (version: 8-SNAPSHOT).. :)
Andrew Robinson wrote:
Could we
Still +1
Andrew Robinson wrote:
Sorry this should have gone to dev@, not users@:
While looking at the Trinidad demo, I was thinking that it is odd that
the skins are shipped inside the demo project as opposed to jars that
can be added to user's applications.
I was thinking this layout
I like this too
does the list of space separated numbers comply to that CSS future spec we
were talking about?
On Fri, Apr 18, 2008 at 11:43 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hmm, that's an interresting format.
Glauco P. Gomes wrote:
@agent ie (versions: 4 5. 6)
where 4 = 4
OK, how about
option 5) the version feature is a String that matches the native
major.minor.whatever format of the browser's engine. If the browser's
engine uses non . for separating versions, . is used instead.
For matches, the * character is allowed in any version section.
For
Cristi Toth said the following On 4/18/2008 2:58 PM PT:
I like this too
does the list of space separated numbers comply to that CSS future
spec we were talking about?
I don't think it does.
-- Blake Sullivan
On Fri, Apr 18, 2008 at 11:43 PM, Scott O'Bryan [EMAIL PROTECTED]
mailto:[EMAIL
On Fri, Apr 18, 2008 at 6:15 PM, Blake Sullivan
[EMAIL PROTECTED] wrote:
OK, how about
option 5)
I like option 5.
Andy
+1
On Fri, Apr 18, 2008 at 4:19 PM, Andy Schwartz
[EMAIL PROTECTED] wrote:
On Fri, Apr 18, 2008 at 6:15 PM, Blake Sullivan
[EMAIL PROTECTED] wrote:
OK, how about
option 5)
I like option 5.
Andy
[
https://issues.apache.org/jira/browse/ORCHESTRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590629#action_12590629
]
Dan Tran commented on ORCHESTRA-23:
---
yeah, we had so much problems after upgrading to
I have to admit it's +1 from me to option 5) :)
On Sat, Apr 19, 2008 at 12:21 AM, Andrew Robinson
[EMAIL PROTECTED] wrote:
+1
On Fri, Apr 18, 2008 at 4:19 PM, Andy Schwartz
[EMAIL PROTECTED] wrote:
On Fri, Apr 18, 2008 at 6:15 PM, Blake Sullivan
[EMAIL PROTECTED] wrote:
OK, how
+1 to option 5
On Fri, Apr 18, 2008 at 4:21 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
+1
On Fri, Apr 18, 2008 at 4:19 PM, Andy Schwartz
[EMAIL PROTECTED] wrote:
On Fri, Apr 18, 2008 at 6:15 PM, Blake Sullivan
[EMAIL PROTECTED] wrote:
OK, how about
option 5)
I like this option, but what hapens if the user wants to match the
version 5? (Only 5, not 5.5)
Glauco P. Gomes
Blake Sullivan escreveu:
OK, how about
option 5) the version feature is a String that matches the native
major.minor.whatever format of the browser's engine. If the
browser's
+1 if this includes multiple major versions (5, 6, 7)
Glauco P. Gomes
Blake Sullivan escreveu:
Glauco P. Gomes said the following On 4/18/2008 3:45 PM PT:
I like this option, but what hapens if the user wants to match the
version 5? (Only 5, not 5.5)
@agent ie and (version:5.0)
That will
It does:
@agent ie and (min-version:5) and (max-version:7) {
/* styles for all 5.*, 6.*, and 7.* versions of the IE agent versions */
}
Regards,
Matt
On Fri, Apr 18, 2008 at 5:02 PM, Glauco P. Gomes
[EMAIL PROTECTED] wrote:
+1 if this includes multiple major versions (5, 6, 7)
Glauco P.
I think that I'm not expressed correctly, what I wanted to say was not
sequencial major versions.
Eg.:
@agent ie and (version: 6 and 8) {
/* styles for all 6.*, and 8.* versions of the IE agent versions */
}
Or this doesn't make sense?
Glauco P. Gomes
Matt Cooper escreveu:
It does:
Glauco P. Gomes said the following On 4/18/2008 4:28 PM PT:
I think that I'm not expressed correctly, what I wanted to say was not
sequencial major versions.
Eg.:
@agent ie and (version: 6 and 8) {
/* styles for all 6.*, and 8.* versions of the IE agent versions */
}
@agent ie and
+1
Glauco P. Gomes
Blake Sullivan escreveu:
Glauco P. Gomes said the following On 4/18/2008 4:28 PM PT:
I think that I'm not expressed correctly, what I wanted to say was not
sequencial major versions.
Eg.:
@agent ie and (version: 6 and 8) {
/* styles for all 6.*, and 8.*
OK, I have implemented and attached a Version class with the desired
behavior and tested that the following works as expected
System.out.println(toString: + new Version(5.0.3, *));
System.out.println(hashCode: + new Version(5.0.3, *).hashCode());
System.out.println(not equals: + new
[
https://issues.apache.org/jira/browse/TOMAHAWK-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hazem Saleh updated TOMAHAWK-1235:
--
Status: Patch Available (was: Open)
Refactoring Calendar component
Hi Team,
I did refactoring for the Tomahawk Calendar component as its renderer class
was very huge.
Here is the patch, please apply if you have some time :
https://issues.apache.org/jira/browse/TOMAHAWK-1235
Thanks all.
--
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog
The beach and purple skins are demos, not meant to be added to a user's app.
They are meant to showcase skinning features, like @rules, etc.
So when we add a new skinning feature, we add it to these skins to demo it.
+1 for suede skin
- Jeanne
Scott O'Bryan wrote, On 4/18/2008 2:49 PM PT:
+1. I really like the *.
Glauco P. Gomes wrote, On 4/18/2008 4:40 PM PT:
+1
Glauco P. Gomes
Blake Sullivan escreveu:
Glauco P. Gomes said the following On 4/18/2008 4:28 PM PT:
I think that I'm not expressed correctly, what I wanted to say was
not sequencial major versions.
Eg.:
@agent ie
in t:datatable columnClasses property doesn't render EL expressions
---
Key: TOMAHAWK-1236
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1236
Project: MyFaces Tomahawk
70 matches
Mail list logo
