[jira] [Closed] (TAP5-1658) Submit context does not work inside Grid

2014-06-01 Thread Jochen Kemnade (JIRA)

 [ 
https://issues.apache.org/jira/browse/TAP5-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jochen Kemnade closed TAP5-1658.


   Resolution: Fixed
Fix Version/s: 5.4

 Submit context does not work inside Grid
 

 Key: TAP5-1658
 URL: https://issues.apache.org/jira/browse/TAP5-1658
 Project: Tapestry 5
  Issue Type: Bug
  Components: tapestry-core
Affects Versions: 5.3.7, 5.4, 5.2
Reporter: Stephan Windmüller
Assignee: Jochen Kemnade
 Fix For: 5.4

 Attachments: TestGrid.tar.gz


 About a year ago, bug #TAP-5-869 was about the usage of submit buttons with 
 context in loops. The bug was closed because using the defer parameter of the 
 submit button fixed the problem.
 Now I have the same problem, but this time in a Grid rather than a loop 
 component. Defer is set to false but every time I click on a button, only the 
 context of the last one is used.
 I created a small example demonstrating the problem, I will attach it to this 
 bugreport. Try clicking on every user and watch the console output: Always 
 the last user is printed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[CONF] Apache Tapestry Localization

2014-06-01 Thread Bob Harner (Confluence)














  


Bob Harner edited the page:
 


Localization   




 Comment: Added Slovenian to the list of supported locales 


...




 en (English) 
  el (Greek)  
  it (Italian)  
  pl (Polish)  
  vi sv (VietnameseSwedish)  


 bg (Bulgarian) 
  es (Spanish)  
  ja (Japanese)  
  pt (Portuguese)  
  zh vi (ChineseVietnamese)  


 cs (Czech)1  
  fi (Finnish)  
  mk (Macedonian)  
  ru (Russian)  
  zh (Chinese)  


  da (Danish)  
  fr (French)  
  nl (Dutch)sr   
sl (SerbianSlovenian)2
  


  de (German)  
  hr (Croatian)  
  no (Norwegian)  
  sv sr (SwedishSerbian)  
  




 1as of Tapestry 5.3.8 
 2 as of Tapestry 5.4 
Providing translations for Tapestry built-in messages
...






   

[jira] [Updated] (TAP5-1381) Page lifecycle documentation: What is called and when

2014-06-01 Thread Bob Harner (JIRA)

 [ 
https://issues.apache.org/jira/browse/TAP5-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bob Harner updated TAP5-1381:
-

Affects Version/s: 5.4

 Page lifecycle documentation: What is called and when
 -

 Key: TAP5-1381
 URL: https://issues.apache.org/jira/browse/TAP5-1381
 Project: Tapestry 5
  Issue Type: Improvement
  Components: documentation
Affects Versions: 5.4
Reporter: Borut Bolcina

 At http://tapestry.apache.org/page-life-cycle.html the documentation about 
 page lifecycle can be improved. It should be more clear to developers what is 
 called and when. Maybe a diagram and short explanations along with good 
 practices what to put in each event method would be in order.
 Geoff has made a good effort at 
 http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen
  and the logging of log4j.category.tapestry.events.com.acme.pages=debug can 
 give clues, but I think the lifecycle is so crucial it should be explained in 
 more detail.
 Also, the link in the sentence As with component rendering, you have the 
 ability to make your components aware of these events by identifying 
 methods to be invoked. is broken.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


svn commit: r910829 - in /websites/production/tapestry/content: cache/main.pageCache localization.html

2014-06-01 Thread buildbot
Author: buildbot
Date: Mon Jun  2 02:19:36 2014
New Revision: 910829

Log:
Production update by buildbot for tapestry

Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/localization.html

Modified: websites/production/tapestry/content/cache/main.pageCache
==
Binary files - no diff available.

Modified: websites/production/tapestry/content/localization.html
==
--- websites/production/tapestry/content/localization.html (original)
+++ websites/production/tapestry/content/localization.html Mon Jun  2 02:19:36 
2014
@@ -166,7 +166,7 @@ public String getDisplayLanguage() {
 return persistentLocale.get().getDisplayLanguage();
 }
 ]]/script
-/div/divpOnce a persistent locale is set, you will see the locale name 
as the first virtual folder in page render and component event requests URLs. 
In this way, a persistent locale will, in fact, persist from request to 
request, or in a user's bookmarks./ppYou will see the new locale take 
effect on the next request. If it is changed in a component event request 
(which is typical), the new locale will be used in the subsequent page render 
request./ppNote that the locale for a page is fixed (it can't change once 
the page instance is created). In addition, a page may only be attached to a 
request once. In other words, if code in your page changes the persistent 
locale, you won't see a change to the page's locale (or localized messages) 
emin that request/em./ph2 id=Localization-Built-inLocalesBuilt-in 
Locales/h2pWhile your application can support any locale (and thus any 
language) that you want, Tapestry provides only a limited set of translations 
for its ow
 n built-in messages. As of Tapestry 5.3, the following locales have 
translations provided:/pdiv class=table-wraptable 
class=confluenceTabletbodytrtd colspan=1 rowspan=1 
class=confluenceTdpen (English)/p/tdtd colspan=1 rowspan=1 
class=confluenceTdpspanel (Greek)/span/p/tdtd colspan=1 
rowspan=1 class=confluenceTdpspanit (Italian)/span/p/tdtd 
colspan=1 rowspan=1 class=confluenceTdpspanpl 
(Polish)/span/p/tdtd colspan=1 rowspan=1 
class=confluenceTdpspanvi (Vietnamese)/span/p/td/trtrtd 
colspan=1 rowspan=1 class=confluenceTdpbg (Bulgarian)/p/tdtd 
colspan=1 rowspan=1 class=confluenceTdpspanes 
(Spanish)/span/p/tdtd colspan=1 rowspan=1 
class=confluenceTdpspanja (Japanese)/span/p/tdtd colspan=1 
rowspan=1 class=confluenceTdpspanpt (Portuguese)/span/p/tdtd 
colspan=1 rowspan=1 class=confluenceTdpspanzh (Chinese)/sp
 an/p/td/trtrtd colspan=1 rowspan=1 class=confluenceTdpcs 
(Czech)sup1/sup/p/tdtd colspan=1 rowspan=1 
class=confluenceTdpspanfi (Finnish)/span/p/tdtd colspan=1 
rowspan=1 class=confluenceTdpspanmk (Macedonian)/span/p/tdtd 
colspan=1 rowspan=1 class=confluenceTdpspanru 
(Russian)/span/p/tdtd colspan=1 rowspan=1 
class=confluenceTdp#160;/p/td/trtrtd colspan=1 rowspan=1 
class=confluenceTdpspanda (Danish)/span/p/tdtd colspan=1 
rowspan=1 class=confluenceTdpspanfr (French)/span/p/tdtd 
colspan=1 rowspan=1 class=confluenceTdpspannl 
(Dutch)/span/p/tdtd colspan=1 rowspan=1 
class=confluenceTdpspansr (Serbian)/span/p/tdtd colspan=1 
rowspan=1 class=confluenceTdp#160;/p/td/trtrtd colspan=1 
rowspan=1 class=confluenceTdpspande (German)/span/p/tdtd 
colspan=1 rowspan=1 class=confluenceTdpsp
 anhr (Croatian)/span/p/tdtd colspan=1 rowspan=1 
class=confluenceTdpspanno (Norwegian)/span/p/tdtd colspan=1 
rowspan=1 class=confluenceTdpspansv (Swedish)/span/p/tdtd 
colspan=1 rowspan=1 
class=confluenceTdp#160;/p/td/tr/tbody/table/divpsup1#160;/supspan
 style=line-height: 1.4285715;as of Tapestry 5.3.8/span/ph3 
id=Localization-ProvidingtranslationsforTapestrybuilt-inmessagesProviding 
translations for Tapestry built-in messages/h3pFortunately, Tapestry uses 
all the same mechanisms for its own locale support as it provides for your 
application. So, to support other locales, just translate the built-in message 
catalog (property) files yourself:/pp#160;/pstyle 
type=text/csstable.sectionMacro { width: auto; }/style
+/div/divpOnce a persistent locale is set, you will see the locale name 
as the first virtual folder in page render and component event requests URLs. 
In this way, a persistent locale will, in fact, persist from request to 
request, or in a user's bookmarks./ppYou will see the new locale take 
effect on the next request. If it is changed in a component event request 
(which is typical), the new locale will be used in the subsequent page render 
request./ppNote that the locale for a page is fixed (it can't change once 
the page instance is created). In addition, a page may only be attached to a 
request once. In other words, if code in your page changes the persistent 
locale, you won't see a change to the page's locale (or localized messages) 
emin that request/em./ph2