Hi Vincent,
> > > > 2. Lists > > > 2.2 Changing of the list order is rather slow > > > Hmmm, I just noticed in my > example<http://twve.tiddlyspot.com/#%5B%5Btwve--Example--List%20Items%5D%5D>that > *it > caused an infinite loop when I tried to move down the last item*, but > worked quite smoothly in other cases, even when moving up the very first > one (well, you may get strange results but that's how TiddlyWiki renders > lists, not the *twve*). Are you saying it is slow in general, or just > cases similar to what I mentioned? If it is general then I would guess it's > some interference with other plugins. > > > Well, no, for me (in FF/Opera) in a list as simple as > * one > * two > * three > moving the first or the second item down takes 3-4 seconds (even if that's > the only open tiddler). > > > I am guessing that could be the AutoSave feature (I remember you had once > mentioned about this?). > > In v3.0.2 (and earlier versions) moving an element (such as a list item) > includes setting the tiddler text twice, which would trigger the saving > action twice if AutoSave is enabled. That could be time consuming. I can > reduce the time of setting tiddler text to once, should save half of the > time but I don't know how to save more with AutoSave enabled. Usually I > disable the AutoSave option and moving elements is very smooth. > Yes, very probably it's autosaving. And moving table rows has sort of the same speed as colomn moving. How about an option that will control whether autosaving should be called? > > > > > > > 3.2 Inline editing (at least adding/removing colomns) seem to remove > additional classes. Say, I have a borderless table > |borderless|k > |text| > After I add a new colomn, the table becomes with borders (it is ok for > edit mode, but in view mode I would like to have my CSS applied). The > |borderless|k part is not removed, if the tiddler is reopened, the > borders are gone again. > CSS here is > .borderless, .borderless tr, .borderless th, .borderless td { border: none > !important; } > Note the !important part: without it, the stying is not applied at all -- > I would consider this as a bug, too. > > > This I really have no idea. The *twve* does not do anything about styles > because I have very limited knowledge about CSS statements. If that is a > bug in *twve*, that must be due to the nothing be done about styles. In > that case it may take a long time to fix... > > > Ouch. I wanted to check if the DOM classes are removed, but the bug is no > longer reproducible.. Let's forget about it until I can reproduce it again. > > However, the need to add the !important part to CSS stays. > > > You mean without twve you don't need this ! important thing, but with it > you do, is that right? That will be a trouble to me because I have no idea > at all what this ! important is! Hope it is not that important. :-) > > Well, this is not of great concern; in short, CSS allows to make some rules have more priority than others -- the !important part is for that. But ok, let forget about this at least for a while, this is not a top priority issue. > > > 3.5 the speed of colomn moving is so-so and seem to depend on the history > of moving: consider this tiddler: > Start with text > |a|b|c| > |d|e|f| > |g|i|j| > end with text > moving the first colomn to the left (or the second to the right) takes > about 1 second; if I move that colomn back, it takes 2-3 seconds (tested in > FF) > > > What about rows? Moving rows is smooth but columns not? I thought it's the > AutoSave again but then moving rows would be as slow as moving columns. > See abouve. > > > > 3.6 tables with several missing cells behave in a tricky way: if I create > this table > |a|b|c| > |d| > and try to edit the bottom-left cell, it opens for editing and then shows > the table as thought as it is edited in a right way (the bottom-left cell > is now with content). However, if I open the tw "code", I see > |a|b|c| > |d|f| > instead of > |a|b|c| > |d||f| > and reloading the tiddler shows incorrectly edited table (the > bottom-center cell is filled with the text). > > > I think you are using FireFox, which version is it? My FireFox 29.0.1 / > Win8 works correctly, but Chrome, IE11 and Opera don't even edit the > missing cells! There is certainly some cross-browser compatibility issue I > need to fix, no matter what. > Yes, I've tested this in FF only. > > > 4. Transclusions (not finished) > 4.1 inserting sections causes and error: if I create a tiddler New > Tiddler to include with the text > !section > Type the text for 'New Tiddler' > and another tiddler with this text: > <<tiddler [[New Tiddler to include##section]]>> > I see the line > Type the text for 'New Tiddler' > but in its end, there's Error in macro <<tiddler>> telling me TypeError: > b.$dom is null > > > In my Win8 box with FireFox 29.0.1 I do not see such an error, but with > IE11, Chrome, and Opera I see this error some times (but not always). I am > not sure what is wrong about it yet, shall need more time to find out. > Well, this was tested in FF and is quite reproducible, same thing in IE and Chrome; at least in these two backstage get hidden when the tiddler with the transclusion is loaded on startup (using permalink), but is not hidden otherwise. Ok, one more thing: 2.x (is it 2.3?) the edit areas for list items are sometimes cut and have scrollbars when it is not desired. Usually it is so when tiddlytext is considerably longer then its wikified version (like when there's a prettyLink [[short text|very very very long target tiddler name]]). Generally, I would expect edit areas without cut+scrolling unless they have height of at least 33% of the total height (the thing I've described when discussing the preview scrolling) -- if they have just 3-5 lines, there's no need to cut them. Best regards, Yakov. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
