Hi Danielo First of all, I am acutely aware that it sounds like I'm telling you what to do, and I can understand how frustrating that might be. Of course, you're free to do things however you want, and there's nothing wrong with anything that works for you.
My comments are relevant because we're part of a community, and we're both trying to build things that are useful for the broader community. The community benefits most if the available components and plugins of TiddlyWiki work together coherently and reliably. Furthermore, you benefit if you can reuse the existing code because it gives you a head start. > It should listen and track changes to tiddlers, be responsible of telling what should be uploaded, what can be refreshed and to start the process of downloading tiddlers on demand > I know it looks like a syncer module and there are many ideas on current syncer modules that I find very useful, What you've described is precisely what the syncer module and sync adaptor do. Not similar: exactly the same. Its the same use case, and is interacting with the TiddlyWiki core in the same way. > but there are may things keeps me away from making a syncer module: I agree the issues you list are all potential limitations of the current syncer implementation. But I'm trying to argue in favour of extending the syncer architecture to cover the use cases you're interested in, rather than making an incompatible fork of the existing architecture and then still having to implement the additional features that you want. As a TW plugin developer, please don't think of the core as something that's frozen and complete; a goal I've mentioned before is to keep refactoring the core as needed to allow plugins to extend and change it. Those kinds of changes can only be made collectively, with the core developers working with plugin developers. I'm sure that over the months you've seen this happen repeatedly: a developer wants to do something outside the scope of the current core implementation, and we extend the core to get the developer moving again. It's a cycle that works well, and gives us continuous improvements and a rich ecosystem of components. Best wishes Jeremy On Tue, Dec 9, 2014 at 8:32 AM, Danielo Rodríguez <[email protected]> wrote: > > Hello, > > As I advance on the development of tiddlydrive things are getting bigger > and complex. I am thinking if I should move some of the existing code to a > new module with the new code should income. Currently I have four JS files: > > > - An TW utils module that manages most of the work. It makes petitions > to the server via event listeners, provides callbacks functions and also > provides functions to compose those petitions. > - A library module with helper functions like configuration getters. > - A library to manage how tiddlers are imported. > - A startup module that creates the event listeners and starts the > process of download tiddlers on startup if configured. > > I'm thinking in create a new module, but I don't know of which type it > should be. It should listen and track changes to tiddlers, be responsible > of telling what should be uploaded, what can be refreshed and to start the > process of downloading tiddlers on demand. I know it looks like a syncer > module and there are many ideas on current syncer modules that I find very > useful, but there are may things keeps me away from making a syncer module: > > - Tiddlywiki will use my syncer as the only way of saving > - There is no way to manage syncs to the server manually. > - I can not control the timeout of when and how the tiddlers are > uploaded or downloaded > - I want to control how and when tiddlers are downloaded > > Thank you for any help. If anybody wants to check it out here is the code > repository: > https://github.com/danielo515/TiddlyDrive > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywikidev. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
