Hi,
Im trying to figure out how to use the tapestry.widget.AlertDialog
widget which as far as I can tell seems to be the tapestry
implementation of the dojo Dialog widget. Will there be a tapestry
component for this later (like tacos:Dialog)?
This is the code Im trying to run but I only get
Hello all,
I've a problem with PopupLinkRenderer and it looks similar to the one Bastian
Voigt had with Script component [1/2].
Did I made right use of the PopupLinkRenderer? Just want to open a Tapestry or
simple HTML page. Is there another way? Any ideas of what is going wrong?
The Disclaimer
I think you need the @Body component in your .html.
Shing
--- Oliver Lietz [EMAIL PROTECTED] wrote:
Hello all,
I've a problem with PopupLinkRenderer and it looks
similar to the one Bastian
Voigt had with Script component [1/2].
Did I made right use of the PopupLinkRenderer? Just
want
Just one more thing on this subject.
Is is really a good ideia to set the default of the inherit-specification to
true?
Like you said Jesse...
...but I worry about what kind of unexpected behaviour would come about as
a result of
doing this. (for people relying on it ~not~ happening)
I'm
Am Montag, 28. August 2006 12:20 schrieb Shing Hing Man:
I think you need the @Body component in your .html.
Thanks Shing - adding @Body to body solved the problem.
Oliver
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Hi,
but how about a dynamically Ajax-rendered component? I have a tacos tree
with AjaxDirectLinks as leaves. By clicking on one of the links the refresh of
an Any component is triggered and displays further detailed information about
the leave.
In this details component a DirectLink with a
If I'm following Andy correctly, his point was that the JWC inheritance tree
can be different from the Java inheritance tree, so you don't want to try to
base one off of the other.
My real-world example is BeanForm, an enhanced Form component. I had to
copy/paste the parameters from Form.jwc in
I did this and it didn't work it seems that Tapestry still does not
send the html to the browser...
Is it expected that Tapestry will render everything before sending the
output to the browser?
Can somebody help me?
Rodnei Couto
Martin Strand escreveu:
Maybe Tapestry needs to render
i think the progressbar is part of the tacos components or am i wrong? so i
think you will get besser answers on their mailinglist:
https://lists.sourceforge.net/lists/listinfo/tacos-devel
greetings
stefan
Phillip Rhodes-2 wrote:
Forgive me, this is my first few hours with ajax/tacos...
On 8/28/06, Rodnei Couto [EMAIL PROTECTED] wrote:
I did this and it didn't work it seems that Tapestry still does not
send the html to the browser...
Is it expected that Tapestry will render everything before sending the
output to the browser?
This is quite strange... what do you have
I am currently evaluating a number of Portlet Development Frameworks.
Since I just got started with tapestry, I have a couple of questions
regarding the Portlet add-on of Tapestry 4.0. I am working with RAD 6.0
and WebSphere 5.x.
1. How do I have to configure Websphere server to run tapestry
According to the docs, calling document.formname.events.cancel()
should do whatever is necessary to disable client side validation and
call my cancel listener on the server. However, when I do this in IE,
I am getting an error about the 'events' object not existing.
JS error - events is null or
If you are using any of the submit kind of components you only need to set
the submitType parameter:
submitType=literal:cancel
I'm assuming you are working in 4.1 if this is the error you are getting.
There is also a rather exhaustive reference for the client side api wrt
forms here:
i would add the normal html script tag directly in the page...
You might also like to take a look at tacos:Gmap component:
http://opencomponentry.com:8080/tacos/tests/Maps.html
All its code is at
https://svn.sourceforge.net/svnroot/tacos/tacos-4.0/trunk/src/java/net/sf/tacos/components/maps/
It
Jesse Kuhnert wrote:
I'm assuming you are working in 4.1 if this is the error you are getting.
or tapestry 4.0 and tacos...
http://tacos.sourceforge.net/faq.html#faq-N10080
--
Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
On 8/28/06, andyhot [EMAIL PROTECTED] wrote:
Henri Dupre wrote:
On 8/28/06, Rodnei Couto [EMAIL PROTECTED] wrote:
I did this and it didn't work it seems that Tapestry still does not
send the html to the browser...
Is it expected that Tapestry will render everything before sending the
Hi
I'm writing my own engine service and I'm basing it on the Chart example in the
Workbench app that ships with the Tapestry distribution. The example uses a
line in ChartAsset.java that's deprecated in Tap 4:
_chartService = engine.getService(ChartService.SERVICE_NAME);
The service
I removed the @Body from the page and now the output seems to be working
fine. The report is being outputed onfly as each component is rendered.
I guess the problem was really the buffer in the tag Body.
Thanks,
Rodnei Couto
Henri Dupre escreveu:
On 8/28/06, andyhot [EMAIL PROTECTED]
Hi there --
I ran into a bug with Hidden and the way it assigns its id.
If I put @Hidden in a @For loop, the Hidden component keeps the supplied id as
the id for all the generated Hidden components. Hidden does not generate a
unique id each time through the loop like other input types do (for
Hi,
Palette Component - Selecting selected items
I need some help with getting a handle to selected items that are already in
the selected column.
For instance I have moved over 5 items and now I select 2 of those 5
selected items and by clicking a button I can get the index or the
Actually, I am on Tap 4.0.2 and it isn't an AjaxForm. Unless you are
saying that merely the existence of tacos causes the overloaded
behaviour, even on regular tapestry forms.
--sam
On 8/28/06, andyhot [EMAIL PROTECTED] wrote:
Jesse Kuhnert wrote:
I'm assuming you are working in 4.1 if this
Hi,
I seem to be running into some trouble with the DatePicker when using
a translator with hours, minutes, and AM/PM.
I originally had a standard TextField that used the following translator:
binding name=translator value=translator:date,pattern=/MM/dd
hh:mm aaa/
The dates would render
I assume that submitType is also a 4.1'ism, since it isn't mentioned
anywhere in the tap 4.0 docs?
As it happens, I am not using a submit component. I am using my own
component and trying to make it cancel a form and failing miserably.
--sam
On 8/28/06, Sam Gendler [EMAIL PROTECTED] wrote:
Sam Gendler wrote:
Actually, I am on Tap 4.0.2 and it isn't an AjaxForm. Unless you are
saying that merely the existence of tacos causes the overloaded
behaviour, even on regular tapestry forms.
if tacos.js and form.js are included in a page, they indeed overload the
cancel and
refresh
It works! Thanks!
Denis
-Original Message-
From: Marcus Matèrn [mailto:[EMAIL PROTECTED]
Sent: segunda-feira, 28 de agosto de 2006 06:15
To: Tapestry users
Subject: Re: Tacos DojoTabs component
If I remember correctly. The way I solved this problem was by adding
this workaround:
Yeah, that definitely needs to be documented somewhere REALLY obvious.
I am using other tacos components on the page, so tacos.js is being
loaded, even though it isn't using an AjaxForm. As a result, tacos.js
is getting loaded and it is overloading the behaviour.
Really, if tacos is going to
If you want to set an explicit height, you can still do that. Just
provide a css override for .dojoTabContainer in order to set the
height to a specific value.
.dojoTabContainer {
width: 100%;
height: 450px;
}
for example, although I recommend using a weaker selector than that,
by
that works even with a doctype, which is necessary for most users,
since running in quirks mode can easily break other aspects of the
page design.
--sam
On 8/28/06, Sam Gendler [EMAIL PROTECTED] wrote:
If you want to set an explicit height, you can still do that. Just
provide a css override
Actually, I still don't have a fix. According to the FAQ entry you
referred me to earlier:
In ajax Forms you'll have to use tacos.refreshForm(document.form) or
tacos.cancelForm(document.form).
but neither function exists anywhere in the tacos object. I get:
tacos.cancelForm is not a function
Nice component! The simplest thing I would suggest enabling is just
using the dojo version (and be careful to always wrap the bugger with
an element with a set width/height. Then its just a matter of doing
what theyre doing here
Currently I am playing with the new @EventListener feature and I like it
very much. That's how Ajax should be.
I have a question: in the form there are two @PropertySelection
components. The second one is supposed the change it's selected value
dependant on the first one. Both
Since Geoff decided to leave the Spindle project i've been thinking
about the future of TapIDEA. As many of you know, TapIDEA is built on
top of Spindle, which means No Spindle - No TapIDEA.
There are several scenarios that can be put into account in the current
situation, and after a long
Hi there Andy,
Why can't you submit the form like you say?
If you read the bottom comments on:
http://tapestry.apache.org/tapestry4.1/ajax/EventListener.html
You'll see that...
When your
listenerhttp://tapestry.apache.org/tapestry4.1/UsersGuide/listenermethods.htmlis
invoked you can be
I plan on upgrading dojo soon, just been waiting for the recent namespace
changes to quiet down some before doing it.
On 8/28/06, Josh Long [EMAIL PROTECTED] wrote:
Nice component! The simplest thing I would suggest enabling is just
using the dojo version (and be careful to always wrap the
Not sure if it's fixed in 4.1, but if you file something in JIRA I'll make
sure it is. (somehow)
On 8/28/06, Patrick Moore [EMAIL PROTECTED] wrote:
Hi there --
I ran into a bug with Hidden and the way it assigns its id.
If I put @Hidden in a @For loop, the Hidden component keeps the supplied
I can't submit it because the user has to fill in some more fields.
Maybe I am wrong. There is nothing about submitting the form (async). I
will try that. The user then might fill in the rest...
Thanks,
Andy
Pedro Viegas schrieb:
Hi there Andy,
Why can't you submit the form like you say?
Yep, all I said only works if you submit the form in async mode.
Be aware that until somewhere last week that had problems. You must use the
current SNAPSHOT for this to work.
If you submit the form asyncronously the validation of the other fileds wont
be a problem and all should work.
Regards,
Just tried it. It does work better by setting the style with
.dojoTabContainer since it makes the scrollbars appear when necessary (which
wasn't happening otherwise and content ended up being hidden when it was
more than could fit in a window), however I would still prefer if I didn't
have to use
You aren't the first one to be bitten by the style rules on that widget.
Someone made me implement an alternate - less obtrusive(much more
performant) - version on a different project...If anything like that makes
it into tapestry it'll be the latter..
On 8/28/06, Denis Souza [EMAIL PROTECTED]
OK, so after pulling the latest tacos source and checking out
tacos.js, I see that the mentioned methods are indeed newer than my
current build. So I ported all my changes to the latest tacos trunk
AND I went ahead an upgraded to a custom build of dojo 0.3.1. Aside
from the (longstanding)
I am guessing that frm.oncancel and frm.onrefresh only get defined if
it is actually an tacos supplied form, rather than a regular tapestry
supplied form. So we have a situation where including any tacos
component causes the tacos.js file to force us to use the tacos
supplied methods, yet the
Initially, therre was this bug report:
http://tacoscomponents.jot.com/BugReporter/Bug109
You can try the demo page at
http://opencomponentry.com:8080/tacos/bugs/Bug109.html
Enter more than six letters (there's a min length validator), hit submit,
then enter one letter and then click on 'Cancel
I am sure the fix fixes AjaxForms. Unfortunately, it breaks any
non-AjaxForms that are on the same page. I have a page with a number
of AjaxForms (included as part of a component) as well as a normal
tapestry @Form component. Since tacos.js overrides functionality
globally, for all forms, it
Sam Gendler wrote:
I am sure the fix fixes AjaxForms. Unfortunately, it breaks any
non-AjaxForms that are on the same page.
I understand your problem, but to be exact,
the fix fixed AjaxForms... it just didn't fix normal Forms cause no one
was aware of that issue.
You can add a new bug
Not to be rude but:
-) This isn't the tacos mailing list.
-) You ~are~ a tacos developer with full commit access.
Besides those obvious statements I'd have to agree that breaking normal
forms probably isn't the nicest thing to do.
On 8/28/06, andyhot [EMAIL PROTECTED] wrote:
Sam Gendler
guys,
is there a component available for tap3 for a progress bar or anything
else which can help me display a progress bar.
now i am thinking of generating something myself using a frames and
constantly updating the main page with the status (1%, 50%, 100% and
so on). this can be using either
You're right and ... here's the rest of the story
I've been trying to reach Alex Kochnev, the author of
http://akochnev.blogspot.com/2006/08/tapestry-netbeans-plugin.html
but since i couldn't wait for his response, I went ahead and created
something
along the lines that he describes.
I made use
I should make a note of it one last time so that guilt doesn't drive me
mad...
The @EventListener annotation was originally Howard's idea, I just
implemented it. I'm sure this will be a common occurrence as more and more
of T5 evolves. (as much as makes sense/is possible at least)
On 8/28/06,
From the sound of things it seems like you must either really enjoy pain or
have an incredibly large project that would prevent you from upgrading to
4.1 ;)
On 8/28/06, Peter Dawn [EMAIL PROTECTED] wrote:
guys,
is there a component available for tap3 for a progress bar or anything
else which
Jesse has no such superhuman abilities. Or...can't fit anymore information
into his brain.
On 8/28/06, andyhot [EMAIL PROTECTED] wrote:
You're right and ... here's the rest of the story
I've been trying to reach Alex Kochnev, the author of
On 8/28/06, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Not to be rude but:
-) This isn't the tacos mailing list.
well, yeah, but the problem started out as a problem with regular
tapestry forms and just happened to turn out to be a problem with
tacos.
-) You ~are~ a tacos developer with full
guys,
i want to underline one letter of a word, which is within my
properties files. i mean say i have a word like Name. I want to
underline N. If i was using static text I could use u tag. but since
this information is now in a properties file, how should i do this.
any ideas.
You could create a custom component for this, and pass the word as a
parameter. In the html part of the component, you use
ognl/java.lang.String to split the String into 2 parts, putting the
first part between u /u.
Regards,
Dick
-Original Message-
From: Peter Dawn [mailto:[EMAIL
53 matches
Mail list logo
