Ciao Mohammad
I guess that three factors are important for me ....
-- getting clear what I want to DO ... by which the mean a *functional
understanding* before actually coding;
-- understanding, when necessary, *modularity. *So I don't up
coding something twice;
-- *knowing what I don't know* -- i.e. knowing when to ask for
help.
In terms of helping users gain better style I suggest ...
-- taking code that works by someone and peer review it with
suggestions to improve it.
I personally am not any kind of good coder. But I do play
with macros.
I would welcome critique to improve them.
What is the best way to *document?*
-- personally I find *well designed example macros* by good
coders the best documentation.
This you are doing and I'm using the macros you wrote to
help understand how to
write them better.
Just thoughts
Josiah
Mohammad wrote:
> I am looking for how develop and document Tiddlywiki macros.
> I am interested in:
>
> 1. Good programming style
> 2. Macro documentation
>
>
--
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/3b2e8695-bab3-4fbd-9fbd-1ca05813cd8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
