asier to extend in the case anyone wants to
> develop support for another wiki syntax (btw, throughout the week I'll
> try to update [#2] with a link to Markdown support and a new section
> on developing an extension for supporting another wiki syntax)
>
> However, right now, the pla
to extend in the case anyone wants to
develop support for another wiki syntax (btw, throughout the week I'll
try to update [#2] with a link to Markdown support and a new section
on developing an extension for supporting another wiki syntax)
However, right now, the plain editor should be working only
gt; syntax displayed by the editor be chosen?
>
>>> Alternatively, you could just leave the whole build unchanged.
>>> And only load the markdown snippets on-top-of the defaults. Actually
overwriting them.
>>> In plain.jsp you could do this
->this is the full haddock-e
ou know way more on the editor / js in general, I feel
your approach is most probably the way to go. How would the wiki
syntax displayed by the editor be chosen?
best regards,
juan pablo
On Fri, Jan 14, 2022 at 12:51 PM Dirk Frederickx
wrote:
>
> Hi Pablo,
>
> Good to see how this
Hi Pablo,
Good to see how this is progressing.
Happy to help on building the markdown support into the editor.
The SNIP editor is build to be pluggable, and this would be a good test
case.
You should only provide a specific "Markdown.Snipe.Command.js" file.
Would you have a specifi
Hi,
last push completed markdown support on the WYIWYG editor. Right now
there's a markdown parser, a markdown renderer, a WYIWYG editor
renderer, and an html from the WYIWYG editor to markdown syntax
converter. [#1] has a bit more info on this.
The only item left, in order to have full Markdown
* markdown support, through either a
behaviour [#1] or through custom parser + renderer [#2].
The former is based on a js markdown compiler / parser, which stores pages
using JSPWiki syntax. The latter will store the
pages using commonmark flavour of markdown, using Flexmark. IIRC, it isn't
100
Hi Juan Pablo,
Would this change make it more "mainstream" to alter the wiki syntax
over to MarkDown? I was thinking of inquiring about the state of
MarkDown support, looked at the changes necessary to get it to
work as the default syntax and thought: no, not ready for prime time.
Th
v 12, 2017 at 9:41 PM, Juan Pablo Santos Rodríguez <
> > > juanpablo.san...@gmail.com> wrote:
> > >
> > > > Hi Dirk,
> > > >
> > > > lot of stuff to cover (meaning: long mail following), will try to
> > address
> > > > all the p
> > > Initial design
> > > --
> > >
> > > yes, the solution, as it is made consists on a MarkdownParser /
> > > MarkdownRendered,
> > > which acts as an alternative to current Parser/Renderer. There's no
> > support
> > &g
; > on user
> > preferences (or whatever). But that raises more questions, though: once
> the
> > page is
> > stored on a given markup, what happens when a user with a different
> markup
> > stored in
> > his/her preferences? The type of markup should be also sto
JSPWiki as a Markdown
> content-publising
> tool. For that flexmark is used, which does 99% of the markup parsing, so
> moving this
> to the client side would imply a totally different take on this. I'm still
> extracting markdown
> support from other custom code, so I expect that b
e as POC for evaluating using JSPWiki as a Markdown
> content-publising
> tool. For that flexmark is used, which does 99% of the markup parsing, so
> moving this
> to the client side would imply a totally different take on this. I'm still
> extracting markdown
> support from oth
this
to the client side would imply a totally different take on this. I'm still
extracting markdown
support from other custom code, so I expect that by Tuesday/Wednesday I'll
have it
uploaded to a github repo.
As it is now, once you commit to a markup style, you're set with that. At
least as a
starting
st of them are specific to our
> infrastructure (workflows, page storage), but the Markdown support is
> pretty agnostic to us so I asked if I could move it to JSPWiki, and I got
> my ok :-)
>
> In order to simplify things regarding code transfer I'll be putting it on a
> pers
I've could look at the POC. Most of them are specific to our
infrastructure (workflows, page storage), but the Markdown support is
pretty agnostic to us so I asked if I could move it to JSPWiki, and I got
my ok :-)
In order to simplify things regarding code transfer I'll be putting it on a
personal
16 matches
Mail list logo
