WAHtmlDocument>>comment:

I know the comment states that by default it doesn't bother to render
comments, but I can't seem to figure why that might be :)

WAHtmlDocument>>comment: aString
        self
                text: '<!--';
                text: aString;
                text: '-->'

Any objections?

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> I know the comment states that by default it doesn't bother to render
> comments, but I can't seem to figure why that might be :)
>
> WAHtmlDocument>>comment: aString
>         self
>                 text: '<!--';
>                 text: aString;
>                 text: '-->'

I don't see a point in emitting a comment to the generated XHTML.
After all it is a single line of compact markup ...

The idea of the #comment: message was to put some annotation into the
pretty printed output, accessible from the halos.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Just to give you some context, I was looking for a way to put hidden
tokens into the output so that our server monitoring software could look
them up and comments seemed like an appropriate venue, semantically
speaking. I guess I could have added a div with display:none, but it
just didn't seem right as these are definitely not part of the page
markup.

Cheers,

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Lukas
Renggli
Sent: Tuesday, February 13, 2007 2:17 PM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: [Seaside] WAHtmlDocument>>comment:

> I know the comment states that by default it doesn't bother to render
> comments, but I can't seem to figure why that might be :)
>
> WAHtmlDocument>>comment: aString
>         self
>                 text: '<!--';
>                 text: aString;
>                 text: '-->'

I don't see a point in emitting a comment to the generated XHTML.
After all it is a single line of compact markup ...

The idea of the #comment: message was to put some annotation into the
pretty printed output, accessible from the halos.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Just to give you some context, I was looking for a way to put hidden
> tokens into the output so that our server monitoring software could  
> look
> them up and comments seemed like an appropriate venue, semantically
> speaking. I guess I could have added a div with display:none, but it
> just didn't seem right as these are definitely not part of the page
> markup.

Boris,

I would rather subclass WARenderCanvas and create a new intention
revealing selector like #emitMonitoringSoftwareInformation:
If you use #html: you can output anything. You can also probably
take advantage of the Canvas to create your own xml-like markup
inside the comment.
Just an idea.

Michel.
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2007/2/13, Boris Popov <[hidden email]>:
> Just to give you some context, I was looking for a way to put hidden
> tokens into the output so that our server monitoring software could look
> them up and comments seemed like an appropriate venue, semantically
> speaking. I guess I could have added a div with display:none, but it
> just didn't seem right as these are definitely not part of the page
> markup.

meta head elements?

Philippe
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Philippe, Michel,

Both excellent suggestions, thanks!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.
look Lukas
> > Renggli
> > Sent: Tuesday, February 13, 2007 2:17 PM
> > To: The Squeak Enterprise Aubergines Server - general discussion.
> > Subject: Re: [Seaside] WAHtmlDocument>>comment:
> >
> > > I know the comment states that by default it doesn't bother to
render the _______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside