Hi Gavin,
if you are stuck with supporting Live Class Reloading, please go ahead with
other features, such as issue 10. Maybe we could concentrate on Live Class
Reloading after GSOC deadline.
Thank you.
2011/8/13 Gavin Lei gavingui2...@gmail.com
Hi Igor,
In the schedule, we should focus on
Implementing it as a mixin has few disadvantages, first of all the change event
of the Select component always sets it's component value, generic mixin can't
do that, I don't think it would be a good idea to have different behavior in
the other form fields.
Next thing is that RadioGroup will
On Sun, 14 Aug 2011 23:22:37 -0300, TG tapestry...@hotmail.com wrote:
Any one know how to resolve this issue?
This should be posted in the Tapestry users list, not the dev one, which
is about Tapestry itself, not using it.
location
On Sat, 13 Aug 2011 01:39:36 -0300, Robert Zeigler
robert.zeig...@roxanemy.com wrote:
I disagree with your assessment of mixins. Mixins are primarily tied to
the component lifecycle, not to specific component implementations.
There are certainly some mixins that can't be universally
The zone parameter is easy to use but not very flexible. I wrote a
bind mixin for jQuery that hooks events to pretty much anything. I
suspect you could do the same thing in Prototype. Bind is subclassed
to the event you want to capture so multiple events can be attached to
a single element. Here
It would be better to have core components more flexible to external changes.
I'm looking into ContextMenuGridCell and I would rather see extended
PropertyOverrides and extension points concept.
For example a Grid would provide default extending point for a row:
tr t:point=loopRow
then
On Thu, 11 Aug 2011 11:19:16 -0300, Shiva ksshan...@rediffmail.com wrote:
What are the implications of setting volatile=true. I am using
Tapestry5. I saw in some of the threads suggesting me not to change this
value. But I am unclear whats the role of volatile. Googled a lot.
Perhaps I am
Ok, i am working for the issue 10 now :-)
在 2011年8月15日 下午2:52，Igor Drobiazko igor.drobia...@gmail.com 写道：
Hi Gavin,
if you are stuck with supporting Live Class Reloading, please go ahead with
other features, such as issue 10. Maybe we could concentrate on Live Class
Reloading after GSOC
Actually, I'd rather ensure that it's easier to re-use the Grid
component's constituent parts in new forms than to try and make Grid
all things to all people. Grid is (supposed to be) scaffolding, like
BeanEditForm, but too often, people make it a major part of the
application, and then are
Hi, in tapestry.js, in the $T function i see:
@deprecated With no specific replacement. To be removed after Tapestry 5.2.
Since that is used in quite a few other places in tapestry.js and also in
autocompleter.js and zone-refresh.js i'm wondering what needs to be
done there...
Is it the
Hi,
On Mon, Aug 15, 2011 at 2:11 PM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
On Sat, 13 Aug 2011 01:39:36 -0300, Robert Zeigler
robert.zeig...@roxanemy.com wrote:
I disagree with your assessment of mixins. Mixins are primarily tied to
the component lifecycle, not to
Looks nice!
On Mon, Aug 15, 2011 at 12:07 AM, Igor Drobiazko (JIRA) j...@apache.org wrote:
[
https://issues.apache.org/jira/browse/TAP5-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Drobiazko reassigned TAP5-1610:
I've just backed out commit d8bf4fe19331faa3eaddc4a3f6a9d48827a7a590
which added the EmbeddedMixin annotation support.
Sorry, Dragan!
On Mon, Aug 15, 2011 at 11:06 AM, dragan.sahpas...@gmail.com
dragan.sahpas...@gmail.com wrote:
Hi,
On Mon, Aug 15, 2011 at 2:11 PM, Thiago H. de Paula
On Mon, Aug 15, 2011 at 6:59 PM, Howard Lewis Ship hls...@gmail.com wrote:
Actually, I'd rather ensure that it's easier to re-use the Grid
component's constituent parts in new forms than to try and make Grid
all things to all people. Grid is (supposed to be) scaffolding, like
BeanEditForm,
On Mon, Aug 15, 2011 at 8:13 PM, Howard Lewis Ship hls...@gmail.com wrote:
I've just backed out commit d8bf4fe19331faa3eaddc4a3f6a9d48827a7a590
which added the EmbeddedMixin annotation support.
Sorry, Dragan!
Nothing to be sorry about. I got pretty useful comments.
Cheers,
Dragan Sahpaski
Is there a way to upload the javadocs using Gradle?
On Mon, Aug 15, 2011 at 8:11 PM, Howard Lewis Ship hls...@gmail.com wrote:
Looks nice!
On Mon, Aug 15, 2011 at 12:07 AM, Igor Drobiazko (JIRA) j...@apache.org
wrote:
[
Thanks again for Robin for doing all the work, and pointing me towards
Sticker Mule.
I used StickerMule for the stickers ... I like them and will probably
use them again. The 2 x 4 sticker is a decent size, though it's one
of the smaller ones on my laptop.
http://www.stickermule.com/
I've
I've been thinking about this as well.
I want to experiment with an approach that does the following:
html
head
script src=/require.js/
/head
body
script src=ajax-protection.js/
...
script
// Use require.js to load everthing else
/script
/html
The ajax-protection
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Tapestry Wiki for
change notification.
The BeanForm page has been changed by newacct:
http://wiki.apache.org/tapestry/BeanForm?action=diffrev1=22rev2=23
Map components = this.getPage().getComponents();
Mostly, I've been changing code to use CSS classes to store this kind
of information, so as not to pollute the DOM.
On Mon, Aug 15, 2011 at 11:02 AM, Andreas Andreou andre...@gmail.com wrote:
Hi, in tapestry.js, in the $T function i see:
@deprecated With no specific replacement. To be removed
Ok - interesting idea, i like it.
Notice though that with the change i'm proposing to
ClientBehaviorSupport it can also be implemented right there,
i.e. ClientBehaviorSupport.addWaitForPage(Element) will be changed
to include ajax-protection.js
On Mon, Aug 15, 2011 at 23:39, Howard Lewis Ship
On Mon, Aug 15, 2011 at 3:08 PM, Andreas Andreou andre...@gmail.com wrote:
Ok - interesting idea, i like it.
Notice though that with the change i'm proposing to
ClientBehaviorSupport it can also be implemented right there,
i.e. ClientBehaviorSupport.addWaitForPage(Element) will be changed
to
Sure, if it's going to always be applied, then there's no need doing
anything specific in AbstractComponentEventLink#beginRender
or Form#beginRender() - and thus no need to extract common code
into ClientBehaviorSupport.
On Tue, Aug 16, 2011 at 01:20, Howard Lewis Ship hls...@gmail.com wrote:
On
On Mon, Aug 15, 2011 at 3:59 PM, Andreas Andreou andre...@gmail.com wrote:
Sure, if it's going to always be applied, then there's no need doing
anything specific in AbstractComponentEventLink#beginRender
or Form#beginRender() - and thus no need to extract common code
into
See https://builds.apache.org/job/tapestry-trunk-freestyle/486/changes
Changes:
[hlship] Roll version number up to 5.3-alpha-14
[hlship] TAP5-1308: Only display the pop-up exception report dialog if the
response content was text/html
[hlship] TAP5-1308: Tweak the layout and adjust it to
25 matches
Mail list logo
