On Aug 20, 6:21 pm, [email protected] wrote: > That seems like a pretty good explanation of what's going on, but if > your analysis is correct, I don't see any easy solutions. ... Me neither. For me it is a syncing problem and syncing isn't easy.
> ... I've got two > opinions though: > > * Having broken-ness in releases is a normal part of the process. It > keeps dialog happening and dialog helps keep stuff happening. Right. But my TW is a "trusted system", and because of this, it is allowed to handle my valuable data. If my "trusted system" get's a flue, I am worried :) > Where that broken-ness causes angry reactions that suggests that the > features that break are poorly considered on various angles: > * They are too hard to test. > * Too complex to get right. > In those cases maybe they shouldn't exist? Pugins .. they need to exist :) IMO most of the time it's problems with plugins and there dependencies, added to the TW. I know, that the core team can't test them. Some users even don't know, that it is a 3rd party plugin that causes a problems, because they downloaded an existing TW, that has a nice predefined feature set, that works for them. The file they are using is TiddlyWiki. Even if it is a heavily adjusted one. > * Personally, I think the self-update functionality is one of those > things that is too hard to test, too complex, and sets up bad > expectations. It should be removed and people should not do > self-update. ... Then the import function, needs to be heavily improved. > ... Instead they should import their existing wikis into > new versions if they feel like it. > That's a _far_ safer way to manage one's data and just a better way > of managing one's information. IMO, this won't work at the moment. A TW, that I use for, let's say one year, contains a lot of minor adjustments to eg: StyleSheets, Plugins, Config tiddlers .... and it has a lot of dependencies. If I try to import all of my modified tiddlers, into a vanilla TW, I can't see, which are my modified tiddlers, and which are shadow or core tiddlers. To make a clean update, I shouldn't import the shadow or core plugins. But I need to import modified shadow tiddlers. ... Let's say I take the time to carefully select all the tiddlers I want to import. I click import ... Let's say I accidentally forgot one or two important tiddlers. The new TW will break. Worst case, the layout and edit mode breaks. So delete the file and start over again. Or some plugins are missing there config tiddlers. Finding the missing tiddler, with the import dialog is close to impossible. (Having 200++ content tiddlers) Some may think: "Most users don't have that many tweaked tiddlers". That doesn't matter. According to Murphy's law it will be the _one_ important thing they tweaked, that will break the system. Also using the "magic select all button" doesn't solve the problem. Because it is the one tiddler they shouldn't have selected, that causes trouble. =========== Most of the tings listed above, are the reason, why I don't update that way anymore. I use ginsu and cook to make an update. ginsu splits the existing TW into nicely separated directories and files. * plugins * themes * shadows * content Since I know, I want to keep the content stuff, I don't need to check it. "shadows" and "themes" directory contain a hand full of tiddlers, that can be easily checked. Plugins needs a bit more attention but checking 20+ files is easier than several hundred. If an import function is structured that way, I think handling would be much easier. It also gives the user some info about 3rd party plugins s/he is using. .... -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
