Some problems about workspace under ccTiddly 1.8.5

[cywhale]

How could I make a plugin (tagged as systemConfig) under one workspace
(or under the site-url) to be also functioned under other workspace?

And when I set-up/ adjusted one stylesheet or template, how could I
make changes to all the workspaces ?

that is, Are there some ways to make one workspace to be the "default"
workspace (only can be modified by administrators), and all the
tiddlers, themes, plugins under the default workspace could also
appear under the others ?

Thanks for your kindly help~~

cywhale

[VL]

Hi,

not sure if I understand what you wish to achieve, but when I need a plugin that should be available to all workspaces, I just use it as an external plugin (stored on filesystem in the form of ...\tiddlers\importedPlugins\pluginName.tiddler).
I have to edit it on the server/filesystem, if I need to, not via cctiddly, though.
The same way you could set common theme or other configurations for all workspaces (setting configs via an external tiddler tagged systemConfig).

Rgds,

VL

2009/10/6 cywhale <cyr...@gmail.com>

--
VL

[cywhale]

I got your point. Thank so much~~

[cywhale]

Hi VL,
Your solution work well, thanks.

However, if we could make one workspace as "default workspace", or say
"a support board", we could publish some declarations, public
informations, common settings or other community-used data to all the
other workspaces(or just to the home-url) by add a new tiddler on-
line, not through the serever/filesystem.

What I think could be illustrated as :
home-url : xxx.com
workspace a1 : xxx.com/a1 , as a "a support board"
workspace a2,a3,a4, created by other community-members

Information stream :
(1). some announcements : a1 ==> home-url
(2). some general settings, functions, or common ideas of team-work :
a1 ==> a2, a3,a4
(3). a collection of newly posts(tiddlers), such as team-work
progress, wiki-like knowledge,... : a2,a3, a4,... ==> home-url

I don't know how to do the above (1) or (2): but the (3), perhaps
could be done by within-site rss.

any opinions would be appreciated~~

cywhale

On 10月6日, 下午9時19分, VL <vladimir.luk...@gmail.com> wrote:

[simon mcmanus]

2009/10/6 cywhale <cyr...@gmail.com>

Hi VL,
Your solution work well, thanks.

However, if we could make one workspace as "default workspace", or say
"a support board", we could publish some declarations, public
informations, common settings or other community-used data to all the
other workspaces(or just to the home-url)  by add a new tiddler on-
line, not through the serever/filesystem.

What I think could be illustrated as :
home-url : xxx.com
workspace a1 : xxx.com/a1 , as a "a support board"
workspace a2,a3,a4, created by other community-members

Information stream :
(1). some announcements : a1 ==> home-url
(2). some general settings, functions, or common ideas of team-work :
a1 ==> a2, a3,a4
(3). a collection of newly posts(tiddlers), such as team-work
progress, wiki-like knowledge,... :  a2,a3, a4,... ==> home-url

I don't know how to do the above (1) or (2):  but the (3), perhaps
could be done by within-site rss.

any opinions would be appreciated~~

Hi,

I think you want to make a ccTiddly plugin.  ccTiddly plugins can add recipe, tid and .js files into all the workspaces.

To create a plugin you need to do the following things :

1 .. in the plugins directory create another directory with an appropriate name.  In this example I will call the directory "singleTiddlerPlugin"

/plugins/singleTiddlerPlugin

2 .. In that directory create an index.php file :

plugins/singleTiddlerPlugin/index.php

3 .. In that file add the following :

<?php
$p = new Plugin('Single Tiddler Plugin','0.1','simonmcmanus.com');
$p->addTiddler(null, getcwd()."/plugins/singleTiddlerPlugin/files/singleTiddlerPlugin.js");
?>

4 .. create a files directory : 

plugins/singleTiddlerPlugin/files

5 .. Create the file singleTiddlerPlugin.js file :

plugins/singleTiddlerPlugin/files/singleTiddlerPlugin.js


Any code that you add to the singleTiddlerPlugin.js should be loaded into each workspace.


Hope that helps.

Thanks

Simon

--
Simon McManus

blog : http://simonmcmanus.com