Hi,
Back again with a new patch
How to generate HTML directives using ehtml (I wanted to send DOCTYPE
using ehtml, but others will work equally well).
e.g. {ehtml, {'!DOCTYPE', ["html", "PUBLIC", "\"...\"", "\"...\""]}
will produce the proper output with the attached patch:
<!DOCTYPE, html PUBLIC "..." "...">
One possible problem: text will not be properly htmlized
(BTW I used the BIF list, instead of is_list, just to be consistent
with the rest of the code).
On to my next problem, how to handle entities correctly. Currently
they are treated as normal text and as such get (properly) htmlized,
but that's not what I think should happen.
Guess that htmlize needs to be adapted.
BTW why doesn't ehtml_expand use htmlize(list)?
/Rob
*** /space/home/rosc/src/yaws/src/yaws_api.erl Wed Dec 17 21:26:45 2003
--- yaws_api.erl Wed Jan 28 16:53:39 2004
***************
*** 1214,1219 ****
--- 1214,1221 ----
ehtml_attrs([]) -> [];
ehtml_attrs([Attribute|Tail]) when atom(Attribute) ->
[[$ |atom_to_list(Attribute)]|ehtml_attrs(Tail)];
+ ehtml_attrs([Attribute|Tail]) when list(Attribute) ->
+ [" ", Attribute|ehtml_attrs(Tail)];
ehtml_attrs([{Name, Value} | Tail]) ->
ValueString = if atom(Value) -> [$",atom_to_list(Value),$"];
list(Value) -> [$",Value,$"];
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

I wrote:
> On Sun, Jan 18, 2004 at 08:52:31PM +0100, Claes Wikstrom wrote:
>> Only thing was that (using gentoo) the cgi capable php executable
>> was called pgp-cgi (as opposed to the hardcoded "php") This either
>> needs to be configurable,
>
> It definitely should be. [...]
>
> I could try to make this configurable some time next week.
[x] done
BTW, cvs access is slowww...
Greetings,
Carsten

On Sun, Jan 18, 2004 at 08:52:31PM +0100, Claes Wikstrom wrote:
> I just wanted to write and report and that I'm successfully running
> a php package called occ (online chess club) using Yaws cgi/php
> functionality. Works like a charm.
Pleased to read this.
> Only thing was that (using gentoo) the cgi capable php executable
> was called pgp-cgi (as opposed to the hardcoded "php") This either
> needs to be configurable,
It definitely should be. I have to admit that I am using a patched
version with a different hardcoded path... Alternatively I could of
course have set PATH in the environment of yaws.
I could try to make this configurable some time next week.
Greetings,
Carsten
--=20
Carsten Schultz (2:38, 33:47), FB Mathematik, FU Berlin
http://carsten.codimi.de/
PGP/GPG key on the pgp.net key servers,=20
fingerprint on my home page.

I just wanted to write and report and that I'm successfully
running a php package called occ (online chess club) using Yaws
cgi/php functionality. Works like a charm.
Only thing was that (using gentoo) the cgi capable php executable
was called pgp-cgi (as opposed to the hardcoded "php")
This either needs to be configurable, changed or there is some php magic
that I don't get yet ......
/klacke
--
Claes Wikstrom -- Caps lock is nowhere and
http://www.hyber.org -- everything is under control

Sorry Johan, I got caught up and didn't reply to this (I think :-)
Johan Bevemyr wrote:
>>I'm thinking about putting my photos online using yaws (rather than
>>album http://MarginalHacks.com/Hacks/album/
>><http://freshmeat.net/redir/album/181/url_homepage/album&gt;). I've noticed
>>a few additions to the wiki to support thumbnails and slideshows,
>>although it doesn't appear to all be there (specifically slideShow.yaws
>>is missing).
>>
>>
>
>Sorry, missed to add that file and some gifs too. I've now
>added them to sourceforge. You will have to cvs update the
>application/wiki/src and application/wiki/wiki directories.
>
>
>
Thanks!
>Sure, I've set up a demo site at show.bevemyr.com. The way
>it works is that you add a bunch of files (gifs or jpegs) to
>a page, and then add the text slideshow:<linkname> to the text.
>When you hit the <linkname> you will get to see the first picture
>(reduced to max 400x400 pixels) and the files description text
>below the picture. You will also get a bunch of icons at the top
>back, forward, thumbnail index and camera (the icons are pretty
>ugly so feel free to contribute with prettier ones :-).
>
>If you click on the picture you will get it in its natrual size
>in a separate window.
>
>All thumbnails and 400x400 pictures are converted using 'convert'
>and cached in the .files directory.
>
>A very useful command when importing large number of files to a
>page is importFiles <path to wob file>. Just copy the files into
>the <page>.files directory and run the importFiles script.
>
>
>
Nice photos. I like the approach, although I'm not sure if I'm going to
use it, I'm either going to use Gallery (as Carsten suggested) or
reimplement Gallery in Erlang (cos its fun). If I reimplement it I think
I will support their client protocol so the Gallery front ends work.
Thanks a lot,
Bruce