[twdev] Re: add viewport macro to core?

2018-02-20 Thread Simon Huber
Hi Riz,

IMHO, shouldn't we add them as a part of existing $:/Info tiddlers? That is 
> where it is expected, right? If we do that, third party themes which 
> radically changes outlook by differing Pagetemplates can make use of it. 
> Please consider if not too late already.
>
> I used $:/state tiddlers because they don't trigger a save-wiki process
If you save a wik html file -i in my case on chromium - a bottom download 
bar appears, that causes a page resize and another dimension change which 
causes it to save again
with auto saving enabled this could be bad

I think it's not too late to change anything but the $:/state tiddlers 
seemed best to me

Simon

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/1cccb817-2eb1-4769-9cd0-41dd4577f0a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] Re: add viewport macro to core?

2018-02-20 Thread Riz
IMHO, shouldn't we add them as a part of existing $:/Info tiddlers? That is 
where it is expected, right? If we do that, third party themes which 
radically changes outlook by differing Pagetemplates can make use of it. 
Please consider if not too late already.

sincerely,
Riz

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/13608af9-9aa2-472e-bf1d-efea0009b776%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] connecting tiddlywiki classic and web app

2018-02-20 Thread Sebastjan Hribar
Hi all,

I've been away from tiddly wiki for a few years now and now I'm trying to 
expand one of my wikis.

Use case: connect a tiddlywiki with a web app via API calls.

Process: 

POST request from tiddly to web app

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/c8f2a66a-e310-4b31-beb8-8d8b195d31be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] Re: Backend protocol in TW5

2018-02-20 Thread joearms
I did some more poking around - my current problem is understanding how the 
first page is built.

It appears that everything starts by expanding 
$:/core/templates/tiddlywiki5.html

If my backend is not written in JS I'll have to write code code to expand 
this file.

Question is - is this easy? I guess it depends - hopefully the expander 
does not do tricky
JS things (this would prevent easy porting to non JS backends)

>From the point of view of porting the backend to a different language than 
node
a pre-computed header would help (ie like a minimal empty.html) page.

Is there a smaller subset of TW5 (ie smaller than empty.html) which 
gets you to the point where only get/put tiddler requests can be 
processed???

Cheers

/Joe



On Sunday, 18 February 2018 16:07:47 UTC+1, joearms wrote:
>
> Hello,
>
> I'm running the node backend downloaded from 
> https://github.com/Jermolene/TiddlyWiki5
> and was wondering exactly what the protocol between the browser and 
> backend was.
>
> At a guess it's JSON over HTTP (I might be wrong) - is the protocol 
> *specified* somewhere
> or do I have to read the code (if so where?)
>
> Is there a way of tracing and dumping to a file all the messages between 
> the browser and node
> so I can see exactly what is happening?
>
> Cheers
>
> /Joe
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/98c4d7f8-0ba5-4880-8b0f-4cb25da76dc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.