great!!
thx!!
于 2012年08月24日 14:03, Joakim Olsson 写道:
Hi,
Just wanted to mention that I have released version 1.1 of my
autocomplete mixin that can populate multiple fields.
There was a problem with IE9 that was found and fixed by wbauer.
See more at https://github.com/argoyle/tapestry-mfautoc
thx
2012/9/5 Dragan Sahpaski [via Tapestry] <
ml-node+s1045711n5716070...@n5.nabble.com>
> Here it is
>
> http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/corelib/mixins/ZoneRefresh.html
>
> Regarding the tapestry documentation. I guess it's not documented yet.
> You should probably op
Possible bug T5.3.5
the toString() method of EventContext doesn't print well
@Log
private void persistCtx(EventContext ctx) {
log.debug("EventContext:{}",ctx);
log.debug("EventContext.class:{}",ctx.getClass());
_state = ctx.get(String.class, 0);
idPreg = ctx.g
On Wed, Sep 5, 2012 at 1:22 PM, Alex Kotchnev wrote:
> This is quite a pesky problem. I tried going w/ the Start page approach
> mentioned in
> https://issues.apache.org/jira/browse/TAP5-879?attachmentOrder=desc ;
> however, as it appears the approach w/ Start pages no longer works (and
> they're
This is quite a pesky problem. I tried going w/ the Start page approach
mentioned in
https://issues.apache.org/jira/browse/TAP5-879?attachmentOrder=desc ;
however, as it appears the approach w/ Start pages no longer works (and
they're deprecated anyway). It certainly is a surprise when the app nev
Here it is
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/corelib/mixins/ZoneRefresh.html
Regarding the tapestry documentation. I guess it's not documented yet.
You should probably open a JIRA for a documentation task regarding ZoneRefresh
Cheers,
Dragan Sahpaski
On Wed, Sep 5, 201
hello!
I was looking for an example of a periodic zone update function and found
this:
http://tawus.wordpress.com/2011/07/01/a-periodic-zone-refresh-mixin-for-tapestry/#comment-501
claiming that it is already part of the tapestry core but i did not find
something in the docs
http://tapestry.apac
I agree with you that this is difficult to override. It would be nice if
there was an overridable service to provide default formats instead of the
current hard-coded DateFormat.SHORT.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Global-setting-for-date-format-tp571605
That's what I was trying to avoid - find different solutions for each case.
Cause I might even just do ${myDateField} and I would expect it to be formatted
as I need.
Since the project is already deployed I don't want to go through each case and
occurrence to check if it is using valid format
> For example in beandisplay component
You will need to contribute a BeanBlockContribution to
BeanBlockOverrideSource. This will require you to create a page which
contains the block that you would like to use instead (the override).
eg:
MyPage.java
@Environmental
@Property
private Pro
You should be able to do this with a mixin but you cannot for the same reason
I'm having trouble with submitLabel in BeanEditForm.
see:
http://tapestry.1045711.n5.nabble.com/Can-t-change-BeanEditForm-submitLabel-with-a-mixin-td5716012.html
If the Parameter is defaulted to a readonly value you ca
For example in beandisplay component. Displaying all date fields for an object
in the same default date format.
Оригинално писмо
От: Lance Java lance.j...@googlemail.com
Относно: Re: Global setting for date format
До: users@tapestry.apache.org
Изпратено на: Сряда,
If you want to convert the existing autocomplete mixin take a look at any of
the providers in com.trsvax.bootstrap.services.bootstrapprovider. You need a
new one that uses a visitor to find the objects in the DOM and convert them
to what bootstrap wants. The FormProvider would be a good place to st
> Hi Lance,
Hi
> I was refering to DateField but I wanted the same thing applied everywhere
ComponentClassTransformWorker2 will do this
> even when I just output a text.
I don't understand this
I just want to be sure that someone did not forget to put a specific
attribute somwhere in the cod
Hi Lance,
I was refering to DateField but I wanted the same thing applied everywhere even
when I just output a text.
I just want to be sure that someone did not forget to put a specific attribute
somwhere in the code.
Оригинално писмо
От: Lance Java lance.j...@goog
This might help
http://tapestry.1045711.n5.nabble.com/form-for-nested-entity-td4264623.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Bean-editor-model-for-XYZ-does-not-contain-a-property-named-ZYX-tp5716057p5716058.html
Sent from the Tapestry - User mailing list ar
Hi all,
Although this is not a strange message, the circumstances under which it
happened are strange to me.
Tapestry reports an error when I try to include a non-java-type-object into
the grid.
All standard java types are shown correctly but a custom java type results
with the error.
This is a
Unfortunately, nabble seems to have removed your example so I can't see it.
I'm assuming that your post is related to DateField.
You could use a similar technique to taha's example [1] and add a custom
mixin to all DateField components using a ComponentClassTransformWorker2.
[1]
http://tawus.word
I can't see the usage example you are referring too. Have you tried using
the global *app.properties* file ? I reckon it's named after your module
name so if your module class is *MyAppModule.java*, your application
catalog filename should be *myapp.properties* (Case insensitive I think)
In that f
19 matches
Mail list logo
