Hi Jean-Charles
Apologies for the late reply.
> Data is mostly in databases, so my intend was to throw a web service in
front of my data, and have a custom tiddlywebadaptor-like js to deal with
it.
There is no need to push data "back" to the source at first, but it may be
a future option (for doc
I'd consider with an initial plan of just exporting the user/team data into
tiddler files each night. You'd get a browsable user directory -- minimal
viable product, startup people would say -- and no need to write any custom
adaptors. Once you see people using it, you can work out if it's worth
Hi Jeremy,
Thanks for your feedback,
> Where's the external data coming from, and in what format? Do you want to
sync changes to it back to the external data source?
Data is mostly in databases, so my intend was to throw a web service in
front of my data, and have a custom tiddlywebadaptor-lik
Hi Jean-Charles
Running ~7,000 tiddlers should be fine. Some of the sidebar tab lists will
be slow to render, so you might want to customise them.
> - if yes, I was thinking about the implementation and considering
something like tiddlywebadaptor. Is this a good starting point or are there
bette
It depends on the ammount of data of each tiddler. If you plan to use TW as an
index then yes. If you plan to embed documents I think it is too much. Maybe an
implementation of sync adaptor could deal with this.
--
You received this message because you are subscribed to the Google Groups
"Tid
I'd like to use TW as a front-end to external data, I have two use-cases in
mind :
- mapping all users of my organization into tiddlers, as well as their
teams, etc. Consider ~7000 people here
- mapping my personal documentation (files, links) into tiddlers. Consider
a ~2000 documents here.
T
6 matches
Mail list logo
