Is there a wiki-style "Playground" on this site? [closed]

edit

quoting styles

Blockquote

PRE/CODE here
foo@bar:~/$ for i in blah; do echo harumph; done

Let's play with code!

Here is some code within backticks(0).

Does this mark as code? I = 5; Hope = 0; So = "period"

Yep, that works. Now for syntax highlighting?

ruby a = 5 puts "Superdog " + 5 a.each{|beach, ball| some = stuff = here puts "is important" }

Nope, doesn't seem to have support for syntax highlighting like on GitHub

Note to self: Maybe just file request w/upstream now...

New test: URLs that don't want to link!

Ordinary urls like to be linked:

• http://www.libreoffice.org
• ftp://example.org

Some URLs don't like to be linked:

• URLs with a hash in them:

  • http://productforums.google.com/forum/#!topic/docs/S6IkdnuH91E

• URLs with parenthesis:

  • https://en.wikipedia.org/wiki/Cheese_(software)

  • And with [ ] ( ) syntax:

    • cheese webcam software)

• What if the URL has a paren, just not on the end?

  • https://en.wikipedia.org/wiki/Cheese_(software)#References

Fixes? Workarounds? Hooray!

• Let's try to use the [ ] ( ) syntax!

  [http://productforums.google.com/forum/#!topic/docs/S6IkdnuH91E](http://productforums.google.com/forum/#!topic/docs/S6IkdnuH91E)
  

  • http://productforums.google.com/forum/#!topic/docs/S6IkdnuH91E

• For the paren on the end, use a backslash "\" to quote just that single character, like this:

  [cheese webcam software](https://en.wikipedia.org/wiki/Cheese_(software\))
  

  • cheese webcam software

• If the paren is not on the end, can we just slap parens around the whole shebang?

  [cheese webcam software - References section](https://en.wikipedia.org/wiki/Cheese_(software)#References)
  

  • cheese webcam software - References section#References)

Hmm... looks like a no. Let's try escaping that inner r-paren:

    [cheese webcam software - References section](https://en.wikipedia.org/wiki/Cheese_(software\)#References)

• cheese webcam software - References section

Code commenting styles -- what works, what doesn't work, etc.

    /* Some C-style code */
    #include <stdio.h>

    int main(void) {
      printf("hello, world\n"); /* End of line comment */
    }

C works pretty well.

Java?

    // Some Java code
    class HelloLibO {
      public static void main(String[] args) {
        System.out.println("Hello World!"); // End of line comment
      }
    }

Java looks pretty good!

How about Python?

    # A Hello-world function (with some extra stuff thrown in).
    def HelloWorld(s):
        print("Hello world")
        for foo in bar
          if passes(foo)
            print '%s' % foo
          else:
            print "Fails!"

Multi-line comments?

    """ Multi-line comment in Python
    probably isn't going to work right now
    """

No, not working too well.

LibreOffice Basic?

    ' This is a Hello World snippet.
    print "Hello, world!"

Hmm... the formatter hates the unclosed single-quote. Let's try again using 'REM'

    REM This is a Hello World snippet.
    print "Hello, world!"

A little better, but the comment is still being highlighted like code, not a comment. Let's try again, using either a C++-style or Bash-style comment.

    REM // This is a Hello World function.
    REM # Hopefully these comments will render as expected!
    Sub Main
      print "Hello, world!" REM # End of line comment.
    End Sub

Here's some more LO Basic as a formatting example (from this question):

    Sub Main
      Set thisBook = ThisComponent
      studentsSheet = thisBook.Sheets.getByName("Students")

      i = 0
      Do
        c = studentsSheet.getCellByPosition(0, i)

        REM // Stop creating sheets for students once we find a
        REM // row with no name.
        If c.Type = com.sun.star.table.CellContentType.EMPTY Then
          print "Exiting: Found row with no student name."
          Exit Do
        EndIf

        studentName = c.String
        sNew = thisBook.createInstance("com.sun.star.sheet.Spreadsheet")
        thisBook.Sheets.insertByName(studentName, sNew)
        i = i + 1

      REM // Sanity-check on looping forever. We don't expect 
      REM // to have over 1000 students.
      Loop Until i > 1000
    End Sub

Here's an upstream post about the code behind the syntax highlighting: http://askbot.org/en/question/3026/syntax-highlighting/

Looks like it's https://code.google.com/p/google-code-prettify/

Also see https://google-code-prettify.googlecode.com/svn/trunk/README.html -- looks like it might be possible to pass-along the language name and get a bit better highlighting. We might need to add a new language handler if LO Basic and Visual Basic use a different grammar.

Syntax test (fdo#1234) here (@qubit)

Testing linking behavior here:

fdo#1234

#fd1234

What other types of linking would be helpful? Possible sites include

• LO wiki
• (A)OO bug tracker

It would also be very helpful to be able to have shortcuts for default responses, such as:

• [fileabug] -> Please file a bug
• [download] -> Please download the latest build of LibreOffice
• [needinfo] -> We need more information about your particular question before we can answer you.