Hi Felix,
Did you have a look at:
https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins/tiddlywiki/codemirror/files/tiddlywiki.files
IMO it would make your build.sh obsolete, since it is OS specific and can't
be used from windows.
-m
--
You received this message because you are
Hi Mario,
I looked at codemirror/files/tiddlywiki.files
https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FJermolene%2FTiddlyWiki5%2Fblob%2Fmaster%2Fplugins%2Ftiddlywiki%2Fcodemirror%2Ffiles%2Ftiddlywiki.filessa=Dsntz=1usg=AFQjCNEKLSPVHQhJsSv2gD0HDbZuxlHL7g
but could you please be more
Just a remark: For the taskgraph plugin I use a node.js taskrunner called
gulp to compile the plugin (using a gulpfile.js). Here it makes absolute
sense to use an os independent approach.
--
You received this message because you are subscribed to the Google Groups
TiddlyWikiDev group.
To
Hello Felix,
In which scenario are you getting this problem? node or standalone? if you
only tested on node, check then with an sntandalone wiki. This kind of
errors can be because the library only works on the browser, and not in the
node. The higlight library suffers the same problem. I
Turns out the library exports itself and not a variable.
Hi Felix, I'm not yet familiar with *exports*, do mind explaining in two
sentences what that means (is vs. supposed to)?
Best wishes, Tobias.
--
You received this message because you are subscribed to the Google Groups
Hi Danielo,
Thank you for your help!
This was also my first thought. Then I saw that the vis.js designers have a
switch-case implemented that decides how to export the object based on
different scenarios.
function webpackUniversalModuleDefinition(root, factory) {
if(typeof exports ===
Hi Tobias,
exports are used in a modular javascript-system to make pieces of code
publicly usable by other js-modules. Otherwise they are not visible.
Javascript itself does not know this concept as everything is stored in one
file. but with node.js it is possible and tw also uses this to
However. I already solved the problem (see a post above)
--
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
Looking at tiddlywiki.com I am finding plenty developer related
information, especially concerning node.js, but also message
specifications, etc which really are not basic user material, imho.
Example: no user will be able to take something practical from
FieldManglerWidget
Hi Tobias
Looking at tiddlywiki.com I am finding plenty developer related
information, especially concerning node.js, but also message
specifications, etc which really are not basic user material, imho.
Example: no user will be able to take something practical from
FieldManglerWidget
Hi Jeremy,
Thanks for the the indepth reply.
Being able to easily track and manage changes is essential, indeed. As you
know, I haven't even tried to commit much, but I'll do some more warm-up
exercises and I hope that will get things started.
I'm afraid the /dev site is not at all finished.
Hi Tobias
I have a mild worry that some features of tw5 require power-user, if not
developer-level knowledge. This shifts the focus away from providing
solutions towards solution design, which of course is an honorable exercise
but might be quite over the top for an everyday wiki user who is
Hi,
Say I have a tiddler T1 with a widget A that uses the transcluded content
of a tiddler T2 as its body.
T1 looks like
$A{T2}/$A
T2 looks e.g. like this
blabla
$list filter=[tag[hi]]/$list
$button message=somemessage param=helloclickbutton/$button
bla
Widget A is now the parent of the
Hi Felix
I can only reply briefly now, but I think the transclude widget is pretty
close to what you're after. You could either take the transclude widget as
a starting point and create a custom variant, or you may be able to
generate the transclude widget as the output of your widget (the
Tobias:
If it doesn't slow down your git warm-up, would you mind making some
rank beginner notes? I've always benefited from the way you explain
things and if that happens again, it will make it much easier for me to
chip in some notes.
Regards, Hans
On Monday, November 17, 2014 6:03:09
Jeremy, is the fake DOM used in tw5 your own implementation or is it a
library like virtual-dom https://github.com/Matt-Esch/virtual-dom? Was
the latter available when you started? If you rolled your own, I'm curious
if you've tested its performance against virtual-dom. This blog post, Blazing
see:
https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/utils/fakedom.js
The first commit of virtual-dom seems to be in January this year. ... TW is
in the works a little bit longer.
mario
--
You received this message because you are subscribed to the Google Groups
17 matches
Mail list logo
