Hi Danielo
When I started with tiddlyDrive project it was very clear on my mind that
I did not want to create a syncAdaptor. The main reason is because the
syncadaptors are focused on server side, so unless the server is running on
your own machine you end up with nothing.
That's not quite
Hi Danielo,
The way I would envision this is rather to have the cloud storage for
content tiddlers... as the main host and then have some form of core /
skelleton / app TiddlyWiki (like Taskgraph) into which you load those
tiddlers via some ServerSync Plugin.
I don't understand
Hello Tobías
I was separating the TiddlyWiki as a setup of plugins, themes, languages,
etc... from the actual content it is to contain, eventually, which at some
point better be something else than just TiddlyWiki... e.g. my tasks, my
notes, my project, my references, my bookmarks...
You are giving me opposite messages. First you said that the sync thing
should not include configurations or plugins, I agree with that, but after
that you wrote that it is a pain to install all the necessary plugins on
every TW. Which setup would you prefer? I prefer the first one, and
Hello Felix,
When I started with tiddlyDrive project it was very clear on my mind that I
did not want to create a syncAdaptor. The main reason is because the
syncadaptors are focused on server side, so unless the server is running on
your own machine you end up with nothing. I wanted to
Hello Danielo,
When I started with tiddlyDrive project it was very clear on my mind that I
did not want to create a syncAdaptor. The main reason is because the
syncadaptors are focused on server side, so unless the server is running on
your own machine you end up with nothing. I wanted to
Hello Felix,
Let me know what do you think about this:
https://github.com/danielo515/TiddlyDrive/issues/5
I think it is good that you try to be clear about what your plugin should
provide. Better one tool for one thing than a bloated multitool.
You are right here. Also I want to provide
Hi Danielo,
The way I would envision this is rather to have the cloud storage for
content tiddlers... as the main host and then have some form of core /
skelleton / app TiddlyWiki (like Taskgraph) into which you load those
tiddlers via some ServerSync Plugin.
To go one step further, I'd
El lunes, 1 de diciembre de 2014 13:49:56 UTC+1, Tobias Beer escribió:
Hi Danielo,
The way I would envision this is rather to have the cloud storage for
content tiddlers... as the main host and then have some form of core /
skelleton / app TiddlyWiki (like Taskgraph) into which you load
The problem with a hidden widget is that it cannot retrieve the current
tiddlers title.
Why? Most of the widgets does this.
So it would be better to create a plugin that checks during refresh() if
$:/StoryList is in changedTiddlers and then checks which tiddlers where
opened and
hola
The problem with a hidden widget is that it cannot retrieve the current
tiddlers title.
Why? Most of the widgets does this.
Hmm, I don't think so. You can only do this by passing currentTiddler
as an argument to the widget and reading that argument later with
getAttribute(). But
Hello Felix
Thank you for your example, but I don't know to which of my questions are
trying to answer. I have a startup module already implemented so I know how to
implement them. My question was focused on what can they do DURING the startup
process. I don't want to react to events (well, I
Hola
As part of tiddlydrive I want the plugin to query the server for available
tiddlers on startup. The idea is to give the server a list of the already
available tiddlers on the wiki and the server will reply back with a list
of those tiddlers that are on the server but not on the wiki.
Hello Felix
Yes you helped me a lot with your latest comments. I did not though about the
fact that I'm using callbacks with the ajax calls. Thank you for pointing it
out. The startup graph at tiddlywiky.com/dev helped me a lot for know what I
can do. The startup modules are executed after the
Hi Danielo
Thank you also for the example you provided me.
Nice, you're welcome.
If you have any other idea or suggestions I'm sure it will be very
helpful.
Regards.
Indeed I have some ideas (no need to implement them but maybe worth a
thought)
* maybe you could save the
* maybe you could save the timestamp when the wiki was loaded and have a
global upload button that saves all tiddlers that have changed since that
time.
Or you could also listen to tiddler changes and create list of tiddler
which have changed and not been uploaded yet..
--
You
Hello Felix
I really like your ideas. I also though about starting the ajax automatically
when the tiddler is displayed, but I was not sure on how to implement it. A
hidden widget maybe can be a solution. I don't understand why do you consider
better getting via DOM selection. Also I think
Sorry, in the second paragraph I wrote your second idea and I wanted to refer
to the first one. The upload button for upload all the unsaved tiddlers at
once. I really like it because it's possible to implement it right now without
any extra server functionality.
--
You received this message
Hi Danielo,
I also though about starting the ajax automatically when the tiddler is
displayed, but I was not sure on how to implement it. A hidden widget maybe
can be a solution. I don't understand why do you consider better getting
via DOM selection.
The problem with a hidden widget is
19 matches
Mail list logo
