[jira] [Commented] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809450#comment-13809450 ] Lenny Primak commented on TAP5-2211: That would be wonderful, and will take pressure off this issue for me. Maybe we can do both, fix the "old" datepicker and get this issue fixed a bit later, perhaps based on experience that we have with your project (thanks!) > Replace DatePicker with Bootstrap or JQueryUI DatePicker > > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809443#comment-13809443 ] Barry Books commented on TAP5-2211: --- I was going to use this one instead of jQuery but it was not done yet. I'll try and create a mixin with it and add it to my datepicker probject > Replace DatePicker with Bootstrap or JQueryUI DatePicker > > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TAP5-2211) Replace DatePicker with Bootstrap or JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated TAP5-2211: --- Summary: Replace DatePicker with Bootstrap or JQueryUI DatePicker (was: Replace DatePicker with JQueryUI DatePicker) > Replace DatePicker with Bootstrap or JQueryUI DatePicker > > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809425#comment-13809425 ] Lenny Primak commented on TAP5-2211: Barry, this is it! This date picker does what it needs to do: - it works well - doesn't add much after-the-fact via JavaScript - has lots of options, easy to configure - works in form-horizontal (which JQueryDatepicker doesn't) I think you've stumbled on a gold mine here > Replace DatePicker with JQueryUI DatePicker > --- > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809306#comment-13809306 ] Barry Books commented on TAP5-2211: --- I would keep an eye on this project http://angular-ui.github.io/bootstrap/ > Replace DatePicker with JQueryUI DatePicker > --- > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809268#comment-13809268 ] Lenny Primak commented on TAP5-2211: I just found a good one: https://issues.apache.org/jira/browse/TAP5-1845 If you look at the last comment, even Howard says that we should move to JQuery datepicker. Yes, some bugs mentioned above are closed, but they have clones / related ones that are not. I don't think any of these are indeed completely fixed in T5.4 There are lots of individual issues here, but they are all trivial to fix though. Anyway, I am willing to start by fixing all little bugs mentioned with the existing datefield, and then think about moving to the JQuery one. In the FlowLogix library, I have patches that fix all the issues for T5.3, but with T5.4 the patches no longer work, plus some of the bugs mentioned above are regressions from 5.3 http://code.google.com/p/flowlogix/wiki/TLCalendarPopupPatch > Replace DatePicker with JQueryUI DatePicker > --- > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TAP5-2211) Replace DatePicker with JQueryUI DatePicker
[ https://issues.apache.org/jira/browse/TAP5-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808988#comment-13808988 ] Thiago H. de Paula Figueiredo commented on TAP5-2211: - Hi, Lenny! Tapestry-JQuery datafield is a good component, but that's very different from saying that it is a good replacement for Tapestry's DateField because it would break backward compatibility in the worst way possible: only in runtime. TAP5-1845, TAP5-1998 and TAP5-2144 (which isn't actually related to DateField JS, but server-side) look easy to fix. TAP5-2203 and TAP-2003 will need a little more effort. TAP5-805 is probably fixed in 5.4 due to the way the validation works now. TAP5-2173 is a duplicate of TAP5-1998. TAP5-1799 seems already fixed in 5.4. The localization one described by Lenny in the comment above doesn't look hard to fix at first. I have no objections against having a JQueryDateField component in Tapestry out-of-the-box. What I object would be it replacing the current DateField component due to reasons I've already wrote here. > Replace DatePicker with JQueryUI DatePicker > --- > > Key: TAP5-2211 > URL: https://issues.apache.org/jira/browse/TAP5-2211 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Lenny Primak >Assignee: Thiago H. de Paula Figueiredo > Labels: datefield, datepicker > > The current 3rd party datepicker used by Tapestry is very old, > and isn't very good. It's time to update it to one of > the better currently-available datepickers. > There are about 15 unresolved issues opened against Datepicker that can all > be solved by just replacing it. > I suggest JQueryUI datepicker (if JQuery is included as the default stack) > The current datepicker can be left alone is prototype is chosen. > By default, JQueryUI datepicker should be used with the button-to-activate > option so that it looks similar to the current datepicker. > It should also work properly in BeanEditor and friends and even look good > with form-horizontal version of BeanEditor > -- This message was sent by Atlassian JIRA (v6.1#6144)
svn commit: r884801 - in /websites/production/tapestry/content: cache/main.pageCache community.html
Author: buildbot Date: Wed Oct 30 11:20:40 2013 New Revision: 884801 Log: Production update by buildbot for tapestry Modified: websites/production/tapestry/content/cache/main.pageCache websites/production/tapestry/content/community.html Modified: websites/production/tapestry/content/cache/main.pageCache == Binary files - no diff available. Modified: websites/production/tapestry/content/community.html == --- websites/production/tapestry/content/community.html (original) +++ websites/production/tapestry/content/community.html Wed Oct 30 11:20:40 2013 @@ -192,6 +192,10 @@ IDE Integrations +https://github.com/anjlab/eclipse-tapestry5-plugin"; >Eclipse-tapestry5-plugin + +An Eclipse plugin for Tapestry 5 by Dmitry Gusev, with a "Quick Switch" between templates and component classes, a Tapestry Context view, and many other convenience features. + http://code.google.com/p/tapestrytools/wiki/Install_Guide_Lightweight_TapestryTools"; >Tapestry Tools by Gavin Lei Tapestry Tools is an Eclipse plugin for Tapestry 5 which has been built by Gavin Lei within the timeframe of GSoC 2012. This is currently the best choice for Eclipse users.
[jira] [Resolved] (TAP5-2173) Tapestry DateField converts invalid dates to valid ones.
[ https://issues.apache.org/jira/browse/TAP5-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago H. de Paula Figueiredo resolved TAP5-2173. - Resolution: Duplicate Duplicate of TAP5-1998. > Tapestry DateField converts invalid dates to valid ones. > > > Key: TAP5-2173 > URL: https://issues.apache.org/jira/browse/TAP5-2173 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.4 >Reporter: Barry Books > > The combination of the DateField component and the conversion of strings to > SimpleDateFormat result in the DateField converting invalid dates to valid > ones. There are really two problems. The default for SimpleDateFormat is > lenient so strings are converted with lenient set to true. This causes the > date conversion to changes dates like 9/32/2013 to Wed Oct 02 00:00:00 CDT > 2013. The second problem is DateField allows extra characters after the valid > part of the date. For example 9/01/2013 converts to Sun Sep 01 00:00:00 > CDT 2013. This is more of a problem with formats such as -MM-dd because a > date such as 2013-09-061 is allowed and converted to Thu Oct 31 00:00:00 CDT > 2013. -- This message was sent by Atlassian JIRA (v6.1#6144)
[CONF] Apache Tapestry > Community
Community
Page edited by Bob Harner
Comment:
Added link to "Eclipse Integration for Tapestry 5"
Changes (1)
...
h1. IDE Integrations
[Eclipse-tapestry5-plugin|https://github.com/anjlab/eclipse-tapestry5-plugin] {quote} An Eclipse plugin for Tapestry 5 by Dmitry Gusev, with a "Quick Switch" between templates and component classes, a Tapestry Context view, and many other convenience features. {quote}
[Tapestry Tools|http://code.google.com/p/tapestrytools/wiki/Install_Guide_Lightweight_TapestryTools] by Gavin Lei {quote}
...
Full Content
Tapestry has an active community of users and developers. This is an overview of how to participate, along with a list of some of the great contributions of the community members.
Getting Involved
Reporting Problems / Getting Support
Contributing translations for Tapestry built-in messages
Source Code Access
Becoming a Contributor
Becoming a Committer
Community Contributions
Modules
Extensions
Tutorials
IDE Integrations
Getting Involved
Reporting Problems / Getting Support
Like all Apache projects, Tapestry uses mailing lists for most communication. You can subscribe by sending e-mail to the addresses below. For each list, there are subscribe, unsubscribe, and archive links. All Tapestry users are welcome to subscribe to any of these lists, however questions on how to use Tapestry in your application are best sent to the user mailing list.
Please note that the Nabble archives are set to read-only and don't allow for posting or answering using Nabble's web interface. You have to subscribe to the mailing list in order to post.
Subscribe
Unsubscribe
Apache Archive
Nabble Archive
MarkMail Archive
Tapestry User List
Subscribe
Unsubscribe
mail-archives.apache.org
www.nabble.com
tapestry.markmail.org
Tapestry Developer List
Subscribe
Unsubscribe
mail-archives.apache.org
www.nabble.com
tapestry.markmail.org
Tapestry Commits List
Subscribe
Unsubscribe
mail-archives.apache.org
-
tapestry.markmail.org
Search Multiple Lists
-
-
-
www.nabble.com
tapestry.markmail.org
Tapestry issues are tracked in the Apache JIRA.
Unless your problem is clear as day, it's a good idea to discuss it on the Tapestry Users mailing list first, before adding an issue. At the same time, it's generally unlikely that a bug will be fixed unless a JIRA Issue is created.
Eric Raymond has a detailed guide to asking questions the right way. If you are not getting a response to your problem, it's likely because you aren't asking it the right way.
Just saying something is "broken" or "failed" is not enough. How did it fail? Did it do the wrong thing? Throw an exception? Not respond in any way? What exactly did you expect to happen? All of this information should be made available when looking for help, plus context on the general problem you were trying to solve in the first place (there may be a better solution entirely). Read Eric Raymond's guide ... it's fun and informative.
Contributing translations for Tapestry built-in messages
If Tapestry's built-in messages aren't available in your language, you are welcome to contribute a new translation of the message catalogs. For easy instructions, see Localization.
Source Code Access
Source code for Tapestry can be downloaded along with pre-compiled binaries.
Tapestry uses Git to manage the project's source code.
Web access to the Tapestry repository is available as GIT-WIP at Apache.
Access using Git client:
$ git clone http://git-wip-us.apache.org/repos/asf/tapestry-5.git
(See Building Tapestry from Source for more info.)
Becoming a Contributor
The best way to become a contributor is to become active on the mailing list; Tapestry is known to have an active and helpful community on the mailing list, and the more mentors we can add, the better.
If you want to help out with documentation, you must sign an Apache Contributor License Agreement, at which point we can grant write access to the Confluence Wiki (where official documentation is created).
Providing patches (with tests!) is another way to become a contributor.
Becoming a Committer
Active contributors may be asked to become full committers, with write access to the source code. Generally, contributors who have been consistently active and helpful for three to six months are eligible for committer access. If you think you are in that category, don't be shy about contacting members of the Tapestry PMC (Project Management Committee).
Community Contributions
Modules
Chenille Kit by Massimo Lusetti
Collection of modules, services, utilities and compone
[jira] [Updated] (TAP5-2213) divergent PropertyModelImpl and BeanModelSourceImpl
[
https://issues.apache.org/jira/browse/TAP5-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Rosenberger updated TAP5-2213:
---
Priority: Minor (was: Major)
> divergent PropertyModelImpl and BeanModelSourceImpl
> ---
>
> Key: TAP5-2213
> URL: https://issues.apache.org/jira/browse/TAP5-2213
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.3.3
>Reporter: Benjamin Rosenberger
>Priority: Minor
>
> Given:
> * I create a bean model for an object
> * i add a property with model.add("field",
> AbstractPropertyConduit()) with some logic in the getValue() method
> * i have contributed a view block for DataType in the ioc module (with
> contributeDefaultDataTypeAnalyzer)
> When:
> * i go to the page where the beanmodel is used
> Result:
> * the view block is not used, but the default toString method of DataType
> Expected
> * the view block is used
> Problem description:
> The PropertyModelImpl does not set the datatype in the constructor (which is
> called in the BeanModelImpl.add-method). On the other hand if i do not need
> any logic for getting the property the field is automatically added by the
> BeanModelSourceImpl.createDisplayModel() method (calling the create method
> and setting the datatype after adding the property to the model).
> Possible workaround:
> Setting the datatype to the type of the PropertyConduit to ensure the same
> behavior as the BeanModelSourceImpl
> Suggested Solution:
> add setting the datatype in the PropertyModelImpl to the one of the given
> PropertyConduit or null depending if the dataTypeAnalyzer do know the type)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (TAP5-2213) divergent PropertyModelImpl and BeanModelSourceImpl
Benjamin Rosenberger created TAP5-2213:
--
Summary: divergent PropertyModelImpl and BeanModelSourceImpl
Key: TAP5-2213
URL: https://issues.apache.org/jira/browse/TAP5-2213
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.3.3
Reporter: Benjamin Rosenberger
Given:
* I create a bean model for an object
* i add a property with model.add("field", AbstractPropertyConduit())
with some logic in the getValue() method
* i have contributed a view block for DataType in the ioc module (with
contributeDefaultDataTypeAnalyzer)
When:
* i go to the page where the beanmodel is used
Result:
* the view block is not used, but the default toString method of DataType
Expected
* the view block is used
Problem description:
The PropertyModelImpl does not set the datatype in the constructor (which is
called in the BeanModelImpl.add-method). On the other hand if i do not need any
logic for getting the property the field is automatically added by the
BeanModelSourceImpl.createDisplayModel() method (calling the create method and
setting the datatype after adding the property to the model).
Possible workaround:
Setting the datatype to the type of the PropertyConduit to ensure the same
behavior as the BeanModelSourceImpl
Suggested Solution:
add setting the datatype in the PropertyModelImpl to the one of the given
PropertyConduit or null depending if the dataTypeAnalyzer do know the type)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
