> Cheers,
> Saq

> --
> Tiddly Learning ( http://lewcid.org ) : TiddlyWiki news, plugins, themes and
> educational usage

>  Welcome to TiddlyWiki created by Jeremy Ruston, Copyright (c) 2007 UnaMesa
> Association
> This page requires JavaScript to function properly.

> If you are using Microsoft Internet Explorer you may need to click on the
> yellow bar above and select 'Allow Blocked Content'. You must then click
> 'Yes' on the following security warning.

>  <!--{{{-->
> <link rel='alternate' type='application/rss+xml' title='RSS'
> href='index.xml'/>
> <!--}}}-->

>  Background: #fff
> Foreground: #000
> PrimaryPale: #8cf
> PrimaryLight: #18f
> PrimaryMid: #04b
> PrimaryDark: #014
> SecondaryPale: #ffc
> SecondaryLight: #fe8
> SecondaryMid: #db4
> SecondaryDark: #841
> TertiaryPale: #eee
> TertiaryLight: #ccc
> TertiaryMid: #999
> TertiaryDark: #666
> Error: #f88

>  /*{{{*/
> body {background:[[ColorPalette::Background]];
> color:[[ColorPalette::Foreground]];}

> a {color:[[ColorPalette::PrimaryMid]];}
> a:hover {background-color:[[ColorPalette::PrimaryMid]];
> color:[[ColorPalette::Background]];}
> a img {border:0;}

> h1,h2,h3,h4,h5,h6 {color:[[ColorPalette::SecondaryDark]];
> background:transparent;}
> h1 {border-bottom:2px solid [[ColorPalette::TertiaryLight]];}
> h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}

> .button {color:[[ColorPalette::PrimaryDark]]; border:1px solid
> [[ColorPalette::Background]];}
> .button:hover {color:[[ColorPalette::PrimaryDark]];
> background:[[ColorPalette::SecondaryLight]];
> border-color:[[ColorPalette::SecondaryMid]];}
> .button:active {color:[[ColorPalette::Background]];
> background:[[ColorPalette::SecondaryMid]]; border:1px solid
> [[ColorPalette::SecondaryDark]];}

> .header {background:[[ColorPalette::PrimaryMid]];}
> .headerShadow {color:[[ColorPalette::Foreground]];}
> .headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
> .headerForeground {color:[[ColorPalette::Background]];}
> .headerForeground a {font-weight:normal;
> color:[[ColorPalette::PrimaryPale]];}

> .tabSelected{color:[[ColorPalette::PrimaryDark]];
>  background:[[ColorPalette::TertiaryPale]];
>  border-left:1px solid [[ColorPalette::TertiaryLight]];
>  border-top:1px solid [[ColorPalette::TertiaryLight]];
>  border-right:1px solid [[ColorPalette::TertiaryLight]];
> }
> .tabUnselected {color:[[ColorPalette::Background]];
> background:[[ColorPalette::TertiaryMid]];}
> .tabContents {color:[[ColorPalette::PrimaryDark]];
> background:[[ColorPalette::TertiaryPale]]; border:1px solid
> [[ColorPalette::TertiaryLight]];}
> .tabContents .button {border:0;}

> #sidebar {}
> #sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
> #sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
> #sidebarOptions .sliderPanel a
> {border:none;color:[[ColorPalette::PrimaryMid]];}
> #sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]];
> background:[[ColorPalette::PrimaryMid]];}
> #sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]];
> background:[[ColorPalette::Background]];}

> .wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid
> [[ColorPalette::PrimaryMid]];}
> .wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
> .wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
> .wizardStep {background:[[ColorPalette::Background]];
> color:[[ColorPalette::Foreground]];
>  border:1px solid [[ColorPalette::PrimaryMid]];}
> .wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
> .wizardFooter {background:[[ColorPalette::PrimaryPale]];}
> .wizardFooter .status {background:[[ColorPalette::PrimaryDark]];
> color:[[ColorPalette::Background]];}
> .wizard .button {color:[[ColorPalette::Foreground]];
> background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
>  border-color:[[ColorPalette::SecondaryPale]]
> [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]]
> [[ColorPalette::SecondaryPale]];}
> .wizard .button:hover {color:[[ColorPalette::Foreground]];
> background:[[ColorPalette::Background]];}
> .wizard .button:active {color:[[ColorPalette::Background]];
> background:[[ColorPalette::Foreground]]; border: 1px solid;
>  border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]]
> [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}

> #messageArea {border:1px solid [[ColorPalette::SecondaryMid]];
> background:[[ColorPalette::SecondaryLight]];
> color:[[ColorPalette::Foreground]];}
> #messageArea .button {color:[[ColorPalette::PrimaryMid]];
> background:[[ColorPalette::SecondaryPale]]; border:none;}

> .popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid
> [[ColorPalette::TertiaryMid]];}

> .popup {background:[[ColorPalette::TertiaryPale]];
> color:[[ColorPalette::TertiaryDark]]; border-left:1px solid
> [[ColorPalette::TertiaryMid]]; border-top:1px solid
> [[ColorPalette::TertiaryMid]]; border-right:2px solid
> [[ColorPalette::TertiaryDark]]; border-bottom:2px solid
> [[ColorPalette::TertiaryDark]];}
> .popup hr {color:[[ColorPalette::PrimaryDark]];
> background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
> .popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
> .popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]];
> border: none;}
> .popup li a:hover {background:[[ColorPalette::SecondaryLight]];
> color:[[ColorPalette::Foreground]]; border: none;}
> .popup li a:active {background:[[ColorPalette::SecondaryPale]];
> color:[[ColorPalette::Foreground]]; border: none;}
> .popupHighlight {background:[[ColorPalette::Background]];
> color:[[ColorPalette::Foreground]];}
> .listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}

> .tiddler .defaultCommand {font-weight:bold;}

> .shadow .title {color:[[ColorPalette::TertiaryDark]];}

> .title {color:[[ColorPalette::SecondaryDark]];}
> .subtitle {color:[[ColorPalette::TertiaryDark]];}

> .toolbar {color:[[ColorPalette::PrimaryMid]];}
> .toolbar a {color:[[ColorPalette::TertiaryLight]];}
> .selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
> .selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}

> .tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]];
> background-color:[[ColorPalette::TertiaryPale]];}
> .selected .tagging, .selected .tagged
> {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid
> [[ColorPalette::TertiaryMid]];}
> .tagging .listTitle, .tagged .listTitle
> {color:[[ColorPalette::PrimaryDark]];}
> .tagging .button, .tagged .button {border:none;}

> .footer {color:[[ColorPalette::TertiaryLight]];}
> .selected .footer {color:[[ColorPalette::TertiaryMid]];}

> .sparkline {background:[[ColorPalette::PrimaryPale]]; border:0;}
> .sparktick {background:[[ColorPalette::PrimaryDark]];}

> .error, .errorButton {color:[[ColorPalette::Foreground]];
> background:[[ColorPalette::Error]];}
> .warning {color:[[ColorPalette::Foreground]];
> background:[[ColorPalette::SecondaryPale]];}
> .lowlight {background:[[ColorPalette::TertiaryLight]];}

> .zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px
> solid [[ColorPalette::TertiaryMid]];}

> .imageLink, #displayArea .imageLink {background:transparent;}

> .annotation {background:[[ColorPalette::SecondaryLight]];
> color:[[ColorPalette::Foreground]]; border:2px solid
> [[ColorPalette::SecondaryMid]];}

> .viewer .listTitle {list-style-type:none; margin-left:-2em;}
> .viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
> .viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}

> .viewer table, table.twtable {border:2px solid
> [[ColorPalette::TertiaryDark]];}
> .viewer th, .viewer thead td, .twtable th, .twtable thead td
> {background:[[ColorPalette::SecondaryMid]]; border:1px solid
> [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
> .viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid
> [[ColorPalette::TertiaryDark]];}

> .viewer pre {border:1px solid [[ColorPalette::SecondaryLight]];
> background:[[ColorPalette::SecondaryPale]];}
> .viewer code {color:[[ColorPalette::SecondaryDark]];}
> .viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]];
> color:[[ColorPalette::TertiaryDark]];}

> .highlight, .marked {background:[[ColorPalette::SecondaryLight]];}

> .editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
> .editor textarea {border:1px solid [[ColorPalette::PrimaryMid]];
> width:100%;}
> .editorFooter {color:[[ColorPalette::TertiaryMid]];}

> #backstageArea {background:[[ColorPalette::Foreground]];

> Although perhaps it would be useful to be able to do that to bring in
> plugin updates.

> I can only second that - very impressive indeed! (And all that in only
> two hours... !?)

> > verification source. Eg: a small file sitting at tiddlywiki.com/latest.js
> > with information like, latest version number, file size, sha-1 hash.

> Sounds good.

> > This could also be used to write a quick and simple plugin that notifies the
> > user when a newer version of TiddlyWiki is available.

> That'd be very cool.

> > Ideally, generating that file would be part of the
> > tw.com production process (it's a bit manual at the moment).

>  From my limited knowledge, I think this could easily be incorporated
> into Cook (as an optional argument, of course).

> >> currently the TiddlyWiki can update itself even if there is not a
> >> newer core version available. A check should be added for this.

> > Although perhaps it would be useful to be able to do that to bring in
> > plugin updates.

> I'm not sure whether the default distro's plugins should be updated
> using the core-upgrade mechanism - sync'ing them just like regular
> plugins might be less confusing.
> Also see this thread:
>      [twdev] official plugin repository
>      http://tinyurl.com/29o95a
> (http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/53c...)

> -- F.

> Saq

> Saq,

> some thoughts about your questions:
> 1) for the first implementation this is probably enough

> 2) I think we should do some kind of verification. For reference the
> tiddlywiki implementation of SHA1 has does about 30K a second, so
> verifying a tiddlywiki file will take a few seconds (acceptable, but
> not ideal)

> 3) won't we get the compatibility checking for the plugins 'for free',
> when they are reloaded after the upgrade?

> Martin

> On 17/03/2008, Saq Imtiaz <lew...@gmail.com> wrote:
> > I'm quite happy to work on this some more if we can get some consensus
> and
> > momentum going.
> > Some things that we need to decide:
> > 1) What kind of a GUI do we want? For the very first iteration do we
> even
> > want anything more than an upgrade button and notification using alerts?
> >  2) Verification. Do we use filesize? SHA1 hash? do we leave hooks for
> the
> > verification and implement it at a later time?
> > 3) What kind of handling/checking do we want when importing content into
> the
> > new file? Compatibility check for plugins? Or do we implement this at a
> > later date too?

> > Saq

> On Mon, Mar 17, 2008 at 6:24 PM, Martin Budden <mjbud...@gmail.com> wrote:

> > Saq,

> > some thoughts about your questions:
> > 1) for the first implementation this is probably enough

> Agreed

> > 2) I think we should do some kind of verification. For reference the
> > tiddlywiki implementation of SHA1 has does about 30K a second, so
> > verifying a tiddlywiki file will take a few seconds (acceptable, but
> > not ideal)

> My other concern with SHA1 verification is that the relevant code is now
> shipped in the CryptoPlugin and we cant safely assume that every TiddlyWiki
> will have it. Filesize verification is probably a good start, but not really
> sufficient.... ideas? We also need to make sure Cook can generate the
> relevant verification file to live on the serverside. As I mentioned in the
> corresponding thread, Cook is unaware of the version number of the
> TiddlyWiki it is cooking. Since this information must be included in the
> verification file, we need to decide how to handle this. Should Cook grep
> this from the version.js file?

> > 3) won't we get the compatibility checking for the plugins 'for free',
> > when they are reloaded after the upgrade?

> Well, it might be nicer to check for compatibility when importing and
> offer to either skip the import of incompatible plugins or fetch upgrades
> from Source slice in the plugin. But this could be part of the PluginManager
> functionality instead.

> Tomorrow I have a packed schedule, but I'll try and submit a patch for
> this on Wednesday.

> Saq

> > Martin

> > On 17/03/2008, Saq Imtiaz <lew...@gmail.com> wrote:
> > > I'm quite happy to work on this some more if we can get some consensus
> > and
> > > momentum going.
> > > Some things that we need to decide:
> > > 1) What kind of a GUI do we want? For the very first iteration do we
> > even
> > > want anything more than an upgrade button and notification using
> > alerts?
> > >  2) Verification. Do we use filesize? SHA1 hash? do we leave hooks for
> > the
> > > verification and implement it at a later time?
> > > 3) What kind of handling/checking do we want when importing content
> > into the
> > > new file? Compatibility check for plugins? Or do we implement this at
> > a
> > > later date too?

> > > Saq

> --
> Tiddly Learning ( http://lewcid.org ) : TiddlyWiki news, plugins, themes
> and educational usage