[tw] Re: Tree View Plugin for TiddlyWiki 5

[Dave]

Ok, I changed that 

/* LEFT MENU, FIXED IN POSITION */
.tgc-leftmenu {
 position: fixed;
 left: 10;
 top: 30;
 display: block;
 padding: 70px 0 0 40px;
 width: 25%;
 text-align: left;
 z-index: 99;
}


But it just dropped the top of the menu down a bit, not affecting the left 
border.  However, I did experiment by changing the z-index: 99 to 9 instead 
and that worked (not sure what z-index means, but it was the one that made 
room on the left side for the icons menu

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/03dfa7ee-66c8-41d0-9fc7-f4edf7fbeb8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Tree View Plugin for TiddlyWiki 5

[Dave]

Thank you. (would have said so earlier but forgot to turn on "email me 
replies" :)

On Monday, January 2, 2017 at 8:09:35 AM UTC-7, Ton Gerner wrote:
>
> Hi Dave,
>
> Sorry typo, replace 'top' with 'left'; sounds more logical isn't it ;-)
>
> Ton
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/47b076bb-5e0c-4711-80c3-a73f422fc826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: NoteSelf mobile app ( well, kind of)

[Greg Hodgins]

OK, on the Cloudant service page there is a Service Credentials.  Now I 
recall adding this at the beginning.  I didn't ever copy and paste the 
password/key in the view credentials in the first instance?  Regardless 
from a second machine and my mobile I can login with the service 
credentials and all appears well.  Changes sync across all three.

Still can't say I understand the multi-user aspect, which appears supported 
in some fashion given I can create and login with different credentials, 
but shutting down for the night.

On Wednesday, January 4, 2017 at 9:37:50 PM UTC-5, Greg Hodgins wrote:
>
> Well, I'm inadvertently exploring the security aspect.  So much for 
> thinking the GUID in the host name was the key to access.  On a second 
> machine I've tried both copying my working noteself.html file and 
> downloading a fresh one and configuring the CouchDB URL and remote database 
> name.  There is an offline button that I click (because I am clearly not 
> syncing) and I am prompted first with a green, what I assume is a Noteself 
> userID and password prompt for the remote database, and then browser pops 
> up with the same.
>
> I'm not sure what user ID to use.  The only password I created to my 
> knowledge was that associated with my cloudant account.
>
> Also the browser challenge comes up twice and on the second appearance 
> disappears on it's own accord while typing in the password.
>
> A little lost.
>
> On Wednesday, January 4, 2017 at 7:53:05 PM UTC-5, Greg Hodgins wrote:
>>
>> Hi Steve.
>>
>> Thanks Daniel.  I saw your initial NoteSelf press release :-) the other 
>> night.  I tried it mobile and wasn't truly understanding everything you 
>> were trying to achieve.  Initially I thought it was all about the launch 
>> icon on the device making more more like a native app.  Cool, but wasn't 
>> enough to keep me that interested.
>>
>> Then I read a little more in some other posts here and see you are 
>> interested in solving the mobile user experience.  Again, not a huge 
>> concern to me currently BUT something I am definitely interested in.
>>
>> This also led to some more research as to what this couchDB reference 
>> was.  Seeing some more posts including Steve had me checking the difference 
>> (and now understanding relationship) between pouchDB and couchDB.  Now I'm 
>> really interested.
>>
>> Of course much of this is covered here. https://noteself.github.io/. 
>>  Sometimes it's just information overload - although I think there are some 
>> things that could be made clearer off the top.  That said, there are so 
>> many different audiences to cover it is almost impossible.
>>
>> Long story short, I get it - I think.  NoteSelf uses a local in browser 
>> NoSQL database called pouchDB that supports 2 way replication with couchDB.
>>
>> Like Steve I setup a Cloudant couchDB.  Pretty simple.
>>
>> Steve, two things, your couchDB URL is in the URL of your DB admin page. 
>>  It is also visible in Account, Virtual Hosts.It is the name you could 
>> optionally replace with your own host name.  eg: 
>> c4e83ce0-e302-42a2-8d3d-5cd3a8ae59e2-bluemix.cloudant.com.  
>> Obviously I modified above, but hopefully you will recognize that.
>>
>> With respect to your error check the CORS tab on the same account screen. 
>>  While I don't want to leave all domains (*) as currently selected, I am 
>> not sure how to code for a file hosted browser session.  Ultimately even 
>> some kind of local http: host is probably necessary with a host name to 
>> configure restricted CORS from.
>>
>> With those to things I got NoteSelf replicating as advertised.  Very cool.
>>
>> I'm certainly wanting to explore the security aspect a little more.  I 
>> gather that the GUID URL is one form of security and anyone accessing that 
>> URL has read/write access.  I hope you can add a little more security in 
>> that you appear to be able to set the permissions on the database and then 
>> generate API keys.  I'm not sure how/where you embed this in NoteSelf, 
>> assuming you do.
>>
>> Have to run, but will be back.
>>
>> Good luck.
>>
>> P.S.  Exploring this as an alternative to my current node.js hosted on 
>> Google Drive approach that isn't proven sound in any way. No version 
>> control and not multi-user, that that NoteSelf is either me thinks.
>>
>> All the best.
>>
>>
>> On Thursday, December 29, 2016 at 4:15:20 PM UTC-5, Danielo Rodríguez 
>> wrote:
>>>
>>> On their continuous effort to deliver cutting edge features to you, the 
>>> NoteSelf team (formerly known as just me :D) is delighted to announce that 
>>> *NoteSelf online 
>>> edition* is now an offline-first experience.
>>>
>>> This means that you will be able to use the online edition *even if you 
>>> are offline*, isn't that mind-blowing ? 
>>>
>>>
>>> Wait, there is more! 
>>>
>>>
>>> Being an offline-first application allows you to use NoteSelf *like* a 
>>> native mobile app. This mean that you can have it on your *app launcher 
>>> with 

[tw] Re: NoteSelf mobile app ( well, kind of)

[Greg Hodgins]

Well, I'm inadvertently exploring the security aspect.  So much for 
thinking the GUID in the host name was the key to access.  On a second 
machine I've tried both copying my working noteself.html file and 
downloading a fresh one and configuring the CouchDB URL and remote database 
name.  There is an offline button that I click (because I am clearly not 
syncing) and I am prompted first with a green, what I assume is a Noteself 
userID and password prompt for the remote database, and then browser pops 
up with the same.

I'm not sure what user ID to use.  The only password I created to my 
knowledge was that associated with my cloudant account.

Also the browser challenge comes up twice and on the second appearance 
disappears on it's own accord while typing in the password.

A little lost.

On Wednesday, January 4, 2017 at 7:53:05 PM UTC-5, Greg Hodgins wrote:
>
> Hi Steve.
>
> Thanks Daniel.  I saw your initial NoteSelf press release :-) the other 
> night.  I tried it mobile and wasn't truly understanding everything you 
> were trying to achieve.  Initially I thought it was all about the launch 
> icon on the device making more more like a native app.  Cool, but wasn't 
> enough to keep me that interested.
>
> Then I read a little more in some other posts here and see you are 
> interested in solving the mobile user experience.  Again, not a huge 
> concern to me currently BUT something I am definitely interested in.
>
> This also led to some more research as to what this couchDB reference was. 
>  Seeing some more posts including Steve had me checking the difference (and 
> now understanding relationship) between pouchDB and couchDB.  Now I'm 
> really interested.
>
> Of course much of this is covered here. https://noteself.github.io/. 
>  Sometimes it's just information overload - although I think there are some 
> things that could be made clearer off the top.  That said, there are so 
> many different audiences to cover it is almost impossible.
>
> Long story short, I get it - I think.  NoteSelf uses a local in browser 
> NoSQL database called pouchDB that supports 2 way replication with couchDB.
>
> Like Steve I setup a Cloudant couchDB.  Pretty simple.
>
> Steve, two things, your couchDB URL is in the URL of your DB admin page. 
>  It is also visible in Account, Virtual Hosts.It is the name you could 
> optionally replace with your own host name.  eg: 
> c4e83ce0-e302-42a2-8d3d-5cd3a8ae59e2-bluemix.cloudant.com.  
> Obviously I modified above, but hopefully you will recognize that.
>
> With respect to your error check the CORS tab on the same account screen. 
>  While I don't want to leave all domains (*) as currently selected, I am 
> not sure how to code for a file hosted browser session.  Ultimately even 
> some kind of local http: host is probably necessary with a host name to 
> configure restricted CORS from.
>
> With those to things I got NoteSelf replicating as advertised.  Very cool.
>
> I'm certainly wanting to explore the security aspect a little more.  I 
> gather that the GUID URL is one form of security and anyone accessing that 
> URL has read/write access.  I hope you can add a little more security in 
> that you appear to be able to set the permissions on the database and then 
> generate API keys.  I'm not sure how/where you embed this in NoteSelf, 
> assuming you do.
>
> Have to run, but will be back.
>
> Good luck.
>
> P.S.  Exploring this as an alternative to my current node.js hosted on 
> Google Drive approach that isn't proven sound in any way. No version 
> control and not multi-user, that that NoteSelf is either me thinks.
>
> All the best.
>
>
> On Thursday, December 29, 2016 at 4:15:20 PM UTC-5, Danielo Rodríguez 
> wrote:
>>
>> On their continuous effort to deliver cutting edge features to you, the 
>> NoteSelf team (formerly known as just me :D) is delighted to announce that 
>> *NoteSelf online 
>> edition* is now an offline-first experience.
>>
>> This means that you will be able to use the online edition *even if you 
>> are offline*, isn't that mind-blowing ? 
>>
>>
>> Wait, there is more! 
>>
>>
>> Being an offline-first application allows you to use NoteSelf *like* a 
>> native mobile app. This mean that you can have it on your *app launcher 
>> with it's own icon*, that it will appear on your list of opened/recent 
>> apps and some other features restricted to native applications.
>>
>> Hey, hey, hey, I want this! Fine, this is how:
>>
>>1. navigate to noteself.github.io/online with a *compatible browser*
>>2. open your browsers options and select "add to home screen" (text 
>>may vary depending on language and browser version)
>>3. you will see something similar to the below image (sorry it is on 
>>spanish)
>>
>>
>> 
>>
>>   4. NoteSelf can now live along with the test of your apps! 

[tw] Re: NoteSelf mobile app ( well, kind of)

[Greg Hodgins]

Hi Steve.

Thanks Daniel.  I saw your initial NoteSelf press release :-) the other 
night.  I tried it mobile and wasn't truly understanding everything you 
were trying to achieve.  Initially I thought it was all about the launch 
icon on the device making more more like a native app.  Cool, but wasn't 
enough to keep me that interested.

Then I read a little more in some other posts here and see you are 
interested in solving the mobile user experience.  Again, not a huge 
concern to me currently BUT something I am definitely interested in.

This also led to some more research as to what this couchDB reference was. 
 Seeing some more posts including Steve had me checking the difference (and 
now understanding relationship) between pouchDB and couchDB.  Now I'm 
really interested.

Of course much of this is covered here. https://noteself.github.io/. 
 Sometimes it's just information overload - although I think there are some 
things that could be made clearer off the top.  That said, there are so 
many different audiences to cover it is almost impossible.

Long story short, I get it - I think.  NoteSelf uses a local in browser 
NoSQL database called pouchDB that supports 2 way replication with couchDB.

Like Steve I setup a Cloudant couchDB.  Pretty simple.

Steve, two things, your couchDB URL is in the URL of your DB admin page. 
 It is also visible in Account, Virtual Hosts.It is the name you could 
optionally replace with your own host name.  eg: 
c4e83ce0-e302-42a2-8d3d-5cd3a8ae59e2-bluemix.cloudant.com. 
 
Obviously I modified above, but hopefully you will recognize that.

With respect to your error check the CORS tab on the same account screen. 
 While I don't want to leave all domains (*) as currently selected, I am 
not sure how to code for a file hosted browser session.  Ultimately even 
some kind of local http: host is probably necessary with a host name to 
configure restricted CORS from.

With those to things I got NoteSelf replicating as advertised.  Very cool.

I'm certainly wanting to explore the security aspect a little more.  I 
gather that the GUID URL is one form of security and anyone accessing that 
URL has read/write access.  I hope you can add a little more security in 
that you appear to be able to set the permissions on the database and then 
generate API keys.  I'm not sure how/where you embed this in NoteSelf, 
assuming you do.

Have to run, but will be back.

Good luck.

P.S.  Exploring this as an alternative to my current node.js hosted on 
Google Drive approach that isn't proven sound in any way. No version 
control and not multi-user, that that NoteSelf is either me thinks.

All the best.


On Thursday, December 29, 2016 at 4:15:20 PM UTC-5, Danielo Rodríguez wrote:
>
> On their continuous effort to deliver cutting edge features to you, the 
> NoteSelf team (formerly known as just me :D) is delighted to announce that 
> *NoteSelf online 
> edition* is now an offline-first experience.
>
> This means that you will be able to use the online edition *even if you 
> are offline*, isn't that mind-blowing ? 
>
>
> Wait, there is more! 
>
>
> Being an offline-first application allows you to use NoteSelf *like* a 
> native mobile app. This mean that you can have it on your *app launcher 
> with it's own icon*, that it will appear on your list of opened/recent 
> apps and some other features restricted to native applications.
>
> Hey, hey, hey, I want this! Fine, this is how:
>
>1. navigate to noteself.github.io/online with a *compatible browser*
>2. open your browsers options and select "add to home screen" (text 
>may vary depending on language and browser version)
>3. you will see something similar to the below image (sorry it is on 
>spanish)
>
>
> 
>
>   4. NoteSelf can now live along with the test of your apps! (pic 
> below)
>
>
> 
>
>   5. it even has a beautiful (depending on your likings) splash screen!
>
>
> 
>
> The supported browsers for the native app experience are chrome and Opera 
> so far, Firefox is on the way. The offline capabilities should work on a 
> wider range of of browsers.
>
>
> This have several advantages over the offline version:
>
>- Allways up to date. Don't worry anymore about updating, the online 
>version is allways the latest version!
>- Direct access from your launcher with a recognizable icon
>- Easier to use: because we rely on web standards the user experience 
>is delightful. For some reason mobile browser vendors doesn't like opening 
>local html files and 

[tw] Re: TiddlyWiki Hangout #102 will be on Thursday 5th January 2017 at 5pm GMT

[Evan Balster]

I'll be chiming in this meeting about dataflow programming and making 
TiddlyWiki more useful for detailed number-crunching tasks.  I'm interested 
in using TW-like workflows for things like interactive math, data 
visualization, story chronologies, game systems, planning and work logging.

For one of my past projects I designed and implemented a dynamic dataflow 
programming language dealing in audio, video and numeric information... 
 After doing it once, I've got some developed idea on dataflow architecture 
and its pitfalls.  I'm very interested to collide this with TiddlyWiki!

On Wednesday, 4 January 2017 17:55:12 UTC-6, Mat wrote:
>
> Sorry to say I won't make it this time. Will listen to the recording later.
>
> I would also not have much to bring to the table. (Not that one has to, to 
> participate). However, I'm hoping to hear @Jed drop a few words on his 
> latest TWederation advancements and it would be terrific if el @Danielo 
> could make a live NoteSelf demo. Maybe the sprung up documentation 
> initiatives could be commented on too?
>
> If Mario is there, there was much excitement a while ago when he 
> experimented with some ways to CSS tiddlers without using tc-tagged. I 
> would love to hear a bit on why this was not accepted in core (or do I 
> misunderstand something). It seemed so promising.
>
> Thank you!
>
> <:-)
>
>
> On Wednesday, January 4, 2017 at 9:26:53 PM UTC+1, Jeremy Ruston wrote:
>>
>> Apologies for the short notice, but I hope you will be able to join me 
>> for TiddlyWiki Hangout #102 on Thursday 5th January 2017 at 5pm GMT/UTC. 
>> You are welcome to take part as a guest or you can view the proceedings 
>> live or at a later date from the archive; I'll post the links here just 
>> before the scheduled start time.
>>
>> Please let me know if there's anything you'd particularly like to see 
>> discussed.
>>
>> Best wishes
>>
>> -- 
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5baf8e93-33e8-4086-88d9-c5e37ab8cf94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki Hangout #102 will be on Thursday 5th January 2017 at 5pm GMT

[Mat]

Sorry to say I won't make it this time. Will listen to the recording later.

I would also not have much to bring to the table. (Not that one has to, to 
participate). However, I'm hoping to hear @Jed drop a few words on his 
latest TWederation advancements and it would be terrific if el @Danielo 
could make a live NoteSelf demo. Maybe the sprung up documentation 
initiatives could be commented on too?

If Mario is there, there was much excitement a while ago when he 
experimented with some ways to CSS tiddlers without using tc-tagged. I 
would love to hear a bit on why this was not accepted in core (or do I 
misunderstand something). It seemed so promising.

Thank you!

<:-)


On Wednesday, January 4, 2017 at 9:26:53 PM UTC+1, Jeremy Ruston wrote:
>
> Apologies for the short notice, but I hope you will be able to join me for 
> TiddlyWiki Hangout #102 on Thursday 5th January 2017 at 5pm GMT/UTC. You 
> are welcome to take part as a guest or you can view the proceedings live or 
> at a later date from the archive; I'll post the links here just before the 
> scheduled start time.
>
> Please let me know if there's anything you'd particularly like to see 
> discussed.
>
> Best wishes
>
> -- 
> Jeremy Ruston
> mailto:jeremy...@gmail.com 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3216a53d-79e8-4e75-b91d-83ff0d983f99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Does anyone have a strategy for automatically reloading TW when the underlying file changes?

[Evade Flow]

Well... it's only a *partial* solution (and perhaps you're already aware), 
but you can execute an arbitrary script after running git pull in a local 
working copy by creating a post-merge hook like this:

$ cat > .git/hooks/post-merge << EOF
heredoc> #!/bin/sh
heredoc> exec touch I-LIKE-TRAFFIC-LIGHTS.txt
heredoc> EOF

The problem, of course, is figuring out what to run instead of touch I-LIKE-
TRAFFIC-LIGHTS.txt, but it's a start...




On Wednesday, January 4, 2017 at 2:24:45 PM UTC-5, Rob Hoelz wrote:
>
> Hi TiddlyWiki users and devs!
>
> I've been using TiddlyWiki for a while now, and I've had an issue that I'm 
> finally trying to solve.
>
> I use TiddlyWiki on multiple machines, and in order to synchronize changes 
> between them, I took a dumb, but simple and effective,
> route of just storing my wiki.html file in a Git repository and 
> pushing/pulling between the various machines.  This works pretty well,
> only there's a small caveat: if I pull and forget to reload the TiddlyWiki 
> page, I can end up potentially undoing changes I made on another
> machine.
>
> For example, let's say I'm working on machine S and I make a series of 
> changes, which we'll call version A.  I pull the changes onto machine
> T, reload the tab, and then I make some more changes, which we'll call B.  
> I go back to S and pull, but forget to refresh the page with TiddlyWiki 
> open.  If
> I make some edits and push that up, it'll be some sort of version A', 
> which will have blown away all of the changes I made between A and B.
>
> Since this is in a Git repostory, it's not the end of the world - I can 
> recover the change through the commit history.  However, this has bit me a
> few times (and it's rather annoying to recover from), and I don't know if 
> there are times it has happened and I've continued to use my wiki unawares
> (I'm working on a script to detect this).  I would really like to automate 
> this to prevent this from happening again.
>
> I saw this discussion[1] while searching, mentioning syncing of 
> TiddlyWikis; there are some interesting ideas there, but I didn't see 
> mention of the problem
> I've been experiencing.  I've been using the auto reload firefox 
> extension[2] for the last few days, and it largely does the job, but 
> unfortunately it's a bit
> overzealous - it reloads the wiki every time I save it!  It'll work for 
> now, but I was wondering if other users had some tips or ideas on how to 
> handle this issue.
> Perhaps TiddlyFox could be modified to reload a wiki if it's been changed 
> outside of the browser?
>
> Thanks for any help/insight you can offer!
>
> -Rob
>
> [1] https://groups.google.com/d/topic/tiddlywiki/irgt8hUmADQ/discussion
> [2] https://addons.mozilla.org/en-US/firefox/addon/auto-reload/?src=api
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6cfc39e9-5195-4855-833a-edc22af54f16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: NoteSelf mobile app ( well, kind of)

[Ste Wilson]

Ok... 
Well here's the non teach user feedback. 

First question.. Do I need to save it to my device first or just use it 
straight from github because from 'You can start using your notebook right now' 
suggests I can fill in details on the form in front of me i.e 
https://noteself.github.io/online/

1a. What's a couchdb and where can I get one? (I know from your comments here 
that cloudant is the place to go)

2. Cloudant is a whole can of worms for a non techie (I think I've set up a db 
but I'm not sure) . Perhaps a little more hand holding needed. 

3. What is the couchdb url? The couchdb tiddler provides a little more clarity. 

4. Remote database name. 
Is this just the name of the database I think I've created on cloudant or does 
it need a url? 

I've set up a cloudant account and created a db called'noteself'. 

I've filled in the fields. Pressed the button and get; 

Syncer-browser - 22:47:21 4 1 2017
XMLHttpRequest error code: 0

And that's as far as I've got... 

Ste


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3df2f85e-2cd9-46f3-b661-477c669fa09e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Does anyone have a strategy for automatically reloading TW when the underlying file changes?

[Danielo Rodríguez]

Would you consider testing another approach? 
Noteself (noteself.github.io) provides exactly that, synchronization between 
multiple devices in real time. Not as reliable as git is, but much simpler. 

Regards 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/75dda076-1b1b-4e24-80fa-a3c3d1c74ec1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: TiddlyWiki Hangout #102 will be on Thursday 5th January 2017 at 5pm GMT

[Jeremy Ruston]

Hi Jed

> I won't be able to be around for the first half hour or so, but I will be 
> there. I am trying to put some polish on the invoice maker I have been using 
> so I may show that off a bit if I don't have enough to talk about with 
> twederation.

Sounds great, I hope you can make it.

Best wishes

Jeremy.

> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to tiddlywiki@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywiki 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/8e5494df-8425-4895-9611-609966b43a4d%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/871001A4-5D1B-4D48-90EE-EC3BEBB0519D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki Hangout #102 will be on Thursday 5th January 2017 at 5pm GMT

[Jed Carty]

I won't be able to be around for the first half hour or so, but I will be 
there. I am trying to put some polish on the invoice maker I have been 
using so I may show that off a bit if I don't have enough to talk about 
with twederation.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8e5494df-8425-4895-9611-609966b43a4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: NoteSelf mobile app ( well, kind of)

[Danielo Rodríguez]

El lunes, 2 de enero de 2017, 17:03:30 (UTC+1), Josiah escribió:
>
> Ciao Danielo
>
> I think its a BRILLIANT piece of work.
>

Thank you very Much!
 

>
> I don't use mobile phones much and its not my main interest. My main 
> interest is how the PouchDB mechanism works as a potential saving mechanism 
> across all browsers and device types. AND that PouchDB is superb for multi 
> device syncing with a cloud IF you want that too. THAT is really exciting: 
> (1) To see the possibility of a standard "out-of-the-box", easy local 
> saving mechanism PLUS (2) reliable cloud based multi-device sync.
>

I'm happy that you see NoteSelf that way. It's cool to see that both you 
and me, with different interest (mobile + desktop vs desktop only ) can 
find the capabilities of NoteSelf interesting.
 

>
> Whilst there are several current, interesting, new systems emerging for 
> working with TW, your solution SMELLS SWEET to me :-)
>

Again, thank you very much. Feel free to use it as much as you want :-)
 

>
> In earlier threads I note that Jeremy Ruston is wary of having ones 
> TiddlyWiki locked up inside a specific browsers data storage department. I 
> think if his worry is addressed in a clear way with easy routes to export 
> and backup of Tiddler content I hope he'll see the upsides to your work so 
> far.
>

Several users have that worry too, which is perfectly understandable. One 
of the main targets of Tiddlywiki and what users loves the most if the 
reliability and reachability of their data. Explaining those on a clear way 
should be a MUST.
 


> I do wish more people with technical skill were expressing interest in 
> this. I note Mat's enthusiam & am glad for it. Its a lot for one person to 
> do it all. 
>

Yes me too, but I also want regular users giving their feedback. Probably 
regular users is what I need the most.
 
 

> Mat refereed to its "magical" nature. I think that hits the spot. And is 
> it White magic or Black magic? :-). I think part of what would be helpful 
> to reduce the idea you are the "Fairy Godfather" :-) is to explain a bit 
> more about what "in browser storage" is. What the UPSIDES are and what the 
> DOWNSIDES might be. 
>

Yes, you are right. I can't expect people giving me their data without a 
clear explanation of how all this works. Well, regular users will do, but 
not tiddlywiki community.
 

>
> Personally after using it a bit in Firefox I got interested in WHERE is 
> the data kept in Firefox. I still haven't found the DB, though I know it 
> must be there somewhere :-)
>

That should be added to the FAQ too.
 

>
> Just to let you know that I will continue to play with it. I am seriously 
> thinking of it as a very suitable way to create and publish e-pubs for 
> audiences who just want to read & add notes, not fiddle about with a 
> zillion different ways they have to save etc.
>

I never thought about that! It is a very cool idea.

Thank you for your feedback Josiah. 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f23cf945-fe9c-42a3-aed9-d1c97fd504e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] TiddlyWiki Hangout #102 will be on Thursday 5th January 2017 at 5pm GMT

[Jeremy Ruston]

Apologies for the short notice, but I hope you will be able to join me for
TiddlyWiki Hangout #102 on Thursday 5th January 2017 at 5pm GMT/UTC. You
are welcome to take part as a guest or you can view the proceedings live or
at a later date from the archive; I'll post the links here just before the
scheduled start time.

Please let me know if there's anything you'd particularly like to see
discussed.

Best wishes

-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJb6teGZiFY-p9uuDgVJyLRwhMQX_dttEBGqWPPsz-DYFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: NoteSelf mobile app ( well, kind of)

[Danielo Rodríguez]

 

> Heh, a funny thing happened: To try out installing a plugin, I installed 
> the plugin "Documentation from tiddlywiki.com". If I understand, this 
> overwrites both the Default tiddlers and the GettingStarted tiddler... 
> which means I can then not re-access the Noteself GettingStarted tiddler! 
>

Never though about that! To be honest, I don't find the documentation 
plugin of any help. But, I think it is a tiddlywiki limitation that you 
have to overrride the getting started plugin. Ideally you should be able to 
just add things to it. Sadly, If you install another plugin that overrides 
one of my plugins tiddlers there is not  much I can do. But, in any case, 
what are you missing from that tiddler? Once you have your wiki configured 
you don't need it anymore.

 

> The Revisions feature in GettingStarted also does not show anything. Had 
> to uninstall the docs plugin to access the NoteSelf GettingStarted again.
>
>
Do you mean that you have clicked the revisions button of that tiddler? 
That is normal, you are not creating a new version of that tiddler, you are 
just showing a different one.
 
 

> In fiddling with the above, I clicked the site subtitle which opens the 
> Ctrlpanel>TiddlyPouch>Database. 
> IMO the tab label should be "NoteSelf" instead of "TiddlyPouch" - I don't 
> want to have to learn more terminology/names and the tab content is only(?) 
> relevant for the NoteSelf context anyway.
>

That tab is from the TiddlyPouch plugin, which operates under NoteSelf 
edition. I admit that it could be confusing. One solution would be to 
create a NoteSelf customization plugin that overrides those details.


> There the overlapping info in 
>
> GettingStarted
> Ctrlpanel>TiddlyPouch>Database
> Ctrlpanel>Info>Basics
>
> ...this is a bit confusing, mostly because the same info is presented 
> differently.
>

Well, GettingStarted and Ctrlpanel>Info>Basics overlaps even on the default 
edition of tiddlywiki. GettingStarted is not intended to be accessed 
frequently, but to provide a friendly welcome to the user. That's why it 
overlaps with some other tiddlers. But overlapping only occurs between 
GettingStarted and the other two, because they do not overlap between each 
other.
 

>
> Actually, as an end user, where the data is stored even more belongs under 
> the Ctrlpanel>Savings tab.
>

Yes. I should override that tab. I think I discarded that idea long long 
time ago, while my intention was to allow TiddlyPouch live in a regular 
Tiddlywiki edition, but that goal is farther each day.
 


In GettingStarted it says
>
>  You can have as many notebooks as you want. Just change the Notebook Name , 
>> save and reload. 
>
>
> This triggers the "download, save to local drive" process which does not 
> seem correct - or? I was hoping it would just magically create and save to 
> a new browser db. This does not work for me in chrome nor FF. (Win10.)
>

You're right, it is confusing. Well, to be honest, it is confusing for the 
experienced tiddlywiki user, because you know where the save button is 
located. If you look closely, there is a button that reads: "save config" 
Once you hit that button, the rest happens automatically. I think I should 
be even clearer and say click Save Config button and that's all. I feel 
that instructions are from earlier stages of development.
 

...actually, how is it even possible for the system to know if clicking 
> standard save button should mean create a new selfnote db or download local 
> copy (or even upload to a tiddlyspot if such data is filled in)?
>

Yes too many moving parts. The system does not know nothing about uploading 
to tiddlyspot, I should remove those references from standard TW. If you 
click "Save Config" then the system is notified and it knows what to do. If 
you click the regular save button you will get a database export in JSON 
format, some kind of backup/export facility. 

 

> ...
>
> E.g for FAQ:
> What "browser stuff" (cache, cookies, history...) is safe to clear out 
> without affecting my NoteSelf data?
> What about browser "Incognito mode".
>

Good points, should be added to the FAQ
 

 

> Taking a step back to evaluate the situation, I realize that I have some 
> hesitation with using SelfNote because a lot still seems so magical.
>

I understand how do you feel. Many times it feels magical even to me. Not 
to mention that TiddlyWiki itself is pure magic...

 

>
> I see super potential in this tho.
>
> <:-)
>

As usual, thank you for your great feedback Mat
 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

[Danielo Rodríguez]

El viernes, 17 de junio de 2016, 19:39:02 (UTC+2), c pa escribió:
>
>
> Oh right. I do all my editing from dashboards because all my tiddlers are 
> structured. The concept is as follows:
>
> Analysis
> 
>
> # Decide on a structure for your tiddlers
> #* Example "Book" would have the following fields
> #** Title
> #** Authors
> #** Publisher
> #** My random ramblings
> #** My Review
> #** Plot synopsis
> #** ISBN Number
>
> Discussion
> =
>
> * My random ramblings is a good candidate for the text field
> * My Review, and Plot synopsis are good candidates for slices
> * The title of the book should be put in the caption field because two 
> books can have the same title
> * ISBN is unique for books so put that in the title filed (The name of the 
> tiddler - must be unique)
> * Authors can be multiple so this would be a list of authors populated 
> from tiddlers tagged "author"
> ** This requires a macro to populate it. 
> ** You can use crazyListHere from cpashow.tiddlyspot.com 
> ** As you might suspect from the name, my macro currently does all sorts 
> of stuff in addition to populating a list
> * Publisher is a text name populated using a select from tiddlers tagged 
> "publisher"
>
> Code a template
> =
>

I was thinking about  something very similar. We have all that we need 
already on tiddlywiki. The rest is just a matter of how do you present the 
information. Tiddlers have fields, so you can have as many fields as 
sections you need. Then, the only thing you need is a view template to 
transclude all the "_section/name" fields and a edit template to edit them 
comfortable.

Let me say *c pa* that I find your implementation brilliant. Thank you for 
sharing.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fb8a0d50-14e3-490c-8b68-eb08b506b842%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Does anyone have a strategy for automatically reloading TW when the underlying file changes?

[Rob Hoelz]

Hi TiddlyWiki users and devs!

I've been using TiddlyWiki for a while now, and I've had an issue that I'm 
finally trying to solve.

I use TiddlyWiki on multiple machines, and in order to synchronize changes 
between them, I took a dumb, but simple and effective,
route of just storing my wiki.html file in a Git repository and 
pushing/pulling between the various machines.  This works pretty well,
only there's a small caveat: if I pull and forget to reload the TiddlyWiki 
page, I can end up potentially undoing changes I made on another
machine.

For example, let's say I'm working on machine S and I make a series of 
changes, which we'll call version A.  I pull the changes onto machine
T, reload the tab, and then I make some more changes, which we'll call B.  
I go back to S and pull, but forget to refresh the page with TiddlyWiki 
open.  If
I make some edits and push that up, it'll be some sort of version A', which 
will have blown away all of the changes I made between A and B.

Since this is in a Git repostory, it's not the end of the world - I can 
recover the change through the commit history.  However, this has bit me a
few times (and it's rather annoying to recover from), and I don't know if 
there are times it has happened and I've continued to use my wiki unawares
(I'm working on a script to detect this).  I would really like to automate 
this to prevent this from happening again.

I saw this discussion[1] while searching, mentioning syncing of 
TiddlyWikis; there are some interesting ideas there, but I didn't see 
mention of the problem
I've been experiencing.  I've been using the auto reload firefox 
extension[2] for the last few days, and it largely does the job, but 
unfortunately it's a bit
overzealous - it reloads the wiki every time I save it!  It'll work for 
now, but I was wondering if other users had some tips or ideas on how to 
handle this issue.
Perhaps TiddlyFox could be modified to reload a wiki if it's been changed 
outside of the browser?

Thanks for any help/insight you can offer!

-Rob

[1] https://groups.google.com/d/topic/tiddlywiki/irgt8hUmADQ/discussion
[2] https://addons.mozilla.org/en-US/firefox/addon/auto-reload/?src=api

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5f356408-42e3-48a3-927e-5e8aa21c91fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Import Tiddles automatically in Tiddlywiki

[Danielo Rodríguez]

El miércoles, 4 de enero de 2017, 12:42:50 (UTC+1), Stéphane Delaye 
escribió:
>
> Hello guys !
>
> Thanks to Mario guidelines, it works !
>

That instructions looks very similar to the ones that I provided to you on 
github. Did mario Helped you too or do you think that danielo515@github is 
Mario?

In any case, I'm glad it is working. Please don't hesitate to provide your 
feedback.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/31a9ad79-a800-4e69-bcaf-27a2e7520fa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Use multi-file layout without using NodeJS?

[Evade Flow]

> When I try your short-cut approach, I get warnings...

Hmm. I'm still a n00b, so I'm not sure what to suggest. In case it helps, I 
can provide details on how I set up my initial 'tiddler repo'. I started 
with a monolithic HTML file that I've been using for the last week or so to 
explore TiddlyWiki's features. Then, I installed node and npm on a Linux 
machine (just 'because', I think Windows/OS X would have been fine as 
well). Then, I ran:


$ sudo npm install -g tiddlywiki

to install tiddlywiki globally. (It wound up in `/usr/local/bin/tiddlywiki` 
by default.) After that, I ran:

$ tiddlywiki mywiki --init server
Copied edition 'server' to mywiki


Apparently, *that* step is what created tiddlywiki.info:

$ ls mywiki 
tiddlywiki.info


After that, I used my monolithic HTML to 'seed' the mywiki folder created 
in the previous step and start the server:

$ tiddlywiki mywiki --load ~/Desktop/mywiki.html --server


The above command created a tiddlers folder under mywiki containing all my 
tiddlers.

$ ls mywiki/tiddlers | head -15
Can't_embed_QWidget_in_QML_.tid
$__config_DefaultSidebarTab.tid
$__config_PageControlButtons_Visibility_$__core_ui_Buttons_fold-all.tid
$__config_PageControlButtons_Visibility_$__core_ui_Buttons_save-wiki.tid
$__config_PageControlButtons_Visibility_$__core_ui_Buttons_unfold-all.tid
$__config_WikiParserRules_Inline_wikilink.tid
Contents.tid
$__core.json.tid
deb.tid
$__DefaultTiddlers.tid
Getting_Tiddly.tid
How_can_I_extract_files_from_a_DEB_package_.tid
How_can_I_interact_with_TiddlyWiki_using_Alexa_.tid
How_can_I_list_the_contents_of_a_DEB_file_.tid
How_can_I_remove_a_tag_.tid
...

After running all of the above commands, I ran git init in the mywiki 
folder and committed all the files.

HTH!


On Wednesday, January 4, 2017 at 1:02:27 PM UTC-5, Mark S. wrote:
>
> When I try your short-cut approach, I get warnings about missing plugins 
> and the resulting served up TW is formatted wrongly -- as if missing a 
> stylesheet or something. There must be an additional step setting up a 
> tiddlywiki.info file. Perhaps it can just be copied from somewhere?
>
> Return messages:
>
> C:\Users\Mark\Downloads\node\mytestwiki>node.exe tiddlywiki.js .\data1 --
> server
> Warning: Wiki folder '.\data1' does not exist or is missing a tiddlywiki.info 
> file
> Serving on 127.0.0.1:8080
> (press ctrl-C to exit)
> Warning: Plugins required for client-server operation (
> "tiddlywiki/filesystem" a
> nd "tiddlywiki/tiddlyweb") are missing from tiddlywiki.info file
>
>
>
>
> On Tuesday, January 3, 2017 at 9:10:54 PM UTC-8, Arlen Beiler wrote:
>>
>> Normally I store the data directory inside the tiddlywiki folder, but you 
>> can store it anywhere you want.
>>
>> On Jan 4, 2017 12:04 AM, "Arlen Beiler"  wrote:
>>
>>> Welcome to the world of NodeJS. You can search for "commands" on 
>>> TiddlyWiki.com. That will give you all the command line options.
>>>
>>> node.exe tiddlywiki.js [data directory] [command [options]]
>>>
>>> On Jan 4, 2017 12:00 AM, "Arlen Beiler"  wrote:
>>>
 If you do not specify a directory as the first argument after 
 tiddlywiki.js, it will use the current directory. Most of the commands use 
 that directory. So I recommend you set one.

 On Jan 3, 2017 11:56 PM, "Arlen Beiler"  wrote:

> If you specify --init or --load instead --server, then tiddlywiki.js 
> will make that the data directory. Then you specify that directory when 
> you 
> specify --server and it will serve the files from that folder. 
>
> You can find more info on TiddlyWiki.com or by exploring the code.
>
> On Jan 3, 2017 10:55 PM, "'Mark S.' via TiddlyWiki" <
> tiddl...@googlegroups.com> wrote:
>
>> In your example, what is "../data/wiki1" and where does it come from?
>>
>> Thanks!
>> Mark
>>
>> On Tuesday, January 3, 2017 at 7:26:43 PM UTC-8, Arlen Beiler wrote:
>>>
>>> Anything is possible over HTTP. How are you going to save changes? 
>>>
>>> From reading your email, I guess you don't know that you can just 
>>> download any tag or the master from the TiddlyWiki GitHub repository, 
>>> drop 
>>> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 
>>> --server" 
>>> and your good to go. Easy on Windows, don't know about Linux or Mac, 
>>> but 
>>> you're a software developer :)
>>>
>>> (At first I was going to use the stock "I guess you know...") :-)
>>>
>>> Also several of us are working on serving multiple wikis as separate 
>>> folders instead of seperate server instances.
>>>
>>> https://gist.github.com/Arlen22/bbd852f68e328165e49f
>>>
>>> Hope that helps.
>>>
>>> On Jan 3, 2017 7:50 PM, "Evade Flow"  wrote:
>>>
 > is there some way I can access/modify this collection of files 
 using only git and a browser?

Re: [tw] Re: Use multi-file layout without using NodeJS?

[Evade Flow]

> Now I'm thinking perhaps I'll try using git submodules to make the TW 
repo a 'sub-repo' of my tiddler repo...

Well... that didn't work so well. `:-} I got an error saying: "TypeError: 
$tw.utils.replaceString is not a function". It's probably a PEBCAK 
 error, but I created an issue for 
it, just in case, see: https://github.com/Jermolene/TiddlyWiki5/issues/2695


On Wednesday, January 4, 2017 at 11:51:35 AM UTC-5, Evade Flow wrote:
>
> > If I only need the tiddlywiki.js file and node.exe that trims things 
> down considerably.
>
> Ah. I see now that I misunderstood. You didn't say that having *only *
> tiddlywiki.js and node.exe was sufficient, you said to clone the TW repo 
> and drop node.exe into it. Instead, I tried copying both node.exe and 
> tiddlywiki.js into *my *TW folder, and got:
>
>
> module.js:472
> throw err;
> ^
>
> Error: Cannot find module './boot/boot.js'
> at Function.Module._resolveFilename (module.js:470:15)
> at Function.Module._load (module.js:418:25)
> at Module.require (module.js:498:17)
> at require (internal/module.js:20:19)
> at Object. (C:\Users\wod2fh\projects\reverie\tiddlywiki.js:
> 7:11)
> at Module._compile (module.js:571:32)
> at Object.Module._extensions..js (module.js:580:10)
> at Module.load (module.js:488:32)
> at tryModuleLoad (module.js:447:12)
> at Function.Module._load (module.js:439:3)
>
>
> Now I'm thinking perhaps I'll try using git submodules to make the TW repo 
> a 'sub-repo' of my tiddler repo...
>
>
> On Wednesday, January 4, 2017 at 11:31:09 AM UTC-5, Evade Flow wrote:
>>
>> > From reading your email, I guess you don't know that you can just 
>> download any tag or the master from the TiddlyWiki GitHub repository, drop 
>> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 --server"...
>>
>> That's actually *really* helpful, thanks. You mean: I don't need to 
>> download *all* of node/npm? I found these instructions 
>>  for installing 
>> on Windows, and (more-or-less) followed them, installing the npm + nodejs 
>> zip package from here , as recommended 
>> in one of the comments in the gist. It wasn't difficult, but I was a bit 
>> surprised when I saw that the node-v7.2.1-win-x64 folder takes up 70 MB. 
>> I mostly do embedded systems development, so I sometimes have these "Get 
>> off my lawn!" moments when something dumps a ton of files onto my system 
>> whose purpose I don't really understand. (This, even though I've got 315 GB 
>> free on that hard drive. I don't claim it makes any sense. `:-] )
>>
>> Now that I look at it, I see that the node_modules/tiddlywiki subfolder 
>> itself is responsible for ~27 of those 70 MB. And the editions folder 
>> (which I assume I don't need?) contains some 13 MB of 'stuff'. If I only 
>> need the tiddlywiki.js file and node.exe that trims things down 
>> considerably. I'll give it a try!
>>
>>
>> On Tuesday, January 3, 2017 at 10:26:43 PM UTC-5, Arlen Beiler wrote:
>>>
>>> Anything is possible over HTTP. How are you going to save changes? 
>>>
>>> From reading your email, I guess you don't know that you can just 
>>> download any tag or the master from the TiddlyWiki GitHub repository, drop 
>>> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 --server" 
>>> and your good to go. Easy on Windows, don't know about Linux or Mac, but 
>>> you're a software developer :)
>>>
>>> (At first I was going to use the stock "I guess you know...") :-)
>>>
>>> Also several of us are working on serving multiple wikis as separate 
>>> folders instead of seperate server instances.
>>>
>>> https://gist.github.com/Arlen22/bbd852f68e328165e49f
>>>
>>> Hope that helps.
>>>
>>> On Jan 3, 2017 7:50 PM, "Evade Flow"  wrote:
>>>
 > is there some way I can access/modify this collection of files using 
 only git and a browser?

 Driving home this evening, I realized this was a bit of a silly 
 question for somebody who professes to be a software developer by trade to 
 ask—doh! (Can you tell I'm not a web developer?) Looking at the files 
 processed by tiddlywiki+NodeJS, I see that *none* of them are HTML. It 
 truly is "tiddlers all the way down", so... *something* has to convert 
 all those .tid files to HTML so the browser can display them.

 I guess I should rephrase my question as: is there some way of serving 
 multi-file TW content that requires less setup work than NodeJS? I'm 
 thinking about how Python contains builtin modules that let you run 
 something like this in a folder:

 $ python -m SimpleHTTPServer 8000


 For me, this would be a big win because (as it happens) just about 
 every machine I work on already has Python installed. And they *all* 
 have Perl, which I believe has a similar (built-in) capability[?] So 

[tw] Re: [TW5] Is it possible to create external links in the titles of tiddlers?

['Mark S.' via TiddlyWiki]

The title is kind of like a very special field in TW5. And because it often 
contains all sorts of characters, rendering it exactly as it was entered is 
pretty important.

Why not just put your reference in the body of the tiddler? Perhaps 
describe your use-case.

Good luck --
Mark

On Wednesday, January 4, 2017 at 10:22:44 AM UTC-8, Deniz Rende wrote:
>
> Hello Everyone,
>
> Have a quick question or RFE for the subject here.
>
> I'd like to be able to create hyperlinks in the titles of tiddlers. I know 
> that you can create links inside their notes by using conventions like 
> [[test|www.test.com]] or use the hyperlink button, but I'd like to do the 
> same thing for their titles. See the attachment image for this. If this is 
> not possible, may I then kindly request to make this RFE ?
>  
> Thank you!
>
> Regards,
>
> Deniz Rende
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3e5a9224-3256-4e1f-8867-d21ac74e835d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Is it possible to create external links in the titles of tiddlers?

[Deniz Rende]

Hello Everyone,

Have a quick question or RFE for the subject here.

I'd like to be able to create hyperlinks in the titles of tiddlers. I know 
that you can create links inside their notes by using conventions like 
[[test|www.test.com]] or use the hyperlink button, but I'd like to do the 
same thing for their titles. See the attachment image for this. If this is 
not possible, may I then kindly request to make this RFE ?
 
Thank you!

Regards,

Deniz Rende



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2e89dcd3-e3ea-4bed-8b69-4ffc4c6d6f24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Use multi-file layout without using NodeJS?

['Mark S.' via TiddlyWiki]

When I try your short-cut approach, I get warnings about missing plugins and 
the resulting served up TW is formatted wrongly -- as if missing a 
stylesheet or something. There must be an additional step setting up a 
tiddlywiki.info file. Perhaps it can just be copied from somewhere?

Return messages:

C:\Users\Mark\Downloads\node\mytestwiki>node.exe tiddlywiki.js .\data1 --
server
Warning: Wiki folder '.\data1' does not exist or is missing a tiddlywiki.info 
file
Serving on 127.0.0.1:8080
(press ctrl-C to exit)
Warning: Plugins required for client-server operation (
"tiddlywiki/filesystem" a
nd "tiddlywiki/tiddlyweb") are missing from tiddlywiki.info file




On Tuesday, January 3, 2017 at 9:10:54 PM UTC-8, Arlen Beiler wrote:
>
> Normally I store the data directory inside the tiddlywiki folder, but you 
> can store it anywhere you want.
>
> On Jan 4, 2017 12:04 AM, "Arlen Beiler"  
> wrote:
>
>> Welcome to the world of NodeJS. You can search for "commands" on 
>> TiddlyWiki.com. That will give you all the command line options.
>>
>> node.exe tiddlywiki.js [data directory] [command [options]]
>>
>> On Jan 4, 2017 12:00 AM, "Arlen Beiler"  
>> wrote:
>>
>>> If you do not specify a directory as the first argument after 
>>> tiddlywiki.js, it will use the current directory. Most of the commands use 
>>> that directory. So I recommend you set one.
>>>
>>> On Jan 3, 2017 11:56 PM, "Arlen Beiler"  
>>> wrote:
>>>
 If you specify --init or --load instead --server, then tiddlywiki.js 
 will make that the data directory. Then you specify that directory when 
 you 
 specify --server and it will serve the files from that folder. 

 You can find more info on TiddlyWiki.com or by exploring the code.

 On Jan 3, 2017 10:55 PM, "'Mark S.' via TiddlyWiki" <
 tiddl...@googlegroups.com > wrote:

> In your example, what is "../data/wiki1" and where does it come from?
>
> Thanks!
> Mark
>
> On Tuesday, January 3, 2017 at 7:26:43 PM UTC-8, Arlen Beiler wrote:
>>
>> Anything is possible over HTTP. How are you going to save changes? 
>>
>> From reading your email, I guess you don't know that you can just 
>> download any tag or the master from the TiddlyWiki GitHub repository, 
>> drop 
>> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 
>> --server" 
>> and your good to go. Easy on Windows, don't know about Linux or Mac, but 
>> you're a software developer :)
>>
>> (At first I was going to use the stock "I guess you know...") :-)
>>
>> Also several of us are working on serving multiple wikis as separate 
>> folders instead of seperate server instances.
>>
>> https://gist.github.com/Arlen22/bbd852f68e328165e49f
>>
>> Hope that helps.
>>
>> On Jan 3, 2017 7:50 PM, "Evade Flow"  wrote:
>>
>>> > is there some way I can access/modify this collection of files 
>>> using only git and a browser?
>>>
>>> Driving home this evening, I realized this was a bit of a silly 
>>> question for somebody who professes to be a software developer by trade 
>>> to 
>>> ask—doh! (Can you tell I'm not a web developer?) Looking at the files 
>>> processed by tiddlywiki+NodeJS, I see that *none* of them are HTML. 
>>> It truly is "tiddlers all the way down", so... *something* has to 
>>> convert all those .tid files to HTML so the browser can display 
>>> them.
>>>
>>> I guess I should rephrase my question as: is there some way of 
>>> serving multi-file TW content that requires less setup work than 
>>> NodeJS? 
>>> I'm thinking about how Python contains builtin modules that let you run 
>>> something like this in a folder:
>>>
>>> $ python -m SimpleHTTPServer 8000
>>>
>>>
>>> For me, this would be a big win because (as it happens) just about 
>>> every machine I work on already has Python installed. And they *all* 
>>> have Perl, which I believe has a similar (built-in) capability[?] So it 
>>> would be "one less thing" to worry about it when configuring a new 
>>> environment.
>>>
>>>
>>> On Tuesday, January 3, 2017 at 4:44:43 PM UTC-5, Evade Flow wrote:

 I've been experimenting with TiddlyWiki and NodeJS, and discovered 
 that 'importing' my mono-html file (using tiddlywiki --load) 
 causes it to be converted into a bunch of discrete files. Further 
 experiments reveal that it is possible—seemingly, at least—to sync 
 these 
 files (and hence, my entire wiki) to multiple machines using git 
 push/pull. The one catch is: it appears that the only way to 
 actually *use* a TiddlyWiki structured this way is to serve it 
 using NodeJS? Is that correct? Or... is there some way I can 
 access/modify 
 

Re: [tw] Re: Use multi-file layout without using NodeJS?

[Evade Flow]

> If I only need the tiddlywiki.js file and node.exe that trims things down 
considerably.

Ah. I see now that I misunderstood. You didn't say that having *only *
tiddlywiki.js and node.exe was sufficient, you said to clone the TW repo 
and drop node.exe into it. Instead, I tried copying both node.exe and 
tiddlywiki.js into *my *TW folder, and got:


module.js:472
throw err;
^

Error: Cannot find module './boot/boot.js'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\wod2fh\projects\reverie\tiddlywiki.js:7:
11)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)


Now I'm thinking perhaps I'll try using git submodules to make the TW repo 
a 'sub-repo' of my tiddler repo...


On Wednesday, January 4, 2017 at 11:31:09 AM UTC-5, Evade Flow wrote:
>
> > From reading your email, I guess you don't know that you can just 
> download any tag or the master from the TiddlyWiki GitHub repository, drop 
> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 --server"...
>
> That's actually *really* helpful, thanks. You mean: I don't need to 
> download *all* of node/npm? I found these instructions 
>  for installing on 
> Windows, and (more-or-less) followed them, installing the npm + nodejs zip 
> package from here , as recommended in 
> one of the comments in the gist. It wasn't difficult, but I was a bit 
> surprised when I saw that the node-v7.2.1-win-x64 folder takes up 70 MB. 
> I mostly do embedded systems development, so I sometimes have these "Get 
> off my lawn!" moments when something dumps a ton of files onto my system 
> whose purpose I don't really understand. (This, even though I've got 315 GB 
> free on that hard drive. I don't claim it makes any sense. `:-] )
>
> Now that I look at it, I see that the node_modules/tiddlywiki subfolder 
> itself is responsible for ~27 of those 70 MB. And the editions folder 
> (which I assume I don't need?) contains some 13 MB of 'stuff'. If I only 
> need the tiddlywiki.js file and node.exe that trims things down 
> considerably. I'll give it a try!
>
>
> On Tuesday, January 3, 2017 at 10:26:43 PM UTC-5, Arlen Beiler wrote:
>>
>> Anything is possible over HTTP. How are you going to save changes? 
>>
>> From reading your email, I guess you don't know that you can just 
>> download any tag or the master from the TiddlyWiki GitHub repository, drop 
>> node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 --server" 
>> and your good to go. Easy on Windows, don't know about Linux or Mac, but 
>> you're a software developer :)
>>
>> (At first I was going to use the stock "I guess you know...") :-)
>>
>> Also several of us are working on serving multiple wikis as separate 
>> folders instead of seperate server instances.
>>
>> https://gist.github.com/Arlen22/bbd852f68e328165e49f
>>
>> Hope that helps.
>>
>> On Jan 3, 2017 7:50 PM, "Evade Flow"  wrote:
>>
>>> > is there some way I can access/modify this collection of files using 
>>> only git and a browser?
>>>
>>> Driving home this evening, I realized this was a bit of a silly question 
>>> for somebody who professes to be a software developer by trade to ask—doh! 
>>> (Can you tell I'm not a web developer?) Looking at the files processed by 
>>> tiddlywiki+NodeJS, I see that *none* of them are HTML. It truly is 
>>> "tiddlers all the way down", so... *something* has to convert all those 
>>> .tid files to HTML so the browser can display them.
>>>
>>> I guess I should rephrase my question as: is there some way of serving 
>>> multi-file TW content that requires less setup work than NodeJS? I'm 
>>> thinking about how Python contains builtin modules that let you run 
>>> something like this in a folder:
>>>
>>> $ python -m SimpleHTTPServer 8000
>>>
>>>
>>> For me, this would be a big win because (as it happens) just about every 
>>> machine I work on already has Python installed. And they *all* have 
>>> Perl, which I believe has a similar (built-in) capability[?] So it would be 
>>> "one less thing" to worry about it when configuring a new environment.
>>>
>>>
>>> On Tuesday, January 3, 2017 at 4:44:43 PM UTC-5, Evade Flow wrote:

 I've been experimenting with TiddlyWiki and NodeJS, and discovered that 
 'importing' my mono-html file (using tiddlywiki --load) causes it to 
 be converted into a bunch of discrete files. Further experiments reveal 
 that it is possible—seemingly, at least—to sync these files (and hence, my 
 entire wiki) to multiple machines using git push/pull. The one catch 
 is: it appears that the only way to 

Re: [tw] Re: Use multi-file layout without using NodeJS?

[Evade Flow]

> From reading your email, I guess you don't know that you can just 
download any tag or the master from the TiddlyWiki GitHub repository, drop 
node.exe into it and call "node.exe tiddlywiki.js ../data/wiki1 --server"...

That's actually *really* helpful, thanks. You mean: I don't need to 
download *all* of node/npm? I found these instructions 
 for installing on 
Windows, and (more-or-less) followed them, installing the npm + nodejs zip 
package from here , as recommended in one 
of the comments in the gist. It wasn't difficult, but I was a bit surprised 
when I saw that the node-v7.2.1-win-x64 folder takes up 70 MB. I mostly do 
embedded systems development, so I sometimes have these "Get off my lawn!" 
moments when something dumps a ton of files onto my system whose purpose I 
don't really understand. (This, even though I've got 315 GB free on that 
hard drive. I don't claim it makes any sense. `:-] )

Now that I look at it, I see that the node_modules/tiddlywiki subfolder 
itself is responsible for ~27 of those 70 MB. And the editions folder 
(which I assume I don't need?) contains some 13 MB of 'stuff'. If I only 
need the tiddlywiki.js file and node.exe that trims things down 
considerably. I'll give it a try!


On Tuesday, January 3, 2017 at 10:26:43 PM UTC-5, Arlen Beiler wrote:
>
> Anything is possible over HTTP. How are you going to save changes? 
>
> From reading your email, I guess you don't know that you can just download 
> any tag or the master from the TiddlyWiki GitHub repository, drop node.exe 
> into it and call "node.exe tiddlywiki.js ../data/wiki1 --server" and your 
> good to go. Easy on Windows, don't know about Linux or Mac, but you're a 
> software developer :)
>
> (At first I was going to use the stock "I guess you know...") :-)
>
> Also several of us are working on serving multiple wikis as separate 
> folders instead of seperate server instances.
>
> https://gist.github.com/Arlen22/bbd852f68e328165e49f
>
> Hope that helps.
>
> On Jan 3, 2017 7:50 PM, "Evade Flow"  
> wrote:
>
>> > is there some way I can access/modify this collection of files using 
>> only git and a browser?
>>
>> Driving home this evening, I realized this was a bit of a silly question 
>> for somebody who professes to be a software developer by trade to ask—doh! 
>> (Can you tell I'm not a web developer?) Looking at the files processed by 
>> tiddlywiki+NodeJS, I see that *none* of them are HTML. It truly is 
>> "tiddlers all the way down", so... *something* has to convert all those 
>> .tid files to HTML so the browser can display them.
>>
>> I guess I should rephrase my question as: is there some way of serving 
>> multi-file TW content that requires less setup work than NodeJS? I'm 
>> thinking about how Python contains builtin modules that let you run 
>> something like this in a folder:
>>
>> $ python -m SimpleHTTPServer 8000
>>
>>
>> For me, this would be a big win because (as it happens) just about every 
>> machine I work on already has Python installed. And they *all* have 
>> Perl, which I believe has a similar (built-in) capability[?] So it would be 
>> "one less thing" to worry about it when configuring a new environment.
>>
>>
>> On Tuesday, January 3, 2017 at 4:44:43 PM UTC-5, Evade Flow wrote:
>>>
>>> I've been experimenting with TiddlyWiki and NodeJS, and discovered that 
>>> 'importing' my mono-html file (using tiddlywiki --load) causes it to be 
>>> converted into a bunch of discrete files. Further experiments reveal that 
>>> it is possible—seemingly, at least—to sync these files (and hence, my 
>>> entire wiki) to multiple machines using git push/pull. The one catch 
>>> is: it appears that the only way to actually *use* a TiddlyWiki 
>>> structured this way is to serve it using NodeJS? Is that correct? Or... is 
>>> there some way I can access/modify this collection of files using only git 
>>> and a browser?
>>>
>>> I ask because the setup I'm fumbling my way towards seems a bit... 
>>> cumbersome. I'm a software developer by trade, so sync'ing git repos to 
>>> multiple machines comes as naturally as breathing. In contrast, doing a 
>>> local install of Node + npm + tiddlywiki on each machine I want to access 
>>> the data from feels like a lot of extra effort. I use Windows and Linux at 
>>> work, and OS X at home, and I'd rather not bother figuring out the nuances 
>>> of how to do that dance on all three platforms—especially given that I 
>>> don't have admin/root access on all the machines I'd like to access my 
>>> wiki(s) from.
>>>
>>> I already have a *killer* setup for managing my myriad config files (
>>> .vimrc, .zshrc, .tmux.conf, etc.) and various plugins using myrepos 
>>>  and vcsh 
>>> . *Everything* is stored in git, so I 
>>> can sync my setup around to whatever machines I want. It would be 
>>> 

[tw] Re: Use multi-file layout without using NodeJS?

[Evade Flow]

> I think that nowadays nodejs is easy to install and use on any platform, 
and npm is included in nodejs

After going through the process on Windows, OS X and Linux yesterday, I 
have to agree. It wasn't too hard to figure out on each platform. I've 
still got some rough edges to file down, but it seems like I can find a way 
to automate the steps. Or... make them 'semi-automated', anyway. Thanks for 
the feedback!


On Wednesday, January 4, 2017 at 4:36:12 AM UTC-5, BJ wrote:
>
> Going away from nodejs would involve some work. Tiddlywiki is a dual 
> platform application one platform is nodejs the other is the browser. For 
> example:
>
> tiddlywiki contain a packaging application that runs under nodejs - in the 
> boot.js - this contains a build system, one feature is that it can package 
> directory trees containing tiddlers into plugins. This makes it super easy 
> to use git to manage plugin dev.
>
> tiddlywiki is also a dedicated http tiddler server written for nodejs - it 
> 'knows' how to serve and save tiddlers.
>
> I think that nowadays nodejs is easy to install and use on any platform, 
> and npm is included in nodejs
>
> all the best
>
> BJ
>
> On Wednesday, January 4, 2017 at 1:50:28 AM UTC+1, Evade Flow wrote:
>>
>> > is there some way I can access/modify this collection of files using 
>> only git and a browser?
>>
>> Driving home this evening, I realized this was a bit of a silly question 
>> for somebody who professes to be a software developer by trade to ask—doh! 
>> (Can you tell I'm not a web developer?) Looking at the files processed by 
>> tiddlywiki+NodeJS, I see that *none* of them are HTML. It truly is 
>> "tiddlers all the way down", so... *something* has to convert all those 
>> .tid files to HTML so the browser can display them.
>>
>> I guess I should rephrase my question as: is there some way of serving 
>> multi-file TW content that requires less setup work than NodeJS? I'm 
>> thinking about how Python contains builtin modules that let you run 
>> something like this in a folder:
>>
>> $ python -m SimpleHTTPServer 8000
>>
>>
>> For me, this would be a big win because (as it happens) just about every 
>> machine I work on already has Python installed. And they *all* have 
>> Perl, which I believe has a similar (built-in) capability[?] So it would be 
>> "one less thing" to worry about it when configuring a new environment.
>>
>>
>> On Tuesday, January 3, 2017 at 4:44:43 PM UTC-5, Evade Flow wrote:
>>>
>>> I've been experimenting with TiddlyWiki and NodeJS, and discovered that 
>>> 'importing' my mono-html file (using tiddlywiki --load) causes it to be 
>>> converted into a bunch of discrete files. Further experiments reveal that 
>>> it is possible—seemingly, at least—to sync these files (and hence, my 
>>> entire wiki) to multiple machines using git push/pull. The one catch 
>>> is: it appears that the only way to actually *use* a TiddlyWiki 
>>> structured this way is to serve it using NodeJS? Is that correct? Or... is 
>>> there some way I can access/modify this collection of files using only git 
>>> and a browser?
>>>
>>> I ask because the setup I'm fumbling my way towards seems a bit... 
>>> cumbersome. I'm a software developer by trade, so sync'ing git repos to 
>>> multiple machines comes as naturally as breathing. In contrast, doing a 
>>> local install of Node + npm + tiddlywiki on each machine I want to access 
>>> the data from feels like a lot of extra effort. I use Windows and Linux at 
>>> work, and OS X at home, and I'd rather not bother figuring out the nuances 
>>> of how to do that dance on all three platforms—especially given that I 
>>> don't have admin/root access on all the machines I'd like to access my 
>>> wiki(s) from.
>>>
>>> I already have a *killer* setup for managing my myriad config files (
>>> .vimrc, .zshrc, .tmux.conf, etc.) and various plugins using myrepos 
>>>  and vcsh 
>>> . *Everything* is stored in git, so I 
>>> can sync my setup around to whatever machines I want. It would be 
>>> enormously helpful if I could do the same with my TiddlyWiki(s). Is this 
>>> possible?
>>>
>>> *NOTE*: After trying it a few times, I don't have much interest in 
>>> trying to sync changes to monolithic TW files. The mono-HTML files are 
>>> huge, and the diffs contain so much 'noise' that trying to merge updates 
>>> from multiple machines seems like an impossibility. (Perhaps I'll find that 
>>> the multi-file layout has quirks/pitfalls of its own, but so far, it seems 
>>> really easy to understand and reason about...)
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view 

[tw] Slide shows in wikis - Remote for moderator and Stories.

[Jan]

Hi all, Steven just informed me, that there is a Typo in the address;
Correct is
http://slidesnstories.tiddlyspot.com/

It is good you post,
I just finished a new Version of there Remote,
What needs to be done now is a Theme/Storyview for presentations.

Greetings,
Jan





Hi Steven,
thanks for your post. I think creating an environment for slideshows 
would be an important step for TW.
I made a different approach to create slideshows in 
slidesnsotries.tiddlyspot.com.

-It is working with lists instead of tags.
Under stories in the sidebar it contains a tool to save and load lists 
of tiddlers.
-I made a slideshowremote for a second monitor which can be accessed on 
the pagetoolbar,
-This remote contains a list to jump to tiddlers and buttons to change 
theme and pallete.
-I also have chosen punch as a first attempt for a slideshowtheme but I 
am not really satisfied with the punch theme because it has troubles 
with the fullscreen-mode.


I am still looking for a theme/plugin which has more options, especially 
for combining text with images and animations more precisely.
I would like to have a mechanism to split tiddlers in tinier parts for 
presentations (1-5 Prases Maximum) and display the extracted parts with 
something like impress.js or reveal.js.

Alas, this is beyond my skills for now...
I hope some of you share such Ideas, it would be nice to work togethert 
on themes and tools...

- Jan













Am 02.12.2016 um 19:53 schrieb Steven Schneider:

Hello, all.

I am playing with the Punch theme, in an attempt to create slideshows 
within existing TiddlyWikis. I've started by trying to set up a Wiki 
to open with a slide show, and then move into a more familiar 
presentation of the wiki.


In https://stevesunypoly.updog.co/adam/empty.html (a dropbox hosted TW 
via updog), I've done a bunch of work to get it started. I was 
wondering if anyone else has played with a similar approach, or has 
comments on what I'm doing here.


Thanks,

//steve.

--
You received this message because you are subscribed to the Google 
Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to tiddlywiki+unsubscr...@googlegroups.com 
.
To post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d4b515fa-d50e-4f56-a941-f69eea83ae52%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/586D0B5B.2070209%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Import Tiddles automatically in Tiddlywiki

[Stéphane Delaye]

Hello guys !

Thanks to Mario guidelines, it works !
My problem was CORS. It was enabled on my couchDB server but not with the 
right permissions.
 

https://pouchdb.com/getting-started.html#enabling_cors 
Basically this part: 

  npm install -g add-cors-to-couchdb
  add-cors-to-couchdb

Or if your database is not at 127.0.0.1:5984:

$ add-cors-to-couchdb http://me.example.com -u myusername -p mypassword


I worked on ubuntu server 14.04. The script add-cors-to-couchdb doesn't 
work but we can change the options in /etc/couchdb/default.ini

[httpd]
enable_cors = true

[cors]
credentials = true
; List of origins separated by a comma, * means accept all
; Origins must include the scheme: http://example.com
; You can’t set origins: * and credentials = true at the same time.
origins = *
; List of accepted headers separated by a comma
headers = accept, authorization, content-type, origin, referer, x-csrf-token
; List of accepted methods
methods = GET, PUT, POST, HEAD, DELETE

I just have to play with it now!!!

 

> Best regards,
> Stephane 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/797ea5c4-bd6c-4db8-bca4-bd7b4c11fe2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Use multi-file layout without using NodeJS?

[BJ]

Going away from nodejs would involve some work. Tiddlywiki is a dual 
platform application one platform is nodejs the other is the browser. For 
example:

tiddlywiki contain a packaging application that runs under nodejs - in the 
boot.js - this contains a build system, one feature is that it can package 
directory trees containing tiddlers into plugins. This makes it super easy 
to use git to manage plugin dev.

tiddlywiki is also a dedicated http tiddler server written for nodejs - it 
'knows' how to sever and save tiddlers.

I think that nowadays nodejs is easy to install and use on any platform, 
and npm is included in nodejs

all the best

BJ

On Wednesday, January 4, 2017 at 1:50:28 AM UTC+1, Evade Flow wrote:
>
> > is there some way I can access/modify this collection of files using 
> only git and a browser?
>
> Driving home this evening, I realized this was a bit of a silly question 
> for somebody who professes to be a software developer by trade to ask—doh! 
> (Can you tell I'm not a web developer?) Looking at the files processed by 
> tiddlywiki+NodeJS, I see that *none* of them are HTML. It truly is 
> "tiddlers all the way down", so... *something* has to convert all those 
> .tid files to HTML so the browser can display them.
>
> I guess I should rephrase my question as: is there some way of serving 
> multi-file TW content that requires less setup work than NodeJS? I'm 
> thinking about how Python contains builtin modules that let you run 
> something like this in a folder:
>
> $ python -m SimpleHTTPServer 8000
>
>
> For me, this would be a big win because (as it happens) just about every 
> machine I work on already has Python installed. And they *all* have Perl, 
> which I believe has a similar (built-in) capability[?] So it would be "one 
> less thing" to worry about it when configuring a new environment.
>
>
> On Tuesday, January 3, 2017 at 4:44:43 PM UTC-5, Evade Flow wrote:
>>
>> I've been experimenting with TiddlyWiki and NodeJS, and discovered that 
>> 'importing' my mono-html file (using tiddlywiki --load) causes it to be 
>> converted into a bunch of discrete files. Further experiments reveal that 
>> it is possible—seemingly, at least—to sync these files (and hence, my 
>> entire wiki) to multiple machines using git push/pull. The one catch is: 
>> it appears that the only way to actually *use* a TiddlyWiki structured 
>> this way is to serve it using NodeJS? Is that correct? Or... is there some 
>> way I can access/modify this collection of files using only git and a 
>> browser?
>>
>> I ask because the setup I'm fumbling my way towards seems a bit... 
>> cumbersome. I'm a software developer by trade, so sync'ing git repos to 
>> multiple machines comes as naturally as breathing. In contrast, doing a 
>> local install of Node + npm + tiddlywiki on each machine I want to access 
>> the data from feels like a lot of extra effort. I use Windows and Linux at 
>> work, and OS X at home, and I'd rather not bother figuring out the nuances 
>> of how to do that dance on all three platforms—especially given that I 
>> don't have admin/root access on all the machines I'd like to access my 
>> wiki(s) from.
>>
>> I already have a *killer* setup for managing my myriad config files (
>> .vimrc, .zshrc, .tmux.conf, etc.) and various plugins using myrepos 
>>  and vcsh 
>> . *Everything* is stored in git, so I 
>> can sync my setup around to whatever machines I want. It would be 
>> enormously helpful if I could do the same with my TiddlyWiki(s). Is this 
>> possible?
>>
>> *NOTE*: After trying it a few times, I don't have much interest in 
>> trying to sync changes to monolithic TW files. The mono-HTML files are 
>> huge, and the diffs contain so much 'noise' that trying to merge updates 
>> from multiple machines seems like an impossibility. (Perhaps I'll find that 
>> the multi-file layout has quirks/pitfalls of its own, but so far, it seems 
>> really easy to understand and reason about...)
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3bea-6fa5-4d58-9b42-21c356b8c34d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

[Dmitry Sokolov]

Regarding renaming tiddlers, it is not recommended on LikeInMind while 
technically possible.

In order to avoid dead links and lost connections, tiddlers are federated 
under a desired name. The content of the "old" tiddler is replaced with the 
link onto the "fresh" one. :)
Replacement of the obsolete links is done manually, when realised/needed. 
Ideally, a "garbage collector" would be great to have.

Just my 2 cents,
Dmitry

On Saturday, 11 June 2016 20:07:25 UTC+12, Jeremy Ruston wrote:
>
> Hi Jan
>
> Yet two my mind there is two missing features:
>>
>
> I'd acknowledge the impact of the issues you mention, but fixing them is 
> 1,000 times easier than introducing full support for slicing.
>  
>
>> -When you discover that the content you wish to change was transcluded, 
>> it takes some time to get to the real tiddler; in most cases I have to find 
>> and open with the searchbar.
>> It would be practical if transclusions were clickable Links in the 
>> edit-Mode. Could this be done with a template or plugin? 
>>
>
> My favoured approach to fix this is to introduce a mode that makes 
> transclusions visible, so that one can directly click on a link to open the 
> target tiddler.
>  
>
>> -It would be important to have better Security mechanisms against 
>> destroying links. Especially renaming tiddlers can have dangerous effects. 
>> It would be nice if users were shown a Modal informing about Links Lists 
>> and Transclusions for which the Tiddker has importance..
>>
>
> As discussed elsewhere, I'd favour support for automatically replacing 
> references to a tiddler when it is renamed.
>
> Best wishes
>
> Jeremy.
>
>  
>
>>
>> Regards Jan 
>>
>> In TWClassic when changing the Name of a Tag-Tiddler i was asked wheter I 
>> wished to change the tags to. 
>>
>> On Wed, Jun 8, 2016 at 3:40 PM, Jeremy Ruston > > wrote:
>>
>>> It’s clear that users want to be able to write/paste long passages of 
>>> text into a tiddler and then individually address sections (or 
>>> slices/chunks). In practice, I think that means that anything that one can 
>>> presently do to an entire tiddler needs to be possible with a slice: 
>>> transclusion, linking, searching, etc.
>>>
>>> That means that the system has to deal with two levels of granularity: 
>>> slices and entire tiddlers. Internally, everywhere that we manipulate 
>>> tiddlers we’d need to support slices too.
>>>
>>> In fact, slices would become the fundamental unit; an entire tiddler 
>>> would be a special case of a slice covering the entire tiddler.
>>>
>>> That’s where things get interesting: now we’ve redefined a slice to be a 
>>> tiddler (which is just what we call a fundamental discrete unit of content 
>>> in TiddlyWiki). Now, for performance reasons, we’d want to avoid repeatedly 
>>> scanning tiddlers to extract the slices; instead, we’d want to store the 
>>> individual slices separately so that we can efficiently address them as 
>>> needed.
>>>
>>> You can probably see where this goes: we’ve just ended up *renaming* 
>>> “tiddlers” to “slices”, and adding facilities to deal with sequences of 
>>> slices as discrete entities called “tiddlers”.
>>>
>>> That’s pretty much where we are today: it’s easy to combine several 
>>> tiddlers to make them appear to be a single tiddler: we use transclusion, 
>>> or macros based on transclusion like the TOC macro.
>>>
>>> We’ve still got the problem of dealing with long passages of text: 
>>> that’s where the text-slicer plugin comes in, showing one way that these 
>>> long texts can be split into chunks, and the chunks recombined in flexible 
>>> ways.
>>>
>>> So, my position isn’t ideological, nor am I wilfully ignoring feedback 
>>> from users. But I am asserting that from an engineering perspective it’s 
>>> cleaner and more efficient to be dealing with a single fundamental entity, 
>>> and to approach the original problem from the other end: by splitting and 
>>> recombining.
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>> On 8 Jun 2016, at 14:27, Jed Carty  
>>> wrote:
>>>
>>> I am a bit stuck at the moment because while I don't want to discourage 
>>> any exploration into different ways of using TiddlyWiki there is a TW5 way 
>>> of doing what you are talking about, which is to use either more tiddlers 
>>> or fields which you then place wherever you want them using transclusions.
>>>
>>> Using templates you could have the anchor tag part of the transclusion 
>>> so you could navigate to a spot in an open tiddler. If you want to be able 
>>> to both open a tiddler and navigate to some spot in that tiddler than we 
>>> would need a more complex macro but it may be able to be done using only 
>>> wikitext and simple html. Or we may need to make an action widget that does 
>>> the same action as clicking on a normal link.
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this 

[tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

[Dmitry Sokolov]

In LikeInMind practice, transclusion is a very rare case. Transcluded 
tiddlers may change with time in the context of the hosting topic / main 
page. Those changes may conflict with the content of the topic / page they 
are transcluded to. Federation is highly recommended instead.

Both, transcluded and federated tiddlers must have back links to the source 
pages.
To avoid confusion, transcluded tiddlers are framed. Federated tiddlers 
have no formatting differences with the rest of the page they are pasted to.

I hope you find it helpful.
Cheers,
Dmitry

On Saturday, 11 June 2016 11:22:54 UTC+12, Jan wrote:
>
> Hi Jeremy
> The concept of an atomic datastructure sounds logic.
> Yet two my mind there is two missing features:
>
> -When you discover that the content you wish to change was transcluded, it 
> takes some time to get to the real tiddler; in most cases I have to find 
> and open with the searchbar.
> It would be practical if transclusions were clickable Links in the 
> edit-Mode. Could this be done with a template or plugin? 
>
> -It would be important to have better Security mechanisms against 
> destroying links. Especially renaming tiddlers can have dangerous effects. 
> It would be nice if users were shown a Modal informing about Links Lists 
> and Transclusions for which the Tiddker has importance..
>
> Regards Jan 
>
> In TWClassic when changing the Name of a Tag-Tiddler i was asked wheter I 
> wished to change the tags to. 
>
> On Wed, Jun 8, 2016 at 3:40 PM, Jeremy Ruston  > wrote:
>
>> It’s clear that users want to be able to write/paste long passages of 
>> text into a tiddler and then individually address sections (or 
>> slices/chunks). In practice, I think that means that anything that one can 
>> presently do to an entire tiddler needs to be possible with a slice: 
>> transclusion, linking, searching, etc.
>>
>> That means that the system has to deal with two levels of granularity: 
>> slices and entire tiddlers. Internally, everywhere that we manipulate 
>> tiddlers we’d need to support slices too.
>>
>> In fact, slices would become the fundamental unit; an entire tiddler 
>> would be a special case of a slice covering the entire tiddler.
>>
>> That’s where things get interesting: now we’ve redefined a slice to be a 
>> tiddler (which is just what we call a fundamental discrete unit of content 
>> in TiddlyWiki). Now, for performance reasons, we’d want to avoid repeatedly 
>> scanning tiddlers to extract the slices; instead, we’d want to store the 
>> individual slices separately so that we can efficiently address them as 
>> needed.
>>
>> You can probably see where this goes: we’ve just ended up *renaming* 
>> “tiddlers” to “slices”, and adding facilities to deal with sequences of 
>> slices as discrete entities called “tiddlers”.
>>
>> That’s pretty much where we are today: it’s easy to combine several 
>> tiddlers to make them appear to be a single tiddler: we use transclusion, 
>> or macros based on transclusion like the TOC macro.
>>
>> We’ve still got the problem of dealing with long passages of text: that’s 
>> where the text-slicer plugin comes in, showing one way that these long 
>> texts can be split into chunks, and the chunks recombined in flexible ways.
>>
>> So, my position isn’t ideological, nor am I wilfully ignoring feedback 
>> from users. But I am asserting that from an engineering perspective it’s 
>> cleaner and more efficient to be dealing with a single fundamental entity, 
>> and to approach the original problem from the other end: by splitting and 
>> recombining.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On 8 Jun 2016, at 14:27, Jed Carty  
>> wrote:
>>
>> I am a bit stuck at the moment because while I don't want to discourage 
>> any exploration into different ways of using TiddlyWiki there is a TW5 way 
>> of doing what you are talking about, which is to use either more tiddlers 
>> or fields which you then place wherever you want them using transclusions.
>>
>> Using templates you could have the anchor tag part of the transclusion so 
>> you could navigate to a spot in an open tiddler. If you want to be able to 
>> both open a tiddler and navigate to some spot in that tiddler than we would 
>> need a more complex macro but it may be able to be done using only wikitext 
>> and simple html. Or we may need to make an action widget that does the same 
>> action as clicking on a normal link.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com .
>> To post to this group, send email to tiddl...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/097acf29-8df9-45aa-8618-f9c4216a2226%40googlegroups.com
>>  
>>