As original poster and newbie, I'd like to thank all who have offered comments. I'm considering my initial question resolved. Here is some feedback: - if I had some experience with coding, I might have checked for this right off: http://tiddlywiki.org/wiki/Google_Chrome (Import doesn't play nice with Chrome). So much for thinking that Chrome should always be my goto browser! - yes, the import function does work for me in Firefox (3.6.15) - reply to B.S. - the 'import' button appears in the ImportTiddlers bookmarklet. It was never clickable because there were never any Tiddlers to download.
On Mar 8, 1:15 pm, "B. S." <[email protected]> wrote: > OK, then we're crossing multiple issues here. As I probably am here, > below, too. > > Replying to both: > On Mar 8, 6:19 am, rakugo <[email protected]> wrote: > and > On Mar 8, 4:54 am, Eric Shulman <[email protected]> wrote: > > 1. Thank you for the confirmation of the url form, e.g. 'http:// > tiddlytools.com'. > > I confirm that this does NOT work in Chrome. It DOES work in Firefox, > using the native built-in tw functionality. Firefox presented me with > a list of tiddlers, Chrome gives 'Error getting list of tiddlers, > click Cancel to try again.' > > Just so's you know. And it's good to know, personally, what it's > supposed to look like, now, from Firefox. > > So, part of my original confusion, thus my original reply to the OP > (Original Poster), is that Chrome is broken, not tw, but there's no > way I could have known that, only having used tw with Chrome to that > time. > > Thus my premise that seeding the feed list with at least 'http:// > tiddlytools.com', would be useful as a model for a new user to be able > to follow. I do not think there should be any fear of self-promotion, > self-aggrandizement, or apparent 'blessing' of code, here. Even an > entry ofhttp://thisisjustasampleandwillnotactuallywork.com, would be > useful. > > I might also suggest, then, for the moment, that a note be placed in > the import plugin docs that it does not (currently) work in Chrome. > > [Part of the inherent problem, when just trying to grok tw, is it > doesn't take long to encounter, 'and you will find these 42 other > plugins' (that will probably interact in unpredictable ways) also > useful.I don't see how you can avoid the complexity though. But it > would be useful if when trying to follow the instructions, the > instructions worked - thus the request for a sample URL and a note wrt > (with respect to) Chrome. No foul to anyone here, nature of the beast, > and ce la vie.] > > Please take no offence - I do not mean to be dictating anything to > anybody, or telling them what they should do. I am merely reporting my > observations, and suggestions. > > 2. This thread is not about InstantBookmarklets being more useful, nor > about ImportTiddlersPlugin, but that what was expected to happen did > not - from the perspective of a new, inexperienced user. Which is only > to say, all this 'stuff' is confusing to the new user, full stop. > Obviously it's tough enough to wrap one's mind around 'tiddler' > without throwing 'plugin' into the mix, let alone > 'permalink' [misnomer, vs (http) target?], in terms of comprehension > and knowing what's supposed to happen - vs. what am I doing wrong? [Ce > la tw vie?] > > This is NOT to say that information on these other bits isn't useful, > and no foul to the posters or the information - I will most certainly > be looking into them. Just let's not lose sight of 1. above. > > 3. Safari, if 'http://tiddlytools.com/#foo'works, makes sense, http > wise (arguably all browsers should work), as '#' is just an http > target within the returned page. i.e. # does not return just that bit > to a browser. In a normal page, the browser just knows to skip down to > that <target>. tw receives the full file, regardless. (I expect what > is actually coming down is index.html#tiddler.) That it doesn't always > skip down to the one tiddler, depending upon the browser, is probably > not technically unreasonable. Mind you, if safari works, then there > must be tw code in place to remember the requested url, including the > target, and present only it after having received the entire file. > > This would seem to imply a bug in the plugin when tw is used in other > browsers. > > [So, to my mind, not unreasonable behaviour, except there must be code > in there. On the one hand, feature, on the other bug. I don't presume > to postulate which. Merely - inconsistent behaviour. akin to dll hell? > If poster and answerer are using different browsers, inconsistent > answers to questions will be appropriate, and all those reading and > searching messages afterwards will be even more confused.] > > 4. Back to the OP: > "that the 'import' button is always grayed-out, even after I enter a > URL into the proper field." > > I cannot speak to this. I've yet to see the import button greyed out. > One would think if the button is grey it could not be clicked to > provide a field into which an URL could be entered. Having clicked > import, I see no other import button. The button I do see, be it > 'open', or 'cancel', is yellow. Some clarity from the OP, here, would > be useful. > > 5. Back to the OP: Having exited and restarted your browser, and > confirming the imported tiddler is still present - are things now > working for you? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
