On Mon, Oct 27, 2008 at 10:22 PM, Computist <[EMAIL PROTECTED]> wrote:
>
> On Oct 27, 11:13 pm, "alinome.net" <[EMAIL PROTECTED]> wrote:
>
>> I don't understand what you mean, how did you first create a page
>> without creating an empty page. "create a page" means "create a new
>> page"... then you write its name (code.skin.skinname), maybe other
>> data, and the content. Are you having any difficulties?
>
> A skin contains HTML code first and formost. When you click the
> "Create" button  a new, unsaved, page is created. That page will
> contain one field for enternign the file name of that page (and it
> should be code.skin.something).
>
> But it will also contain another, larger field, which is empty, and
> which is supposed to contain the content of the page.
>
> What I did, then, was that I – having allready copied a HTML source –
> pasted the source into that other larger field, and saved. Only to see
> that all the HTML code was "escaped". Meaning that I had created a
> very funny "skin" page.
>
> The trick is, to not fill anyhing into the larger field before saving
> the page. And only thenafter to start editing it.

This is probably a bug.  My guess is the copy action does not save the
content exactly the same way the edit action does (it is much more
complex, & has some special features).  I'll make a note and see if I
can't track it down. I do know I've had similar things happen to me.
The solution generally is simply to re-edit the page and then re-save
it. Usually the escaped code then disappears.

Anyway, here's some helpful info about the farm/skins folder. If you
create a skin you like, you can save all the appropriate files and
graphics to a sub folder, zip it up and upload it to BoltWire. Then
others can download it and extract it as a sub folder under the skins
folder. Let's say you called it stars: you would have
farm/skins/stars... and all the code.skin.stars, code.style.stars,
graphics etc in this folder.  Then to enable it you just set the skin:
stars in site config and the skin pages are automatically imported to
your wiki where they can be edited without modifying the originals. In
a nutshell, it's a very easy way to install a skin.

On the other hand, there's nothing wrong with Marcos suggestion to
just create the skin in the wiki in the first place. In fact Linly was
experimenting with installing them directly via a plugin file and that
works pretty well also.  It also has some nice appeal in that it uses
an already well understood and effective process.

By the way, to create a skin from an existing html page is pretty
easy. Copy it to your skin folder and rename the page. Replace
appropriate content with zones markers. Then enable it in
site.config--and bingo you're done. We need a good tutorial to show
easy this is. We really should have dozens of skins to choose from, as
there's lot's of free stuff out there that could be translated in
minutes. But I haven't gotten around to it. I am happy to help walk
someone through the process if they are willing to write up a
tutorial...

Cheers,
Dan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to