Hello Jeremy,
I really appreciate all of these new features and will give this a
proper test within the next few days.
Fun fact: I don't know how you knew, but the static file server route
uses the same path that my current main wiki also uses to serve static
files, meaning all links/_canoni
Dear Jeremy,
I also really welcome those changes and currently I mostly use the
server with a few routes that I added (serving attachments) to it
myself. I'll keep this short, but I definitely like the changes made
already and I look forward to having it be in the next version.
Here however
Dear Jeremy,
I would very much like for a such feature to be added to the code. The
amount of times where I have created a new tiddler and didn't have an
idea of how its going to be tagged and sorted from the start is pretty
large and it always made me slightly sad that they just end up in the
Hi Josiah,
from what I can tell, in certain browsers, the use of the tag
disallows the javascript contexts of both sites to communicate via
messages. This would be the desired behaviour when embedding things into
your tiddlywiki, as where it is allowed are also allowed to
inject javascript
Hi Joe,
this is most definitely possible and something I think most people in
the community already use. The way I do it is to put these "external"
files into a "files/" directory in the node server directory and add a
tiddler with the "_canonical_uri" field set to the relative path to the
fi
Hi Simon,
that is almost the right place yes, if you have a look at
|core/modules/startup/startup.js| [1], you will see that it initializes
it without the rootElement being given anyway. The next problem is that
all widgets regardless of the window they are rendered in will use
|$tw.popup.tri
Hi Simon,
unfortunately this is a shortcoming of the current PopupMechanism in
TiddlyWiki and will require changes to the core. The only way to open
and close the popup seems to be with a button.
If you happen to know javascript you could in theory write a
plugin/widget to fix this by adding
That's pretty cool.
I imagine if you're running your TW in a node instance or on a server,
all you'd need to do would be to modify '$:/core/save/empty' to a custom
configuration and have that load in on the sidebar and you'd basically
be done. I also remember writing a plugin at some point so
Hi RunningUtes,
as the person who originally documented this feature, I had another look
at the code and I believe this is a bug, since in the code it seems to
be supposed to work that way, but on line 37 of
|$:/core/modules/editor/operations/text/prefix-lines.js|, it seems to
end up comparin
Hi Mat,
you're not quite right. Take a look here:
http://tiddlywiki.com/dev/#Timeline%20of%20the%20startup%20Process
When TW starts up, it at some point loads all the tiddlers it can find
into whats called the tiddler store in memory. Now those also include
the plugin tiddlers, e.g. '$:/cor
Hey Mat,
I must admit, I did have to read up on how shadow tiddlers are actually
treated within TW, but here is my take on your statements:
- Shadow tiddlers exist separately from normal tiddlers and are
therefore effectively marked as "originating from a plugin"
- When you click on a title
Hi Mat,
when it comes to things like this, it is important to be aware that the
"good solution with TW in a very short time" is probably a bad idea in a
professional setting. When it comes to sensitive and important data, you
practically almost always want an established and tested (and secure
Hi Mat,
all of the Drag&Drop features in TW are implemented using said (HTML5)
API. Therefore there is a lot of drag&drop you can do and TW will do the
right thing. (Think of tiddlers being imported and such.)
Could you make a gallery with widgets and macros ? Well yes and no, such
a gallery w
Am 13.07.2015 um 19:40 schrieb Jeremy Ruston:
Some more detail would be handy. At the moment the core only requires
that the reveal widget and the button widget are within the same
relative coordinate system.
I remember this issue coming up in the past but I couldn't find the
relevant GitHub
Am 13.07.2015 um 16:55 schrieb Henry Padilla:
OK, it looks like the position is a thing.
If I get the button out of the it will popup where it's
supposed to. if not, even if it's static text, it will show at the top
of the tiddler.
The $reveal widget can be in the , but the $button cannot.
15 matches
Mail list logo
