Re: writing content offline

I see two existing ways:

a) submit Tiki WikiPages and Articles by e-mail

b) install locally and send WikiPages (I do not really know how the 
feature or functionality is called)

or not yet existing, but nice to have

c) coding some kind of Tiki client for Linux and Android, optionally 
MacOs/iOS, Windows

d) creating some kind of configurable life-windows on a stick for PC and 
optional a boxed version for Android with PHP and mySQL included.

Just thinking loud.

Torsten


On 10/05/2018 03:39 PM, Marc Laporte wrote:
> below
>
>
> On Fri, Oct 5, 2018 at 6:56 AM, Saša Janiška wrote:
>> On Fri, 5 Oct 2018 01:08:22 -0400
>> Marc Laporte wrote:
>>
>>
>>> 15 years ago (!), we had this: https://tiki.org/wBloggar to use a
>>> desktop app to publish blog posts. The code is still there:
>>> https://sourceforge.net/p/tikiwiki/code/HEAD/tree/trunk/
>>> tiki-xmlrpc_services.php
>> That one looks interesting, but, afaict, still does not solve problem of
>> offline writing + using (some) standard markup,right?
>>
>
> I don't think I ever used. And if I did, it was 15 years ago so I
> don't remember how the feature worked exactly.
>
> My point is that there are precedents in that direction (using an
> external tool to publish to Tiki).
>
>
> Not that I want to prolong the discussion. But you could even install
> a Tiki locally, make it all nice there, and use this:
> https://doc.tiki.org/Communication-Center  Not Emacs I know, but it
> gives you the real interface while being offline.
>
>
>
>>> And in Tiki20, we'll an API for most Tiki features, for Federation
>>> (sharing data between sites) and BPMN 2.0:
>>> https://dev.tiki.org/Tiki20#Todo
>> That's new for me, but still, I only need ability to use standardized markup
>> for writing using my preferred (Emacs) editor.
>>
> I understand.
>
>
>>> You tried plugins for a few year, and now you want to move. It you had
>>> picked Tiki years ago, today, you wouldn't be thinking of a change.
>> Well, my personal site is small and not problematic at all, for my business
>> needs I have to create a new one and Tiki looks good, but my old content for
>> non-profit site is *still* in Textpattern CMS, so despite of exploring Tiki few
>> years ago, I haven't migrate to anything else.
>>
> ah, I see.
>
>
>>> Plugins just eat up your time:
>>> https://pluginproblems.com/Modules-Extensions
>> I agree with that and that's why I did eliminate Grav from my equation.
>>
>>> Instead, take the time you save and contribute to Tiki :-)
>> In another email you wrote:
>>
>>> Interesting to read the pros and cons of SSGs. I'd love Tiki to become a SSG:
>>> https://dev.tiki.org/Static-Site-Generator
>> and the above URL references https://github.com/sculpin/sculpin which says:
>> "Sculpin takes plain old text files (Markdown, Textile, etc.) and combines them
>> with Twig templates to produce a set of static HTML files that can be easily
>> deployed to almost any hosting platform."
>>
>> so if you can assure me there is possibility to write e.g.
>> (CommonMark|Extra) Markdown markup and use one's preferred editor
>> (Emacs, ST3, Vim,...) and create blog posts and/or articles (not so
>> important for other content, although it would be cool to use same
>> markup for everything) for Tiki, then I'm sold and, yes, I'll try to
>> contribute as much as I can (even learning some PHP) with full-fledged
>> enthusiasm. ;)
>>
>
> To be clear: your specific requests are not on my personal or business
> roadmap. It happens that I write offline, and I just copy-paste after.
> Even if I didn't know the syntax by heart, I would just write text and
> fix the syntax at the moment of publishing ( I do that when I need to
> use other platforms ). Takes a minute or two that you need to be
> online.
>
> I understand this is very important to you. Tiki is a do-ocracy. So if
> you do it, it will happen. If you don't have the skills to do it, you
> can try to convince a coder somehow. Hiring them usually works :-)
>
> What I can assure you is that:
> 1- A WikiPlugin (as I explained in another thread) would be accepted
> to the Tiki code base, and wouldn't be a lot of work (could be done by
> an intern)
> 2- The upcoming infrastructure improvements (ex.: Rest API) will make
> your use case easier, even if they are not done for your specific use
> case.
>
>
>
>> Btw, I'm also seriously considering to try and/or use WikiSuite - looks
>> terrific without too much admin overhead, no need to have nextCloud just for
>> calendars/contacts etc.
>>
> Super!
>
> On this topic, adding http://sabre.io/dav/ to Tiki is on the roadmap.
> It will replace our old WebDAV lib, and be used to add support for
> Calendars and Contacts.
>
> Our medium/long term plan is: http://wikisuite.org/JMAP
>
> Best regards,
>
> Marc
>
>> Sincerely,
>> Gour
>>
>> --
>> Therefore, without being attached to the fruits of activities,
>> one should act as a matter of duty, for by working without
>> attachment one attains the Supreme.
>>
>>
>> _______________________________________________
>> TikiWiki-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-users
>>
>
> _______________________________________________
> TikiWiki-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-users



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