Stephen Jim:
Thanks for stimulating me to feel young again however fleetingly. --
Hans ( 1968, IBM360/75 Computing Center staff @ U.Waterloo ) ... off to
find the Geritol ... :-)
| Close. Not that it matters at all but... My first job as a programmer
started in 1965. In November of 1979,
I don't think there's a lot of risk of this group going overboard in making
the program user friendly but I do think there are user interface areas
that could tolerate improvement with diluting TW's strong points. It seems
to me that one of the noteworthy ones, based on the number of efforts
Other than loads of more ui,
this may be very practical...
http://tbgtd.tiddlyspot.com
Edit a tiddler and find a button in the toolbar that says *info on
formatting*.
I think something like that triggered as a slider from the Editor, not
unlike the preview pane,
will tremendously help putting
On 1/12/2015 7:24 AM, 'Stephen Kimmel' via TiddlyWiki wrote:
preview pane, the editor is little more than a textarea box. If we
could get it to look as good as the editor we use when posting
messages to this group, I would be ecstatic. And it would make life a
lot easier on the new users
Tiddlywiki is also, by a fair margin, the most sophisticated program I've
run into in years (and I'll wager my number of years in the computer field
rival anyone else's)
I've been 35 years in the industry, 27 with
programmer/engineer/architect attached to my title. Am I close? :)
On 1/12/2015 12:36 PM, 'Stephen Kimmel' via TiddlyWiki wrote:
Close. Not that it matters at all but... My first job as a programmer
started in 1965. In November of 1979, I was a contributing editor of
Creative Computing magazine.
You win. :)
Although even so I realized I am not good doing
Jeremy,
I listened to the discussion on Tiddlywiki's target audience that you
raised in response to my comments in this thread. I just wanted add some
thoughts to that discussion.
I think the most important thing in working out how to focus the effort,
not just for the documentation, but
Jeremy,
I listened to the discussion in the last hangout on Tiddlywiki's target
audience that you raised in response to my comments in this thread. I just
wanted add some thoughts to that discussion.
I think the most important thing in working out how to focus the effort,
not just for the
Hi Neil
I listened to the discussion on Tiddlywiki's target audience that you
raised in response to my comments in this thread. I just wanted add some
thoughts to that discussion.
Great points, Neil, thank you. I think I agree with everything you've said.
Best wishes
Jeremy.
I think
Hi Neil,
I very much appreciate both your points and your stance... as they reflect
mine pretty well.
There are plenty of note taking tools out there, just as there are many
tools for web authoring, data collection, and the various other things that
We should identify what it is that
The casual TW user venturing into js macros does not have 'developer
tools', so yes the popups are a pain, and I agree that TW is not a good
development environment. But for really simple macros, once you have
learned the main pitfalls, it's simple enough to add real value with some
loops or
Yes, I think the question of who is the target user is an important one.
Most of the discussions I have seen on the forum and in the hangouts seem
to be aiming for promoting TW to an audience with relatively low technical
capability. I think this is a mistake both in terms of maximising the
Hi Neil,
I am absolutely not technical. I do think you have a point though. I also
think that planning to use Tiddlywiki for the next 25 years, at least some
of us will want to learn new tricks.
Technical users finding, trying and keep using TW. Some of them will enter
this group and they just
Hi Stephen
I went back and turned on Firebug in Firefox (34.0.5 and Windows 7) and the
built in debugger in Chrome (37.0.2062.120) ... at least I think I did...
and tried reloading my test wiki with the javascript flaw. In both cases, I
got the red popup of death reporting the undeclared
Neil,
I agree virtually 100% though I suspect we might have some quibbles about
where the boundary is for who the target user is. I think if it had some
semblance of a help system other than the full wiki and an editor more like
what Eric did for TWC, TiddlyWiki could reach a significantly
Hi Neil
As an aside, I must say that, despite shying away from using javascript
with TW for a while, I have found that the barrier to entry was very low,
certainly for anyone with any knowledge of a 'C-like' language. I can't
help thinking that many people must be struggling to do things
Ah okay. I think I am some way off understanding the inner workings of TW.
But yes, I can certainly see that there could be many situations where
generating a list of actions to be triggered by one button, whether using a
list widget, or by repeatedly calling a macro with different parameters
We need to remember that participants in this group are not representative
of the general population of users. One reasonable estimate is that only
10% of users have ever participated in a forum or group. None of my failed
Tiddlywiki users even considered consulting the group. My guess is that
Hi Stephen
And much as I hate to say it, Tiddlywiki is a dreadful Javascript
development environment. I have long since lost count on how many Red
Pop-ups of Death I've seen. Some of them simply mean the javascript won't
work... typically ones with a mismatch of {}s... while others seem to
Have you tried
var a=1.0;
return a
?
Neil (also a javascript novice!).
--
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 tiddlywiki+unsubscr...@googlegroups.com.
Neil,
I finally figured out what I was doing wrong and, though I suspect the
majority of folks here already know about this, I'll share what I've found.
Perhaps it will help someone avoid my aggravation. Perhaps someone will
correct me if I’m misinterpreting what is happening.
I'm working
hi Stephen,
Though it seems a bit clunky, I’m working exclusively $macrocall when
sending fields to javascript routines.
Can you perhaps create an example wiki along with a minimalist example
macro that shows what works, what doesn't work and explains how you would
think it should?
Hi Stephen, Tobias
I think the source of the confusion here is that this syntax doesn't work:
sweat {{!!startweight}} {{!!finishweight}}
I agree that it's reasonable to expect that syntax to work.
The rationale for the current arrangement is that there is a conscious
layering of wikitext
Ultimately I don't have a problem with the fact that
sweat {{!!startweight}} {{!!finalweight}}
doesn't work. I've tried several things that didn't work. This one was just
harder than most to diagnose what had gone wrong. Anyway, as Tobias
suggested, I've uploaded a simplified wiki with three
I encountered the same problem and solution in writing my first javascript
macros. I have now come across another difficulty which may also be
related to the layering of features that Jeremy described.
Jeremy: am I interpreting correctly that your bullet list indicates the
order in which the
Hi Neil
Jeremy: am I interpreting correctly that your bullet list indicates the
order in which the features are processed, but last first in your list?
Thus, the transclusion is only processed after the non-widget style
macro invocation?
No, not at all. The layers I was describing are
Hi Jim
I have noticed as I work through building my own macros that sometimes
reloading the TW (or restarting TW under node) will cause code changes to
be picked up that weren't before. So I've kinda gotten into doing it
automatically as sort of a Wave a dead chicken over it superstitious
That pretty much eliminates any chance that I might someday switch to
Node.js.
I am well aware of the save-reload requirements. What drives me up a well
are things like:
a=1.0;
return a
giving NaN as the result. Or
a= 1.0;
return Number(a)
giving NaN as the result no matter how many times
On Monday, December 29, 2014 9:31:55 AM UTC-8, Stephen Kimmel wrote:
Inputs: offset = 6 a= 1 mdate=1/12/2015
The values for a and mdate are correct but offset is not the right number.
As you can see from the code, offset is used but not modified. Even so, the
number that comes out of the
Thanks for the quick reply. Unfortunately I've either missed something or
this has taken a decided turn for the weird.
The relevant lines from the macro now read:
if (out == 7) { out = 0 };
if (offset == 7 - n ) {output= Workout[1]};
and as I saved and reloaded the wiki the result became:
In the general category of I don't know what I did to make the problem go
away but...
I've got it working now. I suspect there is something flaky about how some
of the browsers handle javascript.
Thanks again, Eric for your help.
--
You received this message because you are subscribed to
On Monday, December 29, 2014 3:18:48 PM UTC-6, Stephen Kimmel wrote:
In the general category of I don't know what I did to make the problem go
away but...
I've got it working now. I suspect there is something flaky about how some
of the browsers handle javascript.
Thanks again, Eric
32 matches
Mail list logo
