> > Jed Carty wrote: > I don't think that creating a way to have the cursor appear at the > position clicked in normal text is a problem, but* in the context of > tiddlywiki this doesn't make sense*. You can create tiddlers that have no > text content but they display text generated from other sources ... (my > emphasis) >
I think Jed is absolutely right. Doing this without considering the functional outcome would be a problem. I do think the approach has merit but, exactly WHAT are we talking about? I can imagine a TW that could benefit from direct "surface level" editing when its properly de-limited to direct edit of base Tiddlers--but I can't imagine a TW where that could be a workable universal approach because transclusion would make it very confusing & dysfunctional. I think part of the issue is not just tech--its about conceptual design. In other words: where its possible to do it, HOW do you indicate that in a useful way--whilst ALSO indicating in other cases it can't function? I think the gist of Jed's point is that as TW currently is we spend lots of time "HIDING" the originating Tiddlers in various types of transclusion--and that is pretty central to TW's ability to create integrated wholes. So, I see now, this issue would seriously struggle with that. But maybe a de-limited approach could work for specific types of TW app?? But its hard to see anything generic being viable for all (like many, if not, most) situations. Best wishes Josiah -- 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/b896b7df-8383-4a67-9491-cfaccec8bb29%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
