[web2py] Re: markmin.js

2016-02-12 Thread Massimo Di Pierro
Yes. On Thursday, 11 February 2016 09:02:42 UTC-6, Niphlod wrote: > > hardly 99% it's another markmin version entirely :°°°D > > On Thursday, February 11, 2016 at 3:48:49 PM UTC+1, Massimo Di Pierro > wrote: >> >> For basic thinks like **bold**, ''italic'', ``code``, it is the same. But >>

[web2py] Re: markmin.js

2016-02-11 Thread Ron Chatterjee
So, how do we go about using it? May be an example can be posted using the forum app in appliance? On Thursday, February 11, 2016 at 10:02:42 AM UTC-5, Niphlod wrote: > > hardly 99% it's another markmin version entirely :°°°D > > On Thursday, February 11, 2016 at 3:48:49 PM UTC+1, Massimo D

[web2py] Re: markmin.js

2016-02-11 Thread Niphlod
hardly 99% it's another markmin version entirely :°°°D On Thursday, February 11, 2016 at 3:48:49 PM UTC+1, Massimo Di Pierro wrote: > > For basic thinks like **bold**, ''italic'', ``code``, it is the same. But > the python version does not support embedded html. The JS version does not > su

[web2py] Re: markmin.js

2016-02-11 Thread Massimo Di Pierro
For basic thinks like **bold**, ''italic'', ``code``, it is the same. But the python version does not support embedded html. The JS version does not support tables and nested lists. The python version uses the format [[label http:// image]] while the JS version uses the format image:http://.

[web2py] Re: markmin.js

2016-02-11 Thread Niphlod
what is not 100% compatible ? if we want to push this, we should promote it instead of relying on python code On Thursday, February 11, 2016 at 4:55:19 AM UTC+1, Massimo Di Pierro wrote: > > and the link: > > https://github.com/mdipierro/markmin.js > > On Wednesday, 10 February 2016 21:55:06

[web2py] Re: markmin.js

2016-02-10 Thread Massimo Di Pierro
and the link: https://github.com/mdipierro/markmin.js On Wednesday, 10 February 2016 21:55:06 UTC-6, Massimo Di Pierro wrote: > > I have a new version of markmin.js I recommend this over the python > implementation. It is better to render on the client because oembed does > not require setting