[twdev] Re: Output: image macro vs [img[]]
Hi Jon, Your fixes seem to do the work [1]. At least for me. But they didn't make it to the core yet. Is there a reason for that? thx -m [1] http://fancybox.tiddlyspace.com/#Example_ImageMacro On Jan 28, 10:23 am, rakugo jdlrob...@gmail.com wrote: Fixed:https://github.com/jdlrobson/TiddlyWiki/commit/66628e15c31d46218e09ed... Jon On Jan 27, 2:06 pm, PMario pmari...@gmail.com wrote: On Jan 27, 2:11 pm, rakugo jdlrob...@gmail.com wrote: I've moved this to githttps://github.com/jdlrobson/TiddlyWiki/commit/adb823d8db964d9535b090... You used 2 times imageLink, is that right, or should there be an externalLink and imageLink? Just need to update TiddlySpace to point to..https://github.com/jdlrobson/TiddlyWiki/raw/master/plugins/ImageMacro... Cool, Thx for responding that fast -m -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
[twdev] Re: Proposal: Migrate TiddlyWiki core dev to GitHub
On Feb 1, 10:08 pm, Tobias Beer beertob...@googlemail.com wrote: Somewhere along this thread I read that the discussion is about some +-300 active issues. I would suggest that someone (preferably @Osmosoft) took a few days to browse through them... prioritize the issues (by a beforehand agreed upon evaluation scheme) - see Martin's points - and move whatever is deemed important enough to the new system ...not waiting for anyone else - perhaps new to tw-and-its- shiny-new-git-thingy - to be searching through abandoned (trac) archives for some unresolved backlogs. I agree with this apart from the Osmosoft doing this. We are an open source project and should act like it. The issues list is quite simply too big. As Martin points out some of those issues have changes that will break backwards compatibility, these are not actionable and should be recorded somewhere other than an issues list. A developer wiki or some other system. What might be a good idea is to collaboratively as a community review these trac tickets. We could imagine setting up a TiddlySpace which has imported all the trac tickets where any registered member (or any interested TiddlyWiki community member) can review the tickets CREATE/ AMEND but not DELETE. We could imagine using conventions such as adding a tag discard, needswork or keep to each of these tickets. After this process any tagged discard, we delete, any that have been tagged needswork are improved, any tagged keep are migrated to github. I think a transparent review system like the above will help here. Thoughts? -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
[twdev] possible encode bug in cookies, 2.6.2
HI, I've encountered something that seems to be a bug. The trac site told me it's better to post it here first instead of a ticket. Opera 11.01 does not save settings in a cookie on a local file. After browsing the source it seems that encoding of the cookie value have been removed with changeset 12623 in options.js, function saveCookie(). Right now it seems to me that this piece of code tries to save an invalid cookie: the cookie value either has to be a token or a quoted-string according to the RFC. The return value of String.encodeHashMap(cookies) is however, full of quotation marks, whitespaces and other strange things. Shouldn't it be urlencoded and quoted in order to be compliant? Regards, Gábor Várnagy -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
Re: [twdev] possible encode bug in cookies, 2.6.2
Hi Gábor Thanks for the note, we will investigate and report back, Cheers Jeremy 2011/2/2 Gábor Várnagy gabor.w.varn...@gmail.com: HI, I've encountered something that seems to be a bug. The trac site told me it's better to post it here first instead of a ticket. Opera 11.01 does not save settings in a cookie on a local file. After browsing the source it seems that encoding of the cookie value have been removed with changeset 12623 in options.js, function saveCookie(). Right now it seems to me that this piece of code tries to save an invalid cookie: the cookie value either has to be a token or a quoted-string according to the RFC. The return value of String.encodeHashMap(cookies) is however, full of quotation marks, whitespaces and other strange things. Shouldn't it be urlencoded and quoted in order to be compliant? Regards, Gábor Várnagy -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. -- Jeremy Ruston mailto:jer...@osmosoft.com http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
Re: [twdev] Re: Proposal: Migrate TiddlyWiki core dev to GitHub
The primary practical point under discussion is whether the existing tickets should be transferred from Trac into GitHub's issue system. I share Chris's concern that this is a potentially big job to automate, and I would find it hard to justify undertaking it. I would favour freezing Trac and Subversion, without making any attempt at an automated transfer of information, and encourage individuals to raise new tickets for the issues that are fixable, given Martin's criteria above. Cheers Jeremy On Wed, Feb 2, 2011 at 2:46 PM, rakugo jdlrob...@gmail.com wrote: On Feb 1, 10:08 pm, Tobias Beer beertob...@googlemail.com wrote: Somewhere along this thread I read that the discussion is about some +-300 active issues. I would suggest that someone (preferably @Osmosoft) took a few days to browse through them... prioritize the issues (by a beforehand agreed upon evaluation scheme) - see Martin's points - and move whatever is deemed important enough to the new system ...not waiting for anyone else - perhaps new to tw-and-its- shiny-new-git-thingy - to be searching through abandoned (trac) archives for some unresolved backlogs. I agree with this apart from the Osmosoft doing this. We are an open source project and should act like it. The issues list is quite simply too big. As Martin points out some of those issues have changes that will break backwards compatibility, these are not actionable and should be recorded somewhere other than an issues list. A developer wiki or some other system. What might be a good idea is to collaboratively as a community review these trac tickets. We could imagine setting up a TiddlySpace which has imported all the trac tickets where any registered member (or any interested TiddlyWiki community member) can review the tickets CREATE/ AMEND but not DELETE. We could imagine using conventions such as adding a tag discard, needswork or keep to each of these tickets. After this process any tagged discard, we delete, any that have been tagged needswork are improved, any tagged keep are migrated to github. I think a transparent review system like the above will help here. Thoughts? -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. -- Jeremy Ruston mailto:jer...@osmosoft.com http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
[twdev] Small proposal: cosmetic vanilla TW improvments.
Hi. Recently, I've noticed a few things that look like it's proper to improve in vanilla TW. Namely: 1. hide the lists in SideBarTabs into a slider. It is always looks beatiful when there's an index slider there; and I've never met this good without it. Some sites made with TW but not TiddlySpace has those down-to-the-bottom-and-even-more-below-timelines and this never looked good. 2. add ~ to the ViewToolbar and EditToolbar slicenames in ToolbarCommands. Well, it's quite cosmetic thing, but those ViewToolbar and EditToolbar appears in missing tabs each time a user changes this shadow tiddler in a new TW. 3. add references in EditToolbar slice. This is somewhat arguable, but until the link binding is not established (see [1]) 4. add deleteTiddler in the ViewToolbar slice. There's usually no need to go to the edit mode to delete a tiddler. However, I don't mean that it should be removed from EditToolbar slice. Best wishes, Yakov. [1] http://groups.google.com/group/tiddlywikidev/browse_thread/thread/05995a23c80d3d42, search the page for the first mentioning of link binding -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
[twdev] Re: Proposal: Migrate TiddlyWiki core dev to GitHub
@rakugo, I quite like your trains of thoughts here and would sure welcome the effort... a simple TiddlySpace of that sort might just start out with a list of all (open?) tickets. People who cared enough would then somewhat 'grab' them, evaluate them and transfer them if so desired - keeping Martin's suggestions in mind - while also being able to get a feel for which issue has already been dealt with (in terms of migration to git) and which hasn't. Although (if not because) this might put the opensource idea quite to the test, I think your suggestions make a lot of sense. However, I would still favour that anything which during the process indeed were to be transferred to git should be removed from the trac archives ...unless only some part of the ticket that has been deemed essential by the person reviewing it was to be transferred. Eventually, reduncancies hardly ever are anything but cumbersome when it comes to tracking issues. So, if there is a communal effort to sort out remaining tickets... there should be someone with administrative access to the archives who will remove anything from trac that got transferred during the process. Also it might turn out beneficial to point from a trac ticket to a new git ticket once the latter is being created and - for reference purposes - vice versa. Cheers, Tobias. On 2 Feb., 15:46, rakugo jdlrob...@gmail.com wrote: On Feb 1, 10:08 pm, Tobias Beer beertob...@googlemail.com wrote: Somewhere along this thread I read that the discussion is about some +-300 active issues. I would suggest that someone (preferably @Osmosoft) took a few days to browse through them... prioritize the issues (by a beforehand agreed upon evaluation scheme) - see Martin's points - and move whatever is deemed important enough to the new system ...not waiting for anyone else - perhaps new to tw-and-its- shiny-new-git-thingy - to be searching through abandoned (trac) archives for some unresolved backlogs. I agree with this apart from the Osmosoft doing this. We are an open source project and should act like it. The issues list is quite simply too big. As Martin points out some of those issues have changes that will break backwards compatibility, these are not actionable and should be recorded somewhere other than an issues list. A developer wiki or some other system. What might be a good idea is to collaboratively as a community review these trac tickets. We could imagine setting up a TiddlySpace which has imported all the trac tickets where any registered member (or any interested TiddlyWiki community member) can review the tickets CREATE/ AMEND but not DELETE. We could imagine using conventions such as adding a tag discard, needswork or keep to each of these tickets. After this process any tagged discard, we delete, any that have been tagged needswork are improved, any tagged keep are migrated to github. I think a transparent review system like the above will help here. Thoughts? -- You received this message because you are subscribed to the Google Groups TiddlyWikiDev group. To post to this group, send email to tiddlywikidev@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
