Re: [twdev] Announcing: easy Google Drive integration

[Arlen Beiler]

Hey, looks pretty good. Just thought I'd add a few thoughts from my own
experience with https://twcloud.github.io/.

The custom saver idea is interesting. Just thought I'd point out that
TiddlyWiki already includes a saver which uses the DOM instead of
JavaScript to handle the save sequence.
It's fine to have two different methods, I just thought I'd point this one
out as well. It's the one I use with TW Cloud.

The Saver itself:
https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/savers/tiddlyfox.js

Host Window example:
https://github.com/Jermolene/TiddlyDesktop/blob/master/source/js/utils/saving.js

Any plans to add Dropbox? I've worked with the API in other projects and
it's fairly straightforward. Pretty similar to the Google API. It also has
an app folder option as demonstrated at
https://twcloud.github.io/tw5-dropbox/

Most of these online cloud services have a feature that allows you to ask
the user to select a single file for editing and then gives you a token to
use to save the file. I know at least Dropbox does that and I think I've
seen it on Google Drive. Also, Dropbox lets you use an App folder, which
would work perfectly in your case. I'm surprised Drive doesn't have a
similar feature.

I won't ask you about enabling data folders because I already know they
aren't even in the same ball park. Hopefully some day someone will figure
that one out.

Thanks for doing this.
Arlen



On Sun, May 2, 2021 at 11:46 PM Ryan Kramer 
wrote:

> I have prototyped a simple webpage that allows you to load a TiddlyWiki
> from your Google Drive and save the changes back. Perhaps the TiddlyWiki
> project will be interested in hosting a more polished version at
> my.tiddlywiki.com (for example)?
>
> I built this so I can use my wiki from any browser that has internet
> access, as long as I can remember my Google credentials.
>
> Website: https://default-kramer.github.io/
> Source: https://github.com/default-kramer/default-kramer.github.io
> How to Use It:
> 1. Create a fresh Google account if you don't trust me (and why should
> you?)
> 2. Create a folder named "asap.wiki" in the root of your Google Drive.
> (The name asap.wiki comes from an earlier idea of this project.)
> 3. Add exactly one TiddlyWiki file to the asap.wiki folder. It must be a
> new enough version of TiddlyWiki that includes the CustomSaver (added here
> https://github.com/Jermolene/TiddlyWiki5/pull/4908)
> 4. Browse to https://default-kramer.github.io/ and click the Authorize
> button. Continue past the "unverified app" warning.
> 5. The website should load the wiki from your Google Drive and display it
> in an iframe.
> 6. Make some changes and save your wiki.
> 7. Verify that the changes were written back to your Google Drive
>
> Open Issues:
> 1. Obviously UI/UX is not my strong suit. Someone with more
> skill/experience than me could make this look and work a lot better.
> 2. If more than one wiki exists, it should prompt the user which one they
> want to open. (Right now it just fails.)
> 3. The app needs to be verified with Google. I think I am limited to 100
> users right now because I am unverified.
>
> Let me know if there is interest in making this an official TiddlyWiki
> offering and, if so, what I can do to help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/597ccec3-bac5-44c7-8258-b53048aca169n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSSPR%2BRD%3DGYEL-9ziqt%2BNyDR6yx1uJi2cj_a9EU48GRPeA%40mail.gmail.com.

Re: [twdev] Re: Accessing Tiddlers from JavaScript (Crosspost from main TW group)

[Arlen Beiler]

To get the list of tiddler titles, you should probably use a filter and get
the filter from a tiddler. This is standard practice in the core so you or
users can exclude or include tiddler titles in the list.

To get the functions you can call, you probably want to use the global $tw
variable.

If you want to get the exports of an individual Javascript tiddler, you
should probably load it into a proper type checker and get the types from
there.

Just my thoughts. I'm sure there's more than one way to skin the cat.

Arlen

On Sun, May 10, 2020 at 8:53 AM Jed Carty  wrote:

> To get a tiddler in javascript you use the function
> $tw.wiki.getTiddler('tiddler title'), it returns a json object with the
> from:
>
> {
>   fields: {
> title: "tiddler title",
> other_field: "field contents"
>   },
>   cache{}
> }
>
> so to get the text of a tiddler you could use:
>
> var text = $tw.wiki.getTiddler('tiddler title').fields.text
>
> there have been a few efforts to make full documentation for the
> tiddlywiki internals, but no one has succeeded yet.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/c7a0d8c0-7939-4ec7-9cf0-4eccb7733a76%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSTOpefhvC8fiY1UPkqnmxSvmGECAZCej9xF-QkrDdxiSA%40mail.gmail.com.

[twdev] A comprehensive framework

[Arlen Beiler]

There are so many different pieces of TiddlyWiki server solutions scattered
around the internet. What can we do to bring everything together into one
product? For instance, NoteSelf had a lot of good features, but now you
can't get a free storage solution easily for it. TiddlyDesktop accomplishes
the same thing as TiddlyServer, but in NodeWebkit or Electron rather than a
full browser. Bob has a bunch of random features that would be incredibly
useful, but most of them I can't just add to TiddlyServer because they are
actually features of TiddlyWiki. We're slowly getting syncing more
consistent, and now is probably the time to setup server-sent-events, but
how? I guess I'll open an issue for that one.

Thoughts?
Arlen

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSR0V-ms4DfG-NAF1yi%2BrEmmvVJz4UgOiGX55CFW7Xi5QA%40mail.gmail.com.

Re: [twdev] How to hook in SyncAdaptor to execute code before saveTiddler() and after loadTiddler() ?

[Arlen Beiler]

Great idea, just an aside note, for security purposes, you should generate
a 64 byte long random byte array and use that for the encryption key and
then store it as base 64 wherever you would normally trust storing those
private tiddlers, or in your password manager as a secure note. You can
still store it in localstorage for each browser, I just mean when you want
to access it on a new computer it could be in your password manager or
another storage place that you can usually access.

On Sun, Apr 12, 2020 at 11:27 AM LinOnetwo  wrote:

> Hi, I'd like to push TW5-EncryptTiddlerPlugin a step forward.
>
> I want my wiki to work like Notion, so I can mix Public and Private
> content in one wiki, and tag some content to be Public.
>
> So I need to encrypt tiddler with for example "EncryptThis" tag just
> before any SyncAdaptor, e.g., NodeJS SyncAdaptor executes the saveTiddler()
>
> And I need to decrypt tiddler withi such tag, just after any SyncAdaptor
> executes the loadTiddler() .
>
> ---
>
> Only in this way, can we achieve following goals:
>
> 1. On browser that has enter the password ( I will remember password in
> the browser localstorage ) , all tiddlers are always visible, and
> searchable. ( Only when tiddler is sync back to nodejs, it become encrypted
> )
> 2. When I backup tiddlers to Github, Private tiddlers are always encrypted
>
> ---
>
> Additional context:
>
> I'm using NodeJS wiki in localhost, use WebCatalog to make it DesktopApp
> and MenuBarAPP.
> And I backup tiddlers to Github.
> A CI will build HTML from tiddler files after git push, and serve it as a
> website.
>
> ---
>
> Conculsion: I need to hook in SyncAdaptor life cycle, or write a
> middleware for SyncAdaptor. Does anyone know if there is an API to do so?
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/ffbca28a-a263-4873-ad42-bbae0fee6f31%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRdcQgqUZW%2BbOvjQ%3DjFaUP5rFVFOcg2QiTwD5BdxcMbWg%40mail.gmail.com.

Re: [twdev] Re: Worth considering: Ease of installing plugins VS. pressure to include in core

[Arlen Beiler]

I did an experiment to find out exactly how much space we could save. I
took all the Javascript modules, which get loaded during startup, and
dumped the code into a file. The file is 1 MB and when I put it through
Webpack, it brings it down to 650 KB. Of course, this isn't practical for
empty.html, but it was an interesting experiment anyway, and it did work
properly.

I wonder what other optimizations we could do for the HTML store that would
improve the storage size.

For instance, if I dump the entire store area div into a file (which is 2.0
MB) and gzip it, the output is 0.35 MB. The store area actually accounts
for 95 % of the file size, I believe, with boot being only 75 KB. For
empty.html it is 2.18 vs 0.37. While this is probably not the best option,
gzipping the store and base64 encoding it (which increases the size by 4/3)
is a realistic option, at lease for the $:/core tiddler. Since empty.html
entirely consists of the $:/core tiddler (I just checked), that would
definitely reduce the file size.

Obviously there is something inefficient about the HTML storage system
currently being used, because the plugin.info file in TiddlyServer is 1.7
MB and is virtually identical to the JSON stored in the HTML file if I'm
not mistaken. One reason for this is that the double quote, which is 1 byte
long and appears everywhere, is expanded to 6 bytes in the HTML file
(). This also applies to angle brackets. The plugin.info file is
generated with JSON.stringify(core), but the store file is generated with
JSON.stringify(core, null, 2), which uses two space indentation and line
breaks. However, like I said, this is only creates a 15% increase in file
size, compared to gzipping.

As an interesting side note, GZipping the plugin.info file gives an output
of 0.31 MB, which is almost the same as the HTML representation.

Just some thoughts.
Arlen

On Fri, Sep 13, 2019 at 4:03 PM Mohammad  wrote:

> A modular approach!
>
> * core (minimum essential tools)
> * themes
> * languages
> * plugins
> ** highlight.js
> ** katex
> ** codemirror
>
> 
>
> url:
> https://medium.com/5000-things/learning-from-lego-a-step-forward-in-modular-web-design-d8ff953f45a8
>
> On Friday, September 13, 2019 at 10:29:44 PM UTC+4:30, Mat wrote:
>>
>> Just a thing I've been reflecting over:
>>
>> *The easier it is to install plugins*, either permanently install them
>> or - perhaps even more importantly - to do a temporary use+delete install...
>>
>> *...the less the need and pressure to include functionality in the core /
>> std distro.*
>>
>> The coming "dynamic loading of plugins
>> " is a
>> very welcome step in this direction. I can't tell if this is an
>> implementation of the request to Provide a mechanism to register plugins
>> after boot . Another
>> addition was the implementation of making tag pills work for multi-tiddler
>> DnD imports. A more general idea would be a handle to DnD filtered lists
>> . A further step
>> would be to Extend Download button to offer adding plugins
>> . And eventually
>> we'll hopefully be able to solve the Big One, i.e a library that serves a
>> federated collection of plugins.
>>
>> Apropos this, if installing and removing plugins were totally painless,
>> would it be possible to excise features from the core / standard distro?
>> Just curious.
>>
>> <:-)
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/06c2d171-0304-4193-9587-bf50371908e9%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSQ0T9Asv46Pr8PO9NCZf96Sr7ghoskXq8f6Uq0K6BrR5Q%40mail.gmail.com.

Re: [twdev] Re: New Wikitext leading character for paragraphs/text sentences?

[Arlen Beiler]

Maybe we should say if the parser finds the asterisk directly inside a UL
tag then it should just output the LI tag without another UL tag. Some with
the pound sign and the colon. In other words, if the outer list element is
the immediate parent to the list item line, it should not output a second
outer list element inside it but go directly to the inner list item. The
same would apply to the table tag.

On Mon, Sep 2, 2019 at 8:36 AM PMario  wrote:

> On Monday, September 2, 2019 at 1:18:31 PM UTC+2, @TiddlyTweeter wrote:
> ...
>
>> I thought it an interesting question because its trying to find a direct
>> simple solution to a layout issue that makes a bunch of sense.
>>
>
> Mixing content with style isn't the best idea, because there should be
> "separation of concerns". So wikitext should be used for content and CSS
> should be used for styling.
>
> BUT
>
> We already _need_ to mix it eg:
>
> *.userClass list-text
> **.otherClass more-text
>
> Which isn't the best solution, but the only one. ... So if we want to get
> work done, we need to make compromises. ... AND we probably have to live
> with them for ever.
>
> The issue, I think, is, as you indicate, about parsing? Or, maybe, CSS?
>>
>
> I think both. See my other posts.
>
> I think, creating the `^` prefix for "parent-classes" is a real
> improvement, since we only need to use the "ugly syntx" once.
>
> At the moment we need:
>
> *.class some text
> *.class more text
>
> in the future it would be only
>
> *^class some text
> * more text
>
> But I'm not 100% convinced atm.
>
> -mario
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/ef87590d-8887-4a20-978d-83d8b7c0d1f1%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSQH9b3aXpPJe7rjXvN3BnPCt6nWce264SKsCv2pTT59jQ%40mail.gmail.com.

Re: [twdev] Re: New Wikitext leading character for paragraphs/text sentences?

[Arlen Beiler]

I like what is being proposed here.

I agree with mario that it would be better to add a converter, or perhaps
just a search and replace that supports regex so we can replace single line
breaks with double line breaks. That might be another good option.

The Wikipedia community uses the colon character for indenting text in a
forum thread style (which converts to the same HTML as this). It's not the
most efficient but it works fine. Because each reply is indented you'll
sometimes see a long-running debate WITH 12 COLONS STARTING A LINE. That's
a big indent! They don't use it on articles as much as on discussion pages.

Just a couple observations.
Arlen



On Mon, Sep 2, 2019 at 8:25 AM PMario  wrote:

> On Monday, September 2, 2019 at 2:20:46 PM UTC+2, PMario wrote:
>
>
>>  - I'm not sure if the parser can handle that.
>>  - I'm not sure if this can be implemented in a consistent way.
>> Especially:
>>
>> * level 1
>> **^x level 2
>>
>> doesn't make sense, since it is the same as
>>
>> *.x level 1   ... Which is much more readable. <-- uups that's wrong!
>>
>
>
> **^x level 2
>
> Having a look at the HTML code it does make sense. ...
>
> -m
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/522ab1c2-a1e3-4605-bedf-d2edf879%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRNiW0iemL-3L8FoW3B_BMRH-2CVtrbpC%2BLDqJ2ecg%2B5A%40mail.gmail.com.

Re: [twdev] wikification seems work inappropriately

[Arlen Beiler]

I think it helps the user discover when they don't do something quite
write. Seeing an entire paragraph in bold text except for the first two
words is a pretty quick way to tell that you messed something up.

On Fri, Aug 30, 2019 at 3:14 AM Mohammad  wrote:

> In tiddlywiki.com create a new tiddler and put the below text
>
> This is t__tarla and I am there.
>
> On save TW shows the above text as
>
> This is t*tarla and I am here.*
>
>
> Why TW does not check the closing delimiter e.g *__*?
>
> Should TW recognize some word boundaries?
>
>
> --Mohammad
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/ef760a90-0a9b-445e-a7fb-9bc230675946%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRm9DVRP4Pf7TOgnav6P49szwEFC9N%3DMd_1eDok9NrNNw%40mail.gmail.com.

Re: [twdev] Re: Tailwind - a CSS framework as if made for TW !

[Arlen Beiler]

I think for the UI we should have scoped classes. In other words, instead
of setting the classprefix using the quaify macro, we would just set it
directly to "tc-sidebar-", "tc-topbar-", "tc-page-header-" for instance and
then within that each component would have its own class and the CSS would
be in the themes, but it would be written so that each known section would
have its own section in the theme and be very easy to find and modify. The
class names are already basically setup that way, but the CSS definitely is
not! We could add a section to the tiddler edit mode which would add a text
field for the stylesheet that relates to that template tiddler, perhaps
based on a tag such as $:/tags/themed-template and a field specifying the
classprefix. I believe this is already a feature of the edit template, so
it could be easily done without modifying anything besides the theme and
adding the tags and fields to the right tiddlers. The theme stylesheet
would then pull all the themed templates' stylesheets into one generated
stylesheet. The stylesheets would be shadow tiddlers from the theme and
would be named according to the classprefix. With that in place it would
make ton of things a whole lot easier, I think.

This is just me brainstorming a random idea that I see in my head. I
haven't even thought about it before. So I may be missing some other pieces
of the puzzle, but these are my ideas.

I do agree that the whole thing would be a lot easier to do with flex, and
I think that may be a step in the right direction, but block and
inline-block still work excellent with a little extra fiddling.

Arlen

On Wed, Aug 28, 2019 at 7:17 AM TonyM  wrote:

> Arlen
>
> This looks promising because scoping css to a specific tiddler or set of
> tiddlers rather than the page is critical. So often in tiddlywiki we are
> thinking with a tiddler focus not a whole of html file css, except with
> themes which are by definition whole of wiki. It makes me ask if we could
> have one or more tiddler themes.
>
> We know html and css are partners in crime so I would like to see more
> thought about structures within tiddlers that we provide the classes to
> enhance with. An example may be tiddler layouts with supporting css that
> allows the tiddlers to be targeted.
>
> Perhaps we can choose a single other framework for flex boxs etc...  And
> build the css to support that.
>
> Regards
> Tony
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/8498ff57-f699-4b73-9f42-c88bdbf4dffe%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSR-FXNe_EpLGkYQK93wGuTkUOdM9zLNrXf3CupRCEFV9g%40mail.gmail.com.

Re: [twdev] Re: Tailwind - a CSS framework as if made for TW !

[Arlen Beiler]

I'm Shocked! It Worked!

\define class(suffix) $(classprefix)$$suffix$
\define css()
.$(classprefix)$align {
  text-align:right;
}
\end
<$set name="classprefix" value=<>>
<$text text=<<css>>/>
>>Hello world


On Tue, Aug 27, 2019 at 10:29 PM Arlen Beiler  wrote:

> This is why I want the autoparagraph feature GONE! Ok, whatever, maybe
> that won't happen right away, but we'll get somewhere close eventually. I
> love the idea of adding parameters to the mime type. I didn't even know
> that was a thing before today.
>
> But this is a good read (the article from the original post):
> https://adamwathan.me/css-utility-classes-and-separation-of-concerns/
>
> I think we should consider that idea, or perhaps an alternate idea that I
> got from react native where styles are kept near the elements they style.
> So for instance every template tiddler would have a stylesheet tiddler and
> use a variation of the qualify macro to return the class names to use for
> those styles, and also add those classes to the global stylesheet whenever
> the tiddler is rendered, probably using the same macro somehow, but still
> it would be unique based on the position in the widget tree. The styles
> could be defined using a macro as well, I believe. That would probably be
> easier. But I don't quite know how to get the styles into the global
> stylesheet. Maybe we need to have a style widget that just sticks in a
> style tag with its unique class names right there.
>
> On Tue, Aug 27, 2019 at 6:30 PM Thomas Elmiger 
> wrote:
>
>> Hi Mat, Jeremy and Mario,
>>
>> Thanks for thinking of me, Mat, and my usage of tachyons elements in my
>> Bricks studio.
>>
>> The reasons why I (only) adapted selected parts of tachyons (typography,
>> spacing/measures, some colours, ...) are:
>>
>>- I like the simple and useful design concept (as a starting point).
>>- I basically agree with what Mario says.
>>- TiddlyWiki can already do magic stuff (variables, calculations –
>>JavaScript in CSS –, theme-tweaks, palettes, ...).
>>
>> Some things that are difficult in standard TW and that I tried to improve
>> in Bricks:
>>
>>- Find the right spot in the existing CSS to change.
>>- So I transformed it into a collection of specialised small CSS
>>   documents.
>>   - Colour calculations, e.g. to blend or invert colours or to check
>>contrast (accessibility).
>>   - My ambition was: Enable users to choose some base colours, and
>>   then calculate everything else automagically. That turned out to be
>>   incredibly hard.
>>   - Still I think my ColorAction plugin is great and the Colour
>>   Manager <https://tid.li/tw5/test/bricks.html#Colour%20Manager>
>>   points in the right direction (it allows to define/calculate colours 
>> based
>>   on other colour variables – and still see them, a big improvement 
>> compared
>>   to the standard palette manager).
>>   - Use different colour schemes for content and sidebar (e.g. dark
>>sidebar, light background for content)
>>   - I hacked a way around this but it was a long and hard process.
>>   - Save computing power: With TWs flexibility, the more variables
>>you have the more complex calculations are needed to render the design.
>>- So I implemented a simple "compiler" that renders one big
>>   stylesheet without any variables. I can use this "frozen" version to
>>   publish faster wikis.
>>- Adjust spacing to follow a system (margins, paddings, whitespace
>>around headings, ...)
>>   - This is where my tachyons-based variables were extremely helpful.
>>
>> So features like these would be more important for me, than what/if any
>> framework is used. As long as there is a solid concept that goes through
>> all of TW and is easily adaptable (using far less parameters than the
>> ControlPanel offers today) I would actually not care, where it is derived
>> from.
>>
>> All the best,
>> Thomas
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWikiDev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to tiddlywikidev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywikidev/507dced0-8a53-42a7-970c-fa7beb88177e%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywikidev/507dced0-8a53-42a7-970c-fa7beb88177e%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRVa2Uj6ZnPvjobeVObK6Czy86UO0AY4QDS5MR5iqOPcA%40mail.gmail.com.

Re: [twdev] Re: Tailwind - a CSS framework as if made for TW !

[Arlen Beiler]

This is why I want the autoparagraph feature GONE! Ok, whatever, maybe that
won't happen right away, but we'll get somewhere close eventually. I love
the idea of adding parameters to the mime type. I didn't even know that was
a thing before today.

But this is a good read (the article from the original post):
https://adamwathan.me/css-utility-classes-and-separation-of-concerns/

I think we should consider that idea, or perhaps an alternate idea that I
got from react native where styles are kept near the elements they style.
So for instance every template tiddler would have a stylesheet tiddler and
use a variation of the qualify macro to return the class names to use for
those styles, and also add those classes to the global stylesheet whenever
the tiddler is rendered, probably using the same macro somehow, but still
it would be unique based on the position in the widget tree. The styles
could be defined using a macro as well, I believe. That would probably be
easier. But I don't quite know how to get the styles into the global
stylesheet. Maybe we need to have a style widget that just sticks in a
style tag with its unique class names right there.

On Tue, Aug 27, 2019 at 6:30 PM Thomas Elmiger 
wrote:

> Hi Mat, Jeremy and Mario,
>
> Thanks for thinking of me, Mat, and my usage of tachyons elements in my
> Bricks studio.
>
> The reasons why I (only) adapted selected parts of tachyons (typography,
> spacing/measures, some colours, ...) are:
>
>- I like the simple and useful design concept (as a starting point).
>- I basically agree with what Mario says.
>- TiddlyWiki can already do magic stuff (variables, calculations –
>JavaScript in CSS –, theme-tweaks, palettes, ...).
>
> Some things that are difficult in standard TW and that I tried to improve
> in Bricks:
>
>- Find the right spot in the existing CSS to change.
>- So I transformed it into a collection of specialised small CSS
>   documents.
>   - Colour calculations, e.g. to blend or invert colours or to check
>contrast (accessibility).
>   - My ambition was: Enable users to choose some base colours, and
>   then calculate everything else automagically. That turned out to be
>   incredibly hard.
>   - Still I think my ColorAction plugin is great and the Colour
>   Manager 
>   points in the right direction (it allows to define/calculate colours 
> based
>   on other colour variables – and still see them, a big improvement 
> compared
>   to the standard palette manager).
>   - Use different colour schemes for content and sidebar (e.g. dark
>sidebar, light background for content)
>   - I hacked a way around this but it was a long and hard process.
>   - Save computing power: With TWs flexibility, the more variables
>you have the more complex calculations are needed to render the design.
>- So I implemented a simple "compiler" that renders one big stylesheet
>   without any variables. I can use this "frozen" version to publish faster
>   wikis.
>- Adjust spacing to follow a system (margins, paddings, whitespace
>around headings, ...)
>   - This is where my tachyons-based variables were extremely helpful.
>
> So features like these would be more important for me, than what/if any
> framework is used. As long as there is a solid concept that goes through
> all of TW and is easily adaptable (using far less parameters than the
> ControlPanel offers today) I would actually not care, where it is derived
> from.
>
> All the best,
> Thomas
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/507dced0-8a53-42a7-970c-fa7beb88177e%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSRXPpKDy7a3kqrm340y3%2BtC3wsZH4LLcsUNvZ%2B%3DzK9wYA%40mail.gmail.com.

Re: [twdev] SyncAdaptor

[Arlen Beiler]

I think the main benefit of this over making a startup module to load the
user's tiddlers is that it is far simpler. There is a core template which
loads a separate cache-able Javascript file with the core code and plugins
(instead of including it in the HTML page) which uses
$tw.loadPluginsArray(). You can find the related templates here:
https://github.com/Jermolene/TiddlyWiki5/tree/master/core/templates/external-js

On Wed, Aug 21, 2019 at 12:13 AM Xavier Maysonnave 
wrote:

> Thanks Arlen,
> I keep your idea on the margin when I'll go deeper.
> Quite familiar with async call though.
> However is there any benefits to handle tiddlers that way rather than
> using startup modules ?
> Thanks
>
> Le mercredi 21 août 2019 00:22:12 UTC+5:30, Arlen Beiler a écrit :
>>
>> To load tiddlers on startup you can use the preloadTiddlers array.
>>
>> 1. Put this code in a head script: $tw = { boot: { suppressBoot: true },
>> preloadTiddlers: [] };
>> 2. Query the server for the user's tiddlers and handle the response
>> asyncly when it is recieved (good for performance).
>> 3. Wait for the window load event, which indicates that all code is
>> initialized.
>> 4. Push the JSON tiddlers (as field hashmaps) to the preloadTiddlers
>> array.
>> 5. Call $tw.boot.boot();
>>
>> Tiddlywiki doesn't know the difference between this and a single-file
>> wiki. It works the same in the browser once you call $tw.boot.boot();
>>
>> On Tue, Aug 20, 2019 at 10:34 AM Jeremy Ruston 
>> wrote:
>>
>>> Hi Xavier
>>>
>>> If I understand correctly. The save button call a saver (are the savers
>>> chained in case of multiple setup, eg gitub, gitlab...? ) while the
>>> syncadaptor is dynamic and reacts to events ? If its correct I like the
>>> mechanism as it gives users a way to easily backup their wikis.
>>>
>>>
>>> That's correct. The other thing to bear in mind is that the saver
>>> mechanism can also be used to export any data as a file, it's not
>>> restricted to saving the wiki itself.
>>>
>>> I'm not sure to understand here. I think this is why I'm lost. While
>>> studying the syncadaptor I didn't get any understanding about how the
>>> remote stored wiki has been initialized in the first place and this is why
>>> I was thinking about my described mechanism. Load a self contained wiki.
>>> Setup the ipfs target and then use the syncadaptor to push the contents to
>>> IPFS.
>>>
>>>
>>> In the case of the standard client server configution, the browser
>>> connects to the default route triggering a build of the entire wiki file:
>>>
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/server/routes/get-index.js
>>>
>>> Another alternative is to start with an empty index.html stored anywhere
>>> accessible via HTTP and have it interrogate the server for tiddlers when it
>>> starts up.
>>>
>>> I think this is where I'm going to start. Define a saver and save the
>>> whole content. I was too ambitious to jump right away on a SyncAdaptor.
>>> There is always a learning curve...
>>>
>>>
>>> Indeed, the saver mechanism is conceptually much simpler. It's also
>>> likely to perform better in many situations as one large HTTP transaction
>>> is generally faster than lots of little ones.
>>>
>>> I was following my idea. All the syncadaptors I studied assume that the
>>> content is already on a remote server and I didn't see how the content has
>>> been built in the first place. You explained earlier the external build
>>> process but I still don't understand how the first load is working. If I
>>> follow your mind It means that let's say you offer your user to start from
>>> a set of wiki templates. Those templates are already built by an external
>>> process. I was thinking like described. Load a plain wiki, install the
>>> plugin, setup the plugin then sync to IPFS. The property was meant to
>>> detect whether or not this wiki is already synced. I was looking to some
>>> index technics but I didn't figure out yet how to get and process the store
>>> list.
>>>
>>>
>>> The core client-server implementation uses etags to keep track of
>>> whether a particular tiddler has changed.
>>>
>>> Not sure to understand what you mean by updated. I'm targeting a single
>>> user model. The only updates should come from the user actions. (updated
>>> tiddlers, removed tiddlers,etc...)
>>

Re: [twdev] Re: [TW5-Dev] JSON Tools for Tiddlywiki 5.1.20!

[Arlen Beiler]

Ok, I wrote that rather fast. I like templates and hate code duplication.
But I'm also really bad at wikitext. So this should be rather useful for
me. The fields comment is a TiddlyWiki thing, it's not related to this
plugin. Overall I like it, especially using JSON for the definitions, since
that could be majorly expanded on. This has the potential to make
TiddlyWiki really useful for developer documentation, which would be really
epic because the search is so fast.

On Tue, Aug 20, 2019 at 3:12 PM Arlen Beiler  wrote:

> Wow, this is amazing. This has my attention. I really wish that fields
> worked better with arrays, but this is pretty good.
>
> On Fri, Aug 16, 2019 at 7:49 PM TonyM  wrote:
>
>> Joshua,
>>
>> As I have said before the is a valuable contribution to the tiddlywiki
>> platform. I have a single Question for you below
>>
>> *Background*
>> As I see it People who may be interested in using these tools would
>> include people wanting to import, edit or export JSON data beyond simple
>> tiddler bundles. This is likely with people sourcing or wanting to generate
>> data in JSON format, Tiddlywiki could become a JSON development kit. This
>> could help people using JSON for systems integration projects.
>>
>> However the editor and "modular" User Interfaces for TiddlyWiki stands to
>> offer a powerful addition to building and sharing functionality in
>> tiddlywiki. Have you plans for additional "modular design"? or do you mean
>> through the use of schemas and the json editor to generate forms and obtain
>> input?
>>
>> I am asking this at a strategic level. I have invested substantial effort
>> in building methods to define fields and make these editable within
>> tiddlers without the use of JSON, I intend to continue with this to build a
>> set of rapid development tools, but I see the value of JSON editor and
>> "modular design" that can result from this. I am also keen to leverage your
>> tools for rapid development as well.
>>
>> I have posted here because I see value in identifying when a designer
>> should choose one method over the other. My solution will help manipulating
>> traditional tiddler fields, your solution keeps these (sand boxed) within
>> json.
>>
>> *Question*
>> What do you think are key questions and issues for designers when
>> deciding if the JSON approach is better?
>>
>> Regards
>> Tony
>>
>> On Tuesday, August 13, 2019 at 5:55:31 AM UTC+10, Joshua Fontany wrote:
>>>
>>> Hi everyone!
>>>
>>> I am really excited to announce that I have my proof of concept ready
>>> for "modular" User Interfaces for TiddlyWiki!
>>>
>>> I'm also very excited to officially announce updated JsonMangler and
>>> JsonEditor plugins for TW v5.1.20!
>>>
>>> There were some last minute tweaks, but I've gotten new example wikis up
>>> and running. Any comments or bug reports are greatly appreciated!
>>>
>>> https://joshuafontany.github.io/TW5-JsonMangler/
>>>
>>> https://joshuafontany.github.io/TW5-jsoneditor/
>>>
>>> But, hey, wait Josh, that first thing you said. What does that mean?
>>>
>>> Screenshots are always nice. :D
>>>
>>> [image: JsonUI_conceptUI_viewTemplate_08.12.2019.png]
>>>
>>> [image: JsonUI_conceptUI_editTemplate_08.12.2019.png]
>>>
>>>
>>> I'll try to keep the explanation high-level, but basically:
>>>
>>>
>>>- A Jsoneditor Widget uses a 'schema definition' (a json tiddler) to
>>>render one of two "data json tiddlers".
>>>- The first data-tiddler holds wiki-text (not raw data!) for the
>>>View Template. This wikitext points to fields on the current tiddler and
>>>renders a custom UI elements for each.
>>>- The second data-tiddler holds wiki-text for the Edit Template! It
>>>points to fields on the current tiddler and renders custom UI elements 
>>> for
>>>each.
>>>- Finally, we have two system tiddlers - one tagged
>>>$:/tags/ViewTemplate and the other tagged $:/tags/EditTemplate.
>>>- The only real difference between the two template tiddler's TEXT
>>>is that one points a JsonEditor to the view-data, and the other points to
>>>the edit-data.
>>>
>>>
>>> In this way, we can "group, organize, and modularize" our UI elements.
>>> This helps to greatly reduce cognative-load (how much stress it take you to
>>> 

Re: [twdev] Re: [TW5-Dev] JSON Tools for Tiddlywiki 5.1.20!

[Arlen Beiler]

Wow, this is amazing. This has my attention. I really wish that fields
worked better with arrays, but this is pretty good.

On Fri, Aug 16, 2019 at 7:49 PM TonyM  wrote:

> Joshua,
>
> As I have said before the is a valuable contribution to the tiddlywiki
> platform. I have a single Question for you below
>
> *Background*
> As I see it People who may be interested in using these tools would
> include people wanting to import, edit or export JSON data beyond simple
> tiddler bundles. This is likely with people sourcing or wanting to generate
> data in JSON format, Tiddlywiki could become a JSON development kit. This
> could help people using JSON for systems integration projects.
>
> However the editor and "modular" User Interfaces for TiddlyWiki stands to
> offer a powerful addition to building and sharing functionality in
> tiddlywiki. Have you plans for additional "modular design"? or do you mean
> through the use of schemas and the json editor to generate forms and obtain
> input?
>
> I am asking this at a strategic level. I have invested substantial effort
> in building methods to define fields and make these editable within
> tiddlers without the use of JSON, I intend to continue with this to build a
> set of rapid development tools, but I see the value of JSON editor and
> "modular design" that can result from this. I am also keen to leverage your
> tools for rapid development as well.
>
> I have posted here because I see value in identifying when a designer
> should choose one method over the other. My solution will help manipulating
> traditional tiddler fields, your solution keeps these (sand boxed) within
> json.
>
> *Question*
> What do you think are key questions and issues for designers when deciding
> if the JSON approach is better?
>
> Regards
> Tony
>
> On Tuesday, August 13, 2019 at 5:55:31 AM UTC+10, Joshua Fontany wrote:
>>
>> Hi everyone!
>>
>> I am really excited to announce that I have my proof of concept ready for
>> "modular" User Interfaces for TiddlyWiki!
>>
>> I'm also very excited to officially announce updated JsonMangler and
>> JsonEditor plugins for TW v5.1.20!
>>
>> There were some last minute tweaks, but I've gotten new example wikis up
>> and running. Any comments or bug reports are greatly appreciated!
>>
>> https://joshuafontany.github.io/TW5-JsonMangler/
>>
>> https://joshuafontany.github.io/TW5-jsoneditor/
>>
>> But, hey, wait Josh, that first thing you said. What does that mean?
>>
>> Screenshots are always nice. :D
>>
>> [image: JsonUI_conceptUI_viewTemplate_08.12.2019.png]
>>
>> [image: JsonUI_conceptUI_editTemplate_08.12.2019.png]
>>
>>
>> I'll try to keep the explanation high-level, but basically:
>>
>>
>>- A Jsoneditor Widget uses a 'schema definition' (a json tiddler) to
>>render one of two "data json tiddlers".
>>- The first data-tiddler holds wiki-text (not raw data!) for the View
>>Template. This wikitext points to fields on the current tiddler and 
>> renders
>>a custom UI elements for each.
>>- The second data-tiddler holds wiki-text for the Edit Template! It
>>points to fields on the current tiddler and renders custom UI elements for
>>each.
>>- Finally, we have two system tiddlers - one tagged
>>$:/tags/ViewTemplate and the other tagged $:/tags/EditTemplate.
>>- The only real difference between the two template tiddler's TEXT is
>>that one points a JsonEditor to the view-data, and the other points to the
>>edit-data.
>>
>>
>> In this way, we can "group, organize, and modularize" our UI elements.
>> This helps to greatly reduce cognative-load (how much stress it take you to
>> think through designs).
>>
>> Also, simply tag a new Tiddler in the wiki with the `Character` tag, and
>> all of that slick UI automatically appears and is completely responsive. ;D
>>
>> More information can be found in the "JsonUI" tiddler in my example wiki:
>> https://joshuafontany.github.io/TW5-jsoneditor/#JsonUI
>>
>> This is only a VERY rough proof-of-concept using a commonly known
>> fictional character (lots of reference data). I have ideas for more complex
>> (behind the scenes complex) versions later on. There are also a few
>> gremlins to work out (jsoneditor tabs re-set state on each wiki update -
>> wooops), and I'm going to be updating my fork of the base json-editor
>> library, would like to be able to set a custom Font-Awesome glyph for the
>> collapse button based on a tiddler's value, etc, etc.
>>
>> This was inspired by working with other languages that use "Model, View,
>> Vew-Model" architecture, and I think we can start to make some really cool
>> complex things by combining this with all of the other plugins that are out
>> there!!
>>
>> Let me know if you all have any questions!
>>
>> Best,
>> Joshua Fontany
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 

Re: [twdev] SyncAdaptor

[Arlen Beiler]

To understand sync adaptors, you should look through these two plugins,
which contain the two sync adaptors used in the official data folder based
server edition (using the listen command).

This one is loaded in the client and saves changes back to the server.
https://github.com/Jermolene/TiddlyWiki5/tree/master/plugins/tiddlywiki/tiddlyweb

This one is loaded on the server and saves changes to the filesystem.
https://github.com/Jermolene/TiddlyWiki5/tree/master/plugins/tiddlywiki/filesystem

In addition, here is the module that calls the sync adaptors to get
everything done.
https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/syncer.js

With a little bit of fiddling I managed to get the filesystem plugin
working in Electron so that it saved browser changes directly to the
filesystem without going through any kind of NodeJS server instance, but
that's a side note. For anyone else reading this who is curious, it
actually did save changes directly from the browser instance. I didn't load
the server listener or go through any kind of intermediary at all. It
required some modifications to boot.js though to correctly detect that a
datafolder was being loaded into the browser!

Hope that helps.

On Tue, Aug 20, 2019 at 2:51 PM Arlen Beiler  wrote:

> To load tiddlers on startup you can use the preloadTiddlers array.
>
> 1. Put this code in a head script: $tw = { boot: { suppressBoot: true },
> preloadTiddlers: [] };
> 2. Query the server for the user's tiddlers and handle the response
> asyncly when it is recieved (good for performance).
> 3. Wait for the window load event, which indicates that all code is
> initialized.
> 4. Push the JSON tiddlers (as field hashmaps) to the preloadTiddlers
> array.
> 5. Call $tw.boot.boot();
>
> Tiddlywiki doesn't know the difference between this and a single-file
> wiki. It works the same in the browser once you call $tw.boot.boot();
>
> On Tue, Aug 20, 2019 at 10:34 AM Jeremy Ruston 
> wrote:
>
>> Hi Xavier
>>
>> If I understand correctly. The save button call a saver (are the savers
>> chained in case of multiple setup, eg gitub, gitlab...? ) while the
>> syncadaptor is dynamic and reacts to events ? If its correct I like the
>> mechanism as it gives users a way to easily backup their wikis.
>>
>>
>> That's correct. The other thing to bear in mind is that the saver
>> mechanism can also be used to export any data as a file, it's not
>> restricted to saving the wiki itself.
>>
>> I'm not sure to understand here. I think this is why I'm lost. While
>> studying the syncadaptor I didn't get any understanding about how the
>> remote stored wiki has been initialized in the first place and this is why
>> I was thinking about my described mechanism. Load a self contained wiki.
>> Setup the ipfs target and then use the syncadaptor to push the contents to
>> IPFS.
>>
>>
>> In the case of the standard client server configution, the browser
>> connects to the default route triggering a build of the entire wiki file:
>>
>>
>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/server/routes/get-index.js
>>
>> Another alternative is to start with an empty index.html stored anywhere
>> accessible via HTTP and have it interrogate the server for tiddlers when it
>> starts up.
>>
>> I think this is where I'm going to start. Define a saver and save the
>> whole content. I was too ambitious to jump right away on a SyncAdaptor.
>> There is always a learning curve...
>>
>>
>> Indeed, the saver mechanism is conceptually much simpler. It's also
>> likely to perform better in many situations as one large HTTP transaction
>> is generally faster than lots of little ones.
>>
>> I was following my idea. All the syncadaptors I studied assume that the
>> content is already on a remote server and I didn't see how the content has
>> been built in the first place. You explained earlier the external build
>> process but I still don't understand how the first load is working. If I
>> follow your mind It means that let's say you offer your user to start from
>> a set of wiki templates. Those templates are already built by an external
>> process. I was thinking like described. Load a plain wiki, install the
>> plugin, setup the plugin then sync to IPFS. The property was meant to
>> detect whether or not this wiki is already synced. I was looking to some
>> index technics but I didn't figure out yet how to get and process the store
>> list.
>>
>>
>> The core client-server implementation uses etags to keep track of whether
>> a particular tiddler has changed.
>>
>> Not sure to understand what

Re: [twdev] SyncAdaptor

[Arlen Beiler]

To load tiddlers on startup you can use the preloadTiddlers array.

1. Put this code in a head script: $tw = { boot: { suppressBoot: true },
preloadTiddlers: [] };
2. Query the server for the user's tiddlers and handle the response asyncly
when it is recieved (good for performance).
3. Wait for the window load event, which indicates that all code is
initialized.
4. Push the JSON tiddlers (as field hashmaps) to the preloadTiddlers
array.
5. Call $tw.boot.boot();

Tiddlywiki doesn't know the difference between this and a single-file wiki.
It works the same in the browser once you call $tw.boot.boot();

On Tue, Aug 20, 2019 at 10:34 AM Jeremy Ruston 
wrote:

> Hi Xavier
>
> If I understand correctly. The save button call a saver (are the savers
> chained in case of multiple setup, eg gitub, gitlab...? ) while the
> syncadaptor is dynamic and reacts to events ? If its correct I like the
> mechanism as it gives users a way to easily backup their wikis.
>
>
> That's correct. The other thing to bear in mind is that the saver
> mechanism can also be used to export any data as a file, it's not
> restricted to saving the wiki itself.
>
> I'm not sure to understand here. I think this is why I'm lost. While
> studying the syncadaptor I didn't get any understanding about how the
> remote stored wiki has been initialized in the first place and this is why
> I was thinking about my described mechanism. Load a self contained wiki.
> Setup the ipfs target and then use the syncadaptor to push the contents to
> IPFS.
>
>
> In the case of the standard client server configution, the browser
> connects to the default route triggering a build of the entire wiki file:
>
>
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/server/routes/get-index.js
>
> Another alternative is to start with an empty index.html stored anywhere
> accessible via HTTP and have it interrogate the server for tiddlers when it
> starts up.
>
> I think this is where I'm going to start. Define a saver and save the
> whole content. I was too ambitious to jump right away on a SyncAdaptor.
> There is always a learning curve...
>
>
> Indeed, the saver mechanism is conceptually much simpler. It's also likely
> to perform better in many situations as one large HTTP transaction is
> generally faster than lots of little ones.
>
> I was following my idea. All the syncadaptors I studied assume that the
> content is already on a remote server and I didn't see how the content has
> been built in the first place. You explained earlier the external build
> process but I still don't understand how the first load is working. If I
> follow your mind It means that let's say you offer your user to start from
> a set of wiki templates. Those templates are already built by an external
> process. I was thinking like described. Load a plain wiki, install the
> plugin, setup the plugin then sync to IPFS. The property was meant to
> detect whether or not this wiki is already synced. I was looking to some
> index technics but I didn't figure out yet how to get and process the store
> list.
>
>
> The core client-server implementation uses etags to keep track of whether
> a particular tiddler has changed.
>
> Not sure to understand what you mean by updated. I'm targeting a single
> user model. The only updates should come from the user actions. (updated
> tiddlers, removed tiddlers,etc...)
>
>
> That will certainly simplify things.
>
> Many thanks for your great work.
>
> Warmly.
>
>
> Thank you for your interest, IPFS is really very cool and I'm delighted to
> see you experiment with it,
>
> Best wishes
>
> Jeremy
>
>
>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWikiDev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to tiddly...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywikidev/004560cd-7acf-4408-a3b2-63e049db291a%40googlegroups.com
>> 
>> .
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/b59dab66-8c82-4739-acd2-cc2a714f5e5f%40googlegroups.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> 

Re: [twdev] Re: Meaning of 5 , 1 , 19 ?

[Arlen Beiler]

I've always read it to be brand:major:minor, as the "5" signifies the
upgrade from "2", using many lessons learned, and is a play on the number
25, which was in the original slogan (TWenty 5 - A remake for the next 25
years). The middle number is major changes to the internal javascript code,
such as a major rewrite of boot.js, which might break certain things like
Bob and TiddlyServer (tools which depend on the internal workings of
TiddlyWiki), and the last number is the number that tells us which bugs we
might be dealing with and which macros and features are available. We don't
really do patch, but we also don't really do breaking minor changes. All
5.1.x wikitext will always work on 5.1.x, and might work on 5.2.x as well,
since breaking changes are rarely introduced into the parser.

That's how it's seemed to work from my observation.
Arlen

On Mon, Apr 22, 2019 at 9:14 PM MidnightLightning 
wrote:

> There's a conversation over at
> https://github.com/Jermolene/TiddlyWiki5/issues/3834 on the GitHub repo
> that asks a pretty similar question too.
>
>
> On Monday, April 22, 2019 at 4:20:38 AM UTC-5, Mat wrote:
>>
>> What does it take to jump "a tenth" in the version number, i.e to get TW
>> version 5.2? Seems like we over modestly increment with 1/1000 even when
>> pretty big improvements are made.
>>
>> More generally put, what do the value positions in 5.1.19 actually
>> signify in TW - there is no exact standard for versioning
>> ?
>> And actually, is "5" a version number or a part of the product name?
>>
>> <:-)
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/023ddcbf-6f5c-4f95-aa19-8b7f442d4feb%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

[Arlen Beiler]

Can someone please invent an attachments system that can serve files
directly from the node data folder! It isn't very hard :)

-Arlen

On Sat, Nov 24, 2018 at 7:58 AM Guillaume Escrivant 
wrote:

> Hello
> I'm a fan user of TW5 on Node.js
>
> I'm one windows with TW5 version 5.1.17
>
> I have a big wiki (230Mo) But the last tiddler i made, i go a node error
> : CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
> with a crash to my node server
>
> And i'm not able to acces my wiki any more.
>
> I've tryed
>
>
>- npm install -g increase-memory-limit
>- increase-memory-limit
>
> adding an option --max-old-space-size=8192 to lauch tiddlywikki
>
> with no success
>
> Does someone have an option ?
>
> Tks for help
>
> Guillaume
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/5a0cc15b-62b4-4587-b70b-336097714fc1%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] [TW5] Refresh Current Tiddler

[Arlen Beiler]

Um, that was well written :)

You should put that in a troubleshooting section.

On Sun, Sep 9, 2018, 22:56 Jeremy Ruston  wrote:

> Hi Tony
>
> If there’s part of the render tree that is not being refreshed as expected
> the likely cause is one of the following:
>
> * You’re using a JavaScript macro whose return value doesn’t exclusively
> depend on the parameters passed in (typically, because it is accessing the
> tiddler store). There are some such macros in the core that are required
> for special purposes (e.g. the jsontiddlers macro), but you’re unlikely to
> be using them.
> * You’re using a core widget that has a subtle refresh bug
> * You’re using a third party widget with faulty refresh logic
>
> The ideal solution in these situations is to try to reduce out a minimum
> test case to narrow down and fix the problem.
>
> Alternatively you could experiment with ways of forcing a refresh: for
> example, you can force a section of wikitext to be refreshed when a
> particular tiddler changes by wrapping the section in a set widget that
> depends on that tiddler:
>
> <$set name="dummyVariable" value={{dependent-tiddler}}>
> ...
> 
>
> Best wishes
>
> Jeremy.
>
>
> On 9 Sep 2018, at 05:47, TonyM  wrote:
>
> Folks,
>
> I have finally build a comprehensive personal wiki on TW5 to replace my
> old TWC solution.
>
> I have lists of tiddlers and I can complete or cancel  however the lists
> are not refreshing to remove the item no longer in the list because of
> their status change.
>
> Is there an action widget I can use that will trigger a refresh of the
> current tiddler?, so I can either;
>
>- Build my own button to trigger a refresh
>- Add to existing buttons including my own to cause a tiddler refresh
>
> Ideally I could make it refresh a specific list but the whole tiddler
> would be fine.
>
> I imagine there is possibly already an action I could use to do it like
> navigate to the current tiddler, but do we have a dedicated method?
>
> Thanks in advance
> Tony
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/ed8661a4-b97a-4556-86f2-c2f160c4770d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/66E5A221-FE58-42FC-A3A5-8E2BA8860D36%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Improving TiddlyWiki 5 web server functionality

[Arlen Beiler]

Yay, this is something I have been looking forward to, although I was
totally unaware you were actually doing it. The thought of setting up
routes as modules has always intrigued me, although I have focused my
energies elsewhere.

On Fri, Jun 22, 2018 at 5:36 PM Jeremy Ruston 
wrote:

> For the last couple of days I’ve been working on a major refactoring of
> the web server functionality of TiddlyWiki 5 — it’s the part that lets you
> access Node.js wikis from any browser. The work was motivated by
> consultancy work I’m engaged on, and builds on some initial work done by
> Devin Weaver back in 2016.
>
> https://github.com/Jermolene/TiddlyWiki5/pull/2679
>
> The improvements that are implemented so far include:
>
> * Refactoring routes as separate modules, making it easier to extend the
> server with new functionality
> * A new module for serving static file attachments over HTTP
> * Adding support for authentication via a trusted header, making it easier
> to integrate with corporate single sign on (and Windows authentication)
> * A new option for outputting additional debugging information
> * Deprecating the existing “—server” command in favour of a new “—listen”
> command that uses a newly implemented command line feature for named
> parameters that can be specified in any order:
>
> --listen host:1270.0.0.1 port:8080 pathPrefix:/Total
>
> Improvements I’m currently working on:
>
> * Adding support for multiple user credentials for basic authentication
> via a CSV file containing usernames/passwords
> * Adding support for more fine grained authorisation (ie granting/denying
> individual users read/write permission to resources)
>
> There’s quite a lot of significant new functionality, so I wanted to bring
> it up here because this is a good time for questions and suggestions.
>
> (Just to clear, at this point I’m not planning to make any changes to the
> tiddlywebadaptor client that runs in the browser talking to the server;
> this round of work is just about enhancing the server).
>
> Best wishes
>
> Jeremy.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/953D329D-CFAC-455A-9DC1-336CB610BC45%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: Multiuser TW implementation idea

[Arlen Beiler]

The short answer is "Wow, simple! And, I think, doable."

I would suggest to have an owner field instead of using creator. Also, the
fields would not be served to the client unless the user has permission to
set them. So if you don't own it you can't set the edit field.

But I think the current code would allow it, quite practically, once we fix
a few bugs and add a couple features.

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

Re: [twdev] Re: Websocket plugin

[Arlen Beiler]

After reading your email, here is a bit of a proposal on a mechanism to
use.

Implement the WebSocket server in the server command (and in TiddlyServer,
trying to use the TiddlyWiki code as much as possible) and then have a
module-type of "websocket-server" and "websocket-client". The server
command (and TiddlyServer) would load "websocket-server" modules once
everything is started, and the browser would load "websocket-client"
modules during startup. The actual WebSocket client module should be loaded
similar to how the sync adapter is loaded.

The other option is to have a $tw.wsServer and $tw.wsClient object which
modules would hook onto. Only the one in use would be defined. The module
would still be loaded like the sync adapter to allow plugins to implement
their own client. I guess this would accomplish the same thing as using the
hooks object.

I'm not sure which of these options should be used. I think they each have
their own merits. Obviously, this is the low-level API, the higher level
stuff would be implemented in separate modules.

Pull Request 3024 (https://github.com/Jermolene/TiddlyWiki5/pull/3024)
should be implemented as part of this to allow a more modular architecture
(and, I believe, a correct use of the hooks mechanism). We can then hook in
the WebSocket server using a startup module instead of modifying the server
command directly. This is not required, but it seems to make sense.

I'm leaning toward adding wsServer and wsClient to the $tw variable and
then loading the correct interface in a method similar to the sync adaptor
mechanism. All other functions would hook onto these two objects depending
on whether they were intended for server or client.

What are your thoughts, in particular, Jeremy, but also everyone?

Arlen

On Mon, Dec 4, 2017 at 5:56 AM, Jeremy Ruston <jeremy.rus...@gmail.com>
wrote:

> Hi Arlen
>
> Just a quick comment about the use of the hooking mechanism; I'm afraid I
> haven't had a chance to look at the code yet.
>
> The hook mechanism is, in effect, a reusable, generic event emitter that
> components can use to emit events instead of creating their own event
> emitter (or equivalent mechanism). It is designed for use with low level
> operations that might need overriding or extending.
>
> I think a component that emits events as a primary part of its interface
> should do so through their own interface, rather than overloading the hooks
> mechanism.
>
> As I say, I haven't had a chance to look at the code but i'm certainly
> interested in incorporating support for websockets. I think for flexibility
> the implementation needs to be layered so that the functionality can be
> used in several different contexts:
>
> * An extension to the current HTTP API to allow immediate broadcast of
> updates from the server to all connected browsers. This will give most
> users the benefits of the real time updates without needing to do anything
> special: they'll just get instant sync
> * High level widget messages (as you describe) to give users a general
> purpose way to use the messaging for non-tiddler syncing tasks
> * A low level JS interface for components that want to ride close to the
> bare metal
>
> Best wishes
>
> Jeremy
>
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 3 Dec 2017, at 06:02, Arlen Beiler <arlen...@gmail.com> wrote:
>
> Hmm, no comments?
>
> Curious whether this seems to be a good design or whether we should look
> at using something else. In a way it could be hackish if this isn't the
> intent of hooks, but it also makes sense to use a mechanism like this.
>
> I guess we could also have a websockets module like we have with the sync
> adapter and then have some mechanism to handle the incoming messages and a
> $tw property to hook onto.
>
> On Dec 1, 2017 13:02, "Arlen Beiler" <arlen...@gmail.com> wrote:
>
>> Hello Everyone,
>>
>> Based on Jed Carty's work, I made a simple WebSocket server and client
>> that uses hooks for message handling. I am hoping this will allow a
>> standardized way of implementing messaging so that TiddlyServer and other
>> similar systems can implement their own method of sending WebSocket
>> messages to Node instances.
>>
>> https://github.com/Arlen22/TW5-WebSocketServer
>> https://github.com/Arlen22/TW5-WebSocketClient
>>
>>- The server uses two hooks: th-websocket-message and
>>th-websocket-broadcast
>>- The client uses two hooks: th-websocket-message and
>>th-websocket-send
>>
>> This allows any other program to use the default $tw.hooks to send and
>> handle websocket messages. It also allows us to swap out the server and
>> client plug

[twdev] Re: Websocket plugin

[Arlen Beiler]

Hmm, no comments?

Curious whether this seems to be a good design or whether we should look at
using something else. In a way it could be hackish if this isn't the intent
of hooks, but it also makes sense to use a mechanism like this.

I guess we could also have a websockets module like we have with the sync
adapter and then have some mechanism to handle the incoming messages and a
$tw property to hook onto.

On Dec 1, 2017 13:02, "Arlen Beiler" <arlen...@gmail.com> wrote:

> Hello Everyone,
>
> Based on Jed Carty's work, I made a simple WebSocket server and client
> that uses hooks for message handling. I am hoping this will allow a
> standardized way of implementing messaging so that TiddlyServer and other
> similar systems can implement their own method of sending WebSocket
> messages to Node instances.
>
> https://github.com/Arlen22/TW5-WebSocketServer
> https://github.com/Arlen22/TW5-WebSocketClient
>
>- The server uses two hooks: th-websocket-message and
>th-websocket-broadcast
>- The client uses two hooks: th-websocket-message and th-websocket-send
>
> This allows any other program to use the default $tw.hooks to send and
> handle websocket messages. It also allows us to swap out the server and
> client plugins to handle the server connection differently. This completely
> separates the websocket connection specifics from the programs that use it.
>
> I like the looks of this system. Let me know what you think.
>
> Thanks, Arlen
>

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

[twdev] Websocket plugin

[Arlen Beiler]

Hello Everyone,

Based on Jed Carty's work, I made a simple WebSocket server and client that
uses hooks for message handling. I am hoping this will allow a standardized
way of implementing messaging so that TiddlyServer and other similar
systems can implement their own method of sending WebSocket messages to
Node instances.

https://github.com/Arlen22/TW5-WebSocketServer
https://github.com/Arlen22/TW5-WebSocketClient

   - The server uses two hooks: th-websocket-message and
   th-websocket-broadcast
   - The client uses two hooks: th-websocket-message and th-websocket-send

This allows any other program to use the default $tw.hooks to send and
handle websocket messages. It also allows us to swap out the server and
client plugins to handle the server connection differently. This completely
separates the websocket connection specifics from the programs that use it.

I like the looks of this system. Let me know what you think.

Thanks, Arlen

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

[twdev] Can core support multiple wikis

[Arlen Beiler]

Hi, Jeremy and core devs,

I have noticed that different parts of the wiki have wiki passed in as an
option, and I'm wondering whether it would be possible to load multiple
wikis and multiple data folders onto one $tw variable. I know it is not
currently possible, but is it close or is it a long way from close? It
seems close, but I don't know for sure.

It would save memory for TiddlyWiki instances in TiddlyServer, it would
drastically improve load times, and would also allow tighter integration
between wikis. If we would do this, given the current configuration, it
would require sharing plugins, correct? Or is everything that involves
plugins centered around Wiki? In other words, is Wiki currently the
instance of the data folder or is $tw?

This would also bring us a step closer to providing a robust multi-user and
multi-wiki solution within TiddlyWiki or as a tightly coupled plugin.

Thanks,
Arlen

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

Re: [twdev] Re: Core design ideas: Inter Wiki links, sub pages, pinned fields

[Arlen Beiler]

Interesting, I never knew about this. But I am actually talking about a
Table of Contents to be used inside the wiki exactly like the TOC macro,
except based on the "path separator" (forward slash) in the tiddler title
instead of the tag hierarchy. So it would actually render the table of
contents the way the TOC macro does. I'm curious if this can be done with a
filter or if someone would need to write a javascript macro for it.

On Tue, Oct 17, 2017 at 12:50 PM, PMario  wrote
>
> IMO http://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming should
> do this?
>
>

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

Re: [twdev] Re: Core design ideas: Inter Wiki links, sub pages, pinned fields

[Arlen Beiler]

I should have made it clearer that these are three unrelated ideas


> I have been thinking about this for a while now. It seems like we should
> have some way of being able to transclude tiddlers from other wikis. And we
> should have a syntax that makes this easy. This one might be better done as
> a plugin.


I'm thinking that the NodeJS server command would be useful as the
server-side component for this one. I know federation has also done this,
but it involves loading the client wiki into an iframe. I guess that could
work fine in some cases, but it is definitely more data to transfer. The
TiddlyWeb spec looks daunting to implement in some ways. You're right,
TiddlyWeb is probably the way to go on this one. I was thinking more in
terms of transcluding individual tiddlers, so recipes and filters might be
overkill.

Another thing I have been thinking is that we need a simple way to group
> pages [should be tiddlers] according to "folders". Maybe all this entails
> is a macro like TOC that lists all the folders under a prefix. It seems
> like a filter of some sort should work.
>

For this one, I am talking about tiddlers within one wiki. I'm thinking of
the way the Mediawiki software gives you the option to treat slashes in the
page title like a folder path. When you enable this option, as Wikipedia
does, it will treat page titles with slashes as a subpage. So in our case,
we would write a macro that looks like the TOC macro, but groups the
tiddlers using the title field instead of tags. For instance, the shadow
tiddlers of the core plugin would look like this:

$:/core

   - modules
   - macros
  - parsers
  - startup
  - utils
  - widgets
  - templates
   - ui
   - Buttons
  - ControlPanel
  - EditorToolbar


Another thing that would be nice is the ability to add preset fields to the
> edit template between the title and the body. That way I could specify that
> I always want the caption field available, for instance, even if nothing
> has been specified for that field yet.


I mean, we could just give this the same functionality as the field editor
below the body, where it would have the field name preset, but you would
still need to click create before it would actually save the value. Or
require the user to click create before it will show the value edit box.
Would that work? This is something I run into quite a bit with some of my
wikis, and I usually figure I'm not the only one.

Thoughts?
Arlen

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

[twdev] Core design ideas: Inter Wiki links, sub pages, pinned fields

[Arlen Beiler]

I have been thinking about this for a while now. It seems like we should
have some way of being able to transclude tiddlers from other wikis. And we
should have a syntax that makes this easy. This one might be better done as
a plugin.

Another thing I have been thinking is that we need a simple way to group
pages according to folders. Maybe all this entails is a macro like TOC that
lists all the folders under a prefix. It seems like a filter of some sort
should work.

Another thing that would be nice is the ability to add preset fields to the
edit template between the title and the body. That way I could specify that
I always want the caption field available, for instance, even if nothing
has been specified for that field yet.

Thoughts?
Arlen

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

[twdev] Code editor

[Arlen Beiler]

Good morning everyone,
I have been using visual studio code for quite a lot of things recently but
it does have a few drawbacks so I thought I would see what everyone else is
using especially since the tiddlywiki code bases quite massive and yet
there do not seem to be any interfaces or anything like that such as Visual
Studio code seems to enjoy. Actually, vs code is more built for working
with TypeScript than JavaScript.

So what do you all use?

- Arlen

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

Re: [twdev] Re: Proposal for improving TW Documentation - Structure (part 1)

[Arlen Beiler]

Toward that end, I updated the page with the list you posted in your
original email. Here it is.

https://en.wikibooks.org/wiki/TiddlyWiki_for_Users

I have a feeling the reference might end up in a separate book.

We could call it the *TiddlyWiki Desk Reference*.

Someday, there will hopefully be an artfully and tastefully written *TiddlyWiki
for Dummies.*

On Thu, Jun 29, 2017 at 10:27 PM, Arlen Beiler <arlen...@gmail.com> wrote:

> We could use Wikibooks as well if we wanted to. Plus they already are used
> to doing things in the book sort of way. I started a couple books there a
> few months ago, but I am not a writer. However I believe Wikibooks would
> work perfect if we want to use MediaWiki. We can also have our own project
> area to discuss things related to documentation.
>
> On Thu, Jun 29, 2017 at 9:19 PM, TonyM <anthony.mus...@gmail.com> wrote:
>
>> This requires deeper thought, perhaps with different "tracks" Newby,
>> User, Dev - but here is a quick one
>>
>>
>>- Overview should describe the feature and what id does in both
>>simlple and advanced uses
>>- Context - the various contexts in which this feature fits and can
>>be used eg actionWidgets
>>- Syntax simple and full
>>- Examples - various meeting most needs "out of the box", ideally
>>complete not context dependent snipits
>>- Advanced usage - extended uses such as in macros/plugins, detailed
>>info
>>- Community notes -User and Developer sections with a series of posts
>>on this command inc snipits, on review may incorporate into other
>>documentation tabs
>>
>>
>> On Friday, June 30, 2017 at 11:05:55 AM UTC+10, TonyM wrote:
>>>
>>> I can provide a free MediaWiki instance if you want, in a day or so, but
>>> my preference was someone to build such a thing in tiddlyWiki itself.
>>>
>>> Just ask if you want the mediaWiki instance and provide a user name and
>>> email address (to AM [at] PSaT.com.au) if you want me to grant full
>>> update rights, otherwise I will allow moderated new user account requests.
>>>
>>> To clarify, the same documentation repository can serve multiple users
>>> by providing alternate entry points,  a different index or lists into the
>>> content. I Would also see value in the Multi-tab tiddler Idea where each
>>> tab references an external tiddler, I will provide a mock up soon.
>>>
>>> Regards
>>> Tony
>>>
>>>
>>>
>>> On Thursday, June 29, 2017 at 9:09:25 PM UTC+10, moros...@gmail.com
>>> wrote:
>>>>
>>>> @TonyM I don't know if I clearly understood what you said but maybe we
>>>> have a similar perspective. I imagine a documentation system that's dynamic
>>>> not static, with multiple views, capable to morph based on some user
>>>> selected criteria. That means, the ability to find knowledge in multiple
>>>> ways: parsing a standard progressive structure, selecting knowledge by tags
>>>> or sort it by difficulty level, dependencies/requirements, intended results
>>>> etc.but I guess this is a long term objective. So maybe it's wiser to start
>>>> with just the basic (and feasible) improvements. In the beginning, my
>>>> expectations are that a clearer and meaningful (logical) doc structure will
>>>> more appealing for users that wish to contribute. Every doc page at it's
>>>> right place so everybody will have a clear picture of what already exists
>>>> and what's needed. But enough talking :), we should do something, to have a
>>>> baseline and continue from that. I will try to go on TonyM path and looking
>>>> for a free wiki hosting service and put my initial proposal there.
>>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWikiDev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to tiddlywikidev+unsubscr...@googlegroups.com.
>> To post to this group, send email to tiddlywikidev@googlegroups.com.
>> Visit this group at https://groups.google.com/group/tiddlywikidev.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/tiddlywikidev/62719adf-24fa-4023-b9b0-4ff9461f112e%40googlegroups.com
>> <https://groups.google.com/d/msgid/tiddlywikidev/62719adf-24fa-4023-b9b0-4ff9461f112e%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [twdev] Re: Proposal for improving TW Documentation - Structure (part 1)

[Arlen Beiler]

We could use Wikibooks as well if we wanted to. Plus they already are used
to doing things in the book sort of way. I started a couple books there a
few months ago, but I am not a writer. However I believe Wikibooks would
work perfect if we want to use MediaWiki. We can also have our own project
area to discuss things related to documentation.

On Thu, Jun 29, 2017 at 9:19 PM, TonyM  wrote:

> This requires deeper thought, perhaps with different "tracks" Newby, User,
> Dev - but here is a quick one
>
>
>- Overview should describe the feature and what id does in both
>simlple and advanced uses
>- Context - the various contexts in which this feature fits and can be
>used eg actionWidgets
>- Syntax simple and full
>- Examples - various meeting most needs "out of the box", ideally
>complete not context dependent snipits
>- Advanced usage - extended uses such as in macros/plugins, detailed
>info
>- Community notes -User and Developer sections with a series of posts
>on this command inc snipits, on review may incorporate into other
>documentation tabs
>
>
> On Friday, June 30, 2017 at 11:05:55 AM UTC+10, TonyM wrote:
>>
>> I can provide a free MediaWiki instance if you want, in a day or so, but
>> my preference was someone to build such a thing in tiddlyWiki itself.
>>
>> Just ask if you want the mediaWiki instance and provide a user name and
>> email address (to AM [at] PSaT.com.au) if you want me to grant full
>> update rights, otherwise I will allow moderated new user account requests.
>>
>> To clarify, the same documentation repository can serve multiple users by
>> providing alternate entry points,  a different index or lists into the
>> content. I Would also see value in the Multi-tab tiddler Idea where each
>> tab references an external tiddler, I will provide a mock up soon.
>>
>> Regards
>> Tony
>>
>>
>>
>> On Thursday, June 29, 2017 at 9:09:25 PM UTC+10, moros...@gmail.com
>> wrote:
>>>
>>> @TonyM I don't know if I clearly understood what you said but maybe we
>>> have a similar perspective. I imagine a documentation system that's dynamic
>>> not static, with multiple views, capable to morph based on some user
>>> selected criteria. That means, the ability to find knowledge in multiple
>>> ways: parsing a standard progressive structure, selecting knowledge by tags
>>> or sort it by difficulty level, dependencies/requirements, intended results
>>> etc.but I guess this is a long term objective. So maybe it's wiser to start
>>> with just the basic (and feasible) improvements. In the beginning, my
>>> expectations are that a clearer and meaningful (logical) doc structure will
>>> more appealing for users that wish to contribute. Every doc page at it's
>>> right place so everybody will have a clear picture of what already exists
>>> and what's needed. But enough talking :), we should do something, to have a
>>> baseline and continue from that. I will try to go on TonyM path and looking
>>> for a free wiki hosting service and put my initial proposal there.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/62719adf-24fa-4023-b9b0-4ff9461f112e%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: Proposing \* as pragma rule for comments?

[Arlen Beiler]

I heartily agree, although, I would like to see the double forward slash
used for single line comments and forward slash and star used as multi-line
comments. Is there a reason why we cannot use forward slash? Maybe the
double forward slash is already taken for italics.

On Wed, Jun 28, 2017 at 8:37 PM, @TiddlyTweeter 
wrote:

> Mat
>
> Commenting on your comments on comments.
>
> Comments are good.
>
> One important role for them is to declare authorship.
>
> If life were fair Mark S. would have a very high ranking on first
> copyright comment lines. At the moment he gets none.
>
> Best wishes
> Josiah
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/tiddlywikidev/a8a487b5-ee7a-4a32-8405-fed9615c9ad1%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

[twdev] TiddlyServer 2.0

[Arlen Beiler]

Good Evening All,

I'm sorry if all of you are already on the regular TiddlyWiki group and so
are seeing this twice, but I thought I would post it here as well, since
this is in its early stages and deals directly with NodeJS.

This weekend I wrapped up a project that has been brewing in my mind for
years. It allows you to serve and save any single file TiddlyWiki (it uses
the put saver). And it also allows you to serve any data folder that can be
loaded into TiddlyWiki 5.1.14+.

The documentation is in the link below, but if it finds a tiddlywiki.info

 file inside a folder, that folder becomes a data folder (aka TiddlyWiki
Folder) and will get loaded into its own instance of TiddlyWiki and serve
requests to that path. The tiddlywiki.info

 file needs to specify the correct server plugins, as usual, otherwise the
wiki will be readonly (actually sounds useful!).

So without further ado, TiddlyServer 2.0!!!

https://github.com/Arlen22/TiddlyServer


Any questions or comments, feel free to reply here or on Github

Special thanks to Matt Lauber for allowing me to use the name TiddlyServer.
He has announced that this version is replacing his as the latest version.

Enjoy!

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

Re: [twdev] @dev - Why dev for Chrome is a MUST

[Arlen Beiler]

It can be a bit disconcerting at times, that's for sure. But I have to say
that I think NodeJS is probably​ going to give us a good platform to
replace what we've been using up to now.

On Jun 1, 2017 05:56, "Jeremy Ruston" <jeremy.rus...@gmail.com> wrote:

Hi Arlen

Thanks for the clarification.

It’s a shame that Google have killed Chrome Applications; they had some
neat capabilities. But it’s also a reminder that Google’s habit of
discontinuing technologies and platforms is pretty dispiriting from a
developers perspective…

Best wishes

Jeremy

On 31 May 2017, at 14:21, Arlen Beiler <arlen...@gmail.com> wrote:

Good overview Jeremy.

Just thought I'd mention that TiddlyChrome is a Chrome App, rather than an
extension, and as such is given the privilege of editting such files as the
user specifically chooses using an open file dialog.

Because apps are going to be removed from Chrome within a year or so, I
have not developed it to it's full potential and instead have been focusing
on writing a TiddlyServer implementation which will work around a lot of
the drawbacks of the stock Tiddlywiki server, such as external file support
and serving multiple data folders.

On May 30, 2017 13:55, "@TiddlyTweeter" <tiddlytwee...@assays.tv> wrote:

> Some of your thoughts should get pinned.
>
> My issue with this is not on saving per se, its on what is a TW
> "standalone".
>
> Daniello's NoteSelf seems to instance a very interesting mid-place of easy
> saving and conventional TW authorial autonomy that makes this more rich,
> and interestingly, complex.
>
> Josiah
>
>
>> Jeremy Ruston wrote ...
>>
>> I do not think that making the single file edition easier to use is the
>> best way to get TiddlyWiki more widely used. Working with the single file
>> edition is inherently conceptually alien and risky for anyone raised on
>> conventional, contemporary web services; the barriers are not just about
>> the number of clicks. I believe that the way to get TiddlyWiki more widely
>> used is through online implementations that avoid the user having to worry
>> about saving.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/tiddlywikidev/14297989-c4fa-47cb-8d96-59883e9a9768%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywikidev/14297989-c4fa-47cb-8d96-59883e9a9768%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywikidev/CAJ1vdSQpkzAeuL4MwQbbG%2B9M2BxEbK_tnNQOEj0e%
3DQ4YWMLONQ%40mail.gmail.com
<https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSQpkzAeuL4MwQbbG%2B9M2BxEbK_tnNQOEj0e%3DQ4YWMLONQ%40mail.gmail.com?utm_medium=email_source=footer>
.

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


-- 
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywikidev/427B52E3-3F9B-4876-A414-DB2FEA517417%40gmail.com
<https://groups.google.com/d/msgid/tiddlywikidev/427B52E3-3F9B-4876-A414-DB2FEA517417%40gmail.com?utm_medium=email_source=footer>
.

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

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

Re: [twdev] @dev - Why dev for Chrome is a MUST

[Arlen Beiler]

Good overview Jeremy.

Just thought I'd mention that TiddlyChrome is a Chrome App, rather than an
extension, and as such is given the privilege of editting such files as the
user specifically chooses using an open file dialog.

Because apps are going to be removed from Chrome within a year or so, I
have not developed it to it's full potential and instead have been focusing
on writing a TiddlyServer implementation which will work around a lot of
the drawbacks of the stock Tiddlywiki server, such as external file support
and serving multiple data folders.

On May 30, 2017 13:55, "@TiddlyTweeter"  wrote:

> Some of your thoughts should get pinned.
>
> My issue with this is not on saving per se, its on what is a TW
> "standalone".
>
> Daniello's NoteSelf seems to instance a very interesting mid-place of easy
> saving and conventional TW authorial autonomy that makes this more rich,
> and interestingly, complex.
>
> Josiah
>
>
>> Jeremy Ruston wrote ...
>>
>> I do not think that making the single file edition easier to use is the
>> best way to get TiddlyWiki more widely used. Working with the single file
>> edition is inherently conceptually alien and risky for anyone raised on
>> conventional, contemporary web services; the barriers are not just about
>> the number of clicks. I believe that the way to get TiddlyWiki more widely
>> used is through online implementations that avoid the user having to worry
>> about saving.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/14297989-c4fa-47cb-8d96-59883e9a9768%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: Multi-user TiddlyWiki

[Arlen Beiler]

Thanks for the discussion :)

I am glad to hear other people debate the pros and cons of my ideas :)

I think the most obvious thing to me right now is that I am thinking too
far ahead. Here is my thought process:

My goal is to make TiddlyWiki allow more than one person to edit a wiki at
> the same time.
> Last time more than one person edited a wiki, the list of page titles grew
> to 70 MB (that's the size of all the title strings put together on English
> Wikipedia ).

Therefore I need to make sure that my implementation can handle 70MB of
> titles, plus the resulting skinny tiddlers.


So that's approximately what led to all that. Obviously that is not
preventing us from implementing multi-user, so this discussion has been
profitable :)



On Tue, Apr 4, 2017 at 1:02 PM, Douglas Counts 
wrote:

> but TWs containing many Mb of content (both text and embedded images) is
>> possible
>>
>
> That was my point, in that his Google Docs paper discusses building
> something large like wikipedia using GigaBytes to TerraBytes of data.
> Search and many other features would either fail or be painfully slow.  My
> understanding of search, as implemented, linearly searches through
> everything and doesn't use saved index trees. If one had millions of
> records, they could probably take a long coffee break before the search was
> completed.
>
> I just don't see how TiddlyWiki can scale that high without changing major
> operational components like search regardless of whether the search is
> performed within the browser or the server.
>
> -Doug
>
>
>
> On Tuesday, April 4, 2017 at 7:25:59 AM UTC-5, Eric Shulman wrote:
>>
>> On Tuesday, April 4, 2017 at 4:32:58 AM UTC-7, Douglas Counts wrote:
>>>
>>> TiddlyWiki, the app inside the browser, is designed to stand on its own
>>> because all the content is already contained within it.  A user can save
>>> the file locally and still run it even offline.  So your discussions there
>>> about using a database and building in dependencies upon a website don't
>>> really fit the purpose/mindset behind TW.  You are right in your discussion
>>> there that no one would want to load all of wikipedia into their computer's
>>> memory space all at once, but that isn't the mindset behind TiddlyWiki.
>>>
>>
>> TiddlyWiki5 natively supports use as EITHER an SPA (Single-Page
>> Application) -- where all tiddler content is loaded at startup, and all
>> changes are local to the browser until the file is saved -- OR as a
>> client-server setup using nodejs -- where tiddlers are stored in separate
>> files that can be updated as soon as they are edited (autosave).
>>
>> Running under NodeJS, TiddlyWiki5 supports HTTP request protocols that
>> allows you to "serve" your TiddlyWiki in your browser using either a local
>> IP loopback and portID (e.g., http://128.0.0.1:8080) or a true remote
>> host IP and port.  The nodeJS client-server architecture also supports use
>> of "skinny" tiddlers that initially send only the basic tiddler definitions
>> without the actual content (i.e., just the title, created/modified dates,
>> author, etc.), and fetches the tiddler content on demand when actually
>> referenced.  In theory, this permits you to create a TiddlyWiki of
>> virtually any size.  In practice, some issues can arise when working with
>> particularly large data sets.  The upper limit depends greatly on the
>> specific implementation details of your use-case and your system
>> performance/resources but TWs containing many Mb of content (both text and
>> embedded images) is possible.
>>
>> You can, of course, still save a local stand-alone HTML file from the
>> TiddlyWiki loaded in the browser, and you can also export your TiddlyWiki
>> to individual "static HTML" files that can be be published and served
>> (read-only) from a standard web server, without needing NodeJS.
>>
>> enjoy,
>> -e
>> Eric Shulman
>> TiddlyTools: "Small Tools for Big Ideas" (tm)
>> InsideTiddlyWiki: The Missing Manuals
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/18b19e8b-0ba5-45d7-905a-a5788f51d537%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: Multi-user TiddlyWiki

[Arlen Beiler]

*I think it's best to keep it as simple as possible while allowing
collaboration - you don't need it turning into SharePoint!*

True that, but I would love to see it become a platform a little like
Wikipedia. However, the mechanisms involved are a bit different, so this
could take an interesting twist.

On Feb 24, 2017 8:25 AM, "David Szego" <david.sz...@gmail.com> wrote:

> I think Jeremy has some revision-handling code hiding in the Core (no?).
>
> Certainly revisions could be handled as Tiddlers, even with the same name,
> where the Core would just pull the latest by "modified" field, or give you
> an Older/Newer button a lá Apple's Time Machine by pulling the
> appropriately modified Tiddler and putting some indicator icon next to the
> title.
>
> Notifications could be either AJAX (doable, see my AJAX plugin in Cardo),
> or simply let each other overwrite and save the millisecond-stamped
> revisions - if you use the above scheme where you keep the name the same
> but just sort by modification, you leave it between the users to figure it
> out without deleting anything. They can agree on which mod is best and mark
> it as "latest".
>
> I think it's best to keep it as simple as possible while allowing
> collaboration - you don't need it turning into SharePoint!
>
>
> On Friday, 24 February 2017 07:09:45 UTC-5, Arlen Beiler wrote:
>>
>> That's a start. How would you handle edit conflicts where two users can
>> both edit the same tiddler? How about notifying other users that an edit
>> was made? Where do you store the tiddlers? What mechanism do you use and
>> what about server side rendering? How about revision history? Those are the
>> main questions I am wondering right now, and maybe at some point I will
>> answer them. Because that is really all that needs to be done. The answers
>> just need to be decided, really.
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/d2157331-ef66-4e53-a950-cbdb340486cf%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywikidev/d2157331-ef66-4e53-a950-cbdb340486cf%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: Multi-user TiddlyWiki

[Arlen Beiler]

That's a start. How would you handle edit conflicts where two users can
both edit the same tiddler? How about notifying other users that an edit
was made? Where do you store the tiddlers? What mechanism do you use and
what about server side rendering? How about revision history? Those are the
main questions I am wondering right now, and maybe at some point I will
answer them. Because that is really all that needs to be done. The answers
just need to be decided, really.

On Feb 23, 2017 11:24 PM, "David Szego"  wrote:

> I'm talking completely in ignorance, but I've always figured entire sets
> of Tiddlers could be given a field called "ro-users" and a field called
> "rw-users" and the Core could just be modified to allow an HTTP Auth login.
>
> At that point, the user could only see and edit what they create, or what
> Tiddlers other creators add their names to.
>
> It doesn't need to be super secure, if the point is just to work
> collaboratively while ensuring you're not trampling on each other's work.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/35064741-1811-4449-9910-91c26fe942e3%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] How include a CDN link?

[Arlen Beiler]

Use the tag $:/tags/RawMarkup

On Feb 6, 2017 17:58, "Mat"  wrote:

> How/where can I include a link like
>
>
> **
> In other words, how do I via TW access the html head because that's where
> it has to be, right?
>
> This option to include e.g css frameworks seems totally unexplored in TW.
>
> <:-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/951d697e-c43a-40c9-b7fb-1cd23a3b56f4%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] TWC: Electron - Your thoughts, please

[Arlen Beiler]

If you use my code be sure to test it to verify that exports don't
overwrite the original tiddlywiki.

On Jan 24, 2017 10:41, "Jeremy Ruston"  wrote:

> Hi Sankar
>
> I searched the group for "electron", and found only a reference to it by
> Matabele Bill.  So I assume there would be people here who are more
> familiar with electron than I (for the record, I am not even a JavaScript
> or HTML person).
>
> Has anyone thought about running TWC on top of electron
> ?  (I am solely
> interested in running TWC and only on desktops.)
>
>
> TiddlyDesktop works with TWC. It is a thin shell around nw.js, which was
> the precursor to Electron. (As in, one of the nw.js developers left the
> project to start Electron).
>
> Best wishes
>
> Jeremy
>
>
> What does it take to run TWC using electron?  If you have some thoughts on
> the feasibility of this and how this can done, I would appreciate it.
>
> Thanks for your time.
>
> Cheers; 'best,
> shankar
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/c2123323-e824-473e-bb00-7624e6480a80%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/B9DBFD8D-E076-4C2F-B196-3675BE2A7C76%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: Multi-user TiddlyWiki

[Arlen Beiler]

Hi Dmitry,
I have been thinking about this and I think TiddlySpot and MediaWiki should
give us some ideas of where to start. Also there is Tank, but that seems to
be basically dead. It may be used by some people though. The Tiddlyweb
protocol comes very close to what I am thinking of, but it will still take
some work.

https://tank.peermore.com

On Dec 18, 2016 20:57, "Dmitry Sokolov" <dmitry.v.soko...@gmail.com> wrote:

> Dear All,
> thank you for the very interesting topic.
>
>
> From my experience, better if all the information is collected on a
> "single page" where it can be found easy for co-editing and reuse.
>
> I am currently working on PBWorks but looking forward to switching to a
> hybrid P2P platform, yet to be developed, to my understanding.
>
> Here is where all the information on this topic is being collected:
>
> http://confocal-manawatu.pbworks.com/w/page/113792539/
> MultiUser%20TiddlyWiki#view=edit
>
>
> I would like to start working on it's implementation and would appreciate
> your suggestions:
>
>- where to start from
>- how to contibute
>- what to focus on
>
> Should TWederation be the solution?
>
>
> Cheers,
>
> Dmitry
>
> On Saturday, 17 December 2016 11:07:02 UTC+13, Arlen Beiler wrote:
>>
>> Hello Everyone,
>> After making the comment on the documentation, I started wondering
>> exactly what it would require to re-invent the MediaWiki juggernaut as
>> TiddlyWiki. Here is what I came up with. Part of this comes from my
>> experience on Wikipedia, and part from setting up my own MediaWiki
>> installations on my computer. Not that I have a lot of experience, but for
>> what it's worth.
>>
>> https://docs.google.com/document/d/1Y8qV6I9BI1vgvve5kfThLKUO
>> Pu0aeF-FiCNpWvP62Hs/edit?usp=sharing
>>
>> Feel free to add comments on the document itself or here.
>>
>> Enjoy!
>> -Arlen
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/0b4e7234-830a-4477-9654-4d0a4db1695d%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywikidev/0b4e7234-830a-4477-9654-4d0a4db1695d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] Re: [TW5/TWC] Interesting new "Beaker Browser" with peer-to-peer hosting

[Arlen Beiler]

Jeremy,
I suppose Beaker has your spell checker that everyone wanted in
TiddlyDesktop :)

Also, if you do implement a tiddler-based format, would it use the standard
data folder format? Or if you need a new format to get authoritative file
names, could it possibly be ported back to NodeJS?

I have often thought about doing something like this with the TiddlyWiki
Dropbox saver, where it would sync individual files.

Another question, are these site files easily accessible on the file
system? Or is this another "Local store"? :)

Also, can you run regular chrome at the same time as this? I guess that
might be more of a dev question.

Sounds quite interesting.

Cheers,
-Arlen

On Dec 26, 2016 06:17, "PMario"  wrote:

> On Sunday, December 25, 2016 at 11:33:27 AM UTC+1, Mat wrote
>>
>> Very interesting. Only Mac so I can't try anything but just to make sure
>> I understand the implications for a TW context;
>>
>> - is the dat:// scheme not usable in regular browsers? (I find no public
>> site using it and basically no info on it outside of the Beaker project).
>> - ...and therefore, would one need special browsers both to admin a TW?
>> ...
>> - ...and also to visit (merely read) a TW?
>>
>
> As Jeremy points out, the dat:// protocol is not usable with other
> browsers at the moment. ... But if it gets enough traction that other
> browsers would loose market share, they may implement it. ... (in the
> future)
>
> It's beta software atm. The version number is 0.5.x. So imo it's still
> early enough, to get some of the TW ideas into the project, which will be
> beneficial for both projects.
>
> -mario
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/8072fd1b-2759-4dbb-bdc6-e464a1a99ee2%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

[twdev] Multi-user TiddlyWiki

[Arlen Beiler]

Hello Everyone,
After making the comment on the documentation, I started wondering exactly
what it would require to re-invent the MediaWiki juggernaut as TiddlyWiki.
Here is what I came up with. Part of this comes from my experience on
Wikipedia, and part from setting up my own MediaWiki installations on my
computer. Not that I have a lot of experience, but for what it's worth.

https://docs.google.com/document/d/1Y8qV6I9BI1vgvve5kfThLKUOPu0aeF-FiCNpWvP62Hs/edit?usp=sharing

Feel free to add comments on the document itself or here.

Enjoy!
-Arlen

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

Re: [twdev] Re: Sensitive but serious question for the core TW team... may offend.

[Arlen Beiler]

I do like the sound of Cardo.

On Sat, Oct 15, 2016 at 7:33 PM, Michael Joseph Rosenthal <
michael.the.awes...@gmail.com> wrote:

> In the USA/Texas, About 4/5 times I say "TiddlyWiki" to someone, they seem
> disgusted. At least 2 of those times they'll outright say "that's a
> horrible name".
> I agree that renaming TiddlyWiki shouldn't be a top priority, and it might
> not even be worth the switching cost. But given that "tiddler" makes so
> many people think "active pedophile", I'd say renaming the project at the
> first practical opportunity is a good idea.
>
> On Saturday, September 24, 2016 at 9:04:17 PM UTC-5, David Szego wrote:
>>
>> Hope this doesn't offend, especially Jeremy, but it's due to common
>> reactions in conversations lately.
>>
>> When I've been showing my Cardo project to people, and explaining that
>> it's based on this awesome self-contained javascript development
>> environment in a single html file that lets you completely contain your
>> entire knowledge store in a wikified hypercard sort of metaphor etc. etc.
>> called "TiddlyWiki"...
>>
>> ...the reaction I get is usually along the lines of one raised eyebrow, a
>> bit of a disgusted look, and the words "Tiddly winkie?" repeated back to me.
>>
>> I get that "Tiddler" is probably a very fine British term (I'm assuming?)
>> meaning a reminder, or something but here in Canada at least, just
>> saying Tiddler or Tiddly reeks of pedophilic abuse. Especially with the
>> extremely unfortunately paired term "wiki", which ends up making it all
>> sound too much like "diddlywinkie" - "playing with your peepee."
>>
>> That's a big part of why I called it "Cardo". And let's face it - TW
>> Classic and TW5 are basically the amazing evolution of Apple's Hypercard. I
>> have a hard time even typing "Tiddler" in these forums, let alone saying
>> it, but no problem talking about "Cards", which they essentially are, by
>> look and feel as well as by function.
>>
>> So... Maybe the next evolution of TW should be towards something more
>> user-adoptable, like calling it WikiCards or something?
>>
>> Again, sorry to offend... but judging by the reaction I get when talking
>> about the tool, (no innuendo intended there!!), I can't be the only one.
>>
>> Cheers,
>> David.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywikidev+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywikidev@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywikidev/dbf005e5-11f5-4731-83f1-ac472505a700%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [twdev] design of a media player

[Arlen Beiler]

The position of the media is important, as the refresh mechanism can
rerender HTML, thus halting any media that is playing. This is on the
assumption that the user wants to go on and do other stuff in the
tiddlywiki while he is listening to stuff. But maybe that isn't a real big
deal. It should only happen when certain tiddlers get edited. I don't know
much about how libraries work, but I would think that would be something to
look into. At least for audio. Video would probably be more embedded within
the content, but maybe someone would want that for video too. Just a
thought.

On Sat, Jan 24, 2015 at 8:29 AM, BJ buggy...@gmail.com wrote:

 Here are some note about the design of the media player plugin.

 Objective: to play media tiddlers that are linked to remote media, that
 are sequenced via playlists.
 Non functional considerations: controls must react in real-time, ie they
 must feel responsive. Play must not be interrupted.
 Assumption: Tiddlywiki5 should be usable on as many computers as twc, ie
 not just for the latest (fastest) computers.

 tw5 has three devices for widget interactions, the refresh mechanism(RM),
 widget-tree messages(WM) and invokeActions(IA).
 WMs operate from a node in the tree towards the root - for a tree with N
 nodes it takes a max of O(log(N)) operations to send a message from a node
 to
 one of its ancestors. At each widget the message is either forward or
 examined and then possibly forwarded.
 RM does a depth first transversal of the whole tree and is O(N). In
 addition each widget recalculates its parameters when visited.
 IA are applied to only immediate children and are O(1)
 So IA gives the fastest response, then WM.

 Up to now user interactions (via buttons etc) result in mainly RM as
 changes to the ui are mediated by modifying tiddlers, on an atom based
 notebook there is a perceivable delay between clicking a button and the
 resultant action. With a mediaplayer application, delays between user
 actions and results are very noticeable and give a poor user experience.

 The fastest design for a mediaplayer would be to have all the logic within
 a single widget. Players are embedded in the dom  and respond with dom
 events. It would be possible to have the dom 'finished playing' events
 directly trigger logic that would select the next track to play. Such a
 system would not be very flexible/extendable. It is more flexible to split
 the media player into logical components and to represent these components
 are widgets, allow a variable number of players and allowing other elements
 to be associated with the players (eg text and photos with mp3 tracks), as
 the user desires.

 The media play can be split into a sequencer (of a playlist) and players.
 Players respond to events generated by the sequencer or by user interaction
 (eg play pause), and generate events, some of which (eg finished) need to
 be sent to the sequencer.

 As there is one sequencer and many players, it seems logical to have the
 players as children of the sequencer. The device that gives the quickest
 possible inter-widget communication from the sequencer to the players is
 the IA. (Also, when action widgets are used with the button widget they
 separate the source of the event from the actions - this is a similar
 pattern). Likewise the quickest inter-widget comms from the players to the
 sequencer is given by WM.

 Players also respond to user input - different players may different
 controls - (eg fastforwards for video) - having controls as children of the
 players allow for a natural encapsulation.

 all comments wellcome!

 cheers

  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Refresh the widget, then what?

[Arlen Beiler]

Hi everyone, I have a code question here that I have been puzzling over for
a long time. Every single widget returns true or false and a comment says
Selectively refreshes the widget if needed. Returns true if the widget or
any of its children needed re-rendering. Now my question is, is there
anything that uses that returned value to tell if the widget or any of its
children need rerendering? If you know, please tell me where? I have been
unable to find it.
Thanks, Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: TW5 5.1.5 server does not start

[Arlen Beiler]

I'm sorry, the root folder of tiddlywiki. Beside tiddlywiki.js. My Nexus
spell checker keeps replacing tiddlywiki with tiddlywikidev.
-Arlen



On Tue, Dec 9, 2014 at 9:26 PM, Arlen Beiler arlen...@gmail.com wrote:

 Thanks, for your help, Mario. I discovered that after a bit.

 Jeremy, I downloaded the 5.1.5 tag from github, and then copied the node
 executable into the folder beside tiddlywiki.js. That makes it easier for
 me than worrying about the node command line and so forth. So I was in the
 root folder of tiddlywikidev and when I did init it copied the contents of
 the specified edition in beside tiddlywiki.js. Which was kind of odd, so
 then I went to some other command and saw the correct format there. Or else
 I searched the google groups.

 So, yeah. Hope that explains things.

 -Arlen
 On Dec 9, 2014 4:56 PM, Jeremy Ruston jeremy.rus...@gmail.com wrote:

 Hi Arlen

 First, to Mario's point, if you omit the edition folder from the
 tiddlywiki command then it defaults to using the current directory.

 The error message seems to show that you've somehow managed to have your
 TiddlyWiki core files (such as C:\Users\Arlen\Desktop\Arlen's
 Stuff\NodeJS\TW5.1.5\tiddlywiki.js) in the wiki folder that you're using
 (ie C:\Users\Arlen\Desktop\Arlen's Stuff\NodeJS\TW5.1.5).

 I'm not sure how that happened. The command node tiddlywiki --init
 tw5.com-server should raise an error if it is invoked when the current
 folder is empty.

 How did you install TiddlyWiki? What is the content of the TW5.1.5 folder?

 Best wishes

 Jeremy.



 On Tue, Dec 9, 2014 at 5:14 PM, PMario pmari...@gmail.com wrote:

 you missed the edition.

 node tiddlywiki editions/  --server 

 -m

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: TW5 5.1.5 server does not start

[Arlen Beiler]

I copied the complete output there. So I don't think so. It didn't have a
tiddlywiki.json (or whatever that file is) in it, but it did have other
files in it.
-Arlen

On Wed, Dec 10, 2014 at 4:04 PM, Jeremy Ruston jeremy.rus...@gmail.com
wrote:

 Hi Arlen

  So I was in the root folder of tiddlywikidev and when I did init it
 copied the contents of the specified edition in beside tiddlywiki.js. Which
 was kind of odd,

 OK, there's a problem there - the `--init` command should raise an error
 if the edition folder (or current folder) is not empty. Did that not happen
 in your case?

 Best wishes

 Jeremy


 On Wed, Dec 10, 2014 at 2:26 AM, Arlen Beiler arlen...@gmail.com wrote:

 Thanks, for your help, Mario. I discovered that after a bit.

 Jeremy, I downloaded the 5.1.5 tag from github, and then copied the node
 executable into the folder beside tiddlywiki.js. That makes it easier for
 me than worrying about the node command line and so forth. So I was in the
 root folder of tiddlywikidev and when I did init it copied the contents of
 the specified edition in beside tiddlywiki.js. Which was kind of odd, so
 then I went to some other command and saw the correct format there. Or else
 I searched the google groups.

 So, yeah. Hope that explains things.

 -Arlen
 On Dec 9, 2014 4:56 PM, Jeremy Ruston jeremy.rus...@gmail.com wrote:

 Hi Arlen

 First, to Mario's point, if you omit the edition folder from the
 tiddlywiki command then it defaults to using the current directory.

 The error message seems to show that you've somehow managed to have your
 TiddlyWiki core files (such as C:\Users\Arlen\Desktop\Arlen's
 Stuff\NodeJS\TW5.1.5\tiddlywiki.js) in the wiki folder that you're using
 (ie C:\Users\Arlen\Desktop\Arlen's Stuff\NodeJS\TW5.1.5).

 I'm not sure how that happened. The command node tiddlywiki --init
 tw5.com-server should raise an error if it is invoked when the current
 folder is empty.

 How did you install TiddlyWiki? What is the content of the TW5.1.5
 folder?

 Best wishes

 Jeremy.



 On Tue, Dec 9, 2014 at 5:14 PM, PMario pmari...@gmail.com wrote:

 you missed the edition.

 node tiddlywiki editions/  --server 

 -m

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.

  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: RenderTiddler seems to URI encode links in html

[Arlen Beiler]

Jeremy,
I don't really have time for pull requests right now, but if you want to
and like it, feel free to put it in yourself. I haven't signed the CLA
yet...
-Arlen

On Tue, Dec 9, 2014 at 5:07 PM, Jeremy Ruston jeremy.rus...@gmail.com
wrote:

 Hi Arlen

  Here is the result of my exploring today.

 Great stuff, well done. I'd be happy to take a pull request for these
 changes, if you're able. The associated documentation also needs updating.

 There are a few related tickets on the HTTP server module:

 https://github.com/Jermolene/TiddlyWiki5/issues/512 - Refactor routes
 from server.js as separate modules
 https://github.com/Jermolene/TiddlyWiki5/issues/1148 - Route to static
 files in the --server mode
 https://github.com/Jermolene/TiddlyWiki5/pull/976 - Allow additional
 server paths

 Best wishes

 Jeremy


 On Tue, Dec 9, 2014 at 9:51 PM, Arlen Beiler arlen...@gmail.com wrote:

 Actually, if you change the first one to path: /^\/static.html$/, it
 would work fine too.
 -Arlen

 On Tue, Dec 9, 2014 at 4:48 PM, Arlen Beiler arlen...@gmail.com wrote:

 Thank you.

 Here is the result of my exploring today. In order to generate static
 pages dynamically (!!!???), this code gets inserted into server.js. The
 only other change was to clone the $:/core/templates/static.template.html
 tiddler and change the link you mentioned to remove the static/ prefix. So
 here's the code. It comes right after the GET request for the root of the
 site.

 this.server.addRoute({
 method: GET,
 path: /^\/static\/$/,
 handler: function(request,response,state) {
 response.writeHead(200, {Content-Type:
 state.server.get(serveType)});
 var text =
 state.wiki.renderTiddler(text/plain,$:/arlen/static.template.html)
 response.end(text,utf8);
 }
 });
 this.server.addRoute({
 method: GET,
 path: /^\/static\/static.css$/,
 handler: function(request,response,state) {
 response.writeHead(200, {Content-Type: text/css});
 var text =
 state.wiki.renderTiddler(text/plain,$:/core/templates/static.template.css);
 response.end(text,utf8);
 }
 });
 this.server.addRoute({
 method: GET,
 path: /^\/static\/(.+).html$/,
 handler: function(request,response,state) {
 var title =
 decodeURIComponent(decodeURIComponent(state.params[0])),
 tiddler = state.wiki.getTiddler(title);
 if(tiddler) {
 response.writeHead(200, {Content-Type:
 state.server.get(serveType)});
 var text =
 state.wiki.renderTiddler(text/plain,$:/core/templates/static.tiddler.html,{
 variables: { currentTiddler: title }})
 response.end(text,utf8);
 } else {
 response.writeHead(404);
 response.end();
 }
 }
 });

 *Now to put it in a plugin...*

 *And make the tabs work...*

 *And add a static sidebar...*

 *And add the supporting libraries...*


 *And...and...and...*
 But I like the idea of having a clean, fast interface that does most of
 it's processing on the server.

 Enjoy!
 -Arlen

 On Tue, Dec 9, 2014 at 3:35 PM, Jeremy Ruston jeremy.rus...@gmail.com
 wrote:

 Hi Arlen

 The default static templates reconfigure the way that links are
 rendered so as to convert internal tiddler links into file links.

 At the top of $:/core/templates/static.template.html you'll see:

 \define tv-wikilink-template() static/$uri_doubleencoded$.html

 The docs for the link widget explain how the tv-wikilink-template macro
 is used:

 http://tiddlywiki.com/#LinkWidget

 Best wishes

 Jeremy.






 On Tue, Dec 9, 2014 at 8:30 PM, Arlen Beiler arlen...@gmail.com
 wrote:

 To explain in more detail, I am working on adding single page views to
 tiddlywiki that use the static mechanism but are generated on request. I
 think if I would put the title through decodeURIcomponent twice it would 
 be
 fine, but I wanted to make sure that this is according to design.
 -Arlen
 On Dec 9, 2014 2:42 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi all,
 I am working with the renderTiddler command and the tiddlywiki
 server, and the renderTiddler command seems to URI encode links to other
 tiddly documents. I am referring to the commands in this tiddler:
 http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki

 For instance, the command

 --rendertiddler $:/core/templates/static.template.html static.html
 text/plain

 renders internal links as

 static/Ten%2520reasons%2520to%2520switch%2520to%2520TiddlyWiki.html

 $:/core/templates/static.tiddler.html does the same thing, except
 without the static folder prefix.

 Thanks, Arlen

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

[twdev] TW5 5.1.5 server does not start

[Arlen Beiler]

Hi All,
I just downloaded TW5 from GitHub and am trying to start the node server.
However it gives this output.

C:\Users\Arlen\Desktop\Arlen's Stuff\NodeJS\TW5.1.5node tiddlywiki --init
tw5.com-server
Copied edition 'tw5.com-server' to C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5

C:\Users\Arlen\Desktop\Arlen's Stuff\NodeJS\TW5.1.5node tiddlywiki
--server 8080 $:/core/save/all text/plain text/html

fs.js:427
  return binding.open(pathModule._makeLong(path), stringToFlags(flags),
mode);
 ^
Error: ENOENT, no such file or directory 'C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\plugins\tiddlywiki\plugin.info'
at Object.fs.openSync (fs.js:427:18)
at Object.fs.readFileSync (fs.js:284:15)
at $tw.loadPluginFolder (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1454:34)
at $tw.loadWikiTiddlers (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1624:23)
at $tw.loadTiddlersNode (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1664:27)
at $tw.boot.startup (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1774:7)
at C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1943:12
at $tw.boot.decryptEncryptedTiddlers (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1368:2)
at $tw.boot.boot (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\boot\boot.js:1941:11)
at Object.anonymous (C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5\tiddlywiki.js:13:10)

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] RenderTiddler seems to URI encode links in html

[Arlen Beiler]

Hi all,
I am working with the renderTiddler command and the tiddlywiki server, and
the renderTiddler command seems to URI encode links to other tiddly
documents. I am referring to the commands in this tiddler:
http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki

For instance, the command

--rendertiddler $:/core/templates/static.template.html static.html
text/plain

renders internal links as

static/Ten%2520reasons%2520to%2520switch%2520to%2520TiddlyWiki.html

$:/core/templates/static.tiddler.html does the same thing, except without
the static folder prefix.

Thanks, Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: RenderTiddler seems to URI encode links in html

[Arlen Beiler]

To explain in more detail, I am working on adding single page views to
tiddlywiki that use the static mechanism but are generated on request. I
think if I would put the title through decodeURIcomponent twice it would be
fine, but I wanted to make sure that this is according to design.
-Arlen
On Dec 9, 2014 2:42 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi all,
 I am working with the renderTiddler command and the tiddlywiki server, and
 the renderTiddler command seems to URI encode links to other tiddly
 documents. I am referring to the commands in this tiddler:
 http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki

 For instance, the command

 --rendertiddler $:/core/templates/static.template.html static.html
 text/plain

 renders internal links as

 static/Ten%2520reasons%2520to%2520switch%2520to%2520TiddlyWiki.html

 $:/core/templates/static.tiddler.html does the same thing, except
 without the static folder prefix.

 Thanks, Arlen


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: RenderTiddler seems to URI encode links in html

[Arlen Beiler]

Thank you.

Here is the result of my exploring today. In order to generate static pages
dynamically (!!!???), this code gets inserted into server.js. The only
other change was to clone the $:/core/templates/static.template.html
tiddler and change the link you mentioned to remove the static/ prefix. So
here's the code. It comes right after the GET request for the root of the
site.

this.server.addRoute({
method: GET,
path: /^\/static\/$/,
handler: function(request,response,state) {
response.writeHead(200, {Content-Type:
state.server.get(serveType)});
var text =
state.wiki.renderTiddler(text/plain,$:/arlen/static.template.html)
response.end(text,utf8);
}
});
this.server.addRoute({
method: GET,
path: /^\/static\/static.css$/,
handler: function(request,response,state) {
response.writeHead(200, {Content-Type: text/css});
var text =
state.wiki.renderTiddler(text/plain,$:/core/templates/static.template.css);
response.end(text,utf8);
}
});
this.server.addRoute({
method: GET,
path: /^\/static\/(.+).html$/,
handler: function(request,response,state) {
var title =
decodeURIComponent(decodeURIComponent(state.params[0])),
tiddler = state.wiki.getTiddler(title);
if(tiddler) {
response.writeHead(200, {Content-Type:
state.server.get(serveType)});
var text =
state.wiki.renderTiddler(text/plain,$:/core/templates/static.tiddler.html,{
variables: { currentTiddler: title }})
response.end(text,utf8);
} else {
response.writeHead(404);
response.end();
}
}
});

*Now to put it in a plugin...*

*And make the tabs work...*

*And add a static sidebar...*

*And add the supporting libraries...*


*And...and...and...*
But I like the idea of having a clean, fast interface that does most of
it's processing on the server.

Enjoy!
-Arlen

On Tue, Dec 9, 2014 at 3:35 PM, Jeremy Ruston jeremy.rus...@gmail.com
wrote:

 Hi Arlen

 The default static templates reconfigure the way that links are rendered
 so as to convert internal tiddler links into file links.

 At the top of $:/core/templates/static.template.html you'll see:

 \define tv-wikilink-template() static/$uri_doubleencoded$.html

 The docs for the link widget explain how the tv-wikilink-template macro is
 used:

 http://tiddlywiki.com/#LinkWidget

 Best wishes

 Jeremy.






 On Tue, Dec 9, 2014 at 8:30 PM, Arlen Beiler arlen...@gmail.com wrote:

 To explain in more detail, I am working on adding single page views to
 tiddlywiki that use the static mechanism but are generated on request. I
 think if I would put the title through decodeURIcomponent twice it would be
 fine, but I wanted to make sure that this is according to design.
 -Arlen
 On Dec 9, 2014 2:42 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi all,
 I am working with the renderTiddler command and the tiddlywiki server,
 and the renderTiddler command seems to URI encode links to other tiddly
 documents. I am referring to the commands in this tiddler:
 http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki

 For instance, the command

 --rendertiddler $:/core/templates/static.template.html static.html
 text/plain

 renders internal links as

 static/Ten%2520reasons%2520to%2520switch%2520to%2520TiddlyWiki.html

 $:/core/templates/static.tiddler.html does the same thing, except
 without the static folder prefix.

 Thanks, Arlen

  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: RenderTiddler seems to URI encode links in html

[Arlen Beiler]

Actually, if you change the first one to path: /^\/static.html$/, it
would work fine too.
-Arlen

On Tue, Dec 9, 2014 at 4:48 PM, Arlen Beiler arlen...@gmail.com wrote:

 Thank you.

 Here is the result of my exploring today. In order to generate static
 pages dynamically (!!!???), this code gets inserted into server.js. The
 only other change was to clone the $:/core/templates/static.template.html
 tiddler and change the link you mentioned to remove the static/ prefix. So
 here's the code. It comes right after the GET request for the root of the
 site.

 this.server.addRoute({
 method: GET,
 path: /^\/static\/$/,
 handler: function(request,response,state) {
 response.writeHead(200, {Content-Type:
 state.server.get(serveType)});
 var text =
 state.wiki.renderTiddler(text/plain,$:/arlen/static.template.html)
 response.end(text,utf8);
 }
 });
 this.server.addRoute({
 method: GET,
 path: /^\/static\/static.css$/,
 handler: function(request,response,state) {
 response.writeHead(200, {Content-Type: text/css});
 var text =
 state.wiki.renderTiddler(text/plain,$:/core/templates/static.template.css);
 response.end(text,utf8);
 }
 });
 this.server.addRoute({
 method: GET,
 path: /^\/static\/(.+).html$/,
 handler: function(request,response,state) {
 var title =
 decodeURIComponent(decodeURIComponent(state.params[0])),
 tiddler = state.wiki.getTiddler(title);
 if(tiddler) {
 response.writeHead(200, {Content-Type:
 state.server.get(serveType)});
 var text =
 state.wiki.renderTiddler(text/plain,$:/core/templates/static.tiddler.html,{
 variables: { currentTiddler: title }})
 response.end(text,utf8);
 } else {
 response.writeHead(404);
 response.end();
 }
 }
 });

 *Now to put it in a plugin...*

 *And make the tabs work...*

 *And add a static sidebar...*

 *And add the supporting libraries...*


 *And...and...and...*
 But I like the idea of having a clean, fast interface that does most of
 it's processing on the server.

 Enjoy!
 -Arlen

 On Tue, Dec 9, 2014 at 3:35 PM, Jeremy Ruston jeremy.rus...@gmail.com
 wrote:

 Hi Arlen

 The default static templates reconfigure the way that links are rendered
 so as to convert internal tiddler links into file links.

 At the top of $:/core/templates/static.template.html you'll see:

 \define tv-wikilink-template() static/$uri_doubleencoded$.html

 The docs for the link widget explain how the tv-wikilink-template macro
 is used:

 http://tiddlywiki.com/#LinkWidget

 Best wishes

 Jeremy.






 On Tue, Dec 9, 2014 at 8:30 PM, Arlen Beiler arlen...@gmail.com wrote:

 To explain in more detail, I am working on adding single page views to
 tiddlywiki that use the static mechanism but are generated on request. I
 think if I would put the title through decodeURIcomponent twice it would be
 fine, but I wanted to make sure that this is according to design.
 -Arlen
 On Dec 9, 2014 2:42 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi all,
 I am working with the renderTiddler command and the tiddlywiki server,
 and the renderTiddler command seems to URI encode links to other tiddly
 documents. I am referring to the commands in this tiddler:
 http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki

 For instance, the command

 --rendertiddler $:/core/templates/static.template.html static.html
 text/plain

 renders internal links as

 static/Ten%2520reasons%2520to%2520switch%2520to%2520TiddlyWiki.html

 $:/core/templates/static.tiddler.html does the same thing, except
 without the static folder prefix.

 Thanks, Arlen

  --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

Re: [twdev] Re: TW5 5.1.5 server does not start

[Arlen Beiler]

Thanks, for your help, Mario. I discovered that after a bit.

Jeremy, I downloaded the 5.1.5 tag from github, and then copied the node
executable into the folder beside tiddlywiki.js. That makes it easier for
me than worrying about the node command line and so forth. So I was in the
root folder of tiddlywikidev and when I did init it copied the contents of
the specified edition in beside tiddlywiki.js. Which was kind of odd, so
then I went to some other command and saw the correct format there. Or else
I searched the google groups.

So, yeah. Hope that explains things.

-Arlen
On Dec 9, 2014 4:56 PM, Jeremy Ruston jeremy.rus...@gmail.com wrote:

 Hi Arlen

 First, to Mario's point, if you omit the edition folder from the
 tiddlywiki command then it defaults to using the current directory.

 The error message seems to show that you've somehow managed to have your
 TiddlyWiki core files (such as C:\Users\Arlen\Desktop\Arlen's
 Stuff\NodeJS\TW5.1.5\tiddlywiki.js) in the wiki folder that you're using
 (ie C:\Users\Arlen\Desktop\Arlen's Stuff\NodeJS\TW5.1.5).

 I'm not sure how that happened. The command node tiddlywiki --init
 tw5.com-server should raise an error if it is invoked when the current
 folder is empty.

 How did you install TiddlyWiki? What is the content of the TW5.1.5 folder?

 Best wishes

 Jeremy.



 On Tue, Dec 9, 2014 at 5:14 PM, PMario pmari...@gmail.com wrote:

 you missed the edition.

 node tiddlywiki editions/  --server 

 -m

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] About my pull request, I think I'll let you guys...

[Arlen Beiler]

Hi Jeremy,
How are you doing? I think I'm just going to let you guys handle this
new tiddler stuff from here on. I expected this to be a quick hack, but
beings it's been this long, I think I'll let you guys take care of it.
The feature I am requesting which started the whole thing is to create
a tiddler if it doesn't exist, but do nothing if it does. It wouldn't have
to be in the fieldmangler widget, it could be anywhere. This allows state
tiddlers to be initialized to a certain state with any fields needed, and
so on.
Anyway, I normally try making something and then discover I need it so
I ask for it. But once I see what mechanism you guys figure out for this
stuff, I might think of an idea for how to do it if you guys don't already
have it figured out by then.
Thanks a lot for your patience, and you're more than welcome to mine.
:D I've enjoyed this stint, and learned quite a bit along the way, so it
isn't wasted.
--Arlen

P.S. Here are a few gists that list most of my code changes. They are in
the public domain. If there are any help, you are welcome to them.

https://gist.github.com/Arlen22/11149813
https://gist.github.com/Arlen22/9807217
https://gist.github.com/Arlen22/9814436

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Create Tiddler additions

[Arlen Beiler]

Hi Jeremy,
Not sure if you saw my comment on GitHub, but what do you think about
defining the macro body in a separate tiddler? Something like \define
{new-tiddler-test} mySkelaton()
The reason I like the x-tiddler serial format so much is because (1) it
is already made, and (2) it does everything in what seems to be an easy to
use format. The only thing I'm not sure about is backward compatibility
within the navigator widget. Currently, I look for a linebreak in the param
string and if there isn't one then use the old getTiddler method. However,
this constrains us to using multiple lines going forward. Maybe that
doesn't matter. Maybe it does. What do you think?
The fieldmangler widget is getting a new attribute so it isn't affected
as far as backward compatibility.

--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: Create Tiddler additions

[Arlen Beiler]

Here is a gist showing the changes to macrodef.js that would be necessary.
https://gist.github.com/Arlen22/11149813

I copied in the current version first, so if you click revisions you can
see the changes I made. Enjoy!

--Arlen


On Mon, Apr 21, 2014 at 1:11 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi Jeremy,
 Not sure if you saw my comment on GitHub, but what do you think about
 defining the macro body in a separate tiddler? Something like \define
 {new-tiddler-test} mySkelaton()
 The reason I like the x-tiddler serial format so much is because (1)
 it is already made, and (2) it does everything in what seems to be an easy
 to use format. The only thing I'm not sure about is backward compatibility
 within the navigator widget. Currently, I look for a linebreak in the param
 string and if there isn't one then use the old getTiddler method. However,
 this constrains us to using multiple lines going forward. Maybe that
 doesn't matter. Maybe it does. What do you think?
 The fieldmangler widget is getting a new attribute so it isn't
 affected as far as backward compatibility.

 --Arlen


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Add create tiddler functionality to fieldmangler and navigator #510

[Arlen Beiler]

Hi Jeremy,
just wondering about my pull request -- do I need to open a new one now
that we did 5.0.9, or is it probably still good? I'm not really actively
looking into into the macros options, maybe you could give me some input on
what you're thinking about it. When you have time. I'm sure you're busy
right now.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] [TW5] list-after

[Arlen Beiler]

Hi everyone,
Could list-after put the tiddler at the end of the list if it is blank
the way list before does at the beginning of the list? Because some places
we need it after, like CSS styles. For some reason, the PageStylesheet now
lists all user stylesheets at the beginning. Not sure what it's based on.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Theme classes on navigator

[Arlen Beiler]

Pefect. Thanks a lot.


On Fri, Apr 11, 2014 at 4:40 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 I've added CSS classes for the current theme and the current language to
 the tw-page-container DIV:


 https://github.com/Jermolene/TiddlyWiki5/commit/a3cf925e56743d086b1b5ac10a1f618b7f3ca218

 The classes are tw-page-view-{view name} and tw-language-{language
 abbreviation}

 Best wishes

 Jeremy.


 [image: Inline image 1]


 On Wed, Apr 9, 2014 at 11:07 AM, PMario pmari...@gmail.com wrote:

 I personally think, that the base layout and the base CSS needs tweaking
 anyway.
 I did create a small pull request [1] that modifies the right sidebar DOM
 structure.
 It removes the unnecessary p tags, without changing the overall layout.

 At the moment I try to simplify the base CSS, to make it less specific,
 which will make tweaking the themes much easier.
 eg: imo there should be no need to use !Important for any theme or even
 a.something{}

 ... I didn't send those modifications, because there are too many changes
 for one pull request.
 So discussing with Jeremy, we agreed to split them into manageable pieces.

 ... Also Jeremy mentioned in a hangout, that he wants to have the
 possibility to use menu bars on every side (top, right, bottom, left).
 So there may be changes to the base layout in future TW betas.

 The problem here is, that changing the base layout may break existing
 tweaks.  So a bit of care has to be taken.

 So if you need a fluid layout, you'll need to create your own CSS anyway.

 just my thoughts
 mario

 [1] https://github.com/Jermolene/TiddlyWiki5/pull/527

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
inline: image.png

[twdev] Theme classes on navigator

[Arlen Beiler]

Hi everyone,
What are the advantages or disadvantages of adding the current theme
and current view to the page navigator widget class tag? Or the body tag?
I'm currently working with fluid widths and the zoomin view requires the
tiddler width to be set one way, and the classic view requires it to be
another way. I'm sure the cecily view wouldn't even work with what I'm
trying to do (actually, it seems like the same scenario).
The problem I am running into is that the tiddler frame needs to be
100% of the story river for fluid width. In classic, that's fine, since the
tiddler is position:relative. In zoomin, it is absolute and so jumps from
686px to 770px, covering part of the sidebar. I could add css like .zoomin
.tw-tiddler-frame { calc(100% - 84px); }.
Or at least the current view.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Hi guys, just checking in to see how everything is going. I'd love to see
these two bits in 5.0.9, but if there is other things you are waiting on,
that's fine. Also, the newtiddler bit answers everything in skeeve's plugin
without needing a separate tiddler for the skeleton. I'm also adding a
couple more things for tw5.com or the system namespace via comments. For
that matter, why don't we just use the .tid format for the html tiddler
store? It seems like it would work great and shouldn't be hard to change
over. I'm sure it'd break every tiddlywiki and its neighbor, unless the
upgrade mechanism allows for that already. Actually, it shouldn't break
anything.

Just some thoughts. --Arlen


On Mon, Mar 31, 2014 at 1:44 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi Everyone,
 I closed that one and then opened a new pull request:
 https://github.com/Jermolene/TiddlyWiki5/pull/510. I think I understood
 what you wanted. Is there anything I am missing?
  --Arlen




 On Wed, Mar 26, 2014 at 6:08 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 I'll reply on the pull request you created:

 https://github.com/Jermolene/TiddlyWiki5/pull/503

  Best wishes

 Jeremy



 On Mon, Mar 24, 2014 at 8:44 PM, Arlen Beiler arlen...@gmail.com wrote:

 Alright, how's this?

 this.createText  = this.getAttribute(create,false);
 // Process create param
 if(this.createText) {
   var createTiddler =
 $tw.wiki.deserializeTiddlers(application/x-tiddler,this.createText);
   createTiddler[0]['title'] = this.mangleTitle;
   if(!this.wiki.tiddlerExists(this.mangleTitle))
 this.wiki.addTiddler(createTiddler[0]);
 }




 On Mon, Mar 24, 2014 at 10:26 AM, Arlen Beiler arlen...@gmail.comwrote:

 Hi Jeremy,
 Would the syntax use line breaks? Or were you thinking about all on one
 line? How do line breaks work with wikitext like that?

 --Arlen


 On Thu, Mar 20, 2014 at 1:16 PM, Jeremy Ruston jeremy.rus...@gmail.com
  wrote:

 Hi Arlen

 Good stuff. My intention is to do something very similar but for the
 literal tiddler syntax to resemble a .tid file:

 title: myTitle
 tags: one two three
 text: This is the text

 I was primarily thinking about using the syntax with the new tiddler
 message, but it's a good idea to support it on the fieldmangler widget as
 well.

  Best wishes

 Jeremy





 On Thu, Mar 20, 2014 at 1:22 PM, Arlen Beiler arlen...@gmail.comwrote:

 Hi Everyone,
 Here is the result of my latest endeavor. This adds a create
 parameter to the fieldmangler widget which creates the tiddler specified 
 in
 tiddler with the fields in create. This allows temp tiddlers to be
 initialized with state data without needing a button click. Notice that 
 it
 only creates it if it doesn't exist.

 this.mangleTitle = ... ; //Insert after this line in execute()
 this.createText  = this.getAttribute(create,false);
 if(typeof(this.createText) === string) {
   try{ this.createText = JSON.parse(this.createText); }
   catch (e) { console.error(e); this.createText = false; }
   console.log(this.createText);
   if(this.createText){
 this.createText['title'] = this.mangleTitle;
 if(!this.wiki.tiddlerExists(this.mangleTitle))
   this.wiki.addTiddler(this.createText);
   }
 }

 And here is a tiddler that uses it. This tiddler creates a button
 that toggles the story river between centered and normal. Centered is
 default.

  \define createStateTiddler()
 { text: $(default)$ , tags: $:/tags/stylesheet }
 \end
 \define state-1-css()

 \end
 \define state-2-css()
 @media (min-width: 770px) { .story-river { margin: 0 auto; }
 .sidebar-header { left: 50%; right: 0; padding-left: 413px; } }
 \end
 $set name=default value=state-2-css 
 span title=Toggle width/sidebar
  $fieldmangler tiddler=$:/temp/toggle-centered
 create=createStateTiddler
 $reveal type=match state=$:/temp/toggle-centered
 text=state-1-css default=$(default)$
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-2-css  class=btn-invisible
 centered-toggle-1{{$:/_images/right-arrow-button}}/$button
 /$reveal$reveal type=match state=$:/temp/toggle-centered
 text=state-2-css
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-1-css class=btn-invisible
 centered-toggle-2{{$:/_images/left-arrow-button}}/$button
 /$reveal/$fieldmangler
 /span
 /$set

 If you don't have the corresponding images for the buttons, just
 remove the btn-invisible class from the buttons. I'm putting this out as 
 a
 feature request (a hackability request?).

 I haven't changed the buttons yet, so that is how they were working
 before I did this. I had to click the button once to create the tiddler,
 and then a second time to finally see something happen. This way, 
 whatever
 way I initialize it I see the effect on start up.

 Is this something that could be added to the core? Note that
 create, as I wrote it, must be valid JSON and the title gets 
 overwritten
 if it is there. Enjoy!

 --Arlen

 --
 You

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Ok, finally got it. processVariables tiddler:new-tiddler-test 

This takes the tiddler text in the specified tiddler and calls
substituteVariableReferences. It also has a text attribute for passing
straight text. This is a javascript macro.

/*\
title: $:/Arlen/macros/processVariables.js
type: application/javascript
module-type: macro

processVariables ... 

\*/
(function(){

/*jslint node: true, browser: true */
/*global $tw: false */
use strict;

/*
Information about this macro
*/

exports.name = processVariables;

exports.params = [
{name: text},
 {name: tiddler}
];

/*
Run the macro
*/
exports.run = function(text, tiddler) {

var res = ;
if(text) res = this.substituteVariableReferences(text || );
if(tiddler) res =
this.substituteVariableReferences(this.wiki.getTiddlerText(tiddler) || );
return res;
};

})();

On Mon, Apr 7, 2014 at 1:45 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hello Everyone,
 Yes, Danielo, I would like to see them in the next TW5 release, but
 we'll see.
 I take that back about answering everything in Skeeve's plugin. That
 is only if you don't use a separate template tiddler (which was the point,
 but anyway...). I'm still thinking what to do if you are using a separate
 tiddler. I checked it out and it indeed won't work. I thought of
 transcluding the template tiddler into the macro, but transclusions don't
 work in macros. I'm sure this is intentional.
 Actually, if I replace the macro call with a transclusion call (
 param={{new-tiddler-template}} ), this works fine, except that the
 variables are not filled in. Normally, if you want variables in a macro
 result you would use \define me()$($(test)$)$ which results in \define
 me()$(testValue)$ in the new tiddler. However, if I want to transclude
 another tiddler, I would have to process variables in the tw-new-tiddler
 handler, which would result in the wikitext from macros
 (param=tiddlerText) being processed a second time. I'm sure I'm way
 ahead of everyone else, but that just came as I was typing so I just kept
 going. Is this a realistic concern or is it not?
 What about using a global macro called process variables? OK, trying
 that without much success. Can't put widgets inside widget opening tags,
 can't transclude in macro calls. Still thinking over this one. I finally
 think I got skeeve's point. This provides an alternate means but not a
 solution to the problem.

 Note the single line macro me. Nested multiline macros do not work. A
 separate template tiddler would be required.

 \define tiddlerText()



 \define me()$($(test)$)$
 $set name=try value=tried it
 me
 /$set
 \end
 $set name=test value=try 
 $button message=tw-new-tiddler class=btn-invisible
 param=tiddlerText {{$:/core/images/new-button}}/$button
 /$set





 On Mon, Apr 7, 2014 at 10:02 AM, Danielo Rodríguez rdani...@gmail.comwrote:

 Hello Arlen

 Could you explain a little bit what are you talking about? Some of your
 sentences makes me curious about the bits you talk about. But since you
 have commented here and in github I'm a bit lost. Are those things to be
 implemented in the next TW5 release?

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

OK, everyone. That's done and working. Now I am able to use a separate
tiddler as the template, or a macro in the same one. If it is a separate
tiddler, it only uses the text of the tiddler. It does not worry about
anything else.

Here is the macro:
https://github.com/Arlen22/TiddlyWiki5/blob/tiddler-seriel/core/modules/macros/substituteVariable.js

I like skeeve's Let widget. I'm sure it'd need a little tweaking, but... Is
there any reason we couldn't add that to core? Is there any reason why we
would ever need set? Yeah, to assign the variable name via a macro.


On Mon, Apr 7, 2014 at 3:03 PM, Arlen Beiler arlen...@gmail.com wrote:

 Ok, finally got it. processVariables tiddler:new-tiddler-test 

 This takes the tiddler text in the specified tiddler and calls
 substituteVariableReferences. It also has a text attribute for passing
 straight text. This is a javascript macro.



 On Mon, Apr 7, 2014 at 1:45 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hello Everyone,
 Yes, Danielo, I would like to see them in the next TW5 release, but
 we'll see.
 I take that back about answering everything in Skeeve's plugin. That
 is only if you don't use a separate template tiddler (which was the point,
 but anyway...). I'm still thinking what to do if you are using a separate
 tiddler. I checked it out and it indeed won't work. I thought of
 transcluding the template tiddler into the macro, but transclusions don't
 work in macros. I'm sure this is intentional.
 Actually, if I replace the macro call with a transclusion call (
 param={{new-tiddler-template}} ), this works fine, except that the
 variables are not filled in. Normally, if you want variables in a macro
 result you would use \define me()$($(test)$)$ which results in \define
 me()$(testValue)$ in the new tiddler. However, if I want to transclude
 another tiddler, I would have to process variables in the tw-new-tiddler
 handler, which would result in the wikitext from macros
 (param=tiddlerText) being processed a second time. I'm sure I'm way
 ahead of everyone else, but that just came as I was typing so I just kept
 going. Is this a realistic concern or is it not?
 What about using a global macro called process variables? OK, trying
 that without much success. Can't put widgets inside widget opening tags,
 can't transclude in macro calls. Still thinking over this one. I finally
 think I got skeeve's point. This provides an alternate means but not a
 solution to the problem.

 Note the single line macro me. Nested multiline macros do not work. A
 separate template tiddler would be required.

 \define tiddlerText()



 \define me()$($(test)$)$
 $set name=try value=tried it
 me
 /$set
 \end
 $set name=test value=try 
 $button message=tw-new-tiddler class=btn-invisible
 param=tiddlerText {{$:/core/images/new-button}}/$button
 /$set





 On Mon, Apr 7, 2014 at 10:02 AM, Danielo Rodríguez rdani...@gmail.comwrote:

 Hello Arlen

 Could you explain a little bit what are you talking about? Some of your
 sentences makes me curious about the bits you talk about. But since you
 have commented here and in github I'm a bit lost. Are those things to be
 implemented in the next TW5 release?

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.





-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Danielo, this is pull request 510 and centers around creating new tiddlers
using the x-tiddler format, aka .tid files. I wanted a way to be able to
create new tiddlers with whatever fields I wanted and whatever text, and
have the template in the same tiddler as where it was used so I wouldn't
need two or more tiddlers. First I used JSON, and when I posted that here,
Jeremy said he was thinking of something more like the .tid file format for
the navigator widget. So I found the deserializer for the .tid files and
the rest is history: https://github.com/Jermolene/TiddlyWiki5/pull/510

And here is an updated link to the macro.
https://github.com/Arlen22/TiddlyWiki5/blob/tiddler-seriel/core/modules/macros/substituteVariables.js

I hope you can select which commits to pull in, Jeremy.


On Mon, Apr 7, 2014 at 3:59 PM, Arlen Beiler arlen...@gmail.com wrote:

 OK, everyone. That's done and working. Now I am able to use a separate
 tiddler as the template, or a macro in the same one. If it is a separate
 tiddler, it only uses the text of the tiddler. It does not worry about
 anything else.

 Here is the macro:
 https://github.com/Arlen22/TiddlyWiki5/blob/tiddler-seriel/core/modules/macros/substituteVariable.js

 I like skeeve's Let widget. I'm sure it'd need a little tweaking, but...
 Is there any reason we couldn't add that to core? Is there any reason why
 we would ever need set? Yeah, to assign the variable name via a macro.


 On Mon, Apr 7, 2014 at 3:03 PM, Arlen Beiler arlen...@gmail.com wrote:

 Ok, finally got it. processVariables tiddler:new-tiddler-test 

 This takes the tiddler text in the specified tiddler and calls
 substituteVariableReferences. It also has a text attribute for passing
 straight text. This is a javascript macro.



 On Mon, Apr 7, 2014 at 1:45 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hello Everyone,
 Yes, Danielo, I would like to see them in the next TW5 release, but
 we'll see.
 I take that back about answering everything in Skeeve's plugin. That
 is only if you don't use a separate template tiddler (which was the point,
 but anyway...). I'm still thinking what to do if you are using a separate
 tiddler. I checked it out and it indeed won't work. I thought of
 transcluding the template tiddler into the macro, but transclusions don't
 work in macros. I'm sure this is intentional.
 Actually, if I replace the macro call with a transclusion call (
 param={{new-tiddler-template}} ), this works fine, except that the
 variables are not filled in. Normally, if you want variables in a macro
 result you would use \define me()$($(test)$)$ which results in \define
 me()$(testValue)$ in the new tiddler. However, if I want to transclude
 another tiddler, I would have to process variables in the tw-new-tiddler
 handler, which would result in the wikitext from macros
 (param=tiddlerText) being processed a second time. I'm sure I'm way
 ahead of everyone else, but that just came as I was typing so I just kept
 going. Is this a realistic concern or is it not?
 What about using a global macro called process variables? OK, trying
 that without much success. Can't put widgets inside widget opening tags,
 can't transclude in macro calls. Still thinking over this one. I finally
 think I got skeeve's point. This provides an alternate means but not a
 solution to the problem.

 Note the single line macro me. Nested multiline macros do not work. A
 separate template tiddler would be required.

 \define tiddlerText()



 \define me()$($(test)$)$
 $set name=try value=tried it
 me
 /$set
 \end
 $set name=test value=try 
 $button message=tw-new-tiddler class=btn-invisible
 param=tiddlerText {{$:/core/images/new-button}}/$button
 /$set





 On Mon, Apr 7, 2014 at 10:02 AM, Danielo Rodríguez 
 rdani...@gmail.comwrote:

 Hello Arlen

 Could you explain a little bit what are you talking about? Some of your
 sentences makes me curious about the bits you talk about. But since you
 have commented here and in github I'm a bit lost. Are those things to be
 implemented in the next TW5 release?

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.






-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Multitids and plugins

[Arlen Beiler]

Hi Everyone,
It would be nice if plugin bunch tiddlers could be multitid format instead
of JSON. Or is the multitid format not versatile enough. Or a way to
generate the JSON would be nice too.

Just a thought.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Multitids and plugins

[Arlen Beiler]

Well, that's the use case. I do remember seeing it but forgot about it.
Thanks


On Mon, Apr 7, 2014 at 5:46 PM, PMario pmari...@gmail.com wrote:

 Hi Arlen,
 Did you see: How to create plugins in the browser at
 http://tiddlywiki.com ?

 Can you describe your usecase a bit closer?
 -mario

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: Multitids and plugins

[Arlen Beiler]

Hey, another question about that. Is that dependants or dependancies?


On Mon, Apr 7, 2014 at 6:05 PM, Arlen Beiler arlen...@gmail.com wrote:

 Well, that's the use case. I do remember seeing it but forgot about it.
 Thanks


 On Mon, Apr 7, 2014 at 5:46 PM, PMario pmari...@gmail.com wrote:

 Hi Arlen,
 Did you see: How to create plugins in the browser at
 http://tiddlywiki.com ?

 Can you describe your usecase a bit closer?
 -mario

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Hi Everyone,
I closed that one and then opened a new pull request:
https://github.com/Jermolene/TiddlyWiki5/pull/510. I think I understood
what you wanted. Is there anything I am missing?
--Arlen




On Wed, Mar 26, 2014 at 6:08 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 I'll reply on the pull request you created:

 https://github.com/Jermolene/TiddlyWiki5/pull/503

  Best wishes

 Jeremy



 On Mon, Mar 24, 2014 at 8:44 PM, Arlen Beiler arlen...@gmail.com wrote:

 Alright, how's this?

 this.createText  = this.getAttribute(create,false);
 // Process create param
 if(this.createText) {
   var createTiddler =
 $tw.wiki.deserializeTiddlers(application/x-tiddler,this.createText);
   createTiddler[0]['title'] = this.mangleTitle;
   if(!this.wiki.tiddlerExists(this.mangleTitle))
 this.wiki.addTiddler(createTiddler[0]);
 }




 On Mon, Mar 24, 2014 at 10:26 AM, Arlen Beiler arlen...@gmail.comwrote:

 Hi Jeremy,
 Would the syntax use line breaks? Or were you thinking about all on one
 line? How do line breaks work with wikitext like that?

 --Arlen


 On Thu, Mar 20, 2014 at 1:16 PM, Jeremy Ruston 
 jeremy.rus...@gmail.comwrote:

 Hi Arlen

 Good stuff. My intention is to do something very similar but for the
 literal tiddler syntax to resemble a .tid file:

 title: myTitle
 tags: one two three
 text: This is the text

 I was primarily thinking about using the syntax with the new tiddler
 message, but it's a good idea to support it on the fieldmangler widget as
 well.

  Best wishes

 Jeremy





 On Thu, Mar 20, 2014 at 1:22 PM, Arlen Beiler arlen...@gmail.comwrote:

 Hi Everyone,
 Here is the result of my latest endeavor. This adds a create parameter
 to the fieldmangler widget which creates the tiddler specified in 
 tiddler
 with the fields in create. This allows temp tiddlers to be initialized
 with state data without needing a button click. Notice that it only 
 creates
 it if it doesn't exist.

 this.mangleTitle = ... ; //Insert after this line in execute()
 this.createText  = this.getAttribute(create,false);
 if(typeof(this.createText) === string) {
   try{ this.createText = JSON.parse(this.createText); }
   catch (e) { console.error(e); this.createText = false; }
   console.log(this.createText);
   if(this.createText){
 this.createText['title'] = this.mangleTitle;
 if(!this.wiki.tiddlerExists(this.mangleTitle))
   this.wiki.addTiddler(this.createText);
   }
 }

 And here is a tiddler that uses it. This tiddler creates a button that
 toggles the story river between centered and normal. Centered is default.

  \define createStateTiddler()
 { text: $(default)$ , tags: $:/tags/stylesheet }
 \end
 \define state-1-css()

 \end
 \define state-2-css()
 @media (min-width: 770px) { .story-river { margin: 0 auto; }
 .sidebar-header { left: 50%; right: 0; padding-left: 413px; } }
 \end
 $set name=default value=state-2-css 
 span title=Toggle width/sidebar
  $fieldmangler tiddler=$:/temp/toggle-centered
 create=createStateTiddler
 $reveal type=match state=$:/temp/toggle-centered
 text=state-1-css default=$(default)$
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-2-css  class=btn-invisible
 centered-toggle-1{{$:/_images/right-arrow-button}}/$button
 /$reveal$reveal type=match state=$:/temp/toggle-centered
 text=state-2-css
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-1-css class=btn-invisible
 centered-toggle-2{{$:/_images/left-arrow-button}}/$button
 /$reveal/$fieldmangler
 /span
 /$set

 If you don't have the corresponding images for the buttons, just
 remove the btn-invisible class from the buttons. I'm putting this out as a
 feature request (a hackability request?).

 I haven't changed the buttons yet, so that is how they were working
 before I did this. I had to click the button once to create the tiddler,
 and then a second time to finally see something happen. This way, whatever
 way I initialize it I see the effect on start up.

 Is this something that could be added to the core? Note that create,
 as I wrote it, must be valid JSON and the title gets overwritten if it is
 there. Enjoy!

 --Arlen

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

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

[twdev] Remove the scrollable from the story river

[Arlen Beiler]

Hi Everyone,

https://github.com/Jermolene/TiddlyWiki5/commit/59ac38a3da8ea85422f1955a0513f25c1f22


 The problem was that the scrollable required that the mouse be over the
 story river itself in order to scroll it with the wheel. If we fallback to
 scrolling the story by scrolling the browser body then we are able to
 scroll even if the mouse is over the sidebar.


I actually like it if the story river doesn't scroll when you scroll the
sidebar. It makes it feel much cleaner because I can quickly scroll to the
bottom or top without unrelated parts of the page suddenly scrolling.

Just a thought.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Hi Jeremy,
Would the syntax use line breaks? Or were you thinking about all on one
line? How do line breaks work with wikitext like that?

--Arlen


On Thu, Mar 20, 2014 at 1:16 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 Good stuff. My intention is to do something very similar but for the
 literal tiddler syntax to resemble a .tid file:

 title: myTitle
 tags: one two three
 text: This is the text

 I was primarily thinking about using the syntax with the new tiddler
 message, but it's a good idea to support it on the fieldmangler widget as
 well.

  Best wishes

 Jeremy





 On Thu, Mar 20, 2014 at 1:22 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi Everyone,
 Here is the result of my latest endeavor. This adds a create parameter to
 the fieldmangler widget which creates the tiddler specified in tiddler
 with the fields in create. This allows temp tiddlers to be initialized
 with state data without needing a button click. Notice that it only creates
 it if it doesn't exist.

 this.mangleTitle = ... ; //Insert after this line in execute()
 this.createText  = this.getAttribute(create,false);
 if(typeof(this.createText) === string) {
   try{ this.createText = JSON.parse(this.createText); }
   catch (e) { console.error(e); this.createText = false; }
   console.log(this.createText);
   if(this.createText){
 this.createText['title'] = this.mangleTitle;
 if(!this.wiki.tiddlerExists(this.mangleTitle))
   this.wiki.addTiddler(this.createText);
   }
 }

 And here is a tiddler that uses it. This tiddler creates a button that
 toggles the story river between centered and normal. Centered is default.

  \define createStateTiddler()
 { text: $(default)$ , tags: $:/tags/stylesheet }
 \end
 \define state-1-css()

 \end
 \define state-2-css()
 @media (min-width: 770px) { .story-river { margin: 0 auto; }
 .sidebar-header { left: 50%; right: 0; padding-left: 413px; } }
 \end
 $set name=default value=state-2-css 
 span title=Toggle width/sidebar
  $fieldmangler tiddler=$:/temp/toggle-centered
 create=createStateTiddler
 $reveal type=match state=$:/temp/toggle-centered
 text=state-1-css default=$(default)$
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-2-css  class=btn-invisible
 centered-toggle-1{{$:/_images/right-arrow-button}}/$button
 /$reveal$reveal type=match state=$:/temp/toggle-centered
 text=state-2-css
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-1-css class=btn-invisible
 centered-toggle-2{{$:/_images/left-arrow-button}}/$button
 /$reveal/$fieldmangler
 /span
 /$set

 If you don't have the corresponding images for the buttons, just remove
 the btn-invisible class from the buttons. I'm putting this out as a feature
 request (a hackability request?).

 I haven't changed the buttons yet, so that is how they were working
 before I did this. I had to click the button once to create the tiddler,
 and then a second time to finally see something happen. This way, whatever
 way I initialize it I see the effect on start up.

 Is this something that could be added to the core? Note that create, as
 I wrote it, must be valid JSON and the title gets overwritten if it is
 there. Enjoy!

 --Arlen

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Alright, how's this?

this.createText  = this.getAttribute(create,false);
// Process create param
if(this.createText) {
  var createTiddler =
$tw.wiki.deserializeTiddlers(application/x-tiddler,this.createText);
  createTiddler[0]['title'] = this.mangleTitle;
  if(!this.wiki.tiddlerExists(this.mangleTitle))
this.wiki.addTiddler(createTiddler[0]);
}




On Mon, Mar 24, 2014 at 10:26 AM, Arlen Beiler arlen...@gmail.com wrote:

 Hi Jeremy,
 Would the syntax use line breaks? Or were you thinking about all on one
 line? How do line breaks work with wikitext like that?

 --Arlen


 On Thu, Mar 20, 2014 at 1:16 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 Good stuff. My intention is to do something very similar but for the
 literal tiddler syntax to resemble a .tid file:

 title: myTitle
 tags: one two three
 text: This is the text

 I was primarily thinking about using the syntax with the new tiddler
 message, but it's a good idea to support it on the fieldmangler widget as
 well.

  Best wishes

 Jeremy





 On Thu, Mar 20, 2014 at 1:22 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi Everyone,
 Here is the result of my latest endeavor. This adds a create parameter
 to the fieldmangler widget which creates the tiddler specified in tiddler
 with the fields in create. This allows temp tiddlers to be initialized
 with state data without needing a button click. Notice that it only creates
 it if it doesn't exist.

 this.mangleTitle = ... ; //Insert after this line in execute()
 this.createText  = this.getAttribute(create,false);
 if(typeof(this.createText) === string) {
   try{ this.createText = JSON.parse(this.createText); }
   catch (e) { console.error(e); this.createText = false; }
   console.log(this.createText);
   if(this.createText){
 this.createText['title'] = this.mangleTitle;
 if(!this.wiki.tiddlerExists(this.mangleTitle))
   this.wiki.addTiddler(this.createText);
   }
 }

 And here is a tiddler that uses it. This tiddler creates a button that
 toggles the story river between centered and normal. Centered is default.

  \define createStateTiddler()
 { text: $(default)$ , tags: $:/tags/stylesheet }
 \end
 \define state-1-css()

 \end
 \define state-2-css()
 @media (min-width: 770px) { .story-river { margin: 0 auto; }
 .sidebar-header { left: 50%; right: 0; padding-left: 413px; } }
 \end
 $set name=default value=state-2-css 
 span title=Toggle width/sidebar
  $fieldmangler tiddler=$:/temp/toggle-centered
 create=createStateTiddler
 $reveal type=match state=$:/temp/toggle-centered
 text=state-1-css default=$(default)$
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-2-css  class=btn-invisible
 centered-toggle-1{{$:/_images/right-arrow-button}}/$button
 /$reveal$reveal type=match state=$:/temp/toggle-centered
 text=state-2-css
 $button message=tw-add-tag param=$:/tags/stylesheet
 set=$:/temp/toggle-centered setTo=state-1-css class=btn-invisible
 centered-toggle-2{{$:/_images/left-arrow-button}}/$button
 /$reveal/$fieldmangler
 /span
 /$set

 If you don't have the corresponding images for the buttons, just remove
 the btn-invisible class from the buttons. I'm putting this out as a feature
 request (a hackability request?).

 I haven't changed the buttons yet, so that is how they were working
 before I did this. I had to click the button once to create the tiddler,
 and then a second time to finally see something happen. This way, whatever
 way I initialize it I see the effect on start up.

 Is this something that could be added to the core? Note that create,
 as I wrote it, must be valid JSON and the title gets overwritten if it is
 there. Enjoy!

 --Arlen

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit

[twdev] Feature request for $:/core/modules/widgets/fieldmangler.js with code

[Arlen Beiler]

Hi Everyone,
Here is the result of my latest endeavor. This adds a create parameter to
the fieldmangler widget which creates the tiddler specified in tiddler
with the fields in create. This allows temp tiddlers to be initialized
with state data without needing a button click. Notice that it only creates
it if it doesn't exist.

this.mangleTitle = ... ; //Insert after this line in execute()
this.createText  = this.getAttribute(create,false);
if(typeof(this.createText) === string) {
  try{ this.createText = JSON.parse(this.createText); }
  catch (e) { console.error(e); this.createText = false; }
  console.log(this.createText);
  if(this.createText){
this.createText['title'] = this.mangleTitle;
if(!this.wiki.tiddlerExists(this.mangleTitle))
  this.wiki.addTiddler(this.createText);
  }
}

And here is a tiddler that uses it. This tiddler creates a button that
toggles the story river between centered and normal. Centered is default.

\define createStateTiddler()
{ text: $(default)$ , tags: $:/tags/stylesheet }
\end
\define state-1-css()

\end
\define state-2-css()
@media (min-width: 770px) { .story-river { margin: 0 auto; }
.sidebar-header { left: 50%; right: 0; padding-left: 413px; } }
\end
$set name=default value=state-2-css 
span title=Toggle width/sidebar
$fieldmangler tiddler=$:/temp/toggle-centered
create=createStateTiddler
$reveal type=match state=$:/temp/toggle-centered text=state-1-css
default=$(default)$
$button message=tw-add-tag param=$:/tags/stylesheet
set=$:/temp/toggle-centered setTo=state-2-css  class=btn-invisible
centered-toggle-1{{$:/_images/right-arrow-button}}/$button
/$reveal$reveal type=match state=$:/temp/toggle-centered
text=state-2-css
$button message=tw-add-tag param=$:/tags/stylesheet
set=$:/temp/toggle-centered setTo=state-1-css class=btn-invisible
centered-toggle-2{{$:/_images/left-arrow-button}}/$button
/$reveal/$fieldmangler
/span
/$set

If you don't have the corresponding images for the buttons, just remove the
btn-invisible class from the buttons. I'm putting this out as a feature
request (a hackability request?).

I haven't changed the buttons yet, so that is how they were working before
I did this. I had to click the button once to create the tiddler, and then
a second time to finally see something happen. This way, whatever way I
initialize it I see the effect on start up.

Is this something that could be added to the core? Note that create, as I
wrote it, must be valid JSON and the title gets overwritten if it is there.
Enjoy!

--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: [TWC][TW5]Import TiddlyWiki Classic parser

[Arlen Beiler]

I follow you. Alright, I'll see what happens.
--Arlen


On Thu, Mar 20, 2014 at 12:59 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

  Hi all, it seems like it should be easy to dump the classic parser into
 a plugin and make it available for TW5 classic tiddlers

 Indeed. I started TW5's development with a transliteration of the TWC
 parser. I then added the new TW5 parser alongside it, and then more than a
 year ago I removed the old TWC parser. Here's a snapshot that includes both
 parsers:


 https://github.com/Jermolene/TiddlyWiki5/blob/87749397c066d000edb8ff2dd2a5aceed715e435/core/modules/parsers/wikitextparser/wikitextparser.js


 https://github.com/Jermolene/TiddlyWiki5/blob/87749397c066d000edb8ff2dd2a5aceed715e435/core/modules/parsers/wikitextparser/rules/wikitextrules.js

 The main reason for removing the TWC parser was that it was a burden to
 keep it up to date while I was intensively refactoring the parsing engine.
 But I like the idea of having it as a plugin.

 But there are dangers: if we support TWC wikitext out of the box then
 there will be pressure to extend it to support some of the new features,
 and I really don't want to end up having to support two different wikitexts.

 Best wishes

 Jeremy






 On Wed, Mar 19, 2014 at 9:32 PM, Arlen Beiler arlen...@gmail.com wrote:

 Yes, I definitely don't think anyone should have to keep it going. I just
 remember that the TWC parser was relatively self-contained, I think, and it
 seemed it should be easy to add it for TWC tiddlers since it is already
 specified as plain text and the parser is determined by the content type.
 I'd say just grab the latest one and stick it in. Shouldn't take much of
 anything, should it?

 --Arlen


 On Wed, Mar 19, 2014 at 3:47 PM, PMario pmari...@gmail.com wrote:

 I think it should be possible, to have a convenient migration path from
 TWclassic to TW. TWclassic reached its limits, that why TW5 was created. I
 think it makes no sense to support 2 different types of TW markup.

 There has been a discussion, how to make the parser more flexible:
 https://groups.google.com/d/msg/tiddlywikidev/LcQbv5WVcRg/0dZN0qRDRDQJ
 which may be interesting.

 -m

 --
 You received this message because you are subscribed to the Google
 Groups TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] [TWC][TW5]Import TiddlyWiki Classic parser

[Arlen Beiler]

Hi all, it seems like it should be easy to dump the classic parser into a
plugin and make it available for TW5 classic tiddlers. It should be easy
for someone who knows how -- I'd have to go exploring in order to do it.
Just an idea, for what it's worth.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Re: [TWC][TW5]Import TiddlyWiki Classic parser

[Arlen Beiler]

Yes, I definitely don't think anyone should have to keep it going. I just
remember that the TWC parser was relatively self-contained, I think, and it
seemed it should be easy to add it for TWC tiddlers since it is already
specified as plain text and the parser is determined by the content type.
I'd say just grab the latest one and stick it in. Shouldn't take much of
anything, should it?

--Arlen


On Wed, Mar 19, 2014 at 3:47 PM, PMario pmari...@gmail.com wrote:

 I think it should be possible, to have a convenient migration path from
 TWclassic to TW. TWclassic reached its limits, that why TW5 was created. I
 think it makes no sense to support 2 different types of TW markup.

 There has been a discussion, how to make the parser more flexible:
 https://groups.google.com/d/msg/tiddlywikidev/LcQbv5WVcRg/0dZN0qRDRDQJ
 which may be interesting.

 -m

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: NewLine character in strings

[Arlen Beiler]

Ok, if state-2-css is only one line it works as expected.

\define state-2-css()
@media (min-width: 770px) { .story-river { margin: 0 auto; }
.sidebar-header { left: 50%; right: 0; padding-left: 413px; } }
\end

--Arlen


On Wed, Mar 19, 2014 at 5:16 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi everyone,
 Where does this newline character come from? I get an error when I try to
 parse a JSON string containing a string defined in a multiline macro. It's
 that character that appears after 770px) {.
 Thanks --Arlen

 '{ text: @media (min-width: 770px) {↵ .story-river { margin: 0 auto; }↵
 .sidebar-header { left: 50%; right: 0; padding-left: 413px; } ↵} , tags:
 $:/tags/stylesheet }'

 Comes from:

 \define createStateTiddler()
 { text: $(default)$ , tags: $:/tags/stylesheet }
 \end

 \define state-2-css()
 @media (min-width: 770px) {
  .story-river { margin: 0 auto; }
  .sidebar-header { left: 50%; right: 0; padding-left: 413px; }
 }
 \end
 $set name=default value=state-2-css 
 $fieldmangler tiddler=$:/temp/toggle-centered
 create=createStateTiddler
 ...

 In fieldmangler.js:execute()


 this.mangleTitle = ... ;
 this.createText  = this.getAttribute(create,false);
 if(typeof(this.createText) === string) {  try{ this.createText = 
 JSON.parse(this.createText); }  catch (e) { console.error(e); } //message: 
 Unexpected token ↵
 }



-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] NewLine character in strings

[Arlen Beiler]

Hi everyone,
Where does this newline character come from? I get an error when I try to
parse a JSON string containing a string defined in a multiline macro. It's
that character that appears after 770px) {.
Thanks --Arlen

'{ text: @media (min-width: 770px) {↵ .story-river { margin: 0 auto; }↵
.sidebar-header { left: 50%; right: 0; padding-left: 413px; } ↵} , tags:
$:/tags/stylesheet }'

Comes from:

\define createStateTiddler()
{ text: $(default)$ , tags: $:/tags/stylesheet }
\end

\define state-2-css()
@media (min-width: 770px) {
 .story-river { margin: 0 auto; }
 .sidebar-header { left: 50%; right: 0; padding-left: 413px; }
}
\end
$set name=default value=state-2-css 
$fieldmangler tiddler=$:/temp/toggle-centered
create=createStateTiddler
...

In fieldmangler.js:execute()


this.mangleTitle = ... ;
this.createText  = this.getAttribute(create,false);
if(typeof(this.createText) === string) {  try{ this.createText =
JSON.parse(this.createText); }  catch (e) { console.error(e); }
//message: Unexpected token ↵
}

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] SetWidget addition

[Arlen Beiler]

How do I check the plain text that is returned? Do you mean the tiddler
source text in the edit box?

--Arlen



On Fri, Feb 14, 2014 at 3:15 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 There's a much easier way to accomplish what you're trying to do. Using
 variables to store state is a red-herring; you should use tiddlers for
 state storage. Variables are attached to the render tree nodes; they are
 provided as a way of providing values that can vary at different points in
 the tree.

 One further oddity is the way that you are combing both displayable
 wikitext and a stylesheet in the same tiddler. That isn't recommended; the
 plain text output of the wikitext will be parsed as CSS which is probably
 not what you want.

 Here's a simpler alternative:

 $reveal state=$:/state/myTriState type=match text=one
 default=one$button set=$:/state/myTriState setTo=twoOne, click for
 Two/$button/$reveal
 $reveal state=$:/state/myTriState type=match text=two$button
 set=$:/state/myTriState setTo=threeTwo, click for
 Three/$button/$reveal
 $reveal state=$:/state/myTriState type=match text=three$button
 set=$:/state/myTriState setTo=oneThree, click for
 One/$button/$reveal

 Best wishes

 Jeremy



 On Fri, Feb 14, 2014 at 2:06 PM, Arlen Beiler arlen...@gmail.com wrote:

 In widgets/set.js I added an event listener and a handler. I copied the
 idea from the fieldmangler widget.

 var SetWidget = function(parseTreeNode,options) {
 this.initialise(parseTreeNode,options);
  this.addEventListeners([
 {type: tw-set-var, handler: handleSetVarEvent},
 ]);
 };
 SetWidget.prototype.handleSetVarEvent = function(event) {
 console.log([event,this]);
 var params = JSON.parse(event.param);
 if(params != undefined) {
 if(this.setName == params[0])
 this.setValue = params[1];
 } else {
 if(this.setName == currentTiddler)
 this.setValue = event.param;
 }
 this.setVariable(this.setName,this.setValue);
 this.refresh(event.tiddlerTitle)
 };

 And in a tiddler, I have this content. The variable seems to get updated
 according to the console.log output, but how do I make the tiddler refresh
 itself so that everything gets updated? Seems like in TW2 I would have used
 onclick or something like that. I don't know, I never tried a three state
 button on there. Thanks everyone.

 The tiddler $:/Arlen/sidebar3way defines which button is visible and sets
 the other things as well. The tiddler below has a stylesheet tag.

 \define getStyle()
 {{$:/Arlen/sidebar3way##$(state)$}}
 \end
 $set name=state value=normal
 @@float:right;
 span title=Toggle width/sidebar
 $button message=tw-set-var param='[state,wide]'
 class=btn-invisible
 sidebar-toggle-1{{$:/_images/right-arrow-button}}/$button
 $button message=tw-set-var param='[state,full]'
 class=btn-invisible
 sidebar-toggle-2{{$:/_images/right-arrow-button}}/$button
 $button message=tw-set-var param='[state,normal,refresh]'
 class=btn-invisible
 sidebar-toggle-3{{$:/_images/left-arrow-button}}/$button
 /span
 @@
 @@display:none;
 .sidebar-toggle-1,
 .sidebar-toggle-2,
 .sidebar-toggle-3 { display:none; }
 getStyle
 @@
 /$set

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/groups/opt_out.




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

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] $tw.wiki.tiddlers is not pluggable

[Arlen Beiler]

Hi Everyone,

How are you all today. I spent a lot of time the last two days figuring
out core/modules/wiki.js, and one thing I thought of that could possibly be
a great idea would be to use functions to access the list of tiddlers
instead of accessing them directly. This would allow us to put the tiddler
list itself behind an api or just about anything else without overriding a
bunch of core functionality.

Something like mapGetAllTiddlers, mapGetTiddler(title),
mapSetTiddler(title,tiddler), and mapDeleteTiddler(title). Of course, the
first two would have the biggest effect -- the last two are only used in
one wikimethod each I believe. For now they would just replace the property
calls that are there. These would be wikimethods and could probably be
added to boot.

If anyone wanted to write their own tiddler store, they wouldn't have
to override a whole bunch of methods just to change the way they access the
tiddlers object -- they would just make their own map methods to access the
list.

I did think of over-riding the addTiddler and deleteTiddler methods and
use a get accessor on tiddlers, but you won't hear about changes made to
the object unless you actively watch it and listen for tiddler changes. As
far as the override, it is more of an overwrite as the last one wins and
the rest disappear. There is no way to call a previous method. Of course,
now they use events, which was the biggest reason an override was needed in
TW2, but the event only has the tiddler title.

TiddlyWiki is inherently static, and I believe this is the biggest
reason. With TW on Node (which is what I use) the browser TW is a separate,
sovereign entity. This would allow real dependance on the server, which I
don't think should ever be built into the core, but seems to have great
potential in extensibility.

Here's an example. This goes right underneath the $tw.Wiki constructor in
boot.js

$tw.Wiki.prototype.mapGetTiddler(title) { return this.tiddlers[title]; };
$tw.Wiki.prototype.mapGetAllTiddlers() { return this.tiddlers; };
$tw.Wiki.prototype.mapPutTiddler(title,tiddler) { this.tiddlers[title] =
tiddler; };
$tw.Wiki.prototype.mapDeleteTiddler(title) { delete this.tiddlers[title]; };

So, that's my idea. What are your thoughts? I like it, and it is simple to
implement (I tried it), and seems to work fine. the map- prefix reflects on
the nature of the method. It is a map showing where to find the tiddler
list. :)

God bless you all and I look forward to hearing what you have to say.

--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: $tw.wiki.tiddlers is not pluggable

[Arlen Beiler]

Hi everyone,
Sorry for the way the subject line sounds, I forgot to edit it :D

Here is the corrected code. Seems to work well with everything changed over
on a test project I downloaded about 2 days ago. I didn't yet test to make
sure nothing is still calling it direct. That would cause problems. But so
far the only files this seems to affect are wiki.js and core.js. I know
there are a few cases where something uses var self = this, so I'm not sure
how those would work, but would probably need to be changed as well, or
something like that.

$tw.Wiki.prototype.mapGetTiddler = function(title)   { return
this.tiddlers[title]; };
$tw.Wiki.prototype.mapGetAllTiddlers  = function()  { return
this.tiddlers; };
$tw.Wiki.prototype.mapPutTiddler = function(title,tiddler) {
this.tiddlers[title] = tiddler; };
$tw.Wiki.prototype.mapDeleteTiddler   = function(title){ delete
this.tiddlers[title]; };

--Arlen


On Fri, Mar 14, 2014 at 12:52 PM, Arlen Beiler arlen...@gmail.com wrote:

 Hi Everyone,

 How are you all today. I spent a lot of time the last two days
 figuring out core/modules/wiki.js, and one thing I thought of that could
 possibly be a great idea would be to use functions to access the list of
 tiddlers instead of accessing them directly. This would allow us to put the
 tiddler list itself behind an api or just about anything else without
 overriding a bunch of core functionality.

 Something like mapGetAllTiddlers, mapGetTiddler(title),
 mapSetTiddler(title,tiddler), and mapDeleteTiddler(title). Of course, the
 first two would have the biggest effect -- the last two are only used in
 one wikimethod each I believe. For now they would just replace the property
 calls that are there. These would be wikimethods and could probably be
 added to boot.

 If anyone wanted to write their own tiddler store, they wouldn't have
 to override a whole bunch of methods just to change the way they access the
 tiddlers object -- they would just make their own map methods to access the
 list.

 I did think of over-riding the addTiddler and deleteTiddler methods
 and use a get accessor on tiddlers, but you won't hear about changes made
 to the object unless you actively watch it and listen for tiddler changes.
 As far as the override, it is more of an overwrite as the last one wins and
 the rest disappear. There is no way to call a previous method. Of course,
 now they use events, which was the biggest reason an override was needed in
 TW2, but the event only has the tiddler title.

 TiddlyWiki is inherently static, and I believe this is the biggest
 reason. With TW on Node (which is what I use) the browser TW is a separate,
 sovereign entity. This would allow real dependance on the server, which I
 don't think should ever be built into the core, but seems to have great
 potential in extensibility.

 Here's an example. This goes right underneath the $tw.Wiki constructor in
 boot.js

 $tw.Wiki.prototype.mapGetTiddler(title) { return this.tiddlers[title]; };
 $tw.Wiki.prototype.mapGetAllTiddlers() { return this.tiddlers; };
 $tw.Wiki.prototype.mapPutTiddler(title,tiddler) { this.tiddlers[title] =
 tiddler; };
 $tw.Wiki.prototype.mapDeleteTiddler(title) { delete this.tiddlers[title];
 };

 So, that's my idea. What are your thoughts? I like it, and it is simple to
 implement (I tried it), and seems to work fine. the map- prefix reflects on
 the nature of the method. It is a map showing where to find the tiddler
 list. :)

 God bless you all and I look forward to hearing what you have to say.

 --Arlen


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

[twdev] SetWidget addition

[Arlen Beiler]

In widgets/set.js I added an event listener and a handler. I copied the
idea from the fieldmangler widget.

var SetWidget = function(parseTreeNode,options) {
this.initialise(parseTreeNode,options);
 this.addEventListeners([
{type: tw-set-var, handler: handleSetVarEvent},
]);
};
SetWidget.prototype.handleSetVarEvent = function(event) {
console.log([event,this]);
var params = JSON.parse(event.param);
if(params != undefined) {
if(this.setName == params[0])
this.setValue = params[1];
} else {
if(this.setName == currentTiddler)
this.setValue = event.param;
}
this.setVariable(this.setName,this.setValue);
this.refresh(event.tiddlerTitle)
};

And in a tiddler, I have this content. The variable seems to get updated
according to the console.log output, but how do I make the tiddler refresh
itself so that everything gets updated? Seems like in TW2 I would have used
onclick or something like that. I don't know, I never tried a three state
button on there. Thanks everyone.

The tiddler $:/Arlen/sidebar3way defines which button is visible and sets
the other things as well. The tiddler below has a stylesheet tag.

\define getStyle()
{{$:/Arlen/sidebar3way##$(state)$}}
\end
$set name=state value=normal
@@float:right;
span title=Toggle width/sidebar
$button message=tw-set-var param='[state,wide]' class=btn-invisible
sidebar-toggle-1{{$:/_images/right-arrow-button}}/$button
$button message=tw-set-var param='[state,full]' class=btn-invisible
sidebar-toggle-2{{$:/_images/right-arrow-button}}/$button
$button message=tw-set-var param='[state,normal,refresh]'
class=btn-invisible
sidebar-toggle-3{{$:/_images/left-arrow-button}}/$button
/span
@@
@@display:none;
.sidebar-toggle-1,
.sidebar-toggle-2,
.sidebar-toggle-3 { display:none; }
getStyle
@@
/$set

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Re: Wiki paradigm vs Tiddler paradigm

[Arlen Beiler]

Hello Alberto, and everyone else.
I was sitting here reading, and almost had to laugh. I know exactly
what you mean Alberto. Originally I tried to find a way to separate my
tiddlywiki file into separate workspaces with separate files for different
stuff. Eventually I decided that was too complicated, especially since
Chrome couldn't find a CORS header in the file system. ;)
With TW5 and NodeJS I'm hoping to take another shot at it. I noticed
that there is a field called bag. I don't know what it's for yet, but I've
been thinking of a couple options for what you are talking about.

   - Use NodeJS for load and save. Should be able to restrict it to
   localhost.
   - Configure NodeJS to use TiddlyStores instead of folders and bring it
   down to just a few files.
   - Have separate namespaces, each of which would be stored in a different
   file. We already have a system namespace.
   - How about a way to open a tiddler store file which would load a UI
   file. This was what I was aiming for in TW2. Maybe not a tiddler store, but
   you know... It could be a second TW and would load the first one,
   overwriting itself, and then save the whole thing in itself.

I talk a lot about NodeJS, and that's because that seems to be the best way
I can find to do what I want. I'm sure this could be done other ways too.

I like the idea of have multiple wikis and having a plugin wiki. Basically
it's the whole idea of separating design and content. The look would be the
same, but the info would be different. Still, different namespaces with
different interfaces would work too. What about subfolders on the NodeJS
server that would have the Namespace files and then all namespaces would
share System files. Seems like there's an idea somewhere that should work.
Your right, the beauty of tiddlywiki is tiddlers. The thorn of tiddlywiki
is IO. But, hey, roses have thorns, so... :)

God bless you all, Goodnight.
--Arlen


On Tue, Feb 4, 2014 at 6:58 AM, Alberto Molina alberton...@gmail.comwrote:

 Hi Alberto. Chances are you have repeatedly had to go get multiple copies
 of the same plugins to install on your TW's.


 Yes. What I have been doing is creating and updating an empty but heavily
 customized TW, and using it as a template for my real notebooks. Whenever I
 want a new TW I make a copy of the empty one and start writing.

 It is true that when I need/want to update a plugin or something like
 that, I have to repeat the same operation for all the TW's I want to
 update. And you're right, it's a little bit annoying.


 Second, and more importantly, what if tiddlers on your studies overlap
 both the thesis notebook and your lessons (and more)? Should you keep
 multiple copies of the same information? Having to update each instance
 every time? And I'm guessing that as its now, when you're taking notes in
 your lessons and suddenly realize that you will wnat it in the thesis TW,
 you must add a note Remember to put this into thesis instead of just
 having it there automatically with the tiddlyweb approach.


 Actually, my TW's do not often (quite never) overlap.


 Why, actually, is the one single file concept a key feature for you in
 this? Is it because it is easier to email one file than one directory?


 Not because it is easier to email, but because it is easier to manage,
 even psychologically, I mean: cooking recipes and philosophy of science are
 such unrelated things that I prefer to have them physically separated.
 For the same reason I prefer to have different paper notebooks for
 different topics instead of one single huge notebook.

 And the one single file concept is also about beeing offline. I can use
 it wherever I want, regardless of internet access.

 Alberto

  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Log Register

[Arlen Beiler]

Hello Everyone,
I came across this in the TiddlyWiki5 code.

// Temporarily disable logging to help the wood vs. trees situation; we
need better filtering of log messages $tw.utils.log.apply(null,args);

What if we would at least have a logging register of some sort that would
allow us to enable or disable logs at will. Maybe enabled by a developer
mode of some sort. Which would be enabled, perhaps, by a tiddler with a
certain tag, or a SystemSetting (whatever that is called now).

Just an idea.

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Serve TiddlyWiki from one file

[Arlen Beiler]

Hello Everyone, how are you all this evening.
I have a headache, but it seems to me like there should be a way to run
tiddlywiki on a server using just a couple files including a complete HTML
file. Two options come to my mind. People would be able to download three
or four files (NodeJS.exe, empty.html, serve.js). The first is to run it
using standard save and load file commands (good for localhost) (Could have
problems, at your own risk), the second is the ability to unpack empty.html
into a folder, or something like that. Just a thought.
I guess it is a thing of environment, a browser uses HTML, NodeJS uses
JS files. Well, I don't know how this would work, but I'm almost shooting
it down as I think it up, except for the localhost part. That could be a
useful addition.
Anyway, have a good evening. Just an idea.
--Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Question about TW5 tag button list

[Arlen Beiler]

How do I make a button that shows a list of tiddlers with a certain tag. In
TW2 it was tag Journal '' '' -title. Thanks. Been forgetting just
about everything trying to research this in between, so I thought I'd just
ask. I think I was getting there, but couldn't think about my other work.
Thanks again. --Arlen

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] TiddlyWiki5 on Android?

[Arlen Beiler]

Using TiddlyWiki5 which I just downloaded in AndTidWiki, I can edit fine,
but when I try to save it, I get an Internal Javascript Error. Uncaught
TypeError: Cannot call method 'getItem' of null.


On Mon, Jul 29, 2013 at 4:39 AM, Yakov yakov.litvin.publi...@gmail.comwrote:

 Hi Leo,

 by the way, have you tried AndTidWiki? As for now, I only use TiddlyWiki
 Classic on Android, so don't know if TW5 works with it. As a side note:
 with AndTidWiki, I only have to add ToggleLeft/RightSidebar [1], add a
 line-menu on top by changing PageTemplate and a few CSS adjustments, while
 FireFox needs some more work on styles (in fact, I need to create a plugin
 which will apply different styles depending on what browser opened TW).

 Best regards,
 Yakov.

 [1] http://tiddlytools.com/#ToggleRightSidebar%20ToggleLeftSidebar

 вторник, 16 июля 2013 г., 8:54:26 UTC+4 пользователь Leo Staley написал:

 Thank you Eric! I didn't know how to do that from my Android. Firefox
 didn't install it when I clicked on it like I thought it should have.

 After downloading it with another browser (because firefox didn't let me
 save link on long-press) and opening the file using firefox, I was able
 to install it.

 Sadly though, no save button appears under the tools menu. The button
 at the top, to download a copy of the page worked once, but i'm having
 trouble doing it again.

 Additionally, when i create a new tiddler, I first have to delete the
 existing text in both the title and the main text area, which takes some
 time with an android keyboard.

 Eric, How compatible are most of the items on TiddlyTools with Tiddly5?
 Is development still continuing with the current edition of Tiddlywiki, and
 if so, in what Capacity? Forgive me for being such a noob.

 On Monday, July 15, 2013 9:15:47 PM UTC-7, Eric Shulman wrote:



 On Monday, July 15, 2013 9:13:16 PM UTC-7, Leo Staley wrote:

 More significantly, There was no way to save any changes I made. Took
 me a while to realize that.


 As Jeremy noted in his previous post:
... install TiddlyFox to save changes locally on the device (
 https://github.com/**TiddlyWiki/TiddlyFox/raw/**master/tiddlyfox.xpihttps://github.com/TiddlyWiki/TiddlyFox/raw/master/tiddlyfox.xpi
 ).

 enjoy,
 -e
 Eric Shulman
 TiddlyTools / ELS Design Studios

 HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY TIP JAR...

 http://www.TiddlyTools.com/#**Donationshttp://www.TiddlyTools.com/#Donations

 Professional TiddlyWiki Consulting Services...
 Analysis, Design, and Custom Solutions:

 http://www.TiddlyTools.com/#**Contacthttp://www.TiddlyTools.com/#Contact

  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Re: Problem upgrading - Chrome requires permissions but tiddly wiki gets overwritten

[Arlen Beiler]

It probably would, import usually works for me now days. I ended up writing
a little program in c# to just take the content from the old copy, paste it
in to a new empty tiddlywiki, and then save it as a new file. Worked fine
for me. I have like 10 tiddlywikis.

On Mon, Mar 25, 2013 at 10:41 AM, Tobias Beer beertob...@gmail.com wrote:

 Hi Arlen,

 rather than using the upgrade wizard in the backstage area, does importing
 tiddlers into the new version fail as well?

 Cheers, Tobias.

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Re: Problem upgrading - Chrome requires permissions but tiddly wiki gets overwritten

[Arlen Beiler]

Sure, here it is. I did it in VS 2010 targeting .NET 4.0. Not sure whether
Client profile or not.

http://pastebin.com/f31PzRE8

On Mon, Mar 25, 2013 at 12:06 PM, Tobias Beer beertob...@gmail.com wrote:

 Hi Arlen,

 Would you mind showing the (source of) that little program of yours?

 Cheers, Tobias.

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Re: Problem upgrading - Chrome requires permissions but tiddly wiki gets overwritten

[Arlen Beiler]

Oh, and the license is Permanent Public Domain.

On Mon, Mar 25, 2013 at 4:01 PM, Arlen Beiler arlen...@gmail.com wrote:

 Sure, here it is. I did it in VS 2010 targeting .NET 4.0. Not sure whether
 Client profile or not.

 http://pastebin.com/f31PzRE8

 On Mon, Mar 25, 2013 at 12:06 PM, Tobias Beer beertob...@gmail.comwrote:

 Hi Arlen,

 Would you mind showing the (source of) that little program of yours?

 Cheers, Tobias.

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Feature Addition for customFormat formatter

[Arlen Beiler]

Yesterday I finally got down to it and made a few additions to the
customFormat formatter, specifically the class ({{) case.

   - Very often I will want to have a div with a class and an ID, and the
   only way I know to do it by default is to use the HTML tag, which means I
   can't use markup.
   - I changed the lookahead regex in the {{ select case to recognize
   periods and pound signs as well. Before it only recognized spaces and
   letters.
   - Before (I just now discovered) multiple classes could be included by
   adding spaces. I don't know if that takes away some of the need for this as
   core functionality. This is also retained as default.
   - The default behaviour is retained, and since my code only changes the
   handler, not the match regex, it shouldn't change what markup gets snagged.
   - Currently if periods or pound signs are included the result looks like
   this:  .hi.there{hi too}}} I don't think that is considered correct
   functionality, but rather a syntax error.
   - The one change to the default behaviour is the addition of a null
   (HTML: no '=) id attribute in Chrome. I haven't checked Firefox. I don't
   know if this matters or not.
   - Once I've thought about it some more, I'm not sure if this is even
   needed since you can include more than one class, which as I said I just
   discovered. But, oh well, here it is in case anyone wants it.

So, without further ado, here is the code -- as a plugin.
--Arlen

for (var i = 0; i  config.formatters.length; i++){
if(config.formatters[i].name == customFormat){ //look for the
customFormat formatter.
config.formatters[i].handler = function(w)
{
switch(w.matchText) {
case @@:
var e = createTiddlyElement(w.output,span);
var styles = config.formatterHelpers.inlineCssHelper(w);
if(styles.length == 0)
e.className = marked;
else
config.formatterHelpers.applyCssHelper(e,styles);
w.subWikifyTerm(e,/(@@)/mg);
break;
case {{:
var lookaheadRegExp =
/\{\{[\s]*([#\.\w]+[\s\w\.#]*)[\s]*\{(\n?)/mg; //changed this to
include . and #
lookaheadRegExp.lastIndex = w.matchStart;
var lookaheadMatch = lookaheadRegExp.exec(w.source);
if(lookaheadMatch) {
w.nextMatch = lookaheadRegExp.lastIndex;
var lam = String(lookaheadMatch[1]);
var cl = ;
var id = ;
if(lam.indexOf('.') != -1 || lam.indexOf('#') != -1){
//lam = lam.replace(/ /g, );
var i = lam.length;
var cur = ;
while (i--) {
if (lam[i] == '.'  cur.length  0) {
cl = cl +   + cur
cur = ;
} else if (lam[i] == '#'  cur.length  0) {
id = id +   + cur;
cur = ;
} else if ((lam[i] == '#' || lam[i] == '.') 
cur.length == 0) {
continue;
} else cur = lam[i] +  cur;
}
if(id ==   cl == ) cl = lam; //this shouldn't get hit
} else cl = lam;
//the trim removes extra spaces from the beginning and end
e = createTiddlyElement(w.output,lookaheadMatch[2] == \n
? div : span,id.trim(),cl.trim());
w.subWikifyTerm(e,/(\}\}\})/mg);
}
break;
}
}
}
}

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Problem upgrading - Chrome requires permissions but tiddly wiki gets overwritten

[Arlen Beiler]

I have a problem when trying to upgrade from 2.6.5. It upgrades, and loads
a new tiddler and everything, but when it tries to import the content or
something, the chrome requires permission to access the tiddlysaver.
Because of the alert box, I can't give it permission, and when I click ok,
it reloads the page or does something, and my whole tiddler is gone. In
case you're wondering, I do have a current backup, thankfully :) In
Firefox, it just says loading core code forever.

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Re: Problem upgrading - Chrome requires permissions but tiddly wiki gets overwritten

[Arlen Beiler]

Ok, Firefox says [14:30:50.589] TypeError:
window.netscape.security.PrivilegeManager is undefined @
file:///C:/Users/Arlen/Desktop/TiddlyWikis/AI.html:12220

How can I work around this? 2.7.1 has the same problem. Is there a way to
get it to wait for the applet to become available? Or is that not the
problem. Oh, wait, I know. It says it can't save it (regular error
message), and then it says it is going to reload it. There should be a way
to say No, don't reload. Hopefully this email is more sane then the last
one. I hope it didn't rub off on anyone. My apologies :D

On Thu, Mar 21, 2013 at 12:03 PM, Arlen Beiler arlen...@gmail.com wrote:

 I have a problem when trying to upgrade from 2.6.5. It upgrades, and loads
 a new tiddler and everything, but when it tries to import the content or
 something, the chrome requires permission to access the tiddlysaver.
 Because of the alert box, I can't give it permission, and when I click ok,
 it reloads the page or does something, and my whole tiddler is gone. In
 case you're wondering, I do have a current backup, thankfully :) In
 Firefox, it just says loading core code forever.

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Re: Problem upgrading - Chrome requires permissions but tiddly wiki gets overwritten

[Arlen Beiler]

The pre core backup file gets saved fine, then when it reloads it to load
the data from the backup file, it no longer has permission. You can't just
tell it to run always, because this doesn't usually take. Anyway, it
reloads, and then doesn't load anything from the backup file (which does
exist). Next it gives me the standard error message that always comes up
when I haven't given permission. After that it says that the upgrade to
2.7.1 is complete, click OK to reload the newly updated tiddlywiki. Even
before I click OK, I can see that it hasn't actually upgraded it from the
backup. This is in 2.6.5 and 2.7.1.

I did get them all updated, first using firefox, and then manually for 4
that didn't work in firefox. Some kind of invalid uri/url issue. I'm not
exactly sure about it though, and I think I am going to copy them over from
my manuel backup and do them all manually, just to be safe. I noticed that
when I opened a tiddlywiki backup, the SystemSettings tiddler had the
forward slash in my backup folder path changed to the html equivelant. I
don't know if this matters or not.

On Thu, Mar 21, 2013 at 4:55 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 OK, that's useful. What is the exact text of the alert(s) that are
 displayed?

 Cheers

 Jeremy

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


 On 21 Mar 2013, at 20:51, Arlen Beiler arlen...@gmail.com wrote:

 Yes, you are correct. Yes, it does that with an empty tiddlywiki file from
 tiddlywiki.com. I am using the latest java plugin, and as it does it with
 the empty file, that is all. Thanks in advance.

 On Thu, Mar 21, 2013 at 4:48 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:

 Hi Arlen

 Very happy to help. If I understand correctly, the problem is that Chrome
 is asking you for permission to run the TiddlySaver applet via a yellow bar
 at the top of the window while simultaneously displaying an alert that
 prevents you from clicking on the yellow bar. Is that right? Can you give
 more details of the plugins you are using, and whether you can save with a
 vanilla TiddlyWiki freshly downloaded from http://tiddlywiki.com?

 Cheers

 Jeremy



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


 On 21 Mar 2013, at 18:47, Arlen Beiler arlen...@gmail.com wrote:

 Ok, Firefox says [14:30:50.589] TypeError:
 window.netscape.security.PrivilegeManager is undefined @
 file:///C:/Users/Arlen/Desktop/TiddlyWikis/AI.html:12220

 How can I work around this? 2.7.1 has the same problem. Is there a way to
 get it to wait for the applet to become available? Or is that not the
 problem. Oh, wait, I know. It says it can't save it (regular error
 message), and then it says it is going to reload it. There should be a way
 to say No, don't reload. Hopefully this email is more sane then the last
 one. I hope it didn't rub off on anyone. My apologies :D

 On Thu, Mar 21, 2013 at 12:03 PM, Arlen Beiler arlen...@gmail.comwrote:

 I have a problem when trying to upgrade from 2.6.5. It upgrades, and
 loads a new tiddler and everything, but when it tries to import the content
 or something, the chrome requires permission to access the tiddlysaver.
 Because of the alert box, I can't give it permission, and when I click ok,
 it reloads the page or does something, and my whole tiddler is gone. In
 case you're wondering, I do have a current backup, thankfully :) In
 Firefox, it just says loading core code forever.


  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.



  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.




  --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to tiddlywikidev+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.



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

Re: [twdev] Re: Event on tiddler open/close

[Arlen Beiler]

First of all, I have been sleeping over it, as I asked about quitting
time. Second, is there anyway to concatenate a second function onto a
variable? that would be useful.

On Wed, Feb 8, 2012 at 6:57 AM, colmjude colmj...@gmail.com wrote:
 Just wondering how you are getting on with this and how you are
 tackling it?

 Seen as TW comes with jQuery integrated I'd probably use the observer
 pattern[1] and something like the trigger[2] method to fire custom
 events such as openTiddler and closeTiddler.

 Anyway just curious to see how you decide to do it.

 Colm

 [1] - 
 http://addyosmani.com/resources/essentialjsdesignpatterns/book/#observerpatternjavascript
 [2] - http://api.jquery.com/trigger/

 On Feb 8, 1:03 am, Eric Shulman elsdes...@gmail.com wrote:
 On Feb 7, 3:47 pm, Arlen Beiler arlen...@gmail.com wrote:

  Is there anyway to detect when a tiddler is opened or closed? I need
  it to update a list of opened tiddlers. I checked the Story section,
  but I couldn't find any events. Thanks

 Here's the two TWCore functions that you will need to hijack:

    story.prototype.displayTiddler(place,title)
    story.prototype.closeTiddler(title)

 enjoy,
 -e

 --
 You received this message because you are subscribed to the Google Groups 
 TiddlyWikiDev group.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 To unsubscribe from this group, send email to 
 tiddlywikidev+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/tiddlywikidev?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

[twdev] Event on tiddler open/close

[Arlen Beiler]

Is there anyway to detect when a tiddler is opened or closed? I need
it to update a list of opened tiddlers. I checked the Story section,
but I couldn't find any events. Thanks

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

[twdev] how to use latest JQuery

[Arlen Beiler]

Ok, not sure if dev is the right mailing list, but how can I use the latest
JQuery in Tiddlywiki without editing the source code?

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

Re: [twdev] Can't import using Google Chrome

[Arlen Beiler]

Upgrade doesn't work for me, it just says it has problems with the core
code. Import works in Firefox, but never in Chrome (gives a netscape not
defined error). Of course, saving stuff is never a problem. As for
workarounds, the most obvious one I can think of would be to open stuff
through the Java applet, if that is possible. But what about Google Gears?
Has anyone checked into it?

On Sat, Sep 24, 2011 at 5:27 PM, RunningUtes runningu...@gmail.com wrote:

 I have noticed that many of the backstage tools don't seem to work
 well using Google Chrome. Specifically import, tweak and upgrade.

 I am using TiddlyWiki base v2.6.4. Google Chrome v15.0.874.24 beta-m.

 Backstage tools seem to work on Firefox v3.6.16.

 Any workarounds?
 ~Michael

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 To unsubscribe from this group, send email to
 tiddlywikidev+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/tiddlywikidev?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

Re: [twdev] Date.convertFromYYYYMMDDHHMM() wrong by a day!

[Arlen Beiler]

It is assuming the time you are giving it is GMT, so subtract 6 hours from
the starting midnight of March 15 gives you March 14, 6:00. I didn't check
the code, but this is what it appears to be doing.

On Fri, Sep 23, 2011 at 11:23 AM, JMT jonathant...@yahoo.ca wrote:

 There must be a simply answer to this but I'm stumped.
 Date.convertFromMMDDHHMM() consistently returns the wrong date to
 me, off by one day. So for example in this script

 script label=Change date format
 var d = 20110315
 d = Date.convertFromMMDDHHMM(d)
 alert(d)
 /script

 the alert says Mon Mar 14 2011 18:00:00 GMT-0600 (Mountain Daylight
 Time), while it should be (I think) March 15.

 I'm trying to get this sorted out so that I can add a custom date
 field to my tiddlers and have the correct date displayed when I view
 the tiddler.

 Thanks in advance to you tiddlywiki gurus!

 --
 You received this message because you are subscribed to the Google Groups
 TiddlyWikiDev group.
 To post to this group, send email to tiddlywikidev@googlegroups.com.
 To unsubscribe from this group, send email to
 tiddlywikidev+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/tiddlywikidev?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWikiDev group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.