Write a touring-complete BBCODE++ interpreter as a Greasemonkey extension.
Name:
Negrogandhi!jMrh9yh8I.2009-01-19 2:26
BBCODE is already perfect.
Name:
Anonymous2009-01-19 4:48
no u
Name:
Anonymous2009-01-19 4:50
Wait, wait.
We need to design it first.
It should be as terrible as the Sepples language itself.
Ideas welcome.
Name:
Anonymous2009-01-19 4:51
I THINK IT SHOULD HAVE SOME KIND OF FOR LOOP IN IT
Name:
Anonymous2009-01-19 4:54
Must use LISP-style syntax.
Name:
Anonymous2009-01-19 4:59
>>2
More spoiler features would be appreciated, though I don't know exactly what would be good spoiler features. And marquees would be nice. Come to think of it, I'd quite like LATEX support (like /sci/) too. And a [blink] tag.
Name:
Anonymous2009-01-19 5:03
Something to annoyingly obfuscate text to non-BBCODE++ users.
Name:
Anonymous2009-01-19 5:06
[BBCODE++]
[1][PRINT]EXPERT BBCODE++ PROGRAMMER[/PRINT][/1]
[2][GOTO]1[/GOTO][/2]
[/BBCODE++]
Name:
Anonymous2009-01-19 5:38
Will BBCODE++ have animation support?
Name:
Anonymous2009-01-19 6:00
support for functional programming plz
Name:
Anonymous2009-01-19 6:51
it needs to use voice commands - for those EXPERT PROGRAMMERS who don't have hands
As the first draft, I suggest to introduce: [instruction] tags [label] tags [goto] tags [variable][assign] tags [add][subtract][mul][div][mod] tags [int][bool][string][hex] tags [print] tags [if][condition][true][false] tags [equals][not equals] tags
a BBCODE++ application:
[instruction][label]start[/label][print][mul][int]4[/int][int]27[/int][/mul][string] - one hundred and eight[/string][/print][/instruction]
[instruction][variable][name]i[/name][value][int]0[/int][/value][/variable][/instruction]
[instruction][label]increment[/label][assign][name]i[/name][value][add][name]i[/name][int]1[/int][/add][/value][/assign][/instruction]
[instruction][if][condition][equals][name]i[/name][hex]a[/hex][/equals][/condition][true][goto]end[/goto][/true][false][goto]increment[/goto][/false][/if][/instruction]
[instruction][label]end[/label][print][b][sup]your[/sup] [sub]done[/sub][/b][/print][/instruction]
>>40
That completely doesn't follow the FUCKING pattern. BBCode tags are [tag]text[/tag], not [tag OTHER SHIT AND TEXT IN THE MIDDLE]AND NO CLOSING TAG.
>>46
why not just this? [list]lambda [list]x[/list] [list]+ x 1[/list][/list]
Name:
Anonymous2009-01-23 1:26
bampu
Name:
Anonymous2009-01-23 9:34
Instead of making BBCode Touring complete, we should have a markup language based on s-expressions, something like
(b We are (i about to study the idea of a computational process.) Computational processes are abstract beings that inhabit computers.) (m As they evolve, (b processes) manipulate other abstract things called data.) The evolution of a process is directed by a pattern of rules called a program. People create programs to direct processes. In effect, (sup we (sub (b conjure the spirits)) of the computer) (spoiler with our spells.)
Which would be parsed as
We are about to study the idea of a computational process. Computational processes are abstract beings that inhabit computers.As they evolve, processes manipulate other abstract things called data. The evolution of a process is directed by a pattern of rules called a program. People create programs to direct processes. In effect, we conjure the spirits of the computerwith our spells.
I wrote a few hours ago my own BBCODE edit tool
its limited to only one layer of BBCODE(i don't use more) to speed up typing:
typical example: "Forced Indentation "
1.Type out "Forced" not leaving a space
2.F12 bring a JavaScript prompt
3.I enter '1Indentation' and it converts it to BBCODE(using switch(num) for 8 codes)
4. the BBCODEd text is inserted with initial and final space added.
5.If i don't enter initial number it converts to cursive like ℱѲℛℭℇÐ ῙℕÐℇℕŦÅŦῙѲℕ
1) why [instruction] tags? It looks ugly and is unneeded. You should be able to put code anywhere. (or at least shorten instruction to line or something.
2) Needs more use of tag attributes, like [string name="player" value="Suusman"], and [label="LabelName"]. Not all tags have to close.
3) I propose an input tag. It will create a javascript input field with submit button and can be linked to a variable.
Here's an example. I'm too tired to re-write yours.
[input type="string" variable="name"][rem]Input[/rem]
[print]
[rem]Variables can be anonymous[/rem]
[string value="Hello there"][variable="name"][string value="!"]
[/print]
Excuse me if there are any errors, I'm quite tired.
The BBCODE++ language should have the same semantics as XSLT, the only difference being [ ] rather than < > brackets. This means it would be ENTERPRISE