World: r3wp

well, I can remove them and make a part 2 tutorial? such as it is 
now, the code is pretty usable, I think. But it's far from perfect 
in terms of capability, so do we want perfect code across a few examples 
or just this one tutorial?

There's never any such thing as perfect code .. better to get something 
up, and let others build on it .. paraphrasing Isaac Newton

I've set up mediawiki at http://compkarori.com/rebolwiki/index.php/Main_Page
and will see how it goes.

Currently there's a sql error on updating or creating a page, but 
you can ignore that it seems as the page changes are made.

The advantage over Vanilla is that changes can be rolled back using 
the mysql database ...

PS: mediawiki is used to drive wikipedia.

I know mediawiki, as I use it for the Amiga AWeb Webbrowser. be careful 
with spammers....

that's why I have made logging in obligatory to edit pages

otherwise I have found scripts generating spam

yes, they can get pretty nasty, destroying contents and things like 
that

spam search bots create lots of junk in the Vanilla sites

I think my panes cookbook example is ready for one last review: http://hmkdesign.dk/rebol/panescookbook.html


I've removed some unnecessary bits about styles and I've added references 
to the User preferences window in the rebol/view 1.3 desktop

One point that would make it simpler : you didn't used 'of keyword 
for your tog style.

'of keyword allow to group toggle, radio or checkbox in order to 
reset others while you set one.
Like this you don't need 'update-tabs functions :

main: layout [
  space 2 origin 4
  across

  style pane-tog tog of 'panels		; Just to avoid puting {of 'panels} 
  in each tog lines below
  pane1-tab: pane-tog 100x30 "Pane 1" [show-pane pane1]
  pane2-tab: pane-tog 100x30 "Pane 2" [show-pane pane2]
  pane3-tab: pane-tog 100x30 "Pane 3" [show-pane pane3] return
  content-pane: box 300x200 return

  btn white "Save" ; Save and Apply are used here for decorative purposes
  btn orange "Apply"
  btn sky "Close" [unview]
]

amazing! I never knew this. I will rewrite it immediately.

how do you set the default pane?

We learn something each day :)

add "data true" to the default tog

works. bleh. >/(

:-)

I vote for getting VID stuff into the dictionary :-)

:)

tutorial updated now. 15% code reduction

Another comment : it's better to remove the offset at the pane creation 
rather than each time you show one. So use :

pane1: layout/offset [
  across
  text "Setting 1" field return
  text "Setting 2" field
] 0x0

...

You forget et remove the 'update-tabs call in the 'show-pane function.

(you did it in the full code, but not before)

The note talk about layout/TIGHT, but you did not use it before !!!!

where does the function show-pane come from?

I never knew of this word "of" - is that documented somewhere?

I see where the show-pane function came from so nevermind that question

its in the document

'of : If its documented, I don't remember where!

'of sets face/related

hmm... this will mean that the layout/offset is not the same as contents-pane/pane/offset

Chris do you know where that is documented at?  I though 'with was 
for setting face values.

I'm not certain if it is documented, I may have picked it up from 
eg. an IOS reblet.  But if you -- probe svv/facet-words -- you can 
see how it is used...

thanks Chris

a little suggestion.


the current cookbook page at , http://www.rebol.net/cookbook/, needs 
to have better tagging for sorting and searching purposes.

Example. An example can be tag to 'view', 'cgi', 'ios'


Or, we can break it up into 'logical chapters in a book'. Example

1. Part I. Rebol Basics
2. Part II. Advanced Rebol
3. Part III. /View Basics
4. Part IV. /View Styles
5. Part V. /IOS
6. List of Examples

I would vote for Easy, Medium, Hard, Guru sections

rebol.org library already have tagging for the scripts.


Both in terms of levels ["Beginner" "Intermediate" "Advanced"] as 
well as the domain ["cgi" "gui"] etc...


Perhaps there is a way to feed the cookbook examples into rebol.org 
and let the Library be the holding place for future cookbook examples.


There are '3 major' rebol sites (those with rebol in the domain). 
And they are rebol.com, rebol.net, rebol.org.

It is not incredibly clear whether certain docs should be in .org 
or .net. 


Other suggestion to consider is how can we leverage off works done 
in various sites and avoid duplication. Why not let rebol.org be 
the host for cookbooks as well?


I would think new comers will prefer to find both cookbook examples 
and other contributed scripts all in one location. Rebol.org also 
lets you search the mailing list.

REBOL.org also hosts articles -- and you can tag those for anything 
you want.  Might be a solution:
http://www.rebol.org/cgi-bin/cgiwrap/rebol/art-index.r

{so an article  could be tagged as [cookbook advanced ios] etc)

sounds good to me.


maybe Carl can comment or give the green light to put the cookbooks 
examples into rebol.org...

Or poeple could just write some more :-)

If I built a little page to create cookbook entries in wiki style, 
would you use it? It could be useful to have cookbook entries fixed 
quickly this way as I'm too pressed for time to release my tutorials.

Henrik --- One question: how good is the SEO on your site? Little 
point putting cookbook entries where they are hard for the world 
to find.


One idea: why not write a wiki-formatting to HTML function (you'll 
need it anyway) and donate it to the Library ?.....

.... REBOL.org can then accept cookbook entries and other articles 
in wiki format --- we already accept all other major formats: MakeDoc, 
NicomDoc, eText etc.  And we do have good SEO.

sunanda: they are not meant to be published on my site, I simply 
wanted to approve them here before handing them to Carl (which I 
actually have, but he hasn't responded other than "Cool!", but hasn't 
done anything :-)).


I was thinking about a very simple extension to webserv.r which simply 
submits a form to a modified makedoc2.r processor, which generates 
a page, sectioned so that you can edit small parts of it.

my basic thinking is that proper documentation is only possible through 
a wiki

BeOS had the annotated BeBook:  http://www.beunited.org/bebook/
 It was pretty useful  back when people were really coding for the 
OS.

The name of this group contained the text [web-publish], I changed 
it to the correct [web-public]

Tom started this group with a reference to
http://www.rebol.net/cookbook/requests.html

It's a set of outstanding requests for cookbook entries -- ie examples 
that people would like to see.

As he says.some have been done independently of the request, and 
published on the REBOLn Altmes or the Mailing List.

It'd be a great collective community New Year's resolution to clear 
some of the cookbook request by the end of the month (and that leaves 
plenty of time to enter the competition too)