You're viewing old version number 4. - Current version

2 min

Add client-side Textile markup editor

update 21aug2013: have now tagged this as #resolved. I'm going with the splitscreen setup that is currently in place. No need for a live preview editor on the client side right now. I have auto-save implemented.

Some new, interesting code found at Hacker News on Aug 12, 2013:
http://jakiestfu.github.io/Medium.js/docs

update 7aug2013: have decided not to use a live preview editor for now, since I support both textile and markdown, and at the moment, I don't want to support two live preview editors. plus, i have created my own custom formatting commands over the years that can only be viewed when processed on the server. and the live preview display in the right pane is distracting to me when I'm typing in the left pane. i prefer my addition to center the typing window and then go back to split screen when the preview button is clicked. so I've created my own custom split screen mode. have now tagged this as #todo_later.

either a wysiwyg editor or something similar to ghost's planned editing environment.

this would be for the enhanced blog post editing display.

update 9June2013 - top 2 choices

May implement both of the above along with my very basic "enhanced" version, and test or use all three to see which one I prefer.

http://www.buildingwebapps.com/podcasts/79339-using-textile-markup-plus-in-place-editing

http://www.456bereastreet.com/archive/200612/forget_wysiwyg_editors_use_wysiwym_instead/

http://www.wymeditor.org/

Timer

This may be useful for auto-save:

http://stackoverflow.com/questions/2430175/what-is-the-best-jquery-wysiwym-textile-editor

Markup Languages

I've been using Textile since 2005 when I added this Perl module to my Parula code that become the wiki area at ToledoTalk.com. I did not like the standard wiki markup, and I found Textile, which was the syntax used in Texpattern, which is a CMS/blogging tool.

I'm unsure if I looked at Markdown back in 2005. Textile contains more syntax features or options than Markdown. I use too many of these other Textile options to switch to Textile.

Markdown has some easy to learn and use syntax, but I still prefer the Textile syntax, which is also easy to learn and use. The heading lines in Textile are easier.

And I've added my own custom, Textile-like commands, such as:
br.
hr.
q./q..
tmpl./tmpl..
code./code..

plus:

[ [post name to link to]]
{ {text from another post to embed}}
{ {feed=url to rss/atom feed to embed}}

Markdown gets all the attention by the geeks, probably because it was created originally as a Perl module by a popular blogger about Apple products.

read more at:
Markup Languages - Textile and Markdown

#resolved
#junco
#editor
#markup

From JR's : articles
440 words - 3201 chars - 2 min read
created on
updated on - #
source - versions

Related articles
Resolved - Add client-side Textile markup editor - Aug 21, 2013
Resolved - Add Markdown support - Jul 02, 2013
Resolved - Test text for the Textile live preview editor - Aug 21, 2013
Resolved - Junco files to move into production - 6Sep2013 - Sep 06, 2013
Testing fenced code block commands - Sep 23, 2014
more >>



A     A     A     A     A

© 2013-2017 JotHut - Online notebook

current date: Nov 15, 2024 - 12:03 a.m. EST