blah blah fnar fquar har GNU hello!
Feature proof, future proof, crash proof, test proof, 100% proof.
I am sitting in a room, I am sat on a chair, I am looking at this screen, I am seeing you there.
Internal Link to current page.
Forced internal link to current page.
Each page for jwm-art.net is generated by PHP scripts. These scripts read text files which contain the information the scripts need to generate a page for jwm-art.net.
For the main content of a page, each line in the text file represents a specific thing. So you might have a line telling the scripts to display an image.
Or you might have a line telling the scripts to display some text. For things like text, each line (with a couple of exceptions) in the text file gets treated as a paragraph ie, is placed between the <p> and </p> tags.
/*-------------------------------------------------------------------------------------------------- at-tags ie @= and =@ are delimiters used by jwm-art.net to embed links and other HTML elements within blocks of text. everything outside of the @= and =@ is only ever displayed as plain text. What's more, the characters immediately following the @= start tag can only ever contain lower case letters, the exclamation mark, and the forward and backslash characters. The jwm-art.net page creator could put these characters in whatever order he likes, but that does not mean they'll automatically do anything. The at-tags must be valid at-tags, such as ilink, xlink,b, and a few others. As an example, we take a line of unformatted plain text, minus @= and =@ tags: To create bold text do this text to be bold, got it? and then use at-tags to present it's implimented form. Each subsequent line below it, shows the at-tags used to display the line above. To create bold text do this @=b=text to be bold=@, got it? To create @=b=bold text=@ do this @=\=b=text to be bold=@, got it? To create @=\=b=bold text=@ do this @=\=\=b=text to be bold=@, got it? */
In a text file which represents a page, each line represents a single thing. After the lines which specifiy the page title, it's description and keywords, you have two sections in which to place a thing, main, or info. For example, to display an image you would have a line such as: main=image=ride-03 (which in this case would display the image from the page Ride-03.) A paragraph of text looks like main=text=This is one paragraph of text. So main=text=some text here gets translated to HTML as <p class=l>some text here</p>. The limititation of this is that a line of text in the file cannot finish on one line and continue on the next without re-specifying main=text= again - consequently beginning a new paragraph. There is an exception of course and that came about from an affair with preformatted plain-text, of which, this is (almost) an example. To display a pre-formatted block of text, ie to specify the creation of a preformatted block of text in the file you do this: main=@=codeblock=@ ***NOTE:*** main=@=codeblock=@ is the old style method of creating a codeblock. The new method employs a 'heredoc' type syntax, see elsewhere on this page for examples.
can we create a bold ilink?
can we create bold text using @=b=@ followed by an inversion to un-bold-text by using @=b=bold text=@ within the two @=b=@ tags?
This paragraph tests the new heredoc functionality created to allow types besides the codeblock type to be spread over multiple lines. Without it, every individual type within a page, must be contained on a single line. Using 'heredoc' functionality, the beginning of a line is specified in exactly the same way, eg section=type= but instead of the text (data for the type) immediately following the = sign (ie instead of type=type'sdata) we have type=@=<<DELIMITER=@ where DELIMITER is the text string to end the data. The DELIMITER text string must be placed on a line of it's own and cannot contain any spaces.
Notice the use of the @= (at-tags) =@ either side of the <<DELIMITER. This might seem obscure, even
to those already familiar with the term 'heredoc' (purists might argue it is only a superficial heredoc
implimentation, and I'd agree) but what someone wants to start a line of text with << ?
Despite appearing as at-tags, the heredoc syntax is only superficially using at-tags. The processing of the here-doc happens as the data for a page is read from a file - a long time before at-tags are actually processed
// Example of heredoc/DELIMITER for // reading multiple lines as a single // line. main=text=@=<<END=@ This is my first line of text, I'll spread it across several lines but each line will be merged to form a single line which will be passed to whatever peice of code processes the type expressed initialise the block. END // The delimiter (in this case END) // signals the end of the block for the // type and processing will return to // normal thereafter.gkII - Mandelbrot Mangler
This is my first line of text, I'll spread it across several lines but each line will be merged to form a single line which will be passed to whatever peice of code processes the type expressed initialise the block.