[Seaside] Howto Image (picture) instance variable of the class

[Oswall Verny Arguedas C.]

Hi Karsten
""
the biggest challenge in serving pictures via FileLibrary is how to map a
URL <-> Picture. In HTTP all you have is a URL and you need to find a way
to create this URL and then also to resolve your pictures based on a given
URL. So if you use a FileLibrary or a similar RequestHandler, you need a
way to find your Product object and then find its picture based on a given
URL. If this is simple enough in your implementation, go for it. i.e. if
your Products all have an ID and your are stored in a database there’s no
problem in resolving URLs like /pictures?product=1234&picture=1.
""
This first part that you tell me I think is similar to what Esteban says.
I have not implemented it. I am reviewing the documentation.

""
An alternative is to register a URL during rendering (in that case Seaside
takes care of creating and resolving the URLs):
html image document: aProduct picture1 data
The benefit is that you don’t need to think about creating a URL and
resolving it. The downside is that your images have URLs with random keys
in it and they’re only valid as long as your session is alive.
""
Register url while rendering?.
There is some documentation about it.
Thanks

El jue, 3 de jun. de 2021 a la(s) 23:53, Karsten Kusche (karsten at heeg.de)
escribió:

> Hi Oswall,
>
> the biggest challenge in serving pictures via FileLibrary is how to map a
> URL <-> Picture. In HTTP all you have is a URL and you need to find a way
> to create this URL and then also to resolve your pictures based on a given
> URL. So if you use a FileLibrary or a similar RequestHandler, you need a
> way to find your Product object and then find its picture based on a given
> URL. If this is simple enough in your implementation, go for it. i.e. if
> your Products all have an ID and your are stored in a database there’s no
> problem in resolving URLs like /pictures?product=1234&picture=1.
>
> An alternative is to register a URL during rendering (in that case Seaside
> takes care of creating and resolving the URLs):
> html image document: aProduct picture1 data
> The benefit is that you don’t need to think about creating a URL and
> resolving it. The downside is that your images have URLs with random keys
> in it and they’re only valid as long as your session is alive.
>
> Kind regards
> Karsten
>
> —
>
> Georg Heeg eK
>
> Wallstraße 22
> 06366 Köthen
>
> Tel.: 03496/214328
> FAX: 03496/214712
> Amtsgericht Dortmund HRA 12812
>
>
>
> Am 3. Juni 2021 um 20:52:10, Oswall Verny Arguedas C. (sistecaq at gmail.com)
> schrieb:
>
> Greetings,
> I have a query about saving instances of a class that are of type image
> (picture).
> For example. I have a Product class. This class must have two photographs
> of that product. I have to save two instance variables of the Product
> class, picture1, picture2.
> These images must be uploaded from the Product form and displayed after
> uploading.
> In Seaside what would be the best procedure to do it.
> I don't know if WAFileLibrary would be the best option.
> Thanks in advance.
> Oswall
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/seaside/attachments/20210609/46c21fe9/attachment.html>