Making markdown opt-in rather than default

i'm having a go at implementing the dumb version of this.
just drilling in to try and find out how you've implemented markdown...

rich your balsamiq ain't public or is gone?

ok getting there.

• with the db migrations, shall I assume the default (as set in db migration file) for comments and discussions is :uses_markdown, :boolean, default = true ?
  (to preserve existing markdown use)
  nb - in future, forms will have a tickbox whose default position is set by the @user.wants_markdown boolean

• i note in searches that motions use markdown too... presume implement here too

aside - noticed that when you click edit discussion then hit 'cancel', you get an ugly view : http://i.imgur.com/979Cp.png
repeating this sequence cycles the help message away again

@johnirving this link should work. Note the comments on that thread for suggestions of how to improve my mockup. Feel free to edit :)

As a general process thing, I think we want to maintain the 'Features' group as a place for discussing mockups and behaviour. Once the mockups are approved more-or-less then any technical 'behind-the-scenes' questions are probably better dealt with elsewhere, e.g. in the 'Code' group. The intention is to keep this group as accessible as possible, to encourage non-developers to participate in feature design.

Re: aside = that's a known bug

@johnirving that all sounds pretty good. I think we'll need to be careful about the way the user preferences for markdown are implemented on the context panel.

E.g.: if someone doesn't tick "use improved formatting" for the context (so user.wants_markdown == false), and then someone else goes to edit the context who has user.wants_markdown == true, then the markdown box will be unchecked. However, when they submit the edit we don't want the change to edit their user.wants_markdown preference to false. You see what I'm getting at?

@richarddbartlett hmm... I wonder about that process. It means that every feature will have two separate discussions. Could it not just be distinct phases where the first phase is accessible, and the second one isn't? I think eventually what you're saying will make total sense, but I wonder if it's a bit premature to implement it now.

@jonlemmon fair enough; let's try to keep the phases distinct though eh? i.e. try to keep techno speak out of the equation until after the mockup is agreed. I'll stop cluttering up this thread now because it's getting pretty inaccessible :P

@johnirving a few of us had a discussion about how to design this. let me know when you have a minute to discuss on skype.

by design i mean like "which button goes where".

this makes sense, but I guess has been done now with the little A in the right hand corning below the comment box? Or is that still turned on by default? (I can't remember if it was on or off when I first signed up).

Makes me think of something else though... how to archive or close a discussion? which is related to https://www.loomio.org/discussions/1106

@josefdaviescoates unless there's something funny going on, Markdown should be off by default for new users.

Personally, I'd like to move beyond Markdown relatively soon as part of an overall upgrade of the comment box: easy formatting, drag-and-drop images, preview-before-post, attachments, link preview, etc.

I reckon this is a RoR gem waiting to happen :)

Richard how would you feel about a editor like the following but with dnd image/file support?

http://samwillis.co.uk/pagedown-bootstrap/demo/browser/demo.html