Sandbox archive

Question

This post exists purely to house answers formerly attached to the formatting sandbox. You can safely ignore it.

Answer 1

Answer 2

And this is a...

Spoiler!

Answer 3

Multi-line spoiler:

Spoiler line 1 (note the two spaces at the end of this line and the next)

Spoiler line 2

Answer 4

URLs cannot contain parentheses?

Is it the space?

It works with urlencode though

Answer 5

testing slashes escaping in backticks code in answers \, \\ and \a, \\a

Answer 6

Code:

this is
a test

Result:

this is a test

Answer 7

Testing markdown. Thanks Arjan

unfunny.

_unfunny.

Oh gee look, you can so too underline in Stack Exchange sites:

 ̲u̲n̲d̲e̲r̲l̲i̲n̲e̲ ̲

 ̳u̳n̳f̳u̳n̳n̳y̳

 ̳u̳n̳d̳e̳r̳l̳i̳n̳e̳ ̳

  ̲̅M̲̅C̲̅M̲̅X̲̅C̲̅I̲̅X̲̅ ̲̅

  ̲̅m̲̅c̲̅m̲̅x̲̅c̲̅i̲̅x̲̅ ̲̅

Answer 8

Answer 9

Mouse over the left of the tower of hello

Yay you can follow instructions hello

Apparently <kbd> is immune to spoilers

hi

hi again

hi yet again

potato

why is this text drifting out

help

! spoilers don't work now?

! hey that's messed up

---

now they do?!?!

Answer 10

I've always wondered how to put a backtick in a backtick, now I know. Use 2 backticks as delimiters. ``` `.

SELECT `a` from `table` where `b`=`c`;

Answer 11

starts with codez

w00t woot

Answer 12

<pre><code> has highlighting too:

Look ma, <em style="xyz">highlighting<em>!

Answer 13

Testing magical links to questions RegEx match open tags except XHTML self-contained tags and answers https://stackoverflow.com/a/1732454/851811 using the Share button.

Answer 14

http://lmgtfy.com/?q=formatting+sandbox

http://jsfiddle.net/

Answer 15

Click here to stay at this page

Answer 16

what is this magic dust that causes things to appear

Answer 17

Some code formatting for testing of the problem outlined here: What is Wrong with Code Formatting.

asyncTask.ContinueWith(task =>
{
    // Check task status.
    switch (task.Status)
    {
        // Handle any exceptions to prevent UnobservedTaskException.             
        case TaskStatus.RanToCompletion:
            if (asyncTask.Result)
            {
                // Do stuff...
            }
            break;
        case TaskStatus.Faulted:
            if (task.Exception != null)
                mainForm.progressRightLabelText = task.Exception.InnerException.Message;
            else
                mainForm.progressRightLabelText = "Operation failed!";
        default:
            break;
    }
}

This does not format correctly.

Answer 18

Just testing:

Code formatting doesn't work well with NO-BREAK SPACE

-38 y1  +  35 y2  +  31 y3  = -3047

  11 y1 + -13 y2 + -34 y3 = 784

  34 y1 + -21 y2 + 19 y3 = 2949

But works with space (ASCII 32)

-38 y1  +  35 y2  +  31 y3  = -3047

11 y1  + -13 y2  + -34 y3  = 784

34 y1  + -21 y2  +  19 y3  = 2949

Answer 19

>! hides all.

Answer 20

I'd like to see if this causes a formatting problem as described here (this answer is thus a word for word copy of this answer):

---

I generally get a bad feeling about code that has one view model directly communicating with another. I like the idea that the VVM part of the pattern should be basically pluggable and nothing inside that area of the code should depend of the existence of anything else within that section. The reasoning behind this is that without centralising the logic it can become difficult to define responsibility.

On the other hand, based on your actual code, it may just be that the ApplicationViewModel is badly named, it doesn't make a model accessible to a view, so this may simply be a poor choice of name.

Either way, the solution comes down to a break down of responsibility. The way I see it you have three things to achieve 1) Allow the user to request to connect to an address, 2) Use that address to connect to a server 3) Persist that address. I'd suggest that you need three classes instead of your two.

public class ServiceProvider
{
    public void Connect(Uri address)
    {
        //connect to the server
    }
} 

public class SettingsProvider
{
   public void SaveAddress(Uri address)
   {
       //Persist address
   }

   public Uri LoadAddress()
   {
       //Get address from storage
   }
}

public class ConnectionViewModel 
{
    private ServiceProvider serviceProvider;

    public ConnectionViewModel(ServiceProvider provider)
    {
        this.serviceProvider = serviceProvider;
    }

    public void ExecuteConnectCommand()
    {
        serviceProvider.Connect(Address);
    }        
}

The next thing to decide is how the address gets to the SettingsProvider. You could pass it in from the ConnectionViewModel as you do currently, but I'm not keen on that because it increases the coupling of the view model and it isn't the responsibility of the ViewModel to know that it needs persisting. Another option is to make the call from the ServiceProvider, but it doesn't really feel to me like it should be the ServiceProvider's responsibility either. In fact it doesn't feel like anyone's responsibility other than the SettingsProvider. Which leads me to believe that the setting provider should listen out for changes to the connected address and persist them without intervention. In other words an event:

public class ServiceProvider
{
    public event EventHandler<ConnectedEventArgs> Connected;
    public void Connect(Uri address)
    {
        //connect to the server
        if (Connected != null)
        {
            Connected(this, new ConnectedEventArgs(address));
        }
    }
} 

public class SettingsProvider
{

   public SettingsProvider(ServiceProvider serviceProvider)
   {
       serviceProvider.Connected += serviceProvider_Connected;
   }

   protected virtual void serviceProvider_Connected(object sender, ConnectedEventArgs e)
   {
       SaveAddress(e.Address);
   }

   public void SaveAddress(Uri address)
   {
       //Persist address
   }

   public Uri LoadAddress()
   {
       //Get address from storage
   }
}

This introduces tight coupling between the ServiceProvider and the SettingsProvider, which you want to avoid if possible and I'd use an EventAggregator here, which I've discussed in an answer to this question

To address the issues of testability, you now have a very defined expectancy for what each method will do. The ConnectionViewModel will call connect, The ServicePRovider will connect and the SerttingsProvider will persist. To test the ConnectionViewModel you probably want to convert the coupling to the ServiceProvider from a class to an interface:

public class ServiceProvider : IServiceProvider
{
    ...
}

public class ConnectionViewModel 
{
    private IServiceProvider serviceProvider;

    public ConnectionViewModel(IServiceProvider provider)
    {
        this.serviceProvider = serviceProvider;
    }

    ...       
}

Then you can use a mocking framework to introduce a mocked IServiceProvider that you can check to ensure that the connect method was called with the expected parameters.

Testing the other two classes is more challenging since they will rely on having a real server and real persistent storage device. You can add more layers of indirection to delay this (for example a PersistenceProvider that the SettingsProvider uses) but eventually you leave the world of unit testing and enter integration testing. Generally when I code with the patterns above the models and view models can get good unit test coverage, but the providers require more complicated testing methodologies.

Of course, once you are using a EventAggregator to break coupling and IOC to facilitate testing it is probably worth looking into one of the dependency injection frameworks such as Microsoft's Prism, but even if you are too late along in development to re-architect a lot of the rules and patterns can be applied to existing code in a simpler way.

Answer 21

Here is a link to a random .docx (now fixed)

Here is another and the linkifier is broke

Answer 22

test answer with at least 30 characters

see, look, 30 characters

blah blah more chars

Answer 23

n0 quallitee fltr!

tstng coments

Answer 24

Hoy ! This is a test !

La femme est un sujet sur lequel l'homme aime à s'étendre.

Answer 25

Answer 26

1. line of code
   another one
   

2. line of code in a different block
   

Nope, they don't go seamlessly.

Answer 27

#test { background:#f00; }

Answer 28

Banach-Tarski paradox

Banach-Tarski paradox

Answer 29

Testing an HTML link:

http://wayback.archive.org/web/*/http://onemillionpeople.com

Testing a markdown link:
(Presumably it is automatically URL encoded?)

• Simple URL still needs encoding
• [complex URL link](http://www.example.com/downloads/Some Band - En français avec des caractères spéciaux (2013) [7'' EP].zip)
• complex URL encoded already
• http://www.example.com/downloads/Some Band - En français avec des caractères spéciaux (2013) [7'' EP].zip
• [some spaces already encoded](http://www.example.com/downloads/Some+Band+-+En+français+avec+des+caractères+spéciaux+(2013)+[7'' EP].zip)
• Trips on non-ASCII chars

Link entered using the toolbar option: works great!

Answer 30

! Spoiler block testing! Hello world

! Spoiler block testing! Test me

!Spoiler block testing! Yet Another test

! Spoiler block testing!

Hello world

Spoiler block testing!

Test me

Spoiler block testing!

Yet Another test

---

block with paragraph breaks testing-  

Spoiler block testing!
 √√√√√√√√√√√√√√√√√√√√√√√                                  　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 hm, It's cheating I know...