World: r3wp

Mike, I have a special script make-site, that uses the mdp-engine 
to generate web-sites. Take a look at my homepage, it's all done 
with this concept. Maybe it's something you want to check out.

Hi Robert, That is a VERY nice site.  I am continuing this look at 
NoteREB because it manages the source and the tree structure for 
me. For what I want, a tree structure is important.  This approach 
can use makedoc2 or any other variation to make-doc the page.  The 
recursive tree approach combined with any already written make-doc 
function makes it work well so I'll  be done soon  then will have 
a longer look at your site and approach. Thanks.

The make-site approach is based on a directory tree on your disk. 
All path's you see are actually directories, and each dir has only 
one file, an index.html That's why you don't have to hack in any 
document name.

Mike, that Treemenu looks like the same one a site that I now frequent 
uses at http://www.peshitta.org/Which is good but I need something 
that might be a building block to a full blown viewer at some point 
in the future.  For example there are other bible viewers such as 
e-sword but I want something that can support additional book names 
and might make the makedoc extended to support a format as that and 
maybe make a conversion tool that will take some of the popular bible 
formats and output them to text and rthen back in through a tool 
and output the makedoc format so that the output is still compatible 
with makedoc.

I have been inspired by the make-doc line.  Robert's rendition is 
fantastic.  Love the whole site in one file thing.  Keeping the CSS 
out of the rendered html is good, using classes.


MDP-Browser sounds really cool.   a makedoc/spec browser for makedoc 
formatted scripts.


I have been playing with a document format that I call nulldoc, which 
is mostly a set of generaly rules about how plain text documents 
have been formatted traditionally, or how plain text copied from 
a web browser can look, and I started developing a set of broad regular 
expressions to markup plaintext.


based more on what I wanted than what I actually had, the rules I 
came up with go something like:

two blank lines begin a new nulldoc document (segment)
spaces/numbers/letters/symbols represent lists.

tabs/spaces at the beginning of the line denotes code/hierarchy. 
 

tabs that are trapped by non-space on both sides means tabular data.


I differentiate between code and hierarchy indentation by short-circuiting 
code switch with #:


	code section

#	numbered section


I wrote a web page that reads the KJV aloud using an MS Agent character. 
  Used a control from MS for a menu   I had it voice-activated, but 
that was a drag so I used "web navigator control"  stupid name for 
a menu.  I think it's still up at http://members.cox.net/rovingcowboy/kjv/
 probably won't speak unless you have sapi 4 voice installed, though.

What part of the code of makedoc lets me change the individual lines 
being written to 'out?

I'm using a new emit-verse function I created but want to for example 
change the line to display multiple colors and formatted text on 
one line

For example if I post a verse such as John 1:1 "In the beginning 
was the Word......"  - I want to be able to format the book and verse 
separately from the verse text but still group it together in a \verse 
/verse type output

I'll keep looking over the code until I find where to put some parsing 
in.

This is a modified version of the outputter (embedded -- no template, 
no toc).  It does a full parse of each line: http://www.ross-gill.com/w/xhtml/xhtml.html

Paul

If you want to stay with some minor changes to makedoc2, then just 
copy what is provided for NOTE.
Add your verse to the data

\verse author verse
content text
/verse


This is assuming author and verse will be text strings (no spaces). 
Unlike NOTE you need to parse the text after \verse to get the two 
parts so that you can plug them into the output where you like.

Note uses text-line:  [any space copy text thru newline]

which puts everything on the line from the identifier tag \NOTE into 
the variable 'text


One direct way to get the values author & verse from the line is 
by reparsing what text gives you 
that is you let the \verse processing work the same as \NOTE


  | "note" text-line (emit note-in text)   ; this is an existing line

  | "verse" text-line (emit verse-in text) ; this will be added to 
  support verse
		
		note-in     [emit-note doc/2]    ; this is an existing line

  verse-in   [emit-verse doc/2]    ; this will be added to support 
  verse

emit-note then has an emit-verse parallel

emit-verse: func [text] [

 words: parse text none   ; Because text-line was in the rule for 
 verse it contains author and verse

 emit [<div class=verse-box><p class=author> words/1 </p> "&nbsp; 
 " <p class=verse> words/2 </p>]
]


and because you should handle the /verse tag similar to /NOTE which 
should close the html table and the div.

In the above that author and verse are defined as classes so you 
can leverage stylesheet independently of makedoc.

Does \note wrap text?

Mike - I have already kinda did like you said as I somewhat copied 
note but made a new verse type.  The thing that looks like would 
make madedoc better (might have it already) if if each item could 
be parse with styles also.  For example - come up with a way to parse 
one single line item into 3 parts but format each part different 
with different color for this and different font for that but have 
it still be able to be in the template.

Paul, I don't see how makedoc can do that because one of the goals 
was to having simple tagging where the input source is very readable. 
For these the line prefix (===, ---, ... etc) is that simple tagging. 
To be able to differentiate any value you would have to tag it independently 
and a general template can't know what you want to do.  

If you change the base makedoc to use an external stylesheet instead 
of the embedded styles in the template, you are a long way to getting 
what you want. Combine that with the few special tags you need and 
you can accomplish a lot within the design goals noted.

Thanks Mike

Surrounding text with "\verse" and "/verse" looks just like XML.

<verse> author verse
content text
</verse>

hello, is make-doc code still accessible from Desktop in the 1.3.x 
versions?

It's on REBOL.org, so it's available from the Viewtop in the public/library 
folder.

thanks

A quick one for the makedoc pros: How do you tell makedoc2 to not 
make a table of contents. I think it has something to do with no-toc 
but...

=option no-toc I think

Henrik, =options no-toc   And thanks.

henrik exactly  :)

no-toc disable the toc creation in the HTML output

Just a suggestion for Make-doc.. using some form of markup that would 
co-exist with CSS  check out http://www.csszengarden.com/

Done -- http://www.ross-gill.com/make-doc/

how am I supposed to write URL's in MAKEDOC2?

=url http://www.rebol.com?Dunno, let me look ...

that doesn't seem to work

Isn't is supposed to be

=url http://www.rebol.comThe Main REBOL Site

doesn't seem to work in Makedoc2

hmm, using Chris' formatter, I really do use: =url http://www.rebol.com
Rebol

the sdk has this ..


If you need to contact us regarding problems with this distribution,

please use <A HREF="http://www.rebol.com/feedback.html">http://www.rebol.com/feedback.html</A>.

no, looks like it doesn't work.

ah, it does work

I think it only works at the start of a line, not midway through 
one.

that's true for all of those =directives isn't it ?

I think so -- but =url is a natural to use halfway through a sentence, 
so it's easy to make that mistake.

Correct, all the =... stuff onlin works on the start of a line. MDP 
can handle inline-URLS with =url http://...Text for link=

The REBOL MakeDoc Page

 - Updated 27-Jan-2005 ... /  "The MakeDoc Standardization Project" 
 - Updated 26-Jan-2005 ... Is there any activity left regarding those 
 project ?

At work, we use those formats intensively: for project docs, for 
official documents, even for generating psychotechnical tests skelettons 
in XML dialects... So it would be great if a standadization could 
take place, keeping the best of the two worlds MD2 and MDP.

hmm, I wonder how do you aproach printing .... I use Chris' online 
make-doc version at ross-gill.com, and it has strange metrics with 
IE, not to mention Mozilla - it screwes it up (if I want to have 
it with background) ... but maybe the cause is my pdf printer driver 
...

Well, I didn't feel any trouble using PDF-factory and printing to 
it. The process of savinf documents is really simple. Write the doc 
(MD2 or MDP) / generate HTML / print to the PDF-generator / save 
the PDF and publish doc :-)

savinf > saving

I just did not get satisfactory enough result .... but I wanted to 
print with background ...

how did you did it ? did you set the background using the css style 
sheet, or did you address it right into the html code ?

stylesheet imo .... but the result was bad in mozilla ...

In the same area, there is also my NicomDoc: http://home.tiscali.dk/john.niclasen/nicomdoc/

I think, my approach has some advantages over both MD2 and MDP. I 
convert to/from an internal XML-kind of format called RebXML, which 
is much easier to work with, when making importers/exporters to different 
formats. RebXML is defined here: http://home.tiscali.dk/john.niclasen/rebxml/

I'm not sure, if anyone else found my ideas to be usefull, when I 
talked about it here half a year ago, and I haven't have much time 
to do more with NicomDoc, but it's not a dead project.

And don't let the XML part acare you away, it's NOT XML, as you know 
it, just the good thoughts from XML. RebXML is based on blocks, words 
and strings.