Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Reporter: Cale Scholl
Priority: Minor
The following section of code was located in the _subparse function of
trinidad-impl DateFormat.js and was ripped out:
else if (charCount
[
https://issues.apache.org/jira/browse/TRINIDAD-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1821:
--
Status: Patch Available (was: Open)
client-side DateFormat improperly parses year when
Trinidad
Issue Type: Bug
Components: Components
Reporter: Cale Scholl
Priority: Minor
TrDateTimeRangeValidator converts date strings to date objects in order to do
validation. Just use the date objects directly, if available.
--
This message
[
https://issues.apache.org/jira/browse/TRINIDAD-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1818:
--
Status: Patch Available (was: Open)
TrDateTimeRangeValidator should validate using date
[
https://issues.apache.org/jira/browse/TRINIDAD-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12837043#action_12837043
]
Cale Scholl commented on TRINIDAD-1683:
---
Since Java 1.5+ supports covariant return
: 1.2.12-core
Reporter: Cale Scholl
Priority: Minor
MAIN ENHANCEMENT:
In trinidad-impl ColorConverter.getClientScript we have:
--
String[] patterns = getPatterns();
buff.append(_cfs[\);
buff.append(clientId);
buff.append(\]=);
if (patterns.length == 1
I have two related patches available:
https://issues.apache.org/jira/browse/TRINIDAD-1678
https://issues.apache.org/jira/browse/TRINIDAD-1683
Thank you,
Cale
Aloha,
convertNumber currently converts to Long when integerOnly=true; I'd
like to convert to BigInteger instead so that we're less likely to lose
any precision.
There's a test in NumberConverterTestCase called
testIntegerOnlyIsHonoured that expects Long values, so I changed it to
expect
: Components
Affects Versions: 1.2.12-core
Reporter: Cale Scholl
Priority: Minor
ISSUE:
--
JS numbers are 64-bit values and thus only have 16 digits of precision; this
isn't enough to represent the max value of a Long, BigInteger, or BigDecimal.
This means
[
https://issues.apache.org/jira/browse/TRINIDAD-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1683:
--
Status: Patch Available (was: Open)
client-side convertNumber causes loss of precision
[
https://issues.apache.org/jira/browse/TRINIDAD-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798257#action_12798257
]
Cale Scholl commented on TRINIDAD-1678:
---
see also:
https://issues.apache.org/jira
/browse/TRINIDAD-1678
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.2.12-core
Reporter: Cale Scholl
Priority: Minor
ISSUE:
--
Say we have a 22-digit number string 77
[
https://issues.apache.org/jira/browse/TRINIDAD-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1678:
--
Status: Patch Available (was: Open)
TrNumberFormat.prototype.numberToString doesn't
Now that the busy holiday season is over, would someone mind taking a
look at my patch?
Thanks,
Cale
On 12/24/2009 10:34 PM, Cale Scholl (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TRINIDAD-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl
Issue Type: Bug
Components: Components
Affects Versions: 1.2.12-core
Reporter: Cale Scholl
Priority: Minor
ISSUE:
--
Given a default convertNumber e.g. af:convertNumber id=cn1 type=number/:
Enter 1.23456789. Press Submit. You will see that the number
[
https://issues.apache.org/jira/browse/TRINIDAD-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1666:
--
Status: Patch Available (was: Open)
convertNumber without maxfractiondigits specified
There are two issues I'd like to discuss:
1. In trinidad-impl ColorConverter.getClientScript we have:
String[] patterns = getPatterns();
buff.append(_cfs[\);
buff.append(clientId);
buff.append(\]=);
if (patterns.length == 1)
{
buff.append(\);
Howdy folks,
This patch has been available for a week. Could one of the Trinidad
committers take a look?
Thank you,
Cale
Cale Scholl (JIRA) said the following On 7/31/2009 4:12 PM PT:
[
https://issues.apache.org/jira/browse/TRINIDAD-1538?page
[
https://issues.apache.org/jira/browse/TRINIDAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1538:
--
Status: Patch Available (was: Open)
Failing client side validation with some date
[
https://issues.apache.org/jira/browse/TRINIDAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737766#action_12737766
]
Cale Scholl commented on TRINIDAD-1538:
---
Code change in DateFormat.js _subparse
[
https://issues.apache.org/jira/browse/TRINIDAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737812#action_12737812
]
Cale Scholl commented on TRINIDAD-1538:
---
Code review changes:
var isStrict
: Cale Scholl
Grouping regression caused by:
https://issues.apache.org/jira/browse/TRINIDAD-1534
The fix is to replace this:
balance = ints.substring(0, toMuch) + groupingSeparator;
with this:
balance = (counter 4) ? ints.substring(0, toMuch) : ints.substring(0,
toMuch) + groupingSeparator
[
https://issues.apache.org/jira/browse/TRINIDAD-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1539:
--
Status: Patch Available (was: Open)
grouping and parsing regressions in convertNumber
[
https://issues.apache.org/jira/browse/TRINIDAD-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1537:
--
Status: Patch Available (was: Open)
client convertNumber truncates invalid number instead
Issue Type: Bug
Reporter: Cale Scholl
Set browser locale to locale in which grouping-separator is space, like fr_FR.
For the fr_FR case, enter 1 233 456 €, client side converter truncates it
into 1. Same issue for %.
--
This message is automatically generated by JIRA.
-
You can
[
https://issues.apache.org/jira/browse/TRINIDAD-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1536:
--
Status: Patch Available (was: Open)
client convertnumber truncates number when
Trinidad
Issue Type: Bug
Reporter: Cale Scholl
On the client, 123abc45 is truncated to 123, whereas it should throw an
exception; the server throws an exception
The reason that 123abc45 is truncated to 123 is due to a native js function:
parseFloat(123abc45) returns 123
[
https://issues.apache.org/jira/browse/TRINIDAD-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733428#action_12733428
]
Cale Scholl commented on TRINIDAD-1537:
---
Currently cannot provide patch due
[
https://issues.apache.org/jira/browse/TRINIDAD-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1421:
--
Status: Patch Available (was: Open)
incorrect convertNumber behavior when integerOnly
incorrect grouping shown by convertnumber
-
Key: TRINIDAD-1534
URL: https://issues.apache.org/jira/browse/TRINIDAD-1534
Project: MyFaces Trinidad
Issue Type: Bug
Reporter: Cale Scholl
[
https://issues.apache.org/jira/browse/TRINIDAD-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1534:
--
Status: Patch Available (was: Open)
incorrect grouping shown by convertnumber
Works for me on Windows XP x84.
C:\jdevrt\trinidad\trunk_testwhich mvn
/cygdrive/c/program files/apache/maven/maven-2.0.7/bin/mvn
C:\jdevrt\trinidad\trunk_testecho %JAVA_HOME%
C:\java\jdk\jdk1.5.0_17
C:\jdevrt\trinidad\trunk_testmvn clean install
builds successfully
-Cale
Andrew Robinson
Components: Components
Affects Versions: 1.2.11-core
Reporter: Cale Scholl
Attachments: 1.2.11.1-branch_currencySign.patch,
trunk_currencySign.patch
This is concerning the implementation of getLocalizedPattern provided with the
fix for:
https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/TRINIDAD-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1413:
--
Status: Patch Available (was: Open)
getLocalizedPattern displays currency sign in Linux
Hi,
When doing a mvn clean install on Trinidad trunk (formerly trunk
1.2.x) I get the following error:
[INFO]
[INFO] Building Apache MyFaces Trinidad Blank Demo
[INFO]task-segment: [clean, install]
[INFO]
Issue Type: Bug
Affects Versions: 1.0.10-core, 1.2.10-core
Reporter: Cale Scholl
Priority: Minor
When a page contains Trinidad components, h:form will be overridden (rendered
with Trinidad HtmlFormRenderer). If there are any changes in how we override
the h:form
[
https://issues.apache.org/jira/browse/TRINIDAD-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668616#action_12668616
]
Cale Scholl commented on TRINIDAD-1374:
---
According to the comments in
trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1374:
--
Status: Patch Available (was: Open)
NumberConverter with type='number' and pattern set
Components: Components
Affects Versions: 1.0.10-core, 1.2.10-core
Reporter: Cale Scholl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/TRINIDAD-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1380:
--
Status: Patch Available (was: Open)
convertNumber should support 'locale' attribute
Components: Components, Plugins
Affects Versions: 1.0.10-core, 1.2.10-core, 1.2.8-plugins
Reporter: Cale Scholl
Priority: Minor
TrNumberFormat.prototype.percentageToString() just appends the '%' symbol. The
is wrong for the fr_FR locale, since the percent suffix
[
https://issues.apache.org/jira/browse/TRINIDAD-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1366:
--
Status: Patch Available (was: Open)
client percent convertnumber not work well in fr_fr
Type: Bug
Components: Components
Affects Versions: 1.0.10-core, 1.2.10-core
Reporter: Cale Scholl
Regression caused by https://issues.apache.org/jira/browse/TRINIDAD-1344
convertDateTime with secondaryPattern attribute means in
TrDateTimeConverter.prototype
[
https://issues.apache.org/jira/browse/TRINIDAD-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1361:
--
Status: Patch Available (was: Open)
js error when use convertDateTime
Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.0.10-core, 1.2.10-core
Reporter: Cale Scholl
The provided 1.2.10.1_convPatterns.patch fixes multiple issues with
convertDateTime's handling of convenience patterns; convenience patterns
[
https://issues.apache.org/jira/browse/TRINIDAD-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1344:
--
Status: Patch Available (was: Open)
fixed multiple issues with convertDateTime's handling
Components: Components
Affects Versions: 1.0.10-core, 1.2.10-core
Reporter: Cale Scholl
When using convertNumber with type=percent or type=currency, the user
shouldn't be forced to enter the % or currency symbols. If not specified, the
symbols should default to those specified
[
https://issues.apache.org/jira/browse/TRINIDAD-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1338:
--
Status: Patch Available (was: Open)
Users shouldn't be forced to enter % or currency
[
https://issues.apache.org/jira/browse/TRINIDAD-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl reopened TRINIDAD-1231:
---
There is a small error that needs attention. IE7 doesn't support the javascript
syntax
://issues.apache.org/jira/browse/TRINIDAD-1231
Thank you,
Cale
Original Message
Subject: [Trinidad] Resolving differences between client-side and
server-side message formatter?
Date: Thu, 30 Oct 2008 10:50:16 -0700
From: Cale Scholl [EMAIL PROTECTED]
Reply-To: MyFaces Development
Hello,
I'm pretty new to the Trinidad community, so let me apologize in advance
if there's something I've misunderstood.
What I'd like to talk about are the differences between the client-side
message formatter:
trinidad-impl\src\main\javascript\META-INF\adf\jsLibs\Core.js -
function
Versions: 1.2.9-core
Reporter: Cale Scholl
Priority: Minor
Attachments: trunk12_noDash.patch
When the label is null, the error message printed at the top of the screen will
be something like - Invalid data. The - looks unsightly without any text
preceding it, so we
[
https://issues.apache.org/jira/browse/TRINIDAD-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cale Scholl updated TRINIDAD-1278:
--
Status: Patch Available (was: Open)
Don't display - in error message when label is null
Type: Bug
Components: Components
Affects Versions: 1.2.9-core, 1.0.9-core
Reporter: Cale Scholl
Priority: Minor
Whenever a validator has an attribute hintXYZ or messageDetailXYZ that allows
for a custom string, we should escape that string whenever we write
54 matches
Mail list logo
