You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Richard V." <xg...@hotmail.com> on 2005/06/13 20:52:52 UTC
Assets
Hello everyone,
I have been using Tapestry for almost 6 months developing a service system
(on my own in the dark) for students in a computer lab. While using this
great and powerful framework, i noticed some shortcomings in it and I need
some help: (I am using version 3.0.1)
1- Assets: As far as I know, images are assets. But these images must be
files or URLs. What if the images are generated, not stored as files, and I
wish to display them? I noticed that the current design of class
AbstractAsset as well as AssetService does not allow one to generate an
asset on the fly when request comes. Does anyone has a work around to this
limitation besides writing an external servlet that generates the images and
use externalAsset?
2- Component's own css: I created some components of my own which had
cascded style-sheets. If I wanted to use them on some other project, I
needed to append the css to the respective css of the project. This is
really troublesome and would like to propose an extension to the Shell
components to could allow components to export their own css.
Thank you
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Assets
Posted by Nick Stuart <ba...@gmail.com>.
Well, I have an idea for number one. As you said yourself, images can
be urls. So could you not point the url to a servlet of some type that
sends back the generated image data based on the parameters passed?
There's nothing stopping you in Tapestry to not use the low level
Servlet API and have it generate stuff for you.
I believe doing something like this will work. Or, you may be able to
write your own Tapestry service that will do what you are looking for,
either way I'm pretty sure it can be done.
Also, images dont HAVE to be assests. For your dynamic images you may
be able to just hard code the <img> tags in the page itself.
-Nick
On 6/13/05, Richard V. <xg...@hotmail.com> wrote:
> Hello everyone,
>
> I have been using Tapestry for almost 6 months developing a service system
> (on my own in the dark) for students in a computer lab. While using this
> great and powerful framework, i noticed some shortcomings in it and I need
> some help: (I am using version 3.0.1)
>
> 1- Assets: As far as I know, images are assets. But these images must be
> files or URLs. What if the images are generated, not stored as files, and I
> wish to display them? I noticed that the current design of class
> AbstractAsset as well as AssetService does not allow one to generate an
> asset on the fly when request comes. Does anyone has a work around to this
> limitation besides writing an external servlet that generates the images and
> use externalAsset?
>
> 2- Component's own css: I created some components of my own which had
> cascded style-sheets. If I wanted to use them on some other project, I
> needed to append the css to the respective css of the project. This is
> really troublesome and would like to propose an extension to the Shell
> components to could allow components to export their own css.
>
> Thank you
>
> Richard
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Assets
Posted by "Richard V." <xg...@hotmail.com>.
You are right. I overlooked this good example.
Thanks for your help.
Richard
>From: "Devlists" <de...@freemail.hu>
>Reply-To: "Tapestry users" <ta...@jakarta.apache.org>
>To: "Tapestry users" <ta...@jakarta.apache.org>
>Subject: Re: Assets
>Date: Mon, 13 Jun 2005 21:54:03 +0200
>
>Hi,
>
>1. You can create your own service to do this. The workbench example
>contains a chart service which is a good point to start at.
>
>Br,
>Norbi
>
>----- Original Message ----- From: "Richard V." <xg...@hotmail.com>
>To: <ta...@jakarta.apache.org>
>Sent: Monday, June 13, 2005 8:52 PM
>Subject: Assets
>
>
>>Hello everyone,
>>
>>I have been using Tapestry for almost 6 months developing a service system
>>(on my own in the dark) for students in a computer lab. While using this
>>great and powerful framework, i noticed some shortcomings in it and I
>>need
>>some help: (I am using version 3.0.1)
>>
>>1- Assets: As far as I know, images are assets. But these images must be
>>files or URLs. What if the images are generated, not stored as files, and
>>I
>>wish to display them? I noticed that the current design of class
>>AbstractAsset as well as AssetService does not allow one to generate an
>>asset on the fly when request comes. Does anyone has a work around to this
>>limitation besides writing an external servlet that generates the images
>>and
>>use externalAsset?
>>
>>2- Component's own css: I created some components of my own which had
>>cascded style-sheets. If I wanted to use them on some other project, I
>>needed to append the css to the respective css of the project. This is
>>really troublesome and would like to propose an extension to the Shell
>>components to could allow components to export their own css.
>>
>>Thank you
>>
>>Richard
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Assets
Posted by Devlists <de...@freemail.hu>.
Hi,
1. You can create your own service to do this. The workbench example
contains a chart service which is a good point to start at.
Br,
Norbi
----- Original Message -----
From: "Richard V." <xg...@hotmail.com>
To: <ta...@jakarta.apache.org>
Sent: Monday, June 13, 2005 8:52 PM
Subject: Assets
> Hello everyone,
>
> I have been using Tapestry for almost 6 months developing a service system
> (on my own in the dark) for students in a computer lab. While using this
> great and powerful framework, i noticed some shortcomings in it and I
> need
> some help: (I am using version 3.0.1)
>
> 1- Assets: As far as I know, images are assets. But these images must be
> files or URLs. What if the images are generated, not stored as files, and
> I
> wish to display them? I noticed that the current design of class
> AbstractAsset as well as AssetService does not allow one to generate an
> asset on the fly when request comes. Does anyone has a work around to this
> limitation besides writing an external servlet that generates the images
> and
> use externalAsset?
>
> 2- Component's own css: I created some components of my own which had
> cascded style-sheets. If I wanted to use them on some other project, I
> needed to append the css to the respective css of the project. This is
> really troublesome and would like to propose an extension to the Shell
> components to could allow components to export their own css.
>
> Thank you
>
> Richard
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org