Ton, On Friday, November 30, 2012 2:31:48 AM UTC+8, TonG wrote: > > Hi Vincent, > > Sorry, but I could not try your Dropbox prerelease file in Firefox 17 > since the Configuaration/Edit modes are not available to me (Win 7 64- > bit + Firefox v17) > When I hover with the mouse over the table, I only see cell references > like A1, B1 or formulas but no buttons at all. > Are other users of Firefox v17 having the same problem? > > Like usual my FF 17 works fine on Win7 x64. Is it possible that some of your addons left something over and accidentally affects the behavior of the plugin?
> Since TiddlySnip stopped working for me with Firefox v17 (other post), > I have Firefox v16 available as well, and surprise: I see the H, C, > and E buttons when hovering over the table. > I do like it this way: no distracting buttons when you just view > tiddlers with tables. > > And although "2,3" now shows as "2,3", I can "calculate" with it. I > expected something like #VALUE! (as in OpenOffice), but got "strange" > calculations (A1 containing "text", A2 =product(2*A1) ): > A1 A2 > ------------ > 2,3 6 > 3,4 8 > 2,03 6 > 2,003 4006 > 2,013 4026 > > This way it will be difficult to "debug" wrong table entries (e.g. "," > instead of "."). Is it possible to mimic the #VALUE! error of > OpenOffice? > The first three cases are, unfortunately, from Javascript's eval() function, which the TWtcalc calls for final evaluation. I chose to use the eval() function because I thought it should be a good parser, which is needed to handle wrong expressions. I have no idea why it returns 3 when you feed it with "2,3" (2 comma 3), which results in 6 in your first and third test cases and 8 in your 2nd. I did not plan to write a parser for TWtcalc for the reason I just said: I thought Javascript itself is a good parser. Guess I have to rethink about it... The last two cases, 2,003 and 2,013, are from TWtcalc's thousands separation codes, which considers 2,003 as the number two thousand and three (since it happens to have the correct format of thousands separation) and gives the result of 4006. Same for the last case. This should be somewhat fixed in the pre_release file available at https://dl.dropbox.com/u/23745840/pre_release.html, as I now disable the thousands separation codes by default and enable it only when the option chkTWtcalcThousandSeparated is set to true. > And all of a sudden I could not edit the cells anymore. I could go to > edit mode of the tiddler by double clicking the table (or using the > Edit button in the toolbar), but after clicking Cancel, editing the > cells was still not possible. > Only after reloading the TW everything worked again. > I might have fixed this in the pre-release file (link above), please try and let me know if I did. Have fun! Vincent > I hope to do more testing in the weekend. > > Cheers, > > Ton > > On Nov 29, 4:53 pm, Vincent Yeh <[email protected]> wrote: > > Oh, and I forgot to mention that the buttons are now visible only when > > mouse enters the table or the table is in edit mode, and invisible > > otherwise. > > > > > > > > > > > > > > > > On Thursday, November 29, 2012 11:45:59 PM UTC+8, Vincent Yeh wrote: > > > > > Yakov, > > > > > Thank you very much for so much detailed description of your ideas, I > > > actually haven't thought that deep yet! I will think more about it and > > > probably start working on it not far from now, though it seems like a > big > > > project to me. > > > > > About the bugs I think I have fixed a couple of them, > > > > > - the wrong behavior in a closed slider panel, > > > - the strange results in partial self transclusion, > > > > > The keyboard navigation in a spanned cell shall be fixed soon. > > > > > Ton, I should have fixed the TWtcalc bug you mentioned, too. > > > > > A pre_release file is prepared at > > >https://dl.dropbox.com/u/23745840/pre_release.htmlfor you to try. > Please > > > do try it and tell me if there are more I need to fix. Thanks. > > > > > Have fun! > > > Vincent > > > > > On Wednesday, November 28, 2012 10:57:36 PM UTC+8, Yakov wrote: > > > > >> Hello. > > > > >> About sliders: the story seems to be rather complicated and may be > far > > >> from usual usage. I put many tests in one tiddler and that's where > sliders > > >> work incorrectly. I simplified the test and made it closer to real > cases. > > >> Create tiddler 1 with couple of sections and a table in each: > > > > >> !Section 1 > > >> |table 1|c > > >> |editable|k > > >> |h-cell1|h-cell2||h > > >> |c11|c12++|| > > >> |c21|c22|| > > > > >> !Section 2 > > >> with merged cells: > > >> |h-cell1|>|h-cell2|h > > >> |c11|c12|c13| > > >> |~|c22|c23| > > > > >> then create another tiddler which transluces this sections, one via > > >> <<tiddler>> and another via <<slider>>: > > > > >> <<tiddler [[Tiddler 1##Section 1]]>> > > >> <<slider "" [[Tiddler 1##Section 2]] "*" "">> > > > > >> And then try this: first, open the slider and click E on a table. > Each > > >> table will enter the edit mode, no matter which E button was clicked. > (then > > >> click E again or reload the tiddler or go to edit mode and back) And > > >> second, close the slider, click E on the table which is transcluded > via > > >> <<tiddler>>, then (or after clicking E once more) open the slider. > The > > >> table disappears; if you click E on the first table again, the second > table > > >> appears once more, but with messed numeration. > > > > >> Regarding the self transclusion. A usual case for it is when I create > > >> sliders (without NestedSlidersPlugin) and tab sets like this: > > > > >> <<slider "" [[This tiddler##section]] "somelabel" "sometooltip">>/% > > >> !section > > >> some content > > >> !end%/ > > > > >> /% > > >> !section 1 > > >> ... > > >> !section 2 > > >> ... > > >> !end > > >> %/<<tabs .....>> > > > > >> Although, I place the sections *after* the transclusion macros most > of > > >> the times (this test case appear from that tiddler with many tests in > it). > > > > >> As for the test, it doesn't work for me. What I did: > > >> * downloaded the pre_release.html file via FireFox -> save -> save > all > > >> * open it (in both FF 16.0.2, 17.0 with enabled and disabled > TiddlyFox > > >> and in Opera 12.11 without TiddlySaver.jar), opened the "test" > tiddler > > >> * click E, click c14, add "+" in there, click out (in edit mode the > > >> content is shown as "c14+"), then click E again (the content is shown > as > > >> "c14+c14" now) > > >> * open edit mode of the tiddler (in there the table is unchanged, the > > >> content of the cell being "c14") > > >> The behavoir is the same with all the combinations of browsers/saving > > >> engines listed above. > > > > >> Navigation with keyboard is very nice, thanks! I especially like the > > >> behavior of the cursor when navigating left and right. The thing that > needs > > >> some more tweaking is merged cells: currently arrows don't move focus > into > > >> the "~" and ">" cells; what I'd expect is that pressing left always > moves > > >> to the cell on the left (including ones with ">" or "~"), not down or > jump > > >> over a cell. > > > > >> Another idea: instead of clicking E, it can be very convenient to > > >> double-click a table to toggle the edit mode. But this has to > difficulties: > > >> first, to implement this, it's necessary to stop handling even of > > >> double-clicking the tiddler which opens the edit mode of the tiddler > (set > > >> by the fetchTiddler method of the story object [1]); and second, > > >> touchscreens (or, better to say Android browsers) have some different > event > > >> handling (in Android, double-tap doesn't work for opening a tiddler > to > > >> edit). > > > > >> Then, about editing lists. > > > > >> First, there are three basic things which should be handled: > > >> * simple list > > >> * list tree > > >> * list tree with items with wrappers like this {{justDiv{ > > >> > here goes, for instance, a quotation > > >> * or > > >> * another > > >> * list > > >> | or | a | > > >> | table | > > >> etc > > >> }}} and then some more text. Unfortunately, there are other wrappers. > In > > >> some TWs I use NestedSlidersPlugin when makes +++[this wrapper] > > >> some content > > >> === and also /% > > >> comment wrapper > > >> %/ > > >> and it is to be decided what parts are opened in the edit mode. A > simple > > >> way would be to edit a list item with everything inside it, but when > > >> there's only a sublist inside, like this: > > > > >> * item > > >> ** sublist item > > >> ** another sublist item > > > > >> than it's more convenient to open only the > > > > >> * item > > > > >> part on editing the item. > > > > >> Next, there should be some way to activate the edit mode. There has > to be > > >> a method for each list item. There can be some buttons, or a button > can > > >> appear on click, or double-click can activate the edit mode. What I > think: > > >> * double-click is a very good solution but > > >> ** this can have the same problems with touchscreens as I mentioned > above > > >> ** there should be some way to activate other control elements > (analogue > > >> of C button, menu for moving up and down etc). This buttons can > appear in > > >> the edit mode; as for "where?" -- in the end or in the beginning of > the > > >> list (perhaps hovering over a list item marker). > > >> * single-click+buttons is a bit worse, because buttons will appear in > > >> some situations where that's not necessary (like opening a slider or > > >> clicking a <<tag>> macro). The advantage compared to the double-click > > >> approach is that there's no need to open the "editor" for other > operations > > >> and also no need to investigate the "Android double-click event > handling" > > >> issue > > >> * permanent buttons version isn't tidy at all and I guess will be not > > >> good enough in mobile devices as buttons will eat extra space > > > > >> The third things to look into is extra operations. Not necessary to > > >> implement them at once, but they are to be accounted when designing > the > > >> engine. So operations that I see to be useful are: > > >> * the same as in TableEditor: add an item, cut/copy/paste > > >> * move up/down (in principle this can be done by copy-pasting) > > >> hm.. in fact this doesn't seem to make much restrictions.. > > > > >> Finally, a general note (perhaps, too general). I was thinking about > how > > >> this is different from WYSIWYG and concluded that the basic > difference is > > >> between "simple text field" (in the edit mode) and a "text field" > with an > > >> arbitrary element inside. Let me give an example. Consider this line: > > > > >> This is an equation: $a + b = c$ and this is a macro: <<tag > [[smth]]>>. > > > > >> Ordinary "tiddler edit mode" opens this as it is written here. A list > > >> editor made with text fields will do the same (and, for instance, > show the > > >> whole wrapper with the content inside itself). On the other hand, if > there > > >> was a possibility to open this as > > > > >> This is an equation: <here the equation element is generated> and > this is > > >> a macro: <here is the macro element>. > > > > >> where text can be edited and navigated like in the ordinary text > field > > >> and "elements" are shown wikified that would ease many things, like > working > > >> with formulae, or with list items containing wrappers or other things > (and > > >> this is the main step to WYSIWYG). See ASciencePad [2] to get some > ideas: > > >> especially about workflow with formulae inside text (keep in mind > that > > >> that's an adaptation, meaning that the core TW code is altered; and > it also > > >> works only in some browsers partially because of MathML). > > > > >> Hope this post is not totally overwhelming. > > > > >> Best regards, > > >> Yakov. > > > > >> [1] > https://github.com/TiddlyWiki/tiddlywiki/blob/master/js/Story.js#L253 > > >> [2]http://math.chapman.edu/~jipsen/asciencepad/asciencepad.html ( > > >> #MathExamples ) > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/Xo63aQm_UPYJ. 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/tiddlywiki?hl=en.
