On Monday, September 21, 2015 at 2:44:42 PM UTC-7, Eric Shulman wrote: > > On Monday, September 21, 2015 at 12:30:38 PM UTC-7, Pete Johnson wrote: >> >> Tiddlywiki already comes *"barebones."* >> > > The ongoing discussion suggests that some people think otherwise. As > Tobias noted, "bare-bones" possibly means quite different things to > different people. > I think this discussion (and any actionable items that result) is part of > what has made TiddlyWiki so versatile. >
*So let them produce their own barebones. * > > >> Jeremy produces an amazing free product. >> > > Yes, he does. > > >> For those who don't like to advance, they can keep copies of empty >> Tiddlywikis of the versions they like. >> > > "like to"... "want to"... "need to".... pick any verb that fits your > situation... > > No one forces anyone to upgrade to the latest Tiddlywiki. >> > > The discussion about what a "barebones" TiddlyWiki could/should be has > little to do with upgrading. It's more about how to package the underlying > the functionality TW core so it can be used in other scenarios, independent > of the default interface delivered with the standard distro. > *The discussion about what a "barebones" TiddlyWiki mostly has to do with some looking for another or others to do work on their behalf.* > > >> Browsers change. Browser makers change Javascript engines. Browsers don't >> stand still. >> > > Yes. The technology that enables TiddlyWiki to work changes over time. > That is one of the primary reasons that TW5 was created... the old > TiddlyWiki "Classic" codebase was based on 2005-era methods and script > engines, and it was becoming increasingly difficult to maintain because of > "browser drift". A fresh start, using "modern" coding methods and > functionality was the inevitable response. > > >> Jeremy ought to stay focused on the code that makes Tiddlywiki work with >> respect to the latest browsers and the latest browser versions. >> > Currently, Tiddlywiki has a major error when trying to render with the >> latest version of Chrome through http. All should rather see Jeremy work to >> fix those kinds of errors rather than appeasing one-off requests. >> > I've written about it on the forum here: Internal Javascript Error and >> the Latest Version of Chrome >> <https://groups.google.com/forum/#!topic/TiddlyWiki/IH_Qz5dnHFg>. >> > > I have not been able to reproduce the error you reported. I am using > Chrome Version 45.0.2454.99 m (under Windows 7), and I visited > http://TiddlyWiki.com, and there was no error. Please note that I am not > disputing that you are seeing an error message... just that it isn't > reproducible for everyone, so it might not be as much of a "major error" as > you have suggested. > *I can't reproduce the error with Chrome on Android, Chrome version 45.0.2454.94. I'm awaiting on results from other devices.* > > As far as Jeremy "appeasing one-off requests"... that rarely happens. > Jeremy is famously resistant to "putting stuff into the core" just to > support a single use-case. However, sometimes a single use-case can > suggest an area of functionality that has more general applicability, and > Jeremy decides to direct some of his attention there. > *I'll let Jeremy speak for himself.* > > With regard to the "browser drift" problem noted above, that is only ONE > of the many areas of TiddlyWiki that need attention. Other major areas > include: > * improvements/additions to core functionality > * improvements/additions to baseline interface > * efficiency/performance issues > * plugin installation/distribution mechanisms > * documentation > * etc. > > Bottom line, while you might feel that fixing the error you encountered > should be "priority #1", there are numerous other ongoing efforts that are > arguably of greater impact to more people. Of course, we *do* want to > figure out what it happening for you (and *possibly* others), but try to be > a bit more patient and look to the TiddlyWiki community itself for help. > If the problem exists for some people but not others, perhaps we can > narrow down the conditions under which it occurs by having more people test > under a variety of platforms and configurations. > Bottom line. Only you care what you believe what defines "*bottom lines"* for you. I don't. *Good luck! * > > enjoy, > -e > Eric Shulman > ELS Design Studios > TiddlyTools - "Small Tools for Big Ideas!" > InsideTiddlyWiki: The Missing Manuals > > YOUR DONATIONS ARE VERY IMPORTANT! > HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"... > http://TiddlyTools.github.com/fundraising.html#MakeADonation > > Professional TiddlyWiki Consulting Services... > Analysis, Design, and Custom Solutions: > http://www.TiddlyTools.com/#Contact > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b301bc80-34c2-4ef9-9272-cf7de207e051%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
