I think it's been "kibosh"-ed now ...
Sometimes I wish Hani was on ~all~ (vs one) the dev lists I subscribe
to. It certainly would keep things nice and brief.
On 2/17/07, Ryan Holmes <[EMAIL PROTECTED]> wrote:
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consult
On Feb 16, 2007, at 8:32 PM, Kent Tong wrote:
So, what you're really saying is that people are going to prefer
option A:
...
${propertyName}
${propertyValue}
...
with
[
https://issues.apache.org/jira/browse/TAPESTRY-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert closed TAPESTRY-399.
--
Resolution: Invalid
Assignee: Jesse Kuhnert
You can change the locale quite easily by s
[
https://issues.apache.org/jira/browse/TAPESTRY-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-353:
---
Fix Version/s: (was: 4.1.2)
4.2
> Validator API for easy re-validati
[
https://issues.apache.org/jira/browse/TAPESTRY-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473945
]
Jesse Kuhnert commented on TAPESTRY-396:
I'd be interested in hearing more about the signature you'd need f
[
https://issues.apache.org/jira/browse/TAPESTRY-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-220:
---
Fix Version/s: (was: 4.1.2)
4.2
> InsertText should accept java.io.R
[
https://issues.apache.org/jira/browse/TAPESTRY-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-266:
---
Fix Version/s: (was: 4.1.2)
4.2
> Include (JVM) default locale in lo
[
https://issues.apache.org/jira/browse/TAPESTRY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-312:
---
Fix Version/s: (was: 4.1.2)
4.2
> lifecycle of session
> --
Howard Lewis Ship: -1
I really appreciate the work Kent has done with the type safe option,
as well as the unit testing work. I strongly feel that the type safe
approach loses more than it gains, as we've discussed in the relevant
threads. I think making sure Tapestry works with Groovy and JRuby
Select component requires a "value" binding even after an "id" binding has been
specified
-
Key: TAPESTRY-1277
URL: https://issues.apache.org/jira/browse/TAPESTRY-1277
This is a vote on whether or not we want anything in the type safe
refactoring branch to move forward within the confines of the Tapestry
project. It's not a discussion for or against the various aspects of
the arguments - there are obviously plenty of threads dealing with
that.
The only reason I
11 matches
Mail list logo