delay, RE: Re: steel update
[1/3] from: maximo::meteorstudios::com at: 21-Aug-2003 9:55
hello all, I've had to delay the release of the new site, I was busy adding nested tag rebuilding last night and it took a while to debug it. now remark.r can even parse a file or tag which has nested tags and it will parse/replace the innermost tags first, then, its return is checked again, just to be sure that the new html content doesn't contain new dynamic/extended tags... so basically, it allowed me to create a <file! "path"> tag which maps the path and returns it within quotes. In any other tag I want to use a file path, I just specify the path as a <file! "path"> tag instead, and it will then be reduced again. for example, to create an relatively absolute path , I just put <img src=href<file! "images/img.gif">> so when the file is parsed, the file tag will be replaced like so: <img src=href"../images/img.gif"> if the current file is one level deeper than the site root. before, the engine skipped the <file!> tag, because it did not handle nested tags, what's more is that if a nested tag appeared, it would not catch the end of the outermost tag correctly, instead, catching the end of the innermost tag and basically jumbling up the whole file. I did this basically so that I could use the file mapping mechanism in every tag that needs it without having to reimpliment it. It almost like if html tags where now functions, each dynamic tag calling upon other successively lower-level dynamic tags. Although I did work on the site at home, it will not be complete before tonight, SORRY, I hate promising things and not delivering... I'll also check out that bug, just to see if I can make it disapear (although I've never encountered it!). -max ----------- meteor Studios, T.D. ----------- Never Argue with an idiot. They will bring you down to their level and beat you with experience
[2/3] from: andrew:martin:colenso:school at: 22-Aug-2003 8:28
> For example, to create an relatively absolute path , I just put <img
src=href<file! "images/img.gif">> so when the file is parsed, the file tag will be replaced like so: <img src=href"../images/img.gif"> if the current file is one level deeper than the site root. But wouldn't it be easier for the author, instead of writing: <img src=href<file! "images/img.gif">> to write: <img src=href<file! "img.gif">> And let the software work out the correct path? And if there's two img.gif files, the software could choose the file that closest to the source file like same directory, then subdirectory, then elsewhere. And why not use Rebol values? Like writing: <img src=%img.gif> Just my thoughts for the morning. Andrew J Martin Attendance Officer & Information Systems Trouble Shooter Colenso High School Arnold Street, Napier. Tel: 64-6-8310180 ext 826 Fax: 64-6-8336759 http://colenso.net/scripts/Wiki.r?AJM http://www.colenso.school.nz/ DISCLAIMER: Colenso High School and its Board of Trustees is not responsible (or legally liable) for materials distributed to or acquired from user e-mail accounts. You can report any misuse of an e-mail account to our ICT Manager and the complaint will be investigated. (Misuse can come in many forms, but can be viewed as any material sent/received that indicate or suggest pornography, unethical or illegal solicitation, racism, sexism, inappropriate language and/or other issues described in our Acceptable Use Policy.) All outgoing messages are certified virus-free by McAfee GroupShield Exchange 5.10.285.0 Phone: +64 6 843 5095 or Fax: +64 6 833 6759 or E-mail: [postmaster--colenso--school--nz]
[3/3] from: maximo:meteorstudios at: 22-Aug-2003 11:04
> -----Original Message----- > From: Andrew Martin 
<<quoted lines omitted: 6>>> "img.gif" files, the software could choose the file that > closest to the
but that's dangerous, if there are two img.gif on disk, then they should be be different... letting the software choose which one to use will eventually cause it to choose the bad one ... The point of the <file!> tag is to have relative paths from absolute paths. This is because with the menu, I am sharing the site menu and tools menu in 30 different pages. If everything was trying to use paths as you describe, none of them would work. As a quick example, I have an index.html in every directory... But it would only take you 5-10 lines of code to add another tag (or replace this one) which does what you say... that's one of the strenghts of remark.r you prebuild html tags and they get executed when they are persistently and recursively encountered... which takes up less space than putting actual rebol code between the brackets..
> And why not use Rebol values? Like writing: > > <img src=%img.gif>
It actually is possible, it gets converted to a string right at the start of parsing. I do have an <img!> tag, here's how its used: <img! %path/file.gif> can't really be easier. ;-) and for links <link! "path/file.html" "Press Here"> or <link! %path/file.html "any html stuff <img! %path/file>"> it might be improved to expect an image (and build up the <img> tag by itself) when a path is supplied for the second argument, like in... <link! %path/file.html %path/file> -MAx
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted