Tiddly Configuration Management - "Best Practices"?

[SteveM]

I posted this question on the user group, but got no responses. It's
trivial but any advice would be valuable to me.

I am building a couple of end-user prototypes but get lost in
configuration management with the importing of tiddlers. There are
scores of them and some are more useful than others. But importing
over and over is certainly not efficient. Although I suppose I could
save the most used ones locally. And creating general templates with
commonly used plug-ins is another option. And finally, the issue of
backup creation - backup on change will obviously fill up a hard drive
in no time. But before I get immersed in config mgt trial and error,
I'd like to ask you experts:

Can anybody share their "Best Practices" regarding managing their
TiddlyWiki development space?

Thanks Much,

Steve

[SteveM]

One more thing, are there any Con to using the TiddlySpot MPTW TW as a
baseline template?

SteveM

[FND]

> I posted this question on the user group, but got no responses.

Well, you did get a response from Jon, asking for more details:
http://groups.google.com/group/TiddlyWiki/t/172b6e45c4a24d40

Generally speaking, posts lacking specific questions or clear intent are
hard to respond to - which might explain the lack of responses in this
case (e.g. this post is much clearer than your original)

Either way, this really isn't a development-related issue, so it
shouldn't be discussed here.

-- F.

[Simon Baird]

I think you need to invest some time in setting up some "build" scripts. The main one is a ruby script called "cook.rb" and can be found here:
http://trac.tiddlywiki.org/browser/Trunk/tools/cooker

This is the tool used by the core developers (and others). It assembles TW files from "recipes". Unfortunately it's not documented much so you have to rely on the examples in the main repos or people on this list for help. (Someone correct me if I'm wrong).

There is another tool that myself and at least one other person* use (disclaimer: I wrote it) called r4tw.
http://randomibis.com/r4tw/
It's also a ruby script. It doesn't use recipe files, rather you write custom ruby scripts to build your TWs.

If python is your thing there are some python tools emerging too. Take a look on this group for recent posts.

So the good news is there are tools out there and it's definitely worth the effort if you want to become a developer. The bad news is that it's a little hard to get started.

Re MPTW as a base, I highly recommend it (disclaimer: yadda yadda), especially if you want to provide selectable themes and colour palettes. Keeping it fresh (in line with the latest TW releases) and bug free is a high priority for me.



Simon.

* at at least one point in time.. :)

--
simon...@gmail.com

[SteveM]

Simon,

Thanks very much for the references. Some background to explain my
presence here at this site.

My graduate degree is in Operations Research (Management Science/
Applied Mathematics)

I program but I am not a programmer. I will write code to integrate
analytic modeling engines with data bases and a user interface. (I
just learned that that exercise is called a Mash-Up. Which is a great
term-of-art.)

So my professional (and personal) interest is end-user applications as
opposed to component development.

But TW is a unique paradigm. So I want to figure out how it works.
And understand the Tiddler development approaches to I can do the Mash-
Ups and customize functionality.

So given that, I appreciate your patience when my questions fall out
of the sky. Feel free to visit my universe at
http://groups.google.com/group/sci.op-research/topics if you should
need some help with the Farkas Theorem of the Separating Hyper-Plane
or something.

BTW, I think there is a ton a great open-source stuff happening, but
end user product development appears to still be rather shallow. I
think now is a great opportunity for guys like me to leverage the
great work done by guys like you.

SteveM

On Jul 15, 7:00 am, "Simon Baird" <simon.ba...@gmail.com> wrote:
> I think you need to invest some time in setting up some "build" scripts. The
> main one is a ruby script called "cook.rb" and can be found here:http://trac.tiddlywiki.org/browser/Trunk/tools/cooker
>
> This is the tool used by the core developers (and others). It assembles TW
> files from "recipes". Unfortunately it's not documented much so you have to
> rely on the examples in the main repos or people on this list for help.
> (Someone correct me if I'm wrong).
>
> There is another tool that myself and at least one other person* use

> (disclaimer: I wrote it) called r4tw.http://randomibis.com/r4tw/

> simon.ba...@gmail.com