> I've found arrangements like that to be too brittle
That seems to be true anyway; though, while the current mechanism
already works with errors, why not implement this along with somewhat
"refactor links" button? Since tiddlers are not renamed frequently,
this could be an ok solution for link binding.
I must notice, the current behavior (with "errors") has one advantage:
namely, if wikiwords are used as names of classes (in
{{ClassName{..}}} wrappers), the tiddler ClassName (which probably
doesn't exist) has the corresponding list of references which
sometimes is useful for aggregation some semanical elements. Although
the toolbar macro can't make the list of references to some other (not
current) tiddler, which makes such aggregation somewhat awkward.
----
> I'd always favour maintaining tight standards of backwards compatbility
That sounds good, but I've got twisted with words from announcement:
> I was hoping that we'd get to the point where the advantages of completely
> rebuilding TiddlyWiki from the ground up would outweigh the disadvantages of
> losing backwards compatibility.
(this is from http://tiddlywiki.com/tiddlywiki5/ , TiddlyWiki
tiddler). Perhaps I've got something wrong.
> Definitely start with TW2. Any subsequent developments to TiddlyWiki
> will always be strongly related to the current code base.
Thanks. I think I'll start to learn dev secrets and write docs
publicly after the exams, so I hope first pieces of documentation will
appear in the end of Jan - start of Feb.
----
> That sounds like Opera Mobile. Confusingly, Opera have two different mobile
> browsers
Yeap, Opera Mini somewhy doesn't even open local pages, so I was
speaking about Opera Mobile.
Is it true that TiddlySaver is written in JSE and JSE needs a Java
virtual mashine (such as CrEme, http://www.nsicom.com/Default.aspx?tabid=138),
not Java emulator? Can TiddlySaver be rewritten in JME (probably not,
since it interacts with filesystem..)?
> I think that the best bet for many platforms is to use apps -
> little wrapper apps that encapsulate the stock TiddlyWiki
> HTML file and extend it with native saving capabilities.
Since I'm not a proffesional programmer, I'd say "what does that
mean?" Actually I don't understand what should call what. If
TiddlyWiki is launched by browser only browser can interact with file
system; and if it is so, the browser must get access to file system
(for editing!) via some technology - Java or ActiveX or smth else.. So
what technology do you mean; or where I'm wrong and what other
solutions can be achieved? Do you mean that it's probably possible to
create an application which would work much like server - listen to
browser requests and do the edit work with file system?
The problem is my handheld works on Win Mobile 5 and it is unlikely
that a solution appears "by itself".
--
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.
