[tw] Re: Revised Default Theme for TiddlySpace
The current version looks much better. Great job! That's great news, glad you like it. I'll try address some of your points below... One thing I immediately found better looking was to reduce the sidebar border to only 2px instead of 3px. Fair enough, I think this sort of thing really is down to personal preference. I set the width of the border to 3px so that it matched the line that separates the tiddlers. I tried having both thinner but felt that the tiddler divider wasn't visually strong enough at that width so therefore made it 3px with the sidebar border matching. Some more thoughts... A) Why do confirmation popups look different from the default popup message? Also, the public / private buttons are too small! There are still a few things that need modifying/tweaking and this seems to be one of them. Thanks for pointing it out. B) TiddlyWiki already comes with quite a bit of StyleSheetOverhead already making it difficult at times to find the right spot or to undo all the preapplied styling. With lattice there seem to be even more and way too many StyleSheetsThisAndThats. This makes the situation somewhat worse rather than better for TiddlySpace... from my point of view. Agreed, I have also had similar issues but now I will be looking to refactor, optimise and reduce the amount of CSS and the number of stylesheet tiddlers. It does need to be more manageable. C) Please, no word-wrap:break-word in the tabsets or anywhere else... Who even invented that? Hyphenation, anyone? Or, abbreviat...? ;o) I'll get on that too :) D) I find the margins left to the tiddlerDisplay and right to the sidebar to be quite a waste of real-estate. Think of people using iframes or screenshots or photo collections in their tiddlers. I'm afraid this is where I have to disagree with you (although there does seem to be 2 distinct camps), I am a firm believer in trying to make a site as usable and readable as possible. There is solid research that suggests people experience greater cognitive load and find it harder to read lines of text that are greater than 10-15 words long. This is a rule of thumb that is widely used in print media, like books, and becomes even more important when text is on screen. Using this as a baseline, whilst trying to utilise the space as efficiently as possible I decided on the current set up (in an ideal world I would even attempt to shorten the text lines further :) ). Using a standard font size with a resolution of 1280x800 the current tiddler width results in around 22-27 words. At a resolution of 1024x768 it results in around 12-16 words. With the margins reduced you start to get upwards of 30 which becomes harder to read. E) The buttons jump around when being hovered ...set a transparent border to the non-hovered buttons. Also, the gradient does not work properly, not even in FF. Or is it not supposed to? Ok, I'll check that out too. Eventually, I fiddled a bit more with the looks... http://latticetest.tiddlyspace.com Though I tend to sound rather critical ...all in all, this is a real neat theme! Not a problem, this sort of discussion is real good to have. Once again thanks for the comments. I'll carry on iterating and hopefully we'll solve some of the issues. Cheers, Colm -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Opening a new browser tab
Hi Craig To make a form open a new tab I think you need to include something like this in the html for the submit button. input type=submit value=Google Search onclick=this.form.target='_blank';return true; / Let me know how you get on Colm On Sep 28, 2:21 pm, Craig in Calgary craig.prich...@gmail.com wrote: I have this code in a tiddler: {{{ html form method=get action=http://www.google.com/search; div style=border:1px solid black;padding:4px;width:20em; table border=0 cellpadding=0 trtd input type=text name=q size=25 id=q maxlength=255 value= / input type=submit value=Google Search //td/tr trtd align=center style=font-size:75% input type=checkbox name=sitesearch value=groups.google.com checked / Only search Google Groupsbr / /td/tr/table /div/form/html }}} Two (2) questions: when it executes I would like the resulting page to render in a new: * browser tab, not in the same tab as my TiddlyWiki and/or * tiddler or shadow tiddler (like PluginInfo does) What needs modification? Thank you. Craig -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Revised Default Theme for TiddlySpace
Some thoughts: * In GettingStarted the mentions of TiddlySpace are dead linkl. Unfortunate for a 'core' TW, not to mention for the welcoming tiddler. * Also, on the GettingStarted it reads MainMenu [...] on the *left* * The SiteIcon name/upload fields are not elegantly laid out, unevenly like that. * Great first impression of the color scheme, but the tabs box is another color. Would look better if the gradient comes from same blue. * (...and the *default* colors for edit mode are a bit funny, most of all too dark) * (BTW, am I the only one always getting Error saving ColorPalette: Forbidden unless manually open into edit mode and saving? Perhaps an issue for a separate thread.) * Also the Following bubble would look better if lighter. * That gradient box could be used as the separator between tiddlers instead of the thin but dark blue line currently seen on the top of the tiddlers. The tabs box could have the gradient going from blue (at bottom) to white, omitting the need for a top separator. * (Since you're positive to using gradients for the tabs, perhaps the whole top field or the MainMenu could be a (vertical) gradient? Design wise core TW has always been a bit stiff so a gradient here makes it a little more designy but still neutral.) * The search box could be a little further down (e.g as in Tobias demo). :-) On Sep 28, 7:20 pm, colmjude colmj...@gmail.com wrote: Thanks for all the great feedback. I've been revising lattice with that in mind: http://lattice.tiddlyspace.com/ My main aim was to clean up the UI whilst continuing to display all the features tiddlyspace has to offer. I've tried to exhibit all that tiddlyspace has to offer at the present and I will continue to optimise it as it matures. It doesn't introduce any new theming conventions so it should still be super easy to take this theme and make it your own, in whatever way you please. In fact, it would be great if you did that so that there is a whole host of themes available for new users to choose from. Osmosoft are planning to deploy this tomorrow which will affect some of the tiddlers in the system-theme space. For those of you wishing to add your own touches there will be one new tiddler, called StyleSheetColattice. When it gets deployed Osmosoft will provide details on a way to opt out of it for those that want to. Please take a look and let me know what you think, plus get in touch if you foresee any issues with the deployment. Colm -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Macro Error in Trying to Write a Form Inside a Tiddler
Tobias -- Thanks for the tips (and code)! The most important question is: In what context do you want to use this? Do you really want to output a table or would you rather want to provide a count for the length of any input element's value? ...which is what the following does using a bunch of jQuery statements: http://pastebin.com/CgCwt7Rx That is SO much more elegant than my cobbled-together plugin (using a free character-counting script I picked up years ago) -- but I'm trying to eliminate the HTML inside a tiddler. What I'm shooting for a plugin that will allow a technophobic user to type characterCounter into a tiddler and (voila!) have an input area they can type or paste into for counting characters (in view mode). I've posted the one I'm using into a stripped-down TW at TiddlyWiki [dot] Secret-HQ [dot] com -- but I don't want to spread it around too much, since I don't want to be responsible for folks downloading half- baked plugins. ;) In general. Do not put forms as strings into your macro or plugin. Instead put templates into a dedicated tiddler or section (of your plugin) and get it's content in the macro like so... template=store.getTiddlerText('MyTemplateTidler##TemplateSection'); Invoking template sections that way is new to me. I'll start digging momentarily, but here are my immediate questions: How do I define the template section in the tiddler? Just with an H1- level header, like this ... ? /*** !MyPlugin ***/ //{{{ code code code //}}} /*** !Defining the Macro ***/ //{{{ code code code //}}} /*** !OutputTemplate ***/ //{{{ the HTML for the form I want to print inside the tiddler //}}} And how do I call that from the macro? Like so ... ? createTiddlyElement(place,div,divId,class,template); (I suspect that I'm oversimplifying that last bit -- but I'm off to try it out and see!) Thanks for the tips and patience in 'splaining everything. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Opening a new browser tab
You can also get away with just adding target=_blank to the form parameters: form method=get action=http://www.google.com/search; target=_blank -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] Re: Revised Default Theme for TiddlySpace
Thanks for the feedback everyone. We're shortly going to go live with the lattice theme. Chris and Fred are going to do the update shortly. If you'd prefer to stay with the older theme, you can simply include the new-eee space into your space. You can do that now, in advance of the change. Going forwards, we'd like to keep refining and improving the base theme in response to feedback, hopefully with regular updates. Best wishes Jeremy On Wed, Sep 29, 2010 at 12:37 PM, twgrp matiasg...@gmail.com wrote: Some thoughts: * In GettingStarted the mentions of TiddlySpace are dead linkl. Unfortunate for a 'core' TW, not to mention for the welcoming tiddler. * Also, on the GettingStarted it reads MainMenu [...] on the *left* * The SiteIcon name/upload fields are not elegantly laid out, unevenly like that. * Great first impression of the color scheme, but the tabs box is another color. Would look better if the gradient comes from same blue. * (...and the *default* colors for edit mode are a bit funny, most of all too dark) * (BTW, am I the only one always getting Error saving ColorPalette: Forbidden unless manually open into edit mode and saving? Perhaps an issue for a separate thread.) * Also the Following bubble would look better if lighter. * That gradient box could be used as the separator between tiddlers instead of the thin but dark blue line currently seen on the top of the tiddlers. The tabs box could have the gradient going from blue (at bottom) to white, omitting the need for a top separator. * (Since you're positive to using gradients for the tabs, perhaps the whole top field or the MainMenu could be a (vertical) gradient? Design wise core TW has always been a bit stiff so a gradient here makes it a little more designy but still neutral.) * The search box could be a little further down (e.g as in Tobias demo). :-) On Sep 28, 7:20 pm, colmjude colmj...@gmail.com wrote: Thanks for all the great feedback. I've been revising lattice with that in mind: http://lattice.tiddlyspace.com/ My main aim was to clean up the UI whilst continuing to display all the features tiddlyspace has to offer. I've tried to exhibit all that tiddlyspace has to offer at the present and I will continue to optimise it as it matures. It doesn't introduce any new theming conventions so it should still be super easy to take this theme and make it your own, in whatever way you please. In fact, it would be great if you did that so that there is a whole host of themes available for new users to choose from. Osmosoft are planning to deploy this tomorrow which will affect some of the tiddlers in the system-theme space. For those of you wishing to add your own touches there will be one new tiddler, called StyleSheetColattice. When it gets deployed Osmosoft will provide details on a way to opt out of it for those that want to. Please take a look and let me know what you think, plus get in touch if you foresee any issues with the deployment. Colm -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en. -- Jeremy Ruston mailto:jer...@osmosoft.com http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Macro Error in Trying to Write a Form Inside a Tiddler
We ... It looks like I can do this by creating a template for my character counter box and transcluding it anywhere with tiddler CharacterCounterPluginTemplate -- but that still means I've got two tiddlers to hand off to anyone who wants to use it (the plugin and the template). Looking at some other plugins, it struck me that I might be able to define the template as a shadow tiddler within the plugin and then call that shadow tiddler with a macro. I couldn't QUITE figure out how to do that -- as simple as it sounds -- but I COULD use wikify(string,place) to print out a call to the tiddler macro and transclude the shadow tiddler with my form into it. Weird solution, maybe -- but I'm quite happy with it! Once I clean up, I'll post it somewhere and share the link in case anyone wants to have a look. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Macro Error in Trying to Write a Form Inside a Tiddler
Hi again, Secret-HQ, Instead of rendering the template text itself into a div with... createTiddlyElement(place,div,divId,class,template); ...you would rather create the element and then wikify the template into it... wikify( template, createTiddlyElement(place,div,divId,class) ); As for the section in your plugin, I would put it this way if you didn't want to see it in your rendered macro... /*** /% !OutputTemplate htmlformform-contents/form/html !EndTemplate%/ ***/ As for the one on pastebin... did you get it to work for you? It does what you want your characterCounter to do... only just it's called chrCount and requires you to somewhat specify the element for which you want to count the text-length. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Revised Default Theme for TiddlySpace
Going forwards, we'd like to keep refining and improving the base theme in response to feedback, hopefully with regular updates. I think that's a good idea and general philosophy. Plugin or theme authors may extend their contents and thus automatically extend the spaces including them ...even if at the risk of breaking stuff here and there ...assuming minor consequences or at least information as to why the changes and how to adapt. At least, that's the kind of flexible and iterative approach I would find to be the most agile, hence fruitful. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] AttachFilePlugin link behavior
Hi, Eric's AttachFilePlugin (http://www.TiddlyTools.com/#AttachFilePlugin) seems the perfect way to connect TWs with PDF articles stored sometimes locally, sometimes online, sometimes both. I love the fallback behavior that makes this seamless. But, I have a questions about how the links to the attachment tiddlers behave. If I have an attachment tiddler for a document, let's say Smith2009, then the ordinary TiddlyLink syntax [[Smith's important article|Smith2009]] immediately opens the article. But, I would also like to be able to use an icon to jump to the article. So I expected that the syntax [img[Click to open article|docIcon][Smith2009]] would also directly open the article when clicked. But, the icon in this case only opens the attachment *tiddler*, not the attached file. The behavior is the same for the samples at tiddlytools.com, so I'm wondering if it's the intended behavior--and if so, is there some adjustment to the syntax that would go right to the attached file? Thanks, Jon -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] closing PopupMacro's popup window with a second click
How can I make SaqImtiaz's PopupMacro (http://tw.lewcid.org/ #PopupMacro) close the popup window when the button is clicked a second time? -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.