Deleting a TiddlySpace so I can start over again

[dickon]

Follwing helpful advice in an earlier post I want to delete a
tiddlyspace so I can start all over again, and just upload the content
tiddlers, not all the (MPTW) plugins etc, that have been causing
problems with the tiddlyspace code.

I can't see how to do that. Any tips?

Dickon

[PMario]

Hi,
At the moment, there is no simple way, to get rid of many tiddlers.
But may be it is not needed.
I have an other idea.
Goto backstage: plugins
select all
unselect plugins you need
and delete.

Now all plugins, uploaded from a file tw. will be deleted. So there
should be no side effects anymore.
Please report the result. Since I haven't done this yet :))

-m
PS: If you want to get rid of the whole space. see
deleted.tiddlyspace.com but be aware, the name can not be used
anymore.

[Tobias Beer]

Hi Dickon,

First I thought that you could use a tiny, yet dangerous transclusion
which would erase all tiddlers by copying the following into a tiddler
and save:

<<tiddler {{store.forEachTiddler(function(t)
{store.deleteTiddler(t);})autoSaveChanges();'';}}>>

That however does no work on tiddlyspace... *rolleyes*

Maybe someone can tell why this script won't work on tiddlyspace.

Cheers, Tobias.

[FND]

> deleted.tiddlyspace.com

Seconded.

> store.deleteTiddler(t); [...] does no work on tiddlyspace

You wanna use the higher-level removeTiddler method, as that's what the
ServerSideSavingPlugin hooks into.

-- F.

[Tobias Beer]

Hi FND,

Since we're at it, in what respect is...

store.removeTiddler a higher level method than store.getTiddler
(or store.getTiddler higher than store.fetchTiddler)

?

Why two implementations to begin with? How many more of these
"duplicates" are there? I think it were good if an article on
tiddlywiki.org explained this.

Cheers, Tobias.

[FND]

> Since we're at it, in what respect is...
> store.removeTiddler a higher level method than store.getTiddler
> (or store.getTiddler higher than store.fetchTiddler)

The high-level getTiddler method uses low-level fetchTiddler:
http://trac.tiddlywiki.org/browser/Trunk/core/js/TiddlyWiki.js?rev=12238#L97
http://trac.tiddlywiki.org/browser/Trunk/core/js/TiddlyWiki.js?rev=12238#L16

Same for deleteTiddler/removeTiddler.

> Why two implementations to begin with? How many more of these
> "duplicates" are there? I think it were good if an article on
> tiddlywiki.org explained this.

It's not unusual to have multiple layers of abstraction. I think Mike
covered some of this:
http://tiddlywiki.org/wiki/Dev:Introduction
http://softwareas.com/tiddlywiki-internals-1-of-3-architectural-concepts

(we might wanna move this conversation to [twdev])

-- F.

[dickon]

OK - this is partially helpful to my 'low-level' needs! I definitely
want to keep the AMBIT name of the space.

(Re. keeping the AMBIT name: The idea is that we will keep the private
areas of this space for conversation in the AMBIT development group,
and for not-yet-finalised drafts of new material for the AMBIT
treatment manual (currently at Peermore), and the Public areas will
host the core draft of the AMBIT treatment manual. Then for each new
service that starts to work along AMBIT lines, they will simply open
their own TiddlySpace, include the AMBIT space in their own space, and
add their own attunements to the AMBIT manual within their own space.)

If I performed the 'remove all plugins' version, as suggested by
Mario, i am not sure which plugins are 'mine' (from MPTW) and which
ones are from TiddlySpace. In the TiddlyWeb at Peermore, if I deleted
all of them, then the core TiddlyWeb ones would merely take over from
the over-writes that I had added - is this the same in TiddlySpace?
i.e. is it OK to remove ALL the plugins, so that the core TiddlySpace
ones are thus 'revealed'?

Dickon

On 20 Sep, 11:03, FND <F...@gmx.net> wrote:
> > Since we're at it, in what respect is...
> > store.removeTiddler a higher level method than store.getTiddler
> > (or store.getTiddler higher than store.fetchTiddler)
>

> The high-level getTiddler method uses low-level fetchTiddler:http://trac.tiddlywiki.org/browser/Trunk/core/js/TiddlyWiki.js?rev=12...http://trac.tiddlywiki.org/browser/Trunk/core/js/TiddlyWiki.js?rev=12...

>
> Same for deleteTiddler/removeTiddler.
>
> > Why two implementations to begin with? How many more of these
> > "duplicates" are there? I think it were good if an article on
> > tiddlywiki.org explained this.
>
> It's not unusual to have multiple layers of abstraction. I think Mike

> covered some of this:http://tiddlywiki.org/wiki/Dev:Introductionhttp://softwareas.com/tiddlywiki-internals-1-of-3-architectural-concepts

[PMario]

On Sep 20, 1:36 pm, dickon <dickon.beving...@gmail.com> wrote:
...

> If I performed the 'remove all plugins' version, as suggested by
> Mario, i am not sure which plugins are 'mine' (from MPTW) and which
> ones are from TiddlySpace.  In the TiddlyWeb at Peermore, if I deleted
> all of them, then the core TiddlyWeb ones would merely take over from
> the over-writes that I had added - is this the same in TiddlySpace?
> i.e. is it OK to remove ALL the plugins, so that the core TiddlySpace
> ones are thus 'revealed'?

You are right. If you delete every plugin. You can only delete
plugins, where you have write access. So your private or public space.
If you duplicated a tiddlysSpace plugin the "original" plugin will
take over. The ones included in MPTW will give macro error output, So
I think it will be easy to get them back.

I'd suggest a ambit-plugins space, that you include into your ambit
working space, to have a central repo for your plugins. So
accidentally deleting a plugin will not happen. same could be done
with theme. eg: ambit-theme included to your working space.

I did some heavy tweaking/deleting at my private/public pmario space
this weekend.

_important_
To be secure I logged in and downloaded a "logged in" version. having
private + public stuff. Then I logged out - download - only public
stuff. So what ever you do, it will be relatively easy to get your
things back. Also deleted mptw plugins.

have fun!
mario
ps: http://yourspace.tiddlyspace.com/?download=yourFileName.html

[dickon]

this is a brilliant thought (to have a separate ambit-plugins space
within my AMBIT Manual space) - I can see that tiddlySpace (like
TiddlyWeb, only moreso) requires a different way of thinking - spaces
within spaces within spaces.

Cheers

Dickon

[Saverio]

Can someone explain this a little more? I am a heavy TW user, light
tiddlyspot user, and new TiddlySpave user. I uploaded my TW to a
TiddlySpace as an experiment, liked it, but kept updating my local
version. Now I am considering doing all my work on the TiddlySpace
version, but i want to replace what is currently there with my most
recently updated local TW. I don't really understand the idea of
putting tiddlers in different spaces, how spaces work with other, and
the relationship of my spaces to other users' spaces. Also, what is
the easiest way just to get my updated local TW onto TiddlySpace.
With www.tiddlyspot it was easy to simply upload and overwrite with a
new version.
thanks.