>
> Currently images are stored as base64 tiddlers, and displayed by creating
>> a data URI: representation on the fly.
>>
>> What is base64 tiddler?
>

Base64 is a way of encoding binary data as text - see
http://en.wikipedia.org/wiki/Base64

Base64 tiddlers use base64 encoding to store binary data.

You can see an example by doing a view-source on
http://five.tiddlywiki.comand searching for the word "photostream";
you'll end up at the point in the
file where the image tiddler "Motovun Jack.jpg" is stored.


> Do you mean TW5? If so, yes, that's the idea: I'd like TW5 to have decent
>> integrated bitmap and SVG sketching and annotation.
>>
>>
> No, as I understand in TW5 that would be a default instrument, I was
> asking about TW2: is there any limitations to reproduce something similar
> in there?
>

Image editing could be integrated with TW2, but there'd be a bunch of
required changes rippling out: storing and displaying image tiddlers being
the primary one.


> Unfortunately, I can't see many possibilities for me to use TW5 in the
> nearest future, at least until I create a version of SharedTiddlersPlugin
> for TW5 which should take a good amount of time, I guess. The reason is I'm
> continually customizing my wikis and there's a bunch of them. Applying the
> same changes to each is a nightmare, so I really need STP + other plugins
> (which probably won't work with TW5). But image editing within TW would be
> a great feature, especially with touchscreens, for sketches etc.
>

Indeed, moving complex existing TW2 projects over will not be easy.

Thanks for the questions, do keep them coming.
>>
>> The questions regarding encryption are much the same:
>
> * how encrypted tiddlers are stored?
>

Encrypted tiddlers are stored as a block of encrypted text within the
tiddlywiki file. You can see an example by visiting
http://five.tiddlywiki.com/encrypted.html. You can decrypt the file with
the password "password". If you view-source and search for the first
occurance of "encryptedStoreArea" you'll see the encrypted text as a string
of gobbledegook.


> * how are they accessed? can only some tiddlers be encrypted while others
> are not?
>

The way things are set up at the moment all non-system tiddlers are
encrypted. It's certainly possible to configure things so that only a
subset of tiddlers are encrypted, but I took the view that the default
installation should have conservative, safe defaults.

The presence of encrypted tiddlers in the HTML file causes the prompt the
user for a password before decrypting the tiddlers and continuing the boot
process.


> * it there any issues that would prevent implementing such engine in TW2?
> I tried EncryptedVaultPlugin from [1] but it has problems with non-latin
> letters.. there's also EncryptionCommandsPlugin from [2] which I still
> haven't figured how to use, although reviewing it today made much more
> sense than some months ago. Encryption for TW2 is still an issue for me.
>

You could certainly look at incorporating the Stanford JavaScript Crypto
Library into TW2. Again, there'd be a large number of changes around
decrypting the content at boot-time and encrypting it again when saving.


>
> These questions will help understanding TW5 and differences between TW2
> and TW5, too. Honestly, I can't understand much in the TW5 repository using
> my knowledge about TW2 repository and source files structure, I have to
> dig, guess, explore again to understand it which is a big barrier. Neither
> I have any hints of how much the new js codes are different from the old
> ones. Even tiddler.js [3] is far from what I expected to see (you know,
> methods from [4]..)
>

TW5 is a very different beast than TW2, at least in terms of how it is
implemented. A key motivation to begin TW5 was to be able to reverse some
of the constriction stemming from poor design choices right at the
beginning of TW. The good thing is that TW5 is much simpler to understand
than the old code. TW2 is full of inscrutable global variables, fragile
mechanisms, and poorly designed APIs. TW5 is strictly modular, eschews
global variables, and reads like modern JavaScript code.

The key to understanding how TW5 works is to study the boot process. The
code in boot/boot.js is the first thing that runs (both in the browser and
under node.js). It sets up just enough of a TiddlyWiki environment as
pluggable modules, which are stored in the core/modules directory in the
repo.

Comparing the two tiddler.js files is interesting: the missing piece on the
TW5 side is that the $tw.Tiddler constructor and main methods live in
boot.js. Tiddler.js is just a bunch of extension methods that are added to
the $tw.Tiddler prototype.

You might also find it useful to explore the $tw global variable in your
JavaScript console, drilling into the various members.

Best wishes

Jeremy





>
> Best regards,
> Yakov.
>
> [1] http://visualtw.ouvaton.org/VisualTW.html
> [2] http://martinswiki.com/#EncryptionCommandsPlugin
> [3]
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/tiddler.js
> [4] https://github.com/TiddlyWiki/tiddlywiki/blob/master/js/Tiddler.js
>
>
>> Best wishes
>>
>> Jeremy
>>
>>
>>>
>>> Best regards,
>>> Yakov.
>>>
>>> суббота, 23 марта 2013 г., 23:17:38 UTC+4 пользователь Jeremy Ruston
>>> написал:
>>>>
>>>> I've made a screencast introducing TiddlyWiki5 and showing how to use
>>>> it:
>>>>
>>>> http://vimeo.com/62508140
>>>>
>>>> I'd appreciate any feedback, particularly as I intend to make further
>>>> screencasts as TW5 nears beta.
>>>>
>>>> My feedback from making it is that 13 minutes might be too long;
>>>> cleaning up and editing took a long time, and I suspect that I'd be
>>>> more productive trying to do more frequent shorter videos.
>>>>
>>>> Cheers,
>>>>
>>>> Jeremy
>>>>
>>>>
>>>> --
>>>> Jeremy Ruston
>>>> [email protected]
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>>
>>> Visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Jeremy Ruston
>> mailto:[email protected]
>>
>

-- 
Jeremy Ruston
mailto:[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to