[tw] Re: Announcing Tiddlywiki 2.5.2
+1 for this: "[...]little applications as demonstration models for people to try and see some of the advantages. 2009/7/8 Morris Gray : > > On Jul 8, 8:34 am, wolfgang wrote: > >> Thanks for your efforts to create consent. But if there is passion for >> a slim, stable legacy TiddlyWiki - where jQuery remains optional - >> developer will step up and your team can concentrate on your task >> without becoming unnecessarily diverted. I agree with Saq, that if the >> core remains perceived the sole responsibility of Osmosoft, this very >> fast could lead to a dangerous situation.. > > I swore I would comment no more on this subject on the Developers > group. When it comes to this subject it is like talking into the > wind. So before I go back to trying to make practical applications > for TiddlyWiki I'll just say this. > > I'm not sure if there are enough worldly wise people here to see the > unraveling of a cohesive group taking place. An unraveling that can > easily slide into a lowering of moral and dampening enthusiasm for > both users and developers. > > The seeds to this potential unraveling were sown when the decision was > made to drastically change the TiddlyWiki core and subject all users > to the vagueness of unfinished software on a regular basis for months > or years. > > For the core developers it can be demoralizing because they will feel > unappreciated. The fear of bringing an avalanche of criticism with > each bug, not to mention breaking favourite plugins, will slow > development and quell enthusiasm for them. > > Users who long for a stable platform to get real-world applications > done will balk at every disruption to their progress and the extra > uncertainty and distracting discussions that follow. > > The hard-headed unwavering decision to ignore having a continuing > stable platform while continuing with a drastic revamp of the core > without having defined separate branches is dangerous. It will create > a de facto set of branches anyhow but more importantly it will put > users and developers into two separate camps. > > The argument that users need not follow the the upgrades is a weak one > indeed for it actually fosters those de facto branches mentioned > above. What choice does that leave users, to go out on a limb that > that has been sawed off behind them, or follow the uncertain path > development that doesn't really know where it's going. > > The natural flow of TiddlyWiki being improved and tweaked with each > new release will be broken by changing fundamental core functions and > if continued will created a separate branch whether you admit it or > not. How can any application developer feel their product is reliable > enough to be released to the world knowing that the next time their > user upgrades the core something might break. > > The changes to the core using jQuery is a good one, holding great > promise. If it is continued as a separate development it will cause > no disruption. People will be eager to follow its progress and help > with the testing and will be drawn to it through curiosity, and > concern they may be left behind, instead of considering it a threat. > > Whatever extra work separate branches create, whatever extra time it > takes is worth it because the real or imagined uncertainties of not > doing so will slow its progress even more, or worse divide and lose > both developers and users along the way. > > If I was 'in the same room' as you I would emphatically say this - for > it will cost you nothing and you will gain much > > Take the 2.5.x development out of the backstage upgrade path to foster > certainty for users. > > Continue the jQuery core development with enthusiasm and vigor. Make > regular announcements in both groups of new releases. > > But with one addition. Take the time to also develop little > applications as demonstration models for people to try and see some of > the advantages. > > This will give you the testers you need, force you to actually test > and document some of the new additions you've made as you go and give > people ideas of how they can be used. Then when the time comes to make > the switch there will already be enthusiastic users and developers, > already knowledgeable and comfortable, to take advantage of it. > > The time to put version 2.5.x into the backstage upgrade path will > occur naturally, you will know with certainty when it is the right > time, you will have loyal followers and it may actually be demanded by > popular acclaim. > > That's how separate development paths can actually draw people > together instead of one that would divide them. > > Morris Gray > > > > > > > > > > > > > > > > On Jul 8, 8:34 am, wolfgang wrote: >> Sorry to everyone with a short attention span for this long post. One >> could also proceed to the last paragraph, to get the gist. >> >> > To be clear, there have been three changes associated with jQuery: >> >> > - the inclusion of the jQuery library by default; this i
[tw] Re: excel spread sheet that runs in a tiddler ????
I think you may need something to get inline HTML to work; Than put this in your tiddler http://url"; frameborder="0" width="100%" height="600"> Now go to a Google Docs document and open it. Then Copy its address from the browser address line and place it in the place above "http://url";. This may have problems but it looks good, test fully. Closing and exiting the GoogleDoc seems to break out of tiddlywiki. However it may be a lead. TonyM If you have not found an easy way to do it with TiddlyWiki, you have missed something. www.tiddlywiki.com On Sun, Jul 5, 2009 at 15:50, Greg wrote: > > I have a spread sheet that does some statistical calculations for > educationl researchers. I want user to actaully be able to run the > spreadsheet in the tiddler. I have the spreadsheet located in my > google docs directory. I am able to embed it and it is static, but I > want to find out how users can actaully run it. Is this possible? > > thanks > > Dr.Code > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: Announcing Tiddlywiki 2.5.2
On Jul 8, 8:34 am, wolfgang wrote: > Thanks for your efforts to create consent. But if there is passion for > a slim, stable legacy TiddlyWiki - where jQuery remains optional - > developer will step up and your team can concentrate on your task > without becoming unnecessarily diverted. I agree with Saq, that if the > core remains perceived the sole responsibility of Osmosoft, this very > fast could lead to a dangerous situation.. I swore I would comment no more on this subject on the Developers group. When it comes to this subject it is like talking into the wind. So before I go back to trying to make practical applications for TiddlyWiki I'll just say this. I'm not sure if there are enough worldly wise people here to see the unraveling of a cohesive group taking place. An unraveling that can easily slide into a lowering of moral and dampening enthusiasm for both users and developers. The seeds to this potential unraveling were sown when the decision was made to drastically change the TiddlyWiki core and subject all users to the vagueness of unfinished software on a regular basis for months or years. For the core developers it can be demoralizing because they will feel unappreciated. The fear of bringing an avalanche of criticism with each bug, not to mention breaking favourite plugins, will slow development and quell enthusiasm for them. Users who long for a stable platform to get real-world applications done will balk at every disruption to their progress and the extra uncertainty and distracting discussions that follow. The hard-headed unwavering decision to ignore having a continuing stable platform while continuing with a drastic revamp of the core without having defined separate branches is dangerous. It will create a de facto set of branches anyhow but more importantly it will put users and developers into two separate camps. The argument that users need not follow the the upgrades is a weak one indeed for it actually fosters those de facto branches mentioned above. What choice does that leave users, to go out on a limb that that has been sawed off behind them, or follow the uncertain path development that doesn't really know where it's going. The natural flow of TiddlyWiki being improved and tweaked with each new release will be broken by changing fundamental core functions and if continued will created a separate branch whether you admit it or not. How can any application developer feel their product is reliable enough to be released to the world knowing that the next time their user upgrades the core something might break. The changes to the core using jQuery is a good one, holding great promise. If it is continued as a separate development it will cause no disruption. People will be eager to follow its progress and help with the testing and will be drawn to it through curiosity, and concern they may be left behind, instead of considering it a threat. Whatever extra work separate branches create, whatever extra time it takes is worth it because the real or imagined uncertainties of not doing so will slow its progress even more, or worse divide and lose both developers and users along the way. If I was 'in the same room' as you I would emphatically say this - for it will cost you nothing and you will gain much Take the 2.5.x development out of the backstage upgrade path to foster certainty for users. Continue the jQuery core development with enthusiasm and vigor. Make regular announcements in both groups of new releases. But with one addition. Take the time to also develop little applications as demonstration models for people to try and see some of the advantages. This will give you the testers you need, force you to actually test and document some of the new additions you've made as you go and give people ideas of how they can be used. Then when the time comes to make the switch there will already be enthusiastic users and developers, already knowledgeable and comfortable, to take advantage of it. The time to put version 2.5.x into the backstage upgrade path will occur naturally, you will know with certainty when it is the right time, you will have loyal followers and it may actually be demanded by popular acclaim. That's how separate development paths can actually draw people together instead of one that would divide them. Morris Gray On Jul 8, 8:34 am, wolfgang wrote: > Sorry to everyone with a short attention span for this long post. One > could also proceed to the last paragraph, to get the gist. > > > To be clear, there have been three changes associated with jQuery: > > > - the inclusion of the jQuery library by default; this is the decision > > that you go on to critique. There was a fair amount of discussion > > before we did this; the goal was to enable TiddlyWiki to benefit from > > the much higher quality browser compatibility layer in jQuery > > I read parts of them and I'm very well aware that everyone has put > serious consideration be
[tw] Re: Announcing Tiddlywiki 2.5.2
Sorry to everyone with a short attention span for this long post. One could also proceed to the last paragraph, to get the gist. > To be clear, there have been three changes associated with jQuery: > > - the inclusion of the jQuery library by default; this is the decision > that you go on to critique. There was a fair amount of discussion > before we did this; the goal was to enable TiddlyWiki to benefit from > the much higher quality browser compatibility layer in jQuery I read parts of them and I'm very well aware that everyone has put serious consideration before implementing such a big change to the end of bettering TiddlyWiki. You shouldn't misunderstand my posts, that I wouldn't want this to happen. On the contrary, I'm still of the opinion you should go forward with this, and I appreciate you do. Also my arguments for a fork without jQuerry aren't anything you haven't heard already and therefore haven't considered before, nor could I give better ones as those already given by technically more versed contributors before. I just digested all these different perspectives (for example: http://groups.google.co.uk/group/TiddlyWikiDev/browse_thread/thread/c7d270d638383b92# ), multiplied it with the uncertainty factor in life, and salted it with Saq's perspective. And this is what came out of my pondering... I think everyone agrees with the direction of development taken, the advantages of doing so are far too obvious, theoretically. But considering the limited manpower at Osmosoft, these advantages to TW users might become obvious in a few months - or a few years - or, with other uncertainties already talked about, it might make this advantages more obvious to jQuery developers and less obvious to TW users - in the end. That's fine with me this way, and I take the possible risk of never seeing any real advantages. Then I thought - for the many reasons already pondered by others - well, after all it isn't such a big deal, to copy and paste bug fixes into version 2.4.3 and once more get developers on board for a healthy competition, for those who may feel there aren't any opportunities otherwise: > > working at Osmosoft. I don't for a minute believe that there are any > sinister intentions behind this and it has been an unfortunate by- > product of the fact that Jeremy and Martin both work at Osmosoft.. > it's just easier to discuss and develop with those you're in the same > room with. Sadly it means the rest of us don't get an opportunity to > weigh in and contribute. This isn't really meant as criticism, the .. > And once this uncertainty - that there might or might not come betterments to TW end users - has been decided, also the jQuery TW could only profit from it again (without having to take the responsibility to look also for such a kind of legacy TW, beside all the other perceived responsibilities: documentation, tiddly web, cctiddly, cecily, ripple rap, tiddly hub, jquery ...). >From developers, who otherwise may hold back their involvements, because they are simply not sitting in the same room and may wrongly think their forks - if indeed bringing improvements - wouldn't be received well by the community. (if nothing else, these discussions show that there is a real demand for a simple stable TW without an incorporated jQuerry, which at this point is still lacking any perceivable advantage) > > I'm not sure what you mean by the the "code repository for external > jQuery plugin developers". > I mean if an end user needs a piece of functionality he can go to a systemServer, take a tiddler and tag it systemConfig without having to import anything else from this repository. If a jQuerry developer needs a piece of functionality he can come to any TiddlyWiki and use a piece of code - but without the end user having ever decided to distribute code he is ignorant of, nor would know how to use for his own advantage, but costing bandwidth. Sure, also before this was possible with essential functions of TiddlyWiki. But jQuery TW plugins are dependent on jQuery library. And jQuery library dependency wouldn't be necessary for still some time. > > we've done is rearrange the code to make that easier. It sounds like > one of your concerns is that making this functionality into a jQuery > plugin is akin to bloat, which isn't really the case. > At the moment and till above will be decided - in months or years - jQuery library is the bloat. If I upgrade to it without receiving any perceivable advantages yet. > > I'd like to understand more why you think that the integration of > jQuery may be such a big problem. Is it primarily the issue of code > size? > Primarily it is the added size without any perceivable improvement. But I'm aware that this is difficult to understand as a big problem, if you haven't lived for a while in a developing country. However, you don't have too! You can't be responsible for everything - should other developers step up and do it on their own, and for very good reason
[tw] Re: trying to use ListBoxPlugin like formTiddler... on wrong track?
Hi Dave > I tried > <> and it just showed blank fields, and I > tried a ShowWhen thing in the viewTemplate and that also just showed > empty fields. maybe you have the same mistake that I have done: http://groups.google.com/group/TiddlyWiki/browse_thread/thread/6cb99621b50a383e?hl=de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: trying to use ListBoxPlugin like formTiddler... on wrong track?
Are you looking for something like this: http://no-sin.com/wiki/WorkTracker.html#%5B%5B33600-Fakeco%20Inc-Miami%20FL%5D%5D Also take a look at: http://www.hawksworx.com/playground/TeamTasks/#HighPriorityTask%20ValueSwitcherPlugin%20 If either of those are in the line of what you are looking for I can discuss them in more detail. Ken Girard On Jul 7, 10:24 am, Dave Parker wrote: > Hi, > > I was hoping to somehow get a really minimal amount of stuff to show > up in the tiddler body when editing a tiddler that has a lot of > ListBoxPlugin elements - you know, like when you edit a formTiddler > tiddler and see just <> and the > stuff here > > I have a ShowWhen thing happening in the edit template > (ProblemTemplateEdit) and that works great, but I have another > template tiddler to view the fields with and I was hoping to not see > much of that when I open the tiddler to edit the fields. I tried > <> and it just showed blank fields, and I > tried a ShowWhen thing in the viewTemplate and that also just showed > empty fields. > > Is there another way of doing this, or should I just drop this line of > thinking? (I was possibly going to contruct a table with a FET > statement, but wanted to see if there's any way of getting the > ShowWhen to work...) > > thanks, > Dave Parker --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: TW won't save on Safari after java update
Same issue and circumstances here. Workaround working, for now :-) On Jun 28, 12:55 pm, JcMarin wrote: > I have same problem with Safari 4.0.1 an updated Java (don;t have the > problem with 4.0 and previous version of Java > > For some reason the UnaMesa certificate (which point to the Thawte > root cert) is not being trsuted as signed? > > Anyone find a solution? > > I can trust it when opening but will ask again every-time > > On Jun 17, 7:35 am, Andrew Lister wrote: > > > > > Aha - same for me. I didn't try unchecking that box. Thanks, > > > Andrew > > > On Jun 17, 5:33 am, Jeremy Ruston wrote: > > > > I'm running Safari Version 4.0 (5530.17) on Mac OS X 10.5.7, with the > > > new Java update just applying itself this morning. > > > > The permissions dialogue that Safari displays with the applet first > > > loads has changed it's appearance from the earlier release, but seems > > > to work fine for me if I click "Run". It's only if I try to check the > > > "always trust content from this publisher" checkbox that I run into > > > the errors you describe. I'll investigate further, but relieved to > > > find work around. > > > > Cheers > > > > Jerm > > > > On Tue, Jun 16, 2009 at 8:22 PM, Andrew Lister > > > wrote: > > > > > I've been using TW on Safari 4, but after today's Java update it will > > > > no longer save. Here's what I get: > > > > > "Warning - Security: The application's digital signaturre cannot be > > > > verified. Do you want to run the application? Name: TiddlySaver. > > > > Publisher: UnaMesa Association. From: file://" > > > > > Then check "always trust content from this publisher" and "run", which > > > > brings up a second window: > > > > > "The publisher cannot be verified from a trusted source. Code will be > > > > treated as unsigned" > > > > > Then it lists a bunch of code, starting with > > > > java.lang.IndexOutOfBoundsException. After that it won't save. I > > > > tried this on a fresh, empty TW and the same thing happens. > > > > > Actually, I'm not 100% sure this problem started today, with the Java > > > > update, as I also just recently updated to Safari 4, and can't be sure > > > > I saved my TW on 4 prior to the update. I think I did, but I'm not > > > > sure. If others haven't had any problem with Safari 4, then it must > > > > be a problem with the Java update, since I've never seen this problem > > > > before. > > > > > So, back to Firefox for me, I guess, which is a bit disappointing, > > > > because Safari 4 seemed really fast. > > > > -- > > > Jeremy Ruston > > > mailto:jer...@osmosoft.comhttp://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 TiddlyWiki@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] trying to use ListBoxPlugin like formTiddler... on wrong track?
Hi, I was hoping to somehow get a really minimal amount of stuff to show up in the tiddler body when editing a tiddler that has a lot of ListBoxPlugin elements - you know, like when you edit a formTiddler tiddler and see just <> and the stuff here I have a ShowWhen thing happening in the edit template (ProblemTemplateEdit) and that works great, but I have another template tiddler to view the fields with and I was hoping to not see much of that when I open the tiddler to edit the fields. I tried <> and it just showed blank fields, and I tried a ShowWhen thing in the viewTemplate and that also just showed empty fields. Is there another way of doing this, or should I just drop this line of thinking? (I was possibly going to contruct a table with a FET statement, but wanted to see if there's any way of getting the ShowWhen to work...) thanks, Dave Parker --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: "editTiddler" in body
Thank you Morris (and I assume you can use the same approach to all the toolbar tools - very handy!) :-) On Jul 7, 12:51 am, Morris Gray wrote: > Try <> > > Morris > > On Jul 7, 3:49 pm, Dave Parker wrote: > > > I would like to be able to have a button in the tiddler body that > > would open up the tiddler for editing. The reason is that I'd more > > likely than not be doing this from a pop-up where you don't see the > > toolbar. I tried <> but that didn't work. > > > any suggestions? > > > thanks, > > Dave Parker --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: How to left-align MainMenu items?
Hi Wolfgang, many thanks for your detailed answer and the useful links ! Best regards Frank --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: Mgtd + itw ?
Got no iPhone, no iTW. But you might read this thread over in the GTD TiddlyWiki Group: http://groups.google.com/group/GTD-TiddlyWiki/browse_thread/thread/80d51a841808b20d On Jul 6, 10:21 pm, Ido Magal wrote: > Anyone port iTW into Mgtd or vice versa yet? hint hint. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: Multiple notes/tiddler using the TiddlerNotesPlugin
Can you email me your file where you tried to set up two notes on each tiddler using TiddlerNotesPlugin? It will help me debug the problem. Saq On Jul 7, 2:34 am, rouilj wrote: > On Jul 6, 12:06 pm, FND wrote: > > > > I am using the TiddlerNotesPlugin [...] > > > Does anybody know how to embed multiple editable notes > > > I'm not sure whether the TiddlerNotesPlugin supports this. > > Well according to the documentation it does: > > For a tiddler titled "MySlide", the notes are by default saved in a > tiddler titled > "MySlide-Notes" and is given a tag of "Notes". The suffix and tags of > the notes tiddlers > are customizable. You can have one or multiple notes per tiddlers. So > it is possible > to have for example, teacher's notes and student's notes in the same > file. > > I may be misparsing that somehow, but it certainly seems like it > should be possible. > > > You might wanna use a plugin for comments instead: > > http://tiddlywiki.org/wiki/Reader_Comments > > Yeah I tried those out, and they really don't work for the use case. > The TiddlerNotesPlugin > displays the current notes assigned to the tiddler when the tiddler > displays. The user can > edit all the notes directly from the displayed tiddler which must be > considered read only. > The comment plugins didn't really provide this level of functionality > out of the box. > > However one of the comment plugins described how multiple copies of it > could be embedded by using an > included tiddler. I may have a go at that. I still have a feeling I > need to decorate the div somehow > to allow the two notes to be told apart. > > -- rouilj --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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: Announcing Tiddlywiki 2.5.2
> That's my main concern. TW version 2.5 can already be considered as a > fork, since in this thread it has clearly explained, that a standard > TiddlyWiki now serves 2 purposes, for TW users and developers - as it > has been until recently - but also as a code repository for external > jQuery plugin developers - which is really unique. I'm not sure what you mean by the the "code repository for external jQuery plugin developers". To be clear, there have been three changes associated with jQuery: - the inclusion of the jQuery library by default; this is the decision that you go on to critique. There was a fair amount of discussion before we did this; the goal was to enable TiddlyWiki to benefit from the much higher quality browser compatibility layer in jQuery - the refactoring of some internal TiddlyWiki functions to use jQuery functionality where it improves performance or code size - the refactoring of some internal TiddlyWiki functions so that they can more easily be reused. This is something that's happened since the beginning of TiddlyWiki; other open source developers plucking out the unique bits of functionality in TiddlyWiki for their own projects. All we've done is rearrange the code to make that easier. It sounds like one of your concerns is that making this functionality into a jQuery plugin is akin to bloat, which isn't really the case. > The focus has already changed from TW, as now initially and > necessarily much more efforts has to be given for advancing this new > kind of jquery plugins, for which only few or no purposes are > available yet - or already existing the TW way, plus ironing bugs > which such a refactoring might bring. This is such a great task... I'm not sure what you mean here. > .. I slowly start to see the need for a user only oriented fork again > - at least for the next 2-3 years. I need to understand more about why you think this would be desirable, and how it would differ from the TiddlyWiki we've got today. > This can't be a one man task. Nevertheless, how about starting a TW > fork where jQuerry can be included via MarkupPreHead, as it has always > been the case, but doesn't has to? While including recent bugfixes and > attracting outside developers again, to contribute and being part of a > TiddlyWikis evolution without dependency to jQuery. > > What does everyone think? I'd like to understand more why you think that the integration of jQuery may be such a big problem. Is it primarily the issue of code size? > Clear communication has to occur whenever or wherever bluredness > happens to be perceived. Otherwise it isn't really out in the open > anymore ..therefore, lets discuss it here and now with everyone > invited to participate - with as much mutual respect and contrarily as > possible. If people are interested, we could set up another conference call for a discussion as well, Best wishes Jeremy -- 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 TiddlyWiki@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: Doubled tiddler display?
> I would have to spend a few months exclusively learning javascript [...] > This would defeat the beauty of TiddlyWiki [...] > where would it come to, if every user would be converted to a developer I understand that. However, you have very specific demands there, and - well, if you absolutely need a particular shape, but no such Lego brick exists yet, someone's gonna have to mold it first. -- F. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@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 -~--~~~~--~~--~--~---
