On Mon, Aug 31, 2009 at 6:43 PM, Kevin<[email protected]> wrote:
>
> Do you plan on updating the help system pages in an upcoming release?
>
> For example, when you use help and then select Editing Notes, you get
> a page that has some markup rules.
The content of the help file is found at site.help. You can customize
the content as desired. Just be careful about editing the page, so you
don't mess up the help system. You can even create subpages like
site.help.functions, site.help.commands for your users or anything you
like. To link to them from the edit notes page, use links like
[[{p}&help=help.functions|Functions]] or
[[{p}&help=help.commands|Commands]].
The idea here was to have a simplified scaled down help file available
for users--not a cheat sheet for admins. You will notice if you logout
and add &help to the url, all you get is the editing notes page. It's
only when logged in as admin you get the fuller screen. I'm thinking
someday, someone will write a nice little help system for users and/or
admins, and make it available as a plugin. Right now, we just have a
very raw bones start. But the ability to tap into the source code like
this is quite useful.
> Many seem to be only line orientated like:
>
> <center>text</center>
>
> Works but
>
> <center>
> This is test on a line
> This would be a second line
> </center>
>
> Doesn't.
Hmmm. This is a very easy fix. Don't know why we never did this
before. I just added to the core for the next release. In the
meantime, you can get this result by changing line 54 of markups.php
to this:
MarkUp('block', 'align',
'/(<|<)(left|right|center|justify)>(.*)(<|<)\/\2>/Us', "<div
style='text-align:$2;'>$3</p>"); // l, r, c
> Same thing for something like @@monospace text@@.. Works okay on one
> line, but not multiple lines.
This is true, and probably not fixable in the core. The reason is all
these font-styles (**, //, ||, @@, etc) are designed to be shortcuts
for at max one line and therefore don't require a closing tag. You
could make an argument that allowing divs like this is a better design
plan, but it would break a lot of sites using the existing system. I
know it would cause me significant troubles to switch now.
However anything in BoltWire is customizable.
> Looking for ways to mimic forum behaviour which would work with
> multiples of lines like:
>
> [txt] [/txt]
> [code][/code] etc...
>
> (you can tell I'm used to BBcode)... :-)
I'm not very familiar with BBcode, but it is certainly possible to
generate your own markup rules like these and drop them in a plugin or
config file. Are you familiar with regex? It's a bit tricky, but I
could probably help you get started if you to take a stab at
developing something in your site. One advantage is you might be able
to import a bunch of forum posts without having to change the
markup--if we can develop a BBcode compatible set of markup rules.
> Tried using <pre> like:
In BoltWire, pre does not escape the content.
> While writing this up, I took a look at the markups.php file and found
> a possible solution to the code one...
>
> BOLTMcode, which uses <code> </code>. Tried it for the same info
> above. But this doesn't seem to be in examples of many of the pages.
Generally, I use <box> if it doesn't need to be escaped, <code> if I
don't want the markup processed. If you want the code to look
monospaced, its simply a css issue. Open up your style sheet
(code.style), skip down to the .code class, and add this:
font-family: monospace;
That should get you escaping and monospaced together. But again, if
you want custom markup rules that's all doable to in BoltWire.
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
-~----------~----~----~----~------~----~------~--~---
