You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Martin Strand <ma...@entcap.se> on 2006/10/03 22:05:37 UTC
dojo DEBUG messages
Hi all.
How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
>> DEBUG: Opera is not supported with dojo.undo.browser, so back/forward
>> detection will not work.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: dojo DEBUG messages
Posted by Martin Strand <ma...@entcap.se>.
Are you sure you're using 4.1.1? It works here...
On Sat, 07 Oct 2006 00:36:52 +0200, Leo Sakhvoruk
<le...@gmail.com> wrote:
> Thanks for such a quick response, still no luck though.
>
> Leo
>
> Jesse Kuhnert wrote:
>> Ahh..Looks like I made it so that you have to use an ognl expression ...
>>
>> Try debugEnabled="ognl:false" .
>>
>> On 10/6/06, Leo Sakhvoruk <le...@gmail.com> wrote:
>>>
>>> Hi Jesse,
>>>
>>> I tried disabling the dojo debug message in the Shell component per
>>> your
>>> instructions but I get the following runtime exception:
>>>
>>> Component <my page/component>.shell allows only formal parameters,
>>> binding debugEnabled is not allowed.
>>>
>>> This is how I define the Shell component:
>>>
>>> <component id="shell" type="Shell">
>>> <binding name="title" value="pageTitle"/>
>>> <binding name="debugEnabled" value="false"/>
>>> <binding name="stylesheets">{assets.style}</binding>
>>> </component>
>>>
>>> Am I doing something wrong?
>>>
>>> Thanks.
>>>
>>> Jesse Kuhnert wrote:
>>> > Yeah, I thought the most common default behaviour would wanting debug
>>> > on -
>>> > so that's what I've done...If people find this to be
>>> counter-intuitive
>>> > I'll
>>> > disable it by default.
>>> >
>>> > You can control the log levels, as well as whether it's on at all via
>>> the
>>> > @Shell component "debugEnabled" parameter.
>>> >
>>> > http://tapestry.apache.org/tapestry4.1/components/Shell.html
>>> >
>>> > On 10/3/06, Martin Strand <ma...@entcap.se> wrote:
>>> >>
>>> >> Hi all.
>>> >> How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
>>> >>
>>> >> >> DEBUG: Opera is not supported with dojo.undo.browser, so
>>> back/forward
>>> >> >> detection will not work.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: dojo DEBUG messages
Posted by Leo Sakhvoruk <le...@gmail.com>.
Thanks for such a quick response, still no luck though.
Leo
Jesse Kuhnert wrote:
> Ahh..Looks like I made it so that you have to use an ognl expression ...
>
> Try debugEnabled="ognl:false" .
>
> On 10/6/06, Leo Sakhvoruk <le...@gmail.com> wrote:
>>
>> Hi Jesse,
>>
>> I tried disabling the dojo debug message in the Shell component per your
>> instructions but I get the following runtime exception:
>>
>> Component <my page/component>.shell allows only formal parameters,
>> binding debugEnabled is not allowed.
>>
>> This is how I define the Shell component:
>>
>> <component id="shell" type="Shell">
>> <binding name="title" value="pageTitle"/>
>> <binding name="debugEnabled" value="false"/>
>> <binding name="stylesheets">{assets.style}</binding>
>> </component>
>>
>> Am I doing something wrong?
>>
>> Thanks.
>>
>> Jesse Kuhnert wrote:
>> > Yeah, I thought the most common default behaviour would wanting debug
>> > on -
>> > so that's what I've done...If people find this to be counter-intuitive
>> > I'll
>> > disable it by default.
>> >
>> > You can control the log levels, as well as whether it's on at all via
>> the
>> > @Shell component "debugEnabled" parameter.
>> >
>> > http://tapestry.apache.org/tapestry4.1/components/Shell.html
>> >
>> > On 10/3/06, Martin Strand <ma...@entcap.se> wrote:
>> >>
>> >> Hi all.
>> >> How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
>> >>
>> >> >> DEBUG: Opera is not supported with dojo.undo.browser, so
>> back/forward
>> >> >> detection will not work.
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> >> For additional commands, e-mail: users-help@tapestry.apache.org
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: dojo DEBUG messages
Posted by Jesse Kuhnert <jk...@gmail.com>.
Ahh..Looks like I made it so that you have to use an ognl expression ...
Try debugEnabled="ognl:false" .
On 10/6/06, Leo Sakhvoruk <le...@gmail.com> wrote:
>
> Hi Jesse,
>
> I tried disabling the dojo debug message in the Shell component per your
> instructions but I get the following runtime exception:
>
> Component <my page/component>.shell allows only formal parameters,
> binding debugEnabled is not allowed.
>
> This is how I define the Shell component:
>
> <component id="shell" type="Shell">
> <binding name="title" value="pageTitle"/>
> <binding name="debugEnabled" value="false"/>
> <binding name="stylesheets">{assets.style}</binding>
> </component>
>
> Am I doing something wrong?
>
> Thanks.
>
> Jesse Kuhnert wrote:
> > Yeah, I thought the most common default behaviour would wanting debug
> > on -
> > so that's what I've done...If people find this to be counter-intuitive
> > I'll
> > disable it by default.
> >
> > You can control the log levels, as well as whether it's on at all via
> the
> > @Shell component "debugEnabled" parameter.
> >
> > http://tapestry.apache.org/tapestry4.1/components/Shell.html
> >
> > On 10/3/06, Martin Strand <ma...@entcap.se> wrote:
> >>
> >> Hi all.
> >> How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
> >>
> >> >> DEBUG: Opera is not supported with dojo.undo.browser, so
> back/forward
> >> >> detection will not work.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: dojo DEBUG messages
Posted by Leo Sakhvoruk <le...@gmail.com>.
Hi Jesse,
I tried disabling the dojo debug message in the Shell component per your
instructions but I get the following runtime exception:
Component <my page/component>.shell allows only formal parameters,
binding debugEnabled is not allowed.
This is how I define the Shell component:
<component id="shell" type="Shell">
<binding name="title" value="pageTitle"/>
<binding name="debugEnabled" value="false"/>
<binding name="stylesheets">{assets.style}</binding>
</component>
Am I doing something wrong?
Thanks.
Jesse Kuhnert wrote:
> Yeah, I thought the most common default behaviour would wanting debug
> on -
> so that's what I've done...If people find this to be counter-intuitive
> I'll
> disable it by default.
>
> You can control the log levels, as well as whether it's on at all via the
> @Shell component "debugEnabled" parameter.
>
> http://tapestry.apache.org/tapestry4.1/components/Shell.html
>
> On 10/3/06, Martin Strand <ma...@entcap.se> wrote:
>>
>> Hi all.
>> How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
>>
>> >> DEBUG: Opera is not supported with dojo.undo.browser, so back/forward
>> >> detection will not work.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: How do I create a link...
Posted by Hajaansh <ha...@googlemail.com>.
This is also how I do it but I thought I read in a previous post that this
is not the "best" way of doing it. Is this correct?
On 10/4/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> That depends on what you want to happen when they click on that asset?
>
> I've found the "ServiceLink" component indispensable in this regard. You
> can
> create a simple little arbitrary engine service without the hassle of
> creating new link components to run it...So..In your case you could:
>
> Define a new engine service that serves files to people in such a way that
> it'll correctly invoke their browsers application content handling type -
> or
> download if none is found...(Ie setting response type , etc..)
>
> Then use a simple ServiceLink to pass in what you want to give the
> service,
> which is presumably a local asset you have defined.
>
> On 10/3/06, Mark Stang <ms...@pingidentity.com> wrote:
> >
> > I need to create a link to an asset in Tapestry 3.
> >
> > Basically, I have a .pdf which isn't in my "context".
> >
> > Thoughts on how to link to it?
> >
> > thanks,
> >
> > mark
> >
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo/(and a dash of TestNG), team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
>
Re: How do I create a link...
Posted by Jesse Kuhnert <jk...@gmail.com>.
That depends on what you want to happen when they click on that asset?
I've found the "ServiceLink" component indispensable in this regard. You can
create a simple little arbitrary engine service without the hassle of
creating new link components to run it...So..In your case you could:
Define a new engine service that serves files to people in such a way that
it'll correctly invoke their browsers application content handling type - or
download if none is found...(Ie setting response type , etc..)
Then use a simple ServiceLink to pass in what you want to give the service,
which is presumably a local asset you have defined.
On 10/3/06, Mark Stang <ms...@pingidentity.com> wrote:
>
> I need to create a link to an asset in Tapestry 3.
>
> Basically, I have a .pdf which isn't in my "context".
>
> Thoughts on how to link to it?
>
> thanks,
>
> mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
How do I create a link...
Posted by Mark Stang <ms...@pingidentity.com>.
I need to create a link to an asset in Tapestry 3.
Basically, I have a .pdf which isn't in my "context".
Thoughts on how to link to it?
thanks,
mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
Re: dojo DEBUG messages
Posted by Martin Strand <ma...@entcap.se>.
Sounds like a sensible default behaviour, I just hadn't seen the
debugEnabled parameter. Thanks.
Martin
On Tue, 03 Oct 2006 23:22:19 +0200, Jesse Kuhnert <jk...@gmail.com>
wrote:
> Yeah, I thought the most common default behaviour would wanting debug on
> -
> so that's what I've done...If people find this to be counter-intuitive
> I'll
> disable it by default.
>
> You can control the log levels, as well as whether it's on at all via the
> @Shell component "debugEnabled" parameter.
>
> http://tapestry.apache.org/tapestry4.1/components/Shell.html
>
> On 10/3/06, Martin Strand <ma...@entcap.se> wrote:
>>
>> Hi all.
>> How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
>>
>> >> DEBUG: Opera is not supported with dojo.undo.browser, so back/forward
>> >> detection will not work.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: dojo DEBUG messages
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah, I thought the most common default behaviour would wanting debug on -
so that's what I've done...If people find this to be counter-intuitive I'll
disable it by default.
You can control the log levels, as well as whether it's on at all via the
@Shell component "debugEnabled" parameter.
http://tapestry.apache.org/tapestry4.1/components/Shell.html
On 10/3/06, Martin Strand <ma...@entcap.se> wrote:
>
> Hi all.
> How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages?
>
> >> DEBUG: Opera is not supported with dojo.undo.browser, so back/forward
> >> detection will not work.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com