On Sep 26, 4:18 pm, Xavier Verges <
xver...@gmail.com> wrote:
> This is cool. Can stuff be deleted/edited?
The functionality is there, but the path to it is a bit less
straightforward than I would like (suggestions on how to improve most
welcome).
Basically, every twote you make is placed into a storage location
(based on your user name). You can view the list of twotes by the
links on the /twoter/{username} page and click on them to get an HTML
rendering. From that list page there is also a link that allows you to
load the twotes up into a TiddlyWiki. Inside that TiddlyWiki you can
edit the content in all the usual Tiddly ways and an included plugin
(TiddlyWebAutoSavePlugin and TiddlyWebAdaptorPlugin) will save your
changes to the server (if you're connected to the net).
There's no UI for deleting but TiddlyWeb will let you delete content
by sending a DELETE to the canonical URL of the tiddler. This is based
on the name of the bag and the title of the tiddler. For a tiddler
with name 'Logs' in my storage the url is:
http://tiddlyweb.appspot.com/bags/chris_dent-all/tiddlers/Logs
Ideally there would be support for delete in the TiddlyWiki that is
generated by the system. This hasn't happened yet, in part because
I've been focused on making TiddlyWeb and not on making TiddlyWiki
plugins. If people are interested, I'd love some help. Things that are
needed are:
* An easy way to delete tiddlers out of a selected bag.
* A nice interface for controlling access to content. Right now things
are setup so that only you have any access to your content. It doesn't
have to be like this, stuff can be shared (based on what are called
Policies on storage Bags).
* A more scrumptious style for the generated TiddlyWiki. Right now it
is the default, which is a bit tired and not particularly suited to
the twoter use case.
* The bookmarklet working for IE.
Longer term there are going to be some scaling issues which will need
to be addressed. Right now each person's twotes goes into just one
container, which could get huge over time.
> I'm puzzled, though. The bookmarklet code does not work for me. Live
> HTTP headers does not show any activity, and no complain goes to the
> console.
>
> However, if I edit the javascript in there and remove the
> iframe.style.display='none';
> thing work ok... Firefox 2.0.0.17
That's really odd. I've only tested on Safari and Firefox (somewhere
in the version 3), but in my testing I did find that the silliest
little tweaks would make things blow up. It's fragile stuff.