Jed, thanks for a reply! I have a load of return questions that I am hoping you or anyone would be willing to answer. I really hope to make TidBitz into something useful because I really think we need a lower threshold to start working with TW.
I don't know what can be done with [the W3C DnD] example. It is essentially > what tiddlywiki does now. The state has to be saved somewhere and > tiddlywiki works with lists, so it uses lists for keeping track of drag and > drop movements. > I was about to write this: Why does the "state have o be saved somewhere"? If rearranging actually *moves* the div, as it does in the W3C example (...at least according to the inspector tool). In this sentence the word "this" comes before "sentence" - that fact doesn't have to be stored, it is just the nature of text. -? ...that is what I was about to write... but then I read what you wrote: the reason that it is so simple in the example code is that it is all done > in the dom because there is no persistent state, which isn't possible in > tiddlywiki (it would lead to problems like when you have an edit-text > widget edit the same tiddler it is in). Ah. ...but couldn't such a state be saved either manually by the user (save tiddler button) or as part of the action when dropping? I don't know how close your edit-text widget analogy is, but it IS possible to make changes in the current tiddler via the edit-text field, especially single instantaneous changes... such as when dropping something. If you want to re-order the content of tiddlers by dragging and dropping > them than that is possible to make happen, but the most tiddlywiki-like way > to do that is to make a tiddler for each component you want to move around > and then have the drag and drop part modify the order of that list, which > as far as I understand it is what the drag and drop widget does. > Wouldn't that also require that the content is output from some listwidget? In my case, not only does it not make sense to turn them into tiddlers because they're just macro calls - but they are also literal macro calls, not output from some listwidget. To tiddlify that code you would say that each div is a tiddler and when you > drag from one tiddler into another you move all of the content from one to > the other, which I don't think is what you want because it is pretty much > just renaming a tiddler. To use the natural ordering of things in a tiddler > than you have to first define what those things are, otherwise how do you > determine what gets picked up? [...] > Isn't "everything between <div...> and </div>" defined? I.e with some good attributes in the div. There could even be an id attribute in the div. And I think the most important use case is not to drag things between tiddlers but within the same tiddlers text field (in view mode). Does this change anything? [...] You have to define that somehow and then as soon as you define it you > need to have a listing of the 'things' to be picked up somewhere. Which is > why you end up with a list. So, couldn't <div>this</div> sentence be a <div>list</div> with ten elements? ..where element #3 and #7 are such that they trigger actions when manipulated? I.e the list is the text in the textfield. ... Again, thank you or anyone for explaining things. <:-) -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7732cef2-1f2c-4921-a52f-f8fdef4d72d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
