Re: [Tiki-devel] [Tikiwiki-users] importing content

It's on my own roadmap. I plan on adding a commonMark + DOM based plugin parser for a future project. I think leveraging other libraries and not having to create my own parser would make the project size manageable for me. That is unless someone else beats me to it. Its currently a few years away from me starting on it. So the defaults would be tiki-syntax and it would be an option to use this new wiki syntax if you want to. 

I also would not care so much about migrating content. So for my own project, it would be an additional parser option, others could create migration scripts if they have existing projects that they want to migrate to commonMark. 

It's a long-term goal for a project that is a couple years away. I've got lots to do in the meantime. Implementation of plugins might be limited, to begin with. I would focus on ensuring all the plugin I needed work well with both. Others not so much. Maybe I can throw an error if plugins have not been approved for CommonMark instead of supporting them all myself. If others need additional plugins, then they can ensure the plugin is working well with CommonMark before launching their project.

The community thinks its a great idea. Optional features in Tiki are wonderful. If it ends up overtaking and replacing tiki-syntax then that's wonderful. If it turns out to be only useful to a subset of tiki users, that's just fine. If I’m the only one who ends up using it… while we have a problem then.

Brendan



> On Oct 5, 2018, at 2:51 PM, Marc Laporte <[email protected]> wrote:
> 
> below
> 
> 
>> 
>> If I see there is interest amongst Tiki dev to do it, iow. seeing it
>> could be an important evolution in Tiki's lifetime, I'm ready to
>> help/learn as much as I can, but if all this is just a "nice add-on" or
>> as Marc wrote "not on my personal or business roadmap.", then I'll
>> leave it here.
>> 
> 
> Gour,
> 
> You started more than one thread on related topics in the last week.
> 
> I took the time to answer your questions, this time around, and a few
> years ago when you were evaluating Tiki.
> 
> I indicated that it was "not on my personal or business roadmap"
> because I get the feeling you are trying to pressure me or others into
> doing something. And I wanted to be clear about the situation. I
> repeat once more: "I understand this is very important to you. Tiki is
> a do-ocracy. So if you do it, it will happen."
> 
> Tiki is the https://tiki.org/FLOSS-Web-Application-with-the-most-built-in-features
> and people will always want more :-)
> 
> I ask that people stop telling this list that they think it's a good
> idea. We agree. Many people have requested and expressed support. Now,
> the only question is "who will do the work?"
> 
> If anyone is actually going to step up and make this happen: please
> proceed. Tell me your SourceForge username, and I'll grant you commit
> access: https://dev.tiki.org/How-to-get-commit-access
> If anyone has any more opinions that this would be a good idea and
> wants to be a tester: great!
> 
> In all cases, please coordinate on the relevant tasks:
> * https://dev.tiki.org/item6697-Markdown-support
> * https://dev.tiki.org/item6827-Tiki-writer-support-for-Pandoc
> * https://dev.tiki.org/item1413-Offline-Tiki-add-a-way-to-save-view-content-offline
> 
> 
> As for this mailing list, let's get back to general discussions on
> Tiki development and releasing Tiki19:
> https://dev.tiki.org/Tiki19
> 
> Thanks and best regards,
> 
> Marc
> 
> 
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel