Ciao c pa Its good you doing it. In particular I realized you are clear about the background situation ... so hopefully your ...
>> wheel will be rounder ... and at least ... >> so in 5 years I can dig out old code and use it Formats of HOW to present learning material matter. But are not so easy as they might first appear. And its a bit of a Catch-22 in that one oneself does not yet know enough about how to actually DO them. >> I haven't yet developed the standard structure with which to manage those demonstrations Being more positive about it, though, maybe one idea is to use iframes in a TW. Idea being the use case explained in the "mother", and the code needed is presented, NEXT TO the example of the WORKING RESULT in an iframed "daughter". This done for EACH STEP. Just an idea. But the direct demonstration of the "evolution" of solutions sees to me a helpful, and fairly manageable approach. Best wishes Josiah On Saturday, 11 June 2016 01:18:48 UTC+2, c pa wrote: > > > Mat says > >> What makes this one different from the previous initiatives from other > people? > Nothing > >> What would make it successful > Success = helps me. This is an exercise in setting things up so in 5 years > I can dig out old code and use it > >> IMO the faint blue font color is difficult to see when white background. > Changed the pallette to dark > >> possible to get tooltips > That's advanced stuff for a use-case I haven't developed > >> The blue line ... The red dot ... > Took me hours to make that work. Yeah it sucks. That's one of the apps > I'll be documenting. Once the documentation is done ... you folks can > improve it and point to the results so I can use it too. > >> navigation pills > Called that because that is the name of the macro that generates the blue > lines. I'll change the docs to call them blue lines > > Jeremy says > >> talking about documentation improvements: > http://groups.google.com/group/tiddlywikidocs > Ah ha. Excellent. Lots of requests for things > > Josiah says > >> The re-creation of the wheel > That's what I'm doing. My wheel will be rounder > >> concrete demonstration of END RESULTS > The direction I'm going but I haven't yet developed the standard structure > with which to manage those demonstrations. If you look at > [[crazyListHere]], that's my starting point. I've messed around with some > fields and using $:/ and I'll probably end up putting each macro in a > separate tiddler with standard field names to hold standard macro > documentation components and then write other macros to use that structure > to generate slides ... or tooltips ... or something > >> active TRAINING modules on the different facets of TW that are dealt > with through DETAILED USE CASES. > Ahhh ok so this requires yet another structure to be developed > >> In my fantasy is the idea ... > Ya mine too > > Mark says > >> Somebody could write a detailed use case ... There's just too many use > cases > Actually I've found that the generalized use cases tend to be bounded. The > trick is to develop the methodology to lead the user to their particular > use-case with a different methodology to combine cases to address more > granular needs. Then identify outliers which can be added to the standard > pile. To get there requires some technology not currently in TW but folks > seem to be working on it > -- 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/c72ba4e1-b4a7-4196-b27c-076a1910b932%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
