Mario,
Some of your tools are quite handy and useful like link-to-tab which is a
constant part of my development environment!
On Thursday, September 12, 2019 at 11:24:50 PM UTC+4:30, PMario wrote:
>
> Hi Tony,
>
> I'm using 3 different repos to create my editions, themes and plugins.
> see:
On Thursday, September 12, 2019 at 11:11:31 PM UTC+4:30, PMario wrote:
>
> On Thursday, September 12, 2019 at 7:30:23 AM UTC+2, TonyM wrote:
> ...
>
>> Most of my projects are macros only so I tend to build them under
>> $:/brand/project store them in a bundle (Marios) including the bundle
>> t
On Thursday, September 12, 2019 at 8:26:19 PM UTC+4:30, SylvainComte wrote:
>
> Hello all,
>
> pretty interesting thread indeed. I'm not sure to be the most capable
> person on this subject but this last message reminds me of my first time
> developing plugin.
>
> > Plugins are the work of an "
The Mat stuffs are among the great resources in TW community!
I use
- TW version like Mat on the title
- Single wiki per plugin
- Rather good documentation and examples (the most tedious part always
ignored by developers)
- Examples as much as possible
- Try to keep them updat
Hi Tony!
I myself use ThirdFlow + TiddlywikiPluginSkletone for creating new plugins!
It has some conventions and help you a simple workflow to create new
publishable contents!
I have customized the skeleton with some macros, css and tools (like
link-to-tab from wikilabs, tiddler commander, trash
Hi Tony,
I'm using 3 different repos to create my editions, themes and plugins. see:
https://github.com/wikilabs
Since I'm using the TW environment variables, this structure makes it easy
for me to develop the stuff.
I'm not 100% happy with the structure yet. There are some elements, which
On Thursday, September 12, 2019 at 7:30:23 AM UTC+2, TonyM wrote:
...
> Most of my projects are macros only so I tend to build them under
> $:/brand/project store them in a bundle (Marios) including the bundle
> tiddler itself. Is this acceptable?
>
Bundles are intended to be "real tiddlers" th
Hello all,
pretty interesting thread indeed. I'm not sure to be the most capable
person on this subject but this last message reminds me of my first time
developing plugin.
> Plugins are the work of an "auteur" and we respect that. Perhaps too
> much?
Actually they are. Sometimes because of
TonyM wrote:
>
> The social pressure placed on me with people like Mohammad and those of
> you beforehand publishing great content, is for me to publish more of my
> tools and utilities, has led me to build and automate a process to publish
> content.
>
> I am starting this thread to solicit sug
Mat
When you set up a *plugin as a tag-pill, *does this mean you apply a tag to
all plugin related tiddlers? This can import that tag to the wiki it is
installed in, do you think this could be an issue?
Most of my projects are macros only so I tend to build them under
$:/brand/project store t
>
> Can I take it then that you only produce a single wiki for both the demo,
> documentation and plugin distribution?
>
yes.
<:-)
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails
Thanks Mat that is very helpful,
Can I take it then that you only produce a single wiki for both the demo,
documentation and plugin distribution?
Regards
Tony
On Thursday, September 12, 2019 at 12:30:30 AM UTC+10, Mat wrote:
>
> I don't know if this is exactly what you're asking for but here a
I don't know if this is exactly what you're asking for but here are some
"rule of thumbs" and other thoughts that have evolved in my own work:
Only show/serve what is relevant. This can definitely include a wide set of
examples etc but it would mean that one generally sticks to standard TW
beha
13 matches
Mail list logo