Forum - BBwhat?

Home pageGames databaseResourcesUsersVariousAffiliates / Linksabout / features - wip - forum

BBwhat?

threads list

by andread
# 6 days and 12 hours ago (updated 4 days and 22 hours ago)

I was wrong about not choosing a widely known syntax like BBcode.
Moreover, BBcode has a "stronger" syntax than the one I used, being easier to parse, and less error prone.
I could add BBcode parsing (without installing libraries) along with the actual parser (they should not collide) and later convert all the 16699 articles to the new standard.

This is the related Googlecode page:
http://code.google.com/p/uvl/issues/detail?id=15

Well, I could list my owned Nintendo platforms casually:

Gamecube
Wii
Nintendo DS

Or sorted by preference:

Wii
Nintendo DS
Gamecube

As you can argue, I'm using various BBcode tags right now!
I've implemented just the basic ones, I'll try to add the missing ones and convert our custom UVL tags (gameid, etc) too.
~~While in beta, remember to type [bbcode] somewhere inside the text to switch to UVLcode to BBcodes~~.

Bye,

by Sanguine
# 6 days and 10 hours ago

Random note: should be replaced with in the final HTML output because the former is deprecated, IIRC.

by andread
# 5 days and 22 hours ago

Spoiler test:

And (finally!) with custom titles:

- I've now used instead of as Sanguine suggested.
- When fully operational, HTML tags will not be stripped away too.
- You do not need to type [bbcode] to enable it anymore, now I check for [ b ] , [ i ], [ url ], [ img ], [ color ] and [ spoiler ] to enable BBcode parsing.

by Sanguine
# 5 days and 10 hours ago

Remotely related to this... you might want to customize the "standard" wiki labels at code.google.com/p/uvl/adminWiki :) Same for the other labels.

by Zerothis
# 5 days and 3 hours ago

The new spoiler seems to break when a carriage return is used inside

by andread
# 4 days and 23 hours ago

Fixed, thanks.
Now I know what the "s" at the end of a regular expression means :-)
http://www.regular-expressions.info/dot.html

To test the [ code ] tag, here we have the two regular expressions used to match a spoiler:
/\[spoiler\](.+?)\[\/spoiler\]/s /\[spoiler\=(.+?);(.+?)\](.*?)\[\/spoiler\]/s

by andread
# 4 days and 19 hours ago

Note, it is ok if you wish to thest the new BBcode, but it is not necessary to edit all the post to upgrade from the old to the new one.
I'll do it once for all at the end.

by andread
# 4 days and 18 hours ago

Two ways to quote, with [ quote ] ... [ /quote ]

The new spoiler seems to break when a carriage return is used inside

And with [ quote=Name ] ... [ /quote ]

Quoted from Zerothis:
The new spoiler seems to break when a carriage return is used inside

This is some text following the quoted text...

by Sanguine
# 4 days and 17 hours ago

re: re:

Quoted from Andrea:
Two ways to quote

Just remember to make the quote button in articles produce the new bbcode with author :)

by Sanguine
# 3 days and 20 hours ago

[ code ] should not add any newlines by itself. Inline "code" is impossible to write now.

As in, I can't say [spoiler] in middle of the text without [ code ] breaking the text completely.

The produced HTML looks correct, so I assume the default < pre> styling has some issues.

Suggestion: substitute < pre> with < code> (this needs the regular s in there, though) :)

by andread
# 9 hours and 30 mins ago

This is underlined

This text is 75% smaller
This text is 200% bigger

by andread
# 8 hours and 51 mins ago

Looking at how Google wiki parses the [ code ] tag, now I use < tt > instead of < code >
TT (teletype) is in-line, while CODE is a block element.

So this is a test of mixed code tags.

The spoiler tag is much more complex and I doubt we'll have it in-line.

threads list

Welcome new user!

You can create a free account to vote, review, tag games, add images, view galleries and more.

Universal Videogame List - www.uvlist.net