In article <4.1.19990529132727.0098d4b0@mail.atmm.nl>, Martijn Pieters <mj@antraciet.nl> writes
Just wondering if there is a tag/variable that allows us to define a url or image so that I can do this:
<!--#var myimage-->
produces
<a href=http://distant_url><img src=http://www.distant_url.com/images/their_image.jpg width=100 height=40 alt="Their picture off their server"></a>
Just saying <!--#var myimage--> already gets you the whole imagetah as described above. You'd only have to put the A tag around it yourself, like so:
Doesn't seem to on my system. Zope seems to require that the image be local.
Yes, Zope wants the image to be local. Of course, you could define a Property of the top-level folder called (for example) pDistantLogo and then use <IMG SRC="<!--#var pDistantLogo-->"> or something. --Rob
In article <613145F79272D211914B0020AFF6401915C4E5@gandalf.digicool.com> , Rob Page <rob.page@digicool.com> writes
Yes, Zope wants the image to be local. Of course, you could define a Property of the top-level folder called (for example) pDistantLogo and then use <IMG SRC="<!--#var pDistantLogo-->"> or something.
Looks like the image item has limited use, and it most cases it would be simpler to replace all with DTML documents instead. Then at least you can alter where the image location is rather than having to delete the image item, and redefine it. The reason I'm going thru all these contortions is that my ISP doesn't support Zope, so I'm going to have to host it myself on a dial up line, and to maintain speed, I'm leaving all the images on my ISP hosted website. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz
At 01:14 30/05/99 , Graham Chiu wrote:
In article <613145F79272D211914B0020AFF6401915C4E5@gandalf.digicool.com> , Rob Page <rob.page@digicool.com> writes
Yes, Zope wants the image to be local. Of course, you could define a Property of the top-level folder called (for example) pDistantLogo and then use <IMG SRC="<!--#var pDistantLogo-->"> or something.
Looks like the image item has limited use, and it most cases it would be simpler to replace all with DTML documents instead. Then at least you can alter where the image location is rather than having to delete the image item, and redefine it.
The reason I'm going thru all these contortions is that my ISP doesn't support Zope, so I'm going to have to host it myself on a dial up line, and to maintain speed, I'm leaving all the images on my ISP hosted website.
Sorry, I misunderstood your question. Yes, the Image object is designed to contain local images, within your Zope installation.. If you have a load of images on a different server, you'd be better to use properties on the root Folder, like Rob said, or you could use a TinyTable (download from http://www.zope.org/Download/Contrib), and store a list of image names in that. You could for example use the following schema in a TinyTable called ExtImageList: name, html In it you have entries like: 'myimage', '<a href="http://disturl"><img src="http://disturl/myimage.gif" width=100 height=100 border=0></a>' Now you could use code like: <!--#in "ExtImageList('myimage')--><!--#var html--><!--#/in--> You could also factor the previous line out to a DTMLMethod which you then call from all your documents you want to have an image. In the fututre you could use ZClasses for this type of work as well. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-6254545 Fax: +31-35-6254555 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
In article <4.2.0.56.19990530120926.00bc8ed0@lisp.atmm.nl>, Martijn Pieters <mj@antraciet.nl> writes
If you have a load of images on a different server, you'd be better to use properties on the root Folder, like Rob said, or you could use a TinyTable (download from http://www.zope.org/Download/Contrib), and store a list of image names in that.
I tried it out, and got the following: Traceback (innermost last): File "f:\zope\lib\python\OFS\Application.py", line 384, in import_products product=__import__(pname, global_dict, global_dict, silly) File "f:/Zope\lib\python\Products\TinyTable\__init__.py", line 39, in ? import TinyTable File "f:/Zope\lib\python\Products\TinyTable\TinyTable.py", line 39, in ? from PersistentMapping import PersistentMapping ImportError: No module named PersistentMapping This was TinyTableB2 which comes up as a broken product. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz
At 11:59 31/05/99 , Graham Chiu wrote:
In article <4.2.0.56.19990530120926.00bc8ed0@lisp.atmm.nl>, Martijn Pieters <mj@antraciet.nl> writes
If you have a load of images on a different server, you'd be better to use properties on the root Folder, like Rob said, or you could use a TinyTable (download from http://www.zope.org/Download/Contrib), and store a list of image names in that.
I tried it out, and got the following:
Traceback (innermost last): File "f:\zope\lib\python\OFS\Application.py", line 384, in import_products product=__import__(pname, global_dict, global_dict, silly) File "f:/Zope\lib\python\Products\TinyTable\__init__.py", line 39, in ? import TinyTable File "f:/Zope\lib\python\Products\TinyTable\TinyTable.py", line 39, in ? from PersistentMapping import PersistentMapping ImportError: No module named PersistentMapping
This was TinyTableB2 which comes up as a broken product.
This is due to a change in Zope 1.11.0pr1. TinyTables works fine on older versions. Ty has a fix: http://www.zope.org/pipermail/zope/1999-May/004173.html After making the change, delete the TinyTable product from your Products (in Zope), and restart Zope. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-6254545 Fax: +31-35-6254555 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
In article <4.2.0.56.19990531135356.00af6f00@lisp.atmm.nl>, Martijn Pieters <mj@antraciet.nl> writes
This was TinyTableB2 which comes up as a broken product.
This is due to a change in Zope 1.11.0pr1. TinyTables works fine on older versions. Ty has a fix:
http://www.zope.org/pipermail/zope/1999-May/004173.html
After making the change, delete the TinyTable product from your Products (in Zope), and restart Zope.
Thanks, I'll have a look at fixing it asap. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz
participants (3)
-
Graham Chiu -
Martijn Pieters -
Rob Page