[tw] Re: growth-confusion
I would definitely argue that giewiki (as I like to write the name) could be a good fit for your needs. It has features to let you spread your content across multiple pages while still allowing full-text search, as would probably be a good idea with like 700 tiddlers to share. It also has it's own take on custom tiddler templates, and a fairly complete access control mechanism. It is designed to be hosted on the Google App Engine and as such offers you more options for server-side extensibility than you would have by hosting your page on TiddlySpace. Compared to hosting your own TiddlyWeb server, you should also find deployment much easier. The main drawback for some would be that giewiki is based on an older version of TW, and strictly speaking, it is a forked derivative. This may or may not be a problem to you - I would think that most of the changes I've made contribute to making it more suitable for web applications. :-) Poul http://giewiki.appspot.com On Friday, November 23, 2012 2:45:38 AM UTC+1, Kriss wrote: > > Hello guys, > > I am confused about the use of the different TW spin-offs. > > I am organizing a large international benefit event and during the > preparation phase, I have been using tiddlywiki as a tool to structure my > ideas, collect all the information (background-info, lists of all kinds, > contact-info (with *TaggedTemplateTweak*),...) and write a descriptive > document about the different aspects of the project. > (I have been using TW for 2 years now, on *Firefox *(most often on *Prism*) > in combination with *Dropbox *and on *andtidwiki *for my android phone - > the portable and off-line functionality is important to me) > > Now I have reached the point where the concept is mature, I need to start > sharing the information with other people: the volunteers that help in > implementing the project, and later-on maybe partners and sponsors. > > There are close to 700 tiddlers in this wiki, with lots of > links/transclusions and many also with automated contents (FET-lists and > such) > > As I understand Tiddlywiki is intended as a personal document and it was > never really suited for collaboration with different people at the same > time. So I think I will have to move away and towards spaces or tiddlyweb > or ... I don't know; I am confused. > > (I have experimented with the spaces concept, but it seems all the > tiddlers can be accessed? Can I reuse my TW layout in spaces? > (I use a modified color scheme with the left and right sidebars removed > and a small topmenu, conform to and suitable for andtidwiki) > > So I want to share my tiddlers; some of them can be publicly available > (visible, not editable), others should only be visible to certain people. > These people would be grouped in different user profiles. > I estimate there could be up to 20 people to modify tiddlers. (with only a > few changes per day; the tool mainly being used as a reference tool) > And for example sponsors could see more tiddlers than the general public, > but neither should be able to make changes. > Overall, the content/structure would be mainly managed by just one or two > people, with small contributions (only text/markup, no coding or such) from > the other users > (f.e. change contact information or add a journal report) > > The user group will not be very large; but It is quite diverse so I would > still need a good and flexible user-management. > > What would you recommend as the best way to go? > * some plugin for TW and share it on dropbox ? > ** TW5 ? > * move the content to spaces or tiddlyweb? How does user management > function here? > ** create my own server? > * maybe do I need to move to mediawiki or some of the other platforms with > a stronger user management !? (I would not like this option! But if > needed, could you recommend any?) > > Saving TW in the browser seems to be a neverending concern. Does Spaces > experience similar problems? > On the other hand, could I still (how?) access a spaces implementation > offline? > > > Thanks in advance for any advice or helpful comments. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/82XwWimnB8YJ. 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: TWS - a basic TiddlyWiki Server for node.js
I seem to recall this being a FireFox specific issue, but I didn't get to the bottom of it. Try using Chrome. :-) Poul On Sunday, October 21, 2012 11:00:48 AM UTC+2, Måns wrote: > > > >> I've got a little problem with character encoding it seems : >> When I save and then reload the page, some characters are replaced by >> strange ones. >> So the "é" becomes "é". >> >> Any idea to fix it ? >> >> >> +1 > ?? > Cheers Måns Mårtensson > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/30n7C-w7bcoJ. 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: Alternative for saving TW
I certainly sympathize with Chris's disappointment in the ability of server-based TW solutions to gain developer support. But then, I am not a Python believer, and if I were to invest a serious amount of effort in the problem, I would most definitely go the Node.js path. As it is, I am more likely to just pick the fruits of whatever is useful from tweb in the context of giewiki (like server-side wikifiers). But I must take some time to look into what Jeremy is doing with TW5. /Poul Den tirsdag den 16. oktober 2012 15.19.06 UTC+2 skrev Chris Dent: > > On Oct 16, 1:49 am, "Mark S." wrote: > > No one provided a realistic solution other than to suggest a web server. > > The web servers suggested were large. After that I kind of lost interest > in > > TW. > > This seems an opportune moment to remind folk that using TiddlyWeb + > TiddlyWiki doesn't have to be either hard or large, it's just gained > that reputation somehow. This response isn't a reaction to TWS: that > sounds awesome and very convenient. > > TiddlyWeb has been built in a way to allow people to build tools that > could make it extremely easy to use. That is rather than being > initially easy to use it is designed so that interested parties can > make versions of it that are extremely easy to use in different use > cases. Unfortunately there haven't been many of these other versions. > This could mean several different things: > > * My assertion about the tools that TiddlyWeb provides is not true. > * There aren't any interested parties. > * There are interested parties and there a people who can do the > building, and these people are disjunct. > > Each of these statements have persisted in the TiddlyWiki universe > since early on. The noun "TiddlyWeb" can be replaced with a variety of > names for plugins, verticals, server-sides. I'm not sure what this > means or why it is. Any ideas? > > In any case, on a computer that has a healthy Python installation > (many Linux machines and many Macs) the following small number of > steps creates an operational tiddlywebwiki installation on which you > can run as many tiddlywikis as you like: > > virtualenv --no-site-packages tweb > cd tweb > source bin/activate > pip install -U tiddlywebwiki > twinstance tweb > cd tweb > twanager server > open http://0.0.0.0:8080/recipes/default/tiddlers.wiki[1] > > I recognize that for many people that is complete gibberish and having > a "healthy Python installation" is a non-starter, so my point is not > that people should have to do that, but rather that _someone_ could > make a thing that encapsulates the complexity for a particular > environment (such as Windows) and by so doing make a very positive > contribution to getting tiddlers into people's hands. > > If TiddlyWiki is a useful to you (the general you) because of its > standalone-and-save-itself nature, then tools like TiddlyWeb, > ccTiddly, giewiki probably don't matter; but, if what you care about > is tiddlers then each of those tools (especially TiddlyWeb if I may be > so bold) provide huge scope[3] for doing interesting things. Each of > those projects is open source, meaning they rely on community to make > them their best, yet (as far as I can discern) each has only ever had > a very small number of contributions from outside their core > developer. > > Why is that?[2] > > [1] It can actually be shorter than that. That list is for running the > service in a virtualenv, wherein you don't need to root access to > install packages, and the packages don't clobber other installations. > If you are root you can: > > sudo pip install -U tiddlywebwiki > twinstance tweb > cd tweb > twanager server > open http://0.0.0.0:8080/recipes/default/tiddlers.wiki[1] > > [2] The TiddlyWiki community has always had a unique approach to Open > Source. Community members build around the core product, not in or on > it. This has resulted in a very diverse and exciting plugin ecosystem > but not much in the way of collaboration on shared goals. And things > look quite alien to people who are used to open source collaboration > in its common forms. > > [3] Of course that scope comes with the cost of initial complexity but > like with most computer oriented things complexity can be ameliorated > with work: abstraction and encapsulation to the rescue. What can be > done to get more people involved in that work? > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/K9Iw-gp9KI0J. 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: Alternative for saving TW
I don't think there are any security problems to worry about in using node.js for a server as long as it listens only on 127.0.0.1 (the loopback interface), as it is not exposed to outside connection. But as the browsers are becoming increasingly unhappy with java applets, I do believe it is just as much run-anywhere as a solution that relies on the java applet: Windows, Mac, Linux. And certainly more secure. Node.js on Android or iOS, anyone ? /Poul Den tirsdag den 16. oktober 2012 02.49.47 UTC+2 skrev Mark S.: > > Two and half years ago I asked what the future for TW was, given that > browser manufacturer's were trying to shut down the back-doors that allow > TW to save to the local hard drive: > > https://groups.google.com/d/topic/tiddlywiki/5AS-lPmTCbw/discussion > > No one provided a realistic solution other than to suggest a web server. > The web servers suggested were large. After that I kind of lost interest in > TW. > > Something like your solution seems like a candidate. But it means that TW > is no longer a run-anywhere solution. > > What are the security issues with running the node.js server? Can people > from the outside access it and possibly write to your computer? > > Thanks, > Mark > > > On Monday, October 15, 2012 2:30:49 AM UTC-8, Poul wrote: >> >> This is exactly why I wrote TWS (besides getting a feel for node.js). It >> actually already has a mention on TW.com, but in the context of hosted >> options, which is not really it's raison d'etre. >> The way it works does of course break with the accepted paradigm of how >> you work with documents on your own computer, but other than a full branch >> of Chromium or Firefox to get around their security concerns, I see no >> better way. >> >> /Poul >> >> Den mandag den 15. oktober 2012 11.19.14 UTC+2 skrev Bauwe Bijl: >>> >>> Hello People >>> >>> The latest TiddlyWiki saving issues and increased browser security >>> changes are worrying and could interfere with your workflow. >>> Instead of debugging saving issues and doing experiments some of us >>> might prefer to continue working with TW. (or at least have an extra >>> saving alternative) >>> >>> "TWS" (from Poul Staugaard) might be a good solution and to make sure >>> we don't forget, here my post on what it is, how it works and how I >>> use it. >>> >>> TWS : ( https://github.com/PoulStaugaard/TWS ) >>> From the readme: >>> " >>> TWS is a very basic TiddlyWiki server written for Node.js >>> It serves as an alternative to using TiddlyWiki's built-in methods for >>> saving your content. >>> " >>> >>> I've been using TWS for quite some time now since it allows me to edit >>> TW with chrome on linux. >>> Of course any server like TiddlyWeb or Tiddlyspace could do the same >>> but to install these local seems like overkill...for only saving >>> tiddlers... >>> TWS is "just enough server" to help you going and installation is, >>> compared to the big ones, pretty simple. >>> >>> Installation: >>> Install node.js (if you don't already have) >>> ...installation of node is a single click installation in most cases >>> (win mac linux)... >>> http://nodejs.org/ >>> >>> Download TWS: >>> https://github.com/PoulStaugaard/TWS/zipball/master >>> and unzip (change that folder name to what you like ... like "TWS") >>> Place this folder somewhere on your system (I have it in my /home >>> folder) >>> >>> Start: >>> browse to your TWS folder...and start the server with the command: >>> node tws >>> >>> This will start a process that launches the server on >>> http://localhost:1337/ >>> and starts Google Chrome automatically (in browser.js you can >>> change chrome start with other browsers) but also http://localhost:1337/ >>> can be opened manually in browsers. >>> >>> Once started you'll find an empty.html TW in the list which you can >>> start editing (user name and backup folder needs to be set...just as >>> "normal"...in your tw :) >>> Other TiddlyWiki's can be copied to the TWS folder and replace the >>> existing TW. >>> >>> That's it. >>> >>> >>> Some thoughts: >>> >>> Benefit: >>> - once familiar
[tw] Re: Lazy loading. Any news?
Not sure if it matches your requirements, but giewiki certainly does have the ambition to scale much better content-wise, including support for lazy-loading tiddlers and server-side search. It builds on Google's App Engine, and I do not recommend using the SDK for storage of thousands of tiddlers, but if the advantages of a hosted solution outweighs the disadvantages for you, a hosted giewiki is definitely my recommendation. :-) Poul http://giewiki.appspot.com Den onsdag den 17. oktober 2012 16.23.23 UTC+2 skrev Ruler11: > > I haven't been watching at TW-development for a long time due to the lack > of a mechanism of storing thousands of tiddlers. > So is there a plugin for lazy loading of tiddlers or connecting TW to a > MySQL database or even Mediawiki? > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/6T8JpdsgMTEJ. 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: Alternative for saving TW
This is exactly why I wrote TWS (besides getting a feel for node.js). It actually already has a mention on TW.com, but in the context of hosted options, which is not really it's raison d'etre. The way it works does of course break with the accepted paradigm of how you work with documents on your own computer, but other than a full branch of Chromium or Firefox to get around their security concerns, I see no better way. /Poul Den mandag den 15. oktober 2012 11.19.14 UTC+2 skrev Bauwe Bijl: > > Hello People > > The latest TiddlyWiki saving issues and increased browser security > changes are worrying and could interfere with your workflow. > Instead of debugging saving issues and doing experiments some of us > might prefer to continue working with TW. (or at least have an extra > saving alternative) > > "TWS" (from Poul Staugaard) might be a good solution and to make sure > we don't forget, here my post on what it is, how it works and how I > use it. > > TWS : ( https://github.com/PoulStaugaard/TWS ) > From the readme: > " > TWS is a very basic TiddlyWiki server written for Node.js > It serves as an alternative to using TiddlyWiki's built-in methods for > saving your content. > " > > I've been using TWS for quite some time now since it allows me to edit > TW with chrome on linux. > Of course any server like TiddlyWeb or Tiddlyspace could do the same > but to install these local seems like overkill...for only saving > tiddlers... > TWS is "just enough server" to help you going and installation is, > compared to the big ones, pretty simple. > > Installation: > Install node.js (if you don't already have) > ...installation of node is a single click installation in most cases > (win mac linux)... > http://nodejs.org/ > > Download TWS: > https://github.com/PoulStaugaard/TWS/zipball/master > and unzip (change that folder name to what you like ... like "TWS") > Place this folder somewhere on your system (I have it in my /home > folder) > > Start: > browse to your TWS folder...and start the server with the command: > node tws > > This will start a process that launches the server on > http://localhost:1337/ > and starts Google Chrome automatically (in browser.js you can > change chrome start with other browsers) but also http://localhost:1337/ > can be opened manually in browsers. > > Once started you'll find an empty.html TW in the list which you can > start editing (user name and backup folder needs to be set...just as > "normal"...in your tw :) > Other TiddlyWiki's can be copied to the TWS folder and replace the > existing TW. > > That's it. > > > Some thoughts: > > Benefit: > - once familiarized with node.js you might start checking how node is > used for building TW or TW5 (and all the other great things you can do > with it :) > - using chrome on linux is possible > > Discussions: > You might have concerns about using a "helper" system to save > tiddlers... > wasn't that saving.jar and java also a helper? > > Missing: > backstage functionality like import > > > Have fun! > > Bauwe > > > > > > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/iHfNt1iOhN4J. 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] giewiki release 1.17 adds site-wide search
A hitherto badly missing feature of giewiki, that of site-wide search, has finally been implemented, making giewiki's content scale-ability message rather more convincing. For more info, check out http://giewiki.appspot.com - or test the performance by searching Alice In Wonderland at http://tstest.giewiki-hrdta.appspot.com/ :-) Poul -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/e1wFjn5cAL8J. 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: Willing to contribute and promote...
Hi Akhil, If you like Google App Engine, you might be interested in my flavour of TiddlyWiki, which is a branch from TW 2.4.1 with an app engine backend written in Python. I started before Java was an option and I have often wished the server-side was Java. It's called giewiki and the source code is at http://code.google.com/p/giewiki while the homepage is http://giewiki.appspot.com -and as it says, I still welcome if anyone would take a stab at translating the 4000 lines of python into Java. Most recently, I've been working to implement the new full-text search feature of GAE, which is essential to the content volume scaleability of giewiki. I've yet to test it with significant volumes of content, but presumably Google knows how to do these things. They weren't in any hurry to bring it out. :-) Poul Den fredag den 17. august 2012 09.57.45 UTC+2 skrev Akhil Anil: > Hi Guys, > > I'm Akhil. I work as a java developer and have a few blogs (main: http:\\ > akhilspassion.blogspot.com). I love programming and am now learning more > about Google app engine, wikis etc. tiddlywiki is the only one I found the > best after reviewing so many other wikis out there. It has incredible > potentials. I've interest to contribute to this project as well. Pls > provide me with some places to get started as a contributor. I could use my > spare time to help build this. > > -- > Thanks > > Bye. > > May God Bless us! > > A k H! L . > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/r3ukSg0On1QJ. 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.
Re: [tw] Re: [Freedombox-discuss] Who's interested in project management & collaboration tools? And...
It sounds to me like you need investors. Won't investos think: If it's open source, and it's P2P, then where the hell is the business model? /Poul -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/0x21OgTdrVgJ. 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: The magic of MPTW
You're absolutely right, thanks. twcomp.html, line 348:
.toolbar {text-align:right; font-size:.9em; float:right }
:-) Poul
On Saturday, March 24, 2012 2:07:02 PM UTC+1, cmari wrote:
>
> I'm not sure where it would need to be inserted in your specific use case,
> but this line in the Stylesheet seems to be the important one:
>
> .toolbar { float:right; }
>
> cmari
>
>
>
> On Saturday, March 24, 2012 7:39:15 AM UTC-5, Poul wrote:
>>
>> NB: In both cases, it isn't actually ViewTemplate that's used for view
>> template, but rather newsViewTemplate.
>> For more info, see
>>
>> http://giewiki.appspot.com/#%5B%5Btiwinate%20(macro)%3A%20Tiddler%20With%20Named%20Template%5D%5D<http://giewiki.appspot.com/#%5B%5Btiwinate%20%28macro%29%3A%20Tiddler%20With%20Named%20Template%5D%5D>
>>
>>
>> /Poul
>>
>> On Saturday, March 24, 2012 1:33:36 PM UTC+1, Poul wrote:
>>>
>>> Hi guys,
>>>
>>> I could use a bit of help with this one: As you may know, I adapted
>>> Simon Baird's excellent work at http://mptw.tiddlyspot.com/
>>> as an optional alternative page template in giewiki. Recently I used it
>>> for a sample application of the custom tiddler templates facility, that
>>> I've added in giewiki 1.16.
>>> Specifically, I have a ViewTemplate (derivative) that starts like this:
>>> >> macro='toolbar [[ToolbarCommands::ViewToolbar]]'>
>>> in stead of the classic
>>>
>>> If I use the MPTW page template, I get the result I'm hoping for, ie. a
>>> left-aligned span showing the value of the 'topic' field and the usual
>>> right-aligned toolbar, like this:
>>>
>>> http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates#%5B%5BBerlusconi%20is%20out%5D%5D<http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates#%5B%5BBerlusconi%20is%20out%5D%5D>
>>> If I do not use it, I don't get quite what I want (the toolbar isn't
>>> right-aligned):
>>>
>>> http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates/Sport#%5B%5BNavratilova%20is%20back%5D%5D<http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates/Sport#%5B%5BNavratilova%20is%20back%5D%5D>
>>>
>>> What exactly is it that Simon did to make it work (and why doesn't it
>>> work otherwise)?
>>>
>>> Thanks,
>>> Poul
>>>
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/tiddlywiki/-/vchtlWDrdpAJ.
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: The magic of MPTW
NB: In both cases, it isn't actually ViewTemplate that's used for view template, but rather newsViewTemplate. For more info, see http://giewiki.appspot.com/#%5B%5Btiwinate%20(macro)%3A%20Tiddler%20With%20Named%20Template%5D%5D /Poul On Saturday, March 24, 2012 1:33:36 PM UTC+1, Poul wrote: > > Hi guys, > > I could use a bit of help with this one: As you may know, I adapted Simon > Baird's excellent work at http://mptw.tiddlyspot.com/ > as an optional alternative page template in giewiki. Recently I used it > for a sample application of the custom tiddler templates facility, that > I've added in giewiki 1.16. > Specifically, I have a ViewTemplate (derivative) that starts like this: > > in stead of the classic > > If I use the MPTW page template, I get the result I'm hoping for, ie. a > left-aligned span showing the value of the 'topic' field and the usual > right-aligned toolbar, like this: > > http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates#%5B%5BBerlusconi%20is%20out%5D%5D<http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates#%5B%5BBerlusconi%20is%20out%5D%5D> > If I do not use it, I don't get quite what I want (the toolbar isn't > right-aligned): > > http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates/Sport#%5B%5BNavratilova%20is%20back%5D%5D<http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates/Sport#%5B%5BNavratilova%20is%20back%5D%5D> > > What exactly is it that Simon did to make it work (and why doesn't it work > otherwise)? > > Thanks, > Poul > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/q_I5lMlns20J. 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] The magic of MPTW
Hi guys, I could use a bit of help with this one: As you may know, I adapted Simon Baird's excellent work at http://mptw.tiddlyspot.com/ as an optional alternative page template in giewiki. Recently I used it for a sample application of the custom tiddler templates facility, that I've added in giewiki 1.16. Specifically, I have a ViewTemplate (derivative) that starts like this: in stead of the classic If I use the MPTW page template, I get the result I'm hoping for, ie. a left-aligned span showing the value of the 'topic' field and the usual right-aligned toolbar, like this: http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates#%5B%5BBerlusconi%20is%20out%5D%5D If I do not use it, I don't get quite what I want (the toolbar isn't right-aligned): http://giewiki.appspot.com/SandBox/CustomTiddlerTemplates/Sport#%5B%5BNavratilova%20is%20back%5D%5D What exactly is it that Simon did to make it work (and why doesn't it work otherwise)? Thanks, Poul -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/MabPAnjm6GIJ. 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: Use of multiple templates
What I have already achieves the same result. What I'm proposing is rather different: That the URL should be able to specify both the template and the data. Not appropriate in the normal case, but it could have specific applications. /Poul On Feb 13, 2:06 am, TonyM wrote: > I may have this wrong but I assume you have > considered;http://www.TiddlyTools.com/#TaggedTemplateTweakInfo<http://www.tiddlytools.com/#TaggedTemplateTweakInfo> > > I use it for what sounds like what you are after using tags. -- 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: Replace Tiddler Subtitle with History Forward/Back buttons.
Beware that the ViewTemplate is not processed like normal wiki text; it's html with some attributes that indicate macros to call to insert the variable parts. This means that rather than <>, you would have to write On 12 Feb., 01:20, Liam and Holly Erickson wrote: > Thanks for your reply. I do want the history buttons in each tiddler under > the title so it looks like the ViewTemplate is where we're heading. I'm > guessing that I have to add <><> somewhere in this shadow > tiddler. Can you please walk me through this. I'm also anticipating that > the buttons will be the same color as the removed subtitle was, but to make > them noticeable I'd like them to be the same color as any other link (if > possible). > /Poul -- 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: Use of multiple templates
On 12 Feb., 11:06, PMario wrote: > I think this is a very intersting idea. So you tweak the link renderer > according to the "logged in" user. right? It's still just an idea; just how different users would see different links would probably be application-dependant. I haven't actually done anything to facilitate this, but I imagine I would use Eric's InlineJavascriptPlugin to generate the appropriate links based on whatever rules apply. It could also be as simple as mailing a link with the right tiddler link after the # , only that doesn't work with my current solution, which works in onClickTiddlerLink(). /Poul -- 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] Use of multiple templates
It's nothing new that giewiki supports alternative edittemplate and viewtemplate attributes to be defined for specific tiddlers. Prior to the 1.15.8 release, there wasn't however a nice way to specify which, making it effectively a developer-only feature. The new release adds a generic field editing facility (available only to admins and page owners) that lets you set these attributes through the standard UI. I realize that this is only a step on the way; having defined an alternative template, you would naturally want to easily instantiate tiddlers based on it. The primary reason I write is however to float a different idea that came up in the process. The way I have implemented the field editor is as separate pseudo-tiddler, in order to allow it to be opened through a tiddler link of the form "fields:TiddlerName", and it occurred to me that it might be a useful feature if you could apply any template to any tiddler through a link pattern like templatename:TiddlerName. A use case might be to give different people access to the same tiddlers through different templates. But then again, this could be totally redundant, if there are better ways to do the same thing - what do you think..? :-) Poul http://giewiki.appspot.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] Generic XML rendering, w. links
Chrome has recently gained a decent rendering of arbitrary XML. Has anyone made something similar for XML embedded in tiddlers..? Like, borrowing the work that you see in chrome...ideally adding the ability to define click handlers for attributes and text nodes. /Poul -- 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: Sub-structuring TiddlyWikis
Unless local flat-file storage is a must, you may want to consider giewiki, my App Engine hosted derivative, which was designed to support a hierarchy of pages and let you navigate them using a sitemap. Deploying your own instance to Google's hosting system recently got a lot easier, as you no longer need to download it & install (python and) the SDK to get started. You can now do it entirely through the web, using practically any connected device. /Poul http://giewiki.appspot.com On 29 Jan., 09:59, hpon wrote: > Hi, > > A humble suggestion.. > > Some TiddlyWikis, such aswww.tiddlywiki.com, present a somewhat > cluttered structure of information. I believe that this lack in > presentation has the effect that newcomers initially are not as > impressed by TW as they ought to be. I try to "sell" TiddlyWiki to > everyone I know, and I think i would be more successful in that > endeavor ifwww.tiddlywiki.comwas more tidy and really took advantage > of the ways information can be managed in TiddlyWiki. > > I sub-structure my TiddliWikis, using multiple "empty.html" files > arranged in corresponding folders. I use relative file paths within > the TiddlyWiki, which enables me to easily share isolated branches of > the entire body of information. Other advantages of sub-structuring > are transparency, readability, ease maintenance, aesthetics etc. > > It is really good that TiddlyWiki makes it possible to embody an > entire wiki within one file. However, I find that sub-structuring > becomes the most preferable approach even when the complexity of the > TW is quite low. > > Best Regards, > hpon -- 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: Tiddlywiki for groups
I would say, the combination of https and strong passwords should get you a long way. Depending on your setup, you could add client IP address restrictions. And physical access would even be more secure in the cloud. -Poul 24 Jan., 04:57, HansBKK wrote: > On Tuesday, January 24, 2012 1:52:36 AM UTC+7, Poul wrote: > > > I'm not sure what you mean - you can export your pages as stand-alone > > tiddlywikis or just-the-content XML. > > But the native storage used by giewiki is the cloud-hosted App Engine > > data store documented here: > > >http://code.google.com/intl/da-DK/appengine/docs/python/datastore/ > > I am looking for a self-hosted solution, and my specific concern here is > data privacy, as several of my use cases prohibit cloud-based (or in fact > any outside-the-group-accessible) storage. Strong on-disk encryption would > of course be one approach, at a filesystem level, as ideally the tiddler > data would be stored in an easily diffed/merged format and stored > in/distributed by an arbitrary DVCS. > > Any and all suggestions welcome, but don't mean to hijack the thread, feel > free to fork this off if appropriate. -- 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: Tiddlywiki for groups
I'm not sure what you mean - you can export your pages as stand-alone tiddlywikis or just-the-content XML. But the native storage used by giewiki is the cloud-hosted App Engine data store documented here: http://code.google.com/intl/da-DK/appengine/docs/python/datastore/ On Jan 23, 4:50 pm, HansBKK wrote: > Does your solution store one's tiddler data where Eric Schmidt could read > it? -- 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: Tiddlywiki for groups
But unless you are a seasoned Python user, you may still find tiddlyspace deployment to be a far from trivial task with several dependencies. I, for one, got stuck and gave up pretty quickly. But then of course, I am biased toward my own alternative, which can now be deployed to Google's hosting service (App Engine) in less than an hour (I believe). I would of course argue that it has other advantages as well, particularly for the casual users - like more helpful & conventional structuring concepts. The one major catch is that only Google accounts can be used for authentication, but then, who doesn't have one... http://giewiki.appspot.com/#DeploymentGuide https://www.coderbuddy.com/projects/giewiki :-) Poul On 20 Jan., 17:21, colmjude wrote: > On Jan 20, 4:17 pm, Pablo Trujillo wrote: > > > Oh... I was asking more in the way to put TidllySpace in my own > > server. Is that possible? > > Yes. The source code for tiddlyspace is available for anyone to view, > edit, take, deploy on their of servers, do whatever they want to do > with it. > > > > > > > > > > > On Jan 20, 12:24 pm, colmjude wrote: > > > > On Jan 20, 1:13 pm, Pablo Trujillo wrote: > > > > > Oh... that looks good... are you saying that we can get all that site > > > > and create it for us for free? and also access the code to customize > > > > it? > > > > Anybody is free to use the TiddlySpace service[1] but everyone that > > > does should bear in mind that they aren't the only resident of the > > > domain and it is purposefully built for many people. Using this > > > service means that the only customisations that can be made are on the > > > client side, although the number of possibilites here is still huge. > > > Having your own instance will allow you to also modify things on the > > > server side too. > > > > Yes, anyone can access and modify the source code. One of the beauties > > > of Open Source software, which TiddlySpace is. > > > The more people that use their own instances in different ways the > > > more information and opinions available that can aid further > > > development of the project. > > > > Hope that helps, > > > > Colm > > > > [1] - hosted athttp://tiddlyspace.com > > > > > It sounds awesome!!! > > > > > On Jan 20, 10:25 am, colmjude wrote: > > > > > > On Jan 19, 1:59 pm, "Pablo Trujillo (Colombiano en UY)" > > > > > > wrote: > > > > > > Hi all... i would like to ask you, if by your experience if it is > > > > > > possible to have this software for a group of 100 people so each can > > > > > > write their tasks... i know it works fine for personal use, but can > > > > > > we > > > > > > manage it to be in a server and be used by a group. If not.. is > > > > > > there > > > > > > a similar group application for a medium size group (100 people) > > > > > > Thanks a lot!!! > > > > > > Have you seen TiddlySpace? It allows many people to have TWs online, > > > > > work on TWs together, share tiddlers between TWs and many other > > > > > things. > > > > > > There is a freely available service located athttp://tiddlyspace.com > > > > > and if you think it would match your requirements then you could > > > > > install and run your own instance on your own server giving you > > > > > greater control and flexibility. The source code is > > > > > athttps://github.com/TiddlySpace > > > > > > Hope that helps, > > > > > > Colm -- 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] Implementing giewiki for yourself just got a whole lot easier
Now you can even do it from your iPhone. Thanks to Adrian Scott's CoderBuddy.com service, you no longer need to install Python and the App Engine SDK in order to get your own giewiki up and running in the cloud. You still need to set up an App Engine account if you want to go beyond just trying it out, but what CoderBuddy offers is a web- hosted code editor combined with the App Engine SDK for testing and deployment to Google App Engine. And you don't even have to edit any code in order to implement giewiki. Furthermore, users can share projects, i.e. copy each other's public projects or work jointly on the same. You can get started by going to https://www.coderbuddy.com/projects/giewiki and if you care, click "Copy Project" on that page. At this point, you'll have to login of course - just login with your Google account. :-) Poul http://giewiki.appspot.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: TWS - a basic TiddlyWiki Server for node.js
OK - now github has a version that fixes this for Win7/x64 and ubuntu.
:-) Poul
On Jan 2, 4:48 pm, passingby wrote:
> Hi Poul,
> I tried and failed to run the application. I am on windows 7. The error
> message is:
>
> Failed to start "C:\Users\sony/Local Settings/Application
> Data/Google/Chrome/Application/chrome.exe" --homepage
> "http://localhost:1337/";
> {[Error:Command failed: The system cannot find the path specified.]
> killed:false, code:1, signal: null }
>
> I searched and found chrome.exe's path on my system is: C:\Program Files
> (x86)\Google\Chrome\Application
>
> So how do I fix this?
--
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] TWS - a basic TiddlyWiki Server for node.js
I have never been a fan of how TiddlyWiki works when it comes to saving your work. It's becoming increasingly obvious that, for reasons of security, the browser designers don't like it either. So, I've created a basic TiddlyWiki server with an associated plugin, that serves as an alternative to using TiddlyWiki's built-in methods for saving your content. It writes portable TiddlyWiki files just like TW's own code. http://giewiki.appspot.com/Tutorials/nodepad https://github.com/PoulStaugaard/TWS Happy New Year :-) Poul -- 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] nodepad - a (still read-only) server-side
I also have been playing around with node.js and finding it quite useful. http://giewiki.appspot.com/Tutorials/nodepad logs the start of an efford to learn how to make node.js (http://nodejs.org) serve TiddlyWiki pages better than file systems do, although so far, there is nothing TW-specific about it. Hopefully, it should be possible to write platform-independent JavaScript for the server-side, but utility code to launch the browser will be platform-specific. The main part of what I've got so far is code for an ultra-simple server, that will serve local files. Once the server is up, I proceed to launch a browser to hit that server, with an optional filename specified on the command line. The browser is so far to be understood as Google Chrome, and it works on Windows and OS X. -- 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: tiddlywiki and the linux terminal / bash scripting
As much as I like the idea, I have a feeling that it isn't something that general-purpose web browsers should (or will) allow, for reasons of security. There are probably browser-specific ways to accomplish that, but my expertise on the matter is Windows/IE-specific. I suppose the ultimate, platform-neutral way to go would be to do a private build of FireFox or Chrome and work from there. A different approach would be to have a local web server on your own machine, that would allow a custom web app the required permissions - Google's App Engine SDK (+giewiki) comes to mind as the starting point - particularly now that it supports multi-threading with Python 2.7. :-) Poul On 19 Nov., 18:34, Dave wrote: > I finally got a smartphone that can handle editing TW files (thank you > AndTidWiki) and see myself getting back into using TW more... > > Recently though I've invested a lot of time into a linux command line > task application called taskwarrior (http://taskwarrior.org/projects/ > show/taskwarrior). I know there are a lot of good gtd TW plugins, but > I'd like to stay with taskwarrior if possible (interestingly also > known as TW :-) > > Question: is there a way that tiddlywiki can send commands or even > entire bash scripts to the terminal? I'd think that I could use > LaunchApplicationPlugin to launch a script, but how would I get the > output back from that script for displaying/use within the TW (the one > on the pc, not the phone) > > any ideas? -- 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: giewiki - beginner questions
I'm aware that a Google-hosted server might not be acceptable due to 'company policy', but in terms of a good alternative for in-house hosting, I expect AppScale (http://code.google.com/p/appscale/) would be a better solution for multiuser applications than the turnkeylinux option which as I far as I can tell is just a Linux virtual machine preinstalled with the App Engine SDK. I'd very much like if some Linux/ MySQL savvy person would check it out as a platform for giewiki. :-) Poul On 17 Nov., 22:45, Seba wrote: > I'll have a look at that. Basically, I like tiddlywiki very much and I > use it everyday for different purposes, so I want to expand the use to > a server side solution, however I am limited to our own servers. And > unfortunately as I am not a programmer, I can't contribute much to > such development:( > > thank you. > regards, > seba > > On 17 nov., 22:35, Bauwe Bijl wrote: > > > > > > > > > There is also an option to run an appspot server on your own (not the > > sdk dev server). > > For instance you can use this:http://www.turnkeylinux.org/appengine > > > The turnkey appliances are build on ubuntu, small iso's , which can be > > installed to a harddisk as os, booted "live" from cd/usb or installed > > on a virtual machine. > > The virtual machine installation might be an option to use (since the > > virtual environment runs "local" and can be used on all platforms). > > Perhaps the appliance is not an ideal server (it wont take long to > > install...and it's turnkey ready) but a good way to find out if it's > > worth to go for a better setup. > > (...I have not used this appspot-appliance for giewiki b.t.w. but for > > other installations...so it's kind of giewiki untested :) > > I also believe Poul has some more information on the giewiki site > > about a virtual setup... > > > Bauwe -- 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: Tiddler-Based-Communication-Protocol
On 17 Nov., 14:07, chris.d...@gmail.com wrote: > You get people who "believe" in XML and probably once thought XSLT was > going make everything okay and if we can get tiddlers to fit in that > world, all the rest kind of falls out. Initially, I actually designed giewiki to be delivered as XML + XSLT, but I eventually went back to classic HTML mostly because of the flaws in IE's implementation. You can still get the XML version with a URL query string, though. My point about UUID's was that strictly speaking, you really need to know what it is that the uuid identifies, and that's a semantic issue. I could imagine that a collection of tiddlers had the same value for a named uuid, because either: * they were different versions of the same tiddler. * they originated from the same server or page. * they were authored by the same person. * or ... or ... Not to deconstruct too much, my point remains that we should try agree on two things: 1) What the tiddler-identifying id is named (simple). 2) What it means to have identified a tiddler. Not so simple. IMHO. If, say, you receive a document that contains 42 more or less different tiddlers having 17 different uuids, what can be deduced about their relationships..? A plausible interpretation would be 17 tiddlers, some of which have several versions. You may of course choose not to accept such a document. Or try to figure out which is the current version - but don't assume that it's the one with the latest timestamp. /Poul -- 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: giewiki - beginner questions
In the console output from dev_appserver.py you will probably see this message: WARNING 2011-11-17 19:46:42,731 datastore_file_stub.py:512] Could not read datastore data from /tmp/dev_appserver.datastore Apparantly that's where dev_appserver.py puts its database by default - obviously not the way to go if you want the data to be preserved for long. But luckily, you can change that with the '--datastore_path=...' parameter; check out http://code.google.com/appengine/docs/python/tools/devserver.html That page also documents the '--address=0.0.0.0' parameter which you will need to use if you want the server to be accessible from other computers.But please beware that dev_appserver is intended as a development tool, certainly not as a production web server. This is also why anyone can log on as administrator: it does not manage users at all beyond letting the app know the login user name.In short: use it only for evaluation or short-term personal use. Multi-user applications should be based on Google's cloud-hosted app engine service, which is still free for modest use. See also http://giewiki.appspot.com/#DeploymentGuide which has a link to a video tutorial Bauwe made on deploying giewiki to the cloud. :-) Poul On 17 Nov., 14:04, Seba wrote: > I found out when pages don't get saved. Actually, they are saved, but > deleted when restarting the computer (when using Ubuntu). In Windows > everything works fine. Did I miss a step when setting up the Google > app engine in Ubuntu? Apparently nothing gets written to my profile. > And ideas? > > thank you. > regards, > seba > > On 17 nov., 11:01, Seba wrote: > > > > > > > > > Hi Bauwe, > > > thx for the quick reply. I made some progress regarding the user > > management thanks to your help. I am still having problems with admin > > aspect though and here are my next questions: > > > 1) I created a user who should not have the admin rights and yet they > > can log in as administrator based on the check-box on the login > > screen. And as such they have the access to data store and all other > > admin stuff. > > > And even in the development console I can't assign or revoke the admin > > rights to users. How should I proceed so I only have 1 admin user and > > the rest are regular users. Can this be done? > > > 2) Has anyone written some guides for beginners so I could get up and > > running faster? Currently I am learning by doing:) If there isn't any > > such guide I'll probably write it myself as I go along and post it > > when finished. > > > 3) As far as the page saving goes, I haven't found the error yet, but > > I am quite sure I saved it, since it was there after second and third > > login. > > > Thank you for your help. > > > regards, > > seba -- 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: giewiki - beginner questions
In the console output from dev_appserver.py you will probably see this message: WARNING 2011-11-17 19:46:42,731 datastore_file_stub.py:512] Could not read datastore data from /tmp/dev_appserver.datastore Apparantly that's where dev_appserver.py puts its database by default - obviously not the way to go if you want the data to be preserved for long. But luckily, you can change that with the '--datastore_path=...' parameter; check out http://code.google.com/appengine/docs/python/tools/devserver.html That page also documents the '--address=0.0.0.0' parameter which you will need to use if you want the server to be accessible from other computers. But please beware that dev_appserver is intended as a development tool, certainly not as a production web server. This is also why anyone can log on as administrator: it does not manage users at all beyond letting the app know the login user name. In short: use it only for evaluation or short-term personal use. Multi- user applications should be based on Google's cloud-hosted app engine service, which is still free for modest use. See also http://giewiki.appspot.com/#DeploymentGuide which has a link to a video tutorial Bauwe made on deploying giewiki to the cloud. :-) Poul On 17 Nov., 14:04, Seba wrote: > I found out when pages don't get saved. Actually, they are saved, but > deleted when restarting the computer (when using Ubuntu). In Windows > everything works fine. Did I miss a step when setting up the Google > app engine in Ubuntu? Apparently nothing gets written to my profile. > And ideas? > > thank you. > regards, > seba > > On 17 nov., 11:01, Seba wrote: > > > > > > > > > Hi Bauwe, > > > thx for the quick reply. I made some progress regarding the user > > management thanks to your help. I am still having problems with admin > > aspect though and here are my next questions: > > > 1) I created a user who should not have the admin rights and yet they > > can log in as administrator based on the check-box on the login > > screen. And as such they have the access to data store and all other > > admin stuff. > > > And even in the development console I can't assign or revoke the admin > > rights to users. How should I proceed so I only have 1 admin user and > > the rest are regular users. Can this be done? > > > 2) Has anyone written some guides for beginners so I could get up and > > running faster? Currently I am learning by doing:) If there isn't any > > such guide I'll probably write it myself as I go along and post it > > when finished. > > > 3) As far as the page saving goes, I haven't found the error yet, but > > I am quite sure I saved it, since it was there after second and third > > login. > > > Thank you for your help. > > > regards, > > seba -- 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: Tiddler-Based-Communication-Protocol
I'd definitely agree that it should be a field, but without semantics attached to it, I'm not sure that it would even make sense to agree on what the name should be. Giewiki, for example, uses 'id' for what has a UUID format, but without any guarantee that the associated content is the same - indeed, you also have to specify a version number, and even then, a server might allow a tiddler to be changed without incrementing the version number. But if anyone can think of an assertion that can safely be made if you can identify a specific field as being a UUID, please tell me. :-) Poul On 16 Nov., 20:27, chris.d...@gmail.com wrote: > On Wed, 16 Nov 2011, PMario wrote: > > As Jeremy said the easiest way to use UUIDs would be, to use it as a > > tiddler title. All TW core functions will work quite well. > > No, not at all. It is not the easiest, and it would break everything. > > Because the uuid isn't there for > > > [[prettyLink|0d9b98c0-5f73-45eb-ac4a-386d445905e3]] to make a tiddler > > this > > > <> will work > > or this > > It's there for identification. That's all. It's not a name nor an > address nor a label. > > > If you don't want to use the tiddler.title as an UUID, you'll need to > > rewrite most of the core functions. But all this stuff has to be > > programmed. Since the underlaying system doesn't force you to do it, > > nobody will do it. It's as simple as that. > > No, if the uuid a field, _nothing_ needs to change in tiddlywiki. > Nothing at all. > > > <> > > Why would you ever do this? > > -- > Chris Dent http://burningchrome.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: Tiddler-Based-Communication-Protocol
I agree that if a client app - TiddlyWiki or other - assigns a uuid to a tiddler it has created, that uuid should be used also by any server onto which is is put. That's what uuids are for. And no, the uuid should never change unless the user decides to copy the tiddler to a different URL on the same server, in which case it probably should. But a full-featured server should also allow a mechanism by which the same tiddler appears on several pages as in unix-style soft links - but probably not allow it to be edited through either without explicitly breaking the link. :-) Poul On 14 Nov., 17:45, tiddlygrp wrote: > Hi, > > @Jeremy: For me a tiddler uuid has nothing directly to do with a > tiddler. At creation time put a uuid in a field in the tiddler is the > absolute minimum I think tw should do. A lot other stuff can be done > server side. The advantage of creating a uuid at tiddler creation > time is that then it is "uniquely" marked. Then the tiddler might > move to a server (or not). My thought is that by putting the uuid in > tw, all servers should support this standard. If each server builds > up its own uuid semantics, than its hard to get federation and sharing > of tiddlers peer to peer without a server. > > @Chris What I mean by a tiddler communication protocol is more a set > of conventions than a tech specification like http or tcp/ip. In the > protocol we need: which fields are part of a tiddler, which fields > are optional, what is the meaning of the fields (e.g. changes the uuid > with each edit? Or is there a version identifier?). In you first > post from nov. 11 you make a proposal for such a protocol as I mean > it. I suggest to additionally look at Ward's pages definition in > JSON, because it is very similar to a tiddler and already solves in > some way versioning, uuid's and tracking servers. How you then > actually send the tiddlers? Probably just http/atom as you stated. > And probably the uri/url's to get a tiddler will be server dependent. > That is not a problem. The problem to be solved it what do you get > back when you call GET /some.tiddler.json? Which fields are in the > tiddler and what do they mean? -- 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: Tiddler-Based-Communication-Protocol
I suppose whether or not UUID's make sense as an attribute of a tiddler depends on how you define it's identity. Which has 3 aspects that I can think of: 1: Who wrote it ? 2: Where does it physically or logically reside ? You should be able to edit it whether offline or online - ideally the merge should happen automatically. 3: What's the history ? Each of these may have simple answers in one use case, but complex answers in another: 1: A tiddler may have been modified by several people. 2: The need for it to reside on a server and/or on a pocket device at various points in time is perfectly valid. 3: I don't think the title is a sufficiently robust handle in all cases, obviously not if you require the ability to rename it and still preserve history. Basic TiddlyWiki of course relies on the combination of a title and a physical location for identity. Which is a healthy idea from the point of view of the user working with a single, classic kind of document, but it does present some problems as soon as the context changes: * collaborative editing. * federating content. * simply copying it to a different location and forgetting where the most recent version is... One of the desirable aspects of TW is that it breaks the document into more manageable pieces, that ought to make the process of merging changes more automatic. Adding the UUID goes some way towards reducing this problem, but it doesn't solve it completely. At some point you are still going to be faced with the problem of branching and have to decide how you want to deal with it. Giewiki uses UUID's and version numbers to define identity and history. It allows you to take a page offline, edit it as a classic TiddlyWiki and merge your changes back as long as there is no conflict. Conflict is detected based on tiddler version numbers, but it currently does not offer any help in resolving them, except by making it easy to compare the text of any two versions (without presenting them as separate tiddlers like I believe TiddlySpace still does). It naturally still retains the human-friendly requirement that the titles of the tiddlers be unique within a document. The versioning feature also allows you to specify that a version other than the most recent is the current one (i.e. served by default). I do not reserve a handy syntax for including a version number in a URI -that would be via the query string. Most recently, I've built an auto-save feature on top of this, and added the ability to customize which fields should be listed in the version history. A more ambitious plan to support the same editing experience whether online or offline (using the GAE SDK server) still sits somewhat low on my to-do list together with the idea of putting a custom Python interpreter into IOS - dunno if that would be allowed if restricted to just run your server. ;-) Poul http://code.google.com/p/giewiki/ || http://giewiki.appspot.com/ On 14 Nov., 13:47, Jeremy Ruston wrote: > I'm very interested in the work that's going on around federation, and > I'm also drawn to the value of robust history tracking for tiddlers, > and agree that that is one of the key roles for servers in the > TiddlyVerse. > > I've found myself less keen on making UUIDs be a part of the core > definition of a tiddler. I can see that there are some scenarios that > need UUIDs to work, and so I'm interested in ensuring that the core > definition of a tiddler allows for the use of UUIDs (the simplest way > being to choose to use UUIDs in the title field, and use a different > field for the human readable title). I don't see a role for UUIDs in > the TiddlyWiki core, rather I see their usage being driven by server > side (or federation) concerns. > > Adding UUIDs to the core tiddler model would make tiddlers more > specific to a particular class of servers and/or federation systems. > Some of these systems might well want slightly different semantics for > UUIDs. If the tiddler concept is to be universal then I think it needs > to be surgically minimal: it is primarily about cutting up information > into little chunks, and the details of particular persistence or > federation approaches using UUIDs shouldn't intrude on the core model. > We want the idea of a tiddler to be as simple as possible so that as > many people as possible can agree on it. > > Best wishes > > Jeremy > > > > > > > > > > On Mon, Nov 14, 2011 at 10:56 AM, tiddlygrp wrote: > > Hi Chris, > > > the example of Ward's federated wiki was chosen because he has already > > build a simple json representation of pages (something like a tiddler) > > with uuid and semantics to track changes. This could be easily > > adapted for tw. > > In my view uuid's are something for the computer to track. They > &g
[tw] Re: Autosave, revision history, and the cloud
On 11 Sep., 15:56, Måns wrote: > GieWiki by Poul:http://giewiki.appspot.com/ > The auto-save feature is definitely something that would build naturally on the versioning features already present in giewiki, so I was tempted to give it a try. It's not quite finished yet, but stay tuned. /Poul -- 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: tiddlyspace 1.0.40
"Fanchon had once been pretty, and, — to tell the truth — this ornament did not have a very pleasing effect. ". The text renders as intended at http://wolke.tiddlyspace.com/ but not — alas — at http://wolke.tiddlyspace.com/bags/wolke_public/tiddlers/The%20Ludicrous%20Wishes :-) Poul On 9 Sep., 22:33, chris.d...@gmail.com wrote: > http://tiddlyspace.com/has been updated to use the most recent > release of TiddlySpace, 1.0.40. Most of the changes are background > changes to lay in the groundwork for more extensive improvements > later. The two most visible changes are: > > * An improved default HTML representation look and feel. You can see > this in action when viewing search results: > > http://tiddlyspace.com/search?q=mountains > > or clicking on the tiddlers that result from that search. > > * That same page demonstrates the other major change. It used to be > when viewing those results each tiddler would be linked into the > tiddlyspace.com domain. Now they link to the space from which the > tiddler originates. The same thing happens with Atom feeds as well. > This means that when you follow links from searches or feeds you > will get the HTML look and feel desired by the member(s) of the > space. > > Both of these things are part of an ongoing effort to extend the > capabilities of TiddlySpace as service for sharing and manipulating > tiddlers. I'm sure Jeremy, Jon, Colm, Ben and Matt will be sharing > their plans in other postings. > > You can see some examples of the different opportunities: > > * My space:http://cdent.tiddlyspace.com/ > * Jon's space:http://jon.tiddlyspace.com/ > *http://gadabout.tiddlyspace.com/ > * Jeremy's standard tiddlywiki-based space:http://jermolene.tiddlyspace.com/ > * Recent activity on tiddlyspace:http://activity.tiddlyspace.com/ > > -- > Chris Dent http://burningchrome.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] We're being watched
While the term wikigroup seems rather odd there is hardly any doubt what he's talking about: http://www.polecat.co/news/wp-content/uploads/2011/08/User-Type_analysis_of_Tiddlywiki_wikigroup_community_v3.pdf Albeit rather academic and clearly imposing a model, his observations are perhaps still food for thought. Or whatever. /Poul -- 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] Giewiki release 1.14
The short twit: giewiki release 1.14 is out. Read all about it at http://giewiki.appspot.com or just get it at http://code.google.com/p/giewiki - I'd be hard pressed trying to find a common theme beyond usability for the improvements this time around. The highlights ? -well check it out for yourself. But I should note that, despite what it may look like, no animals were harmed in making this release. :-) Poul -- 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] storeArea / shadowArea location
I've wondered if there is any good reason (that I have somehow overlooked) why TiddlyWiki positions the storeArea after the shadowArea, rather than ahead of it in the body element. It seems to me that for search engine friendlyness, it should have the storeArea at the top of the body element, ideally with the tiddlers listed in DefaultTiddlers topmost. As it is, if I search for tiddlywiki, the lead text that Bing has grabbed from TiddlyWiki.org is And equally useful, the lead text that google has grabbed from osmosoft.com for that query is: These [[InterfaceOptions]] for customising [[TiddlyWiki]] are saved in your browser Your username for signing your edits. Write it as a [[WikiWord]] (eg ... But, before I change giewiki in light of this, I thought, maybe there is a good reason for the current file layout somewhere. :-) Poul -- 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: "Save to web" stopped working
Hi, provided that your existing TiddlySpot content is well-formed XHTML (so I can parse it as XML), and provided your files are less than 1MB each, you can from within the page setup dialog of giewiki upload the files or pull them directly from TiddlySpot into a giewiki page. In the latter case, I've managed to remove the 1MB limit in the version you find running at http://giewiki.appspot.com, but this hasn't yet made it into the released download. I've put together a brief tutorial here: http://giewiki.appspot.com/Tutorials/ImportFromLibraries# You are welcome to try it out by creating a page below http://giewiki.appspot.com/SandBox/ (you can make it private if you prefer) and try importing your content. Beware however that giewiki is not intended as a TiddyWiki hoster, so don't rely on them to stay there forever. I could probably be persuaded to let you keep it as a nn.giewiki.appspot.com subdomain until you've decided if giewiki is right for you. /Poul On 17 Aug., 18:48, MummerX wrote: > @PMario - your pojnts, in order ... > Yup, deleting cookies in IE8 fixed the <> error and the stack > errors. > On saving to web, it still fails: "Do you want to navigate away from > this page?" and " '0' is null or not an object". > *** Once (and only once) in many tries, it saved successfully! - This > is getting really screwy now. > OK, your other points ... > <> = 2.5.0 > <> = 2.5.3 > This is for my large wiki; the one I am having problems saving to web > (@ work). Does that give any clues? > Actually, I have just now tried upgrading the wiki software, and it > tells me this can only be done for a locally stored file (and this is > web hosted). So, I guess I have the latest version of both the above? > Sorry to be dim, but what is an include mechanism? Will it allow me to > transfer my content from my old large wiki to another? Happy to RTFM, > if you give me an URL. > > @Bauwe > I only just heard recently about GieWiki, so I was not aware (until > now) that it offers MPTW. Thanks! :o) > Is there an easy way to transfer my content across, if I create a wiki > there? Or must I retype it all? (>175k I think) > > Grateful thanks chaps. I am bowled over by your helpfulness. :o) -- 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: MathQuill as a plugin
I haven't used it, but there's also http://bob.mcelrath.org/tiddlyjsmath-2.0.3.html /Poul On 15 Aug., 09:01, Milind wrote: > Hi, > Is it possible to make a plugin out of MathQuill (http:// > mathquill.github.com/) onto tiddlywiki? It allows WYSIWYG interface > for writing equations and would be really helpful. Don't know how that > can be done if its possible. Can anyone help? > > Thanks, > Milind -- 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 expand text area in editor?
If you use Chrome, it's a non-problem, as it will allow you to resize the control to your immediate needs by dragging the bottom-right corner. /Poul On 17 Aug., 15:04, "Mark S." wrote: > Thanks Ton, > > I changed it both in the options and by a manual configuration > tiddler. Set it to 100. But it doesn't seem to change the number of > rows the text editor shows. Keeps showing about 23 rows, with anything > more than that scrolling. > > What I would like is to show all the lines in the text edit box, with > no scrolling (I'll scroll the entire TW page if I have to). > > Thanks! > Mark > > On Aug 16, 10:38 pm, TonG wrote: > > > > > > > > > Hi Mark, > > > It is one of the configuration options. > > You can set it in Advanced options (check 'Shown unkown options'). > > Or set it in an configuration tiddler with > > config.options.txtMaxEditRows. > > > Cheers, > > > Ton > > > On Aug 16, 10:50 pm, "Mark S." wrote: > > > > Hi all, > > > > Could someone tell me (or remind me) how to expand the number of lines > > > used when editing. I'm using the quickedit capability, if that > > > matters. > > > > Thanks! > > > Mark -- 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: mail notifications
While I haven't yet implemented this particular feature in giewiki, the Google App Engine hosting environment includes services that would let me do so easily. It should definitely be on my to-do list, I suppose - having so far introduced mail integration only as a way to allow sending messages to the author of a tiddler. /Poul http://giewiki.appspot.com | http://code.google.com/p/giewiki On Aug 13, 8:53 pm, Seba wrote: > Hi, > > Can anyone tell me if it is possible to setup automatic mail > notifications in tiddly with a plugin or a macro? > > For example, certain action triggers mail notification sent to a > specific user. > > Thank you. > > regards, > seba -- 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: ornamental border for tiddlers?
I haven't tried it, but the way to go would be to edit the ViewTemplate shadow tiddler, wrapping the elements that you wanna wrap in new element that you would adorn with various CSS attributes (padding, background-image) - either directly or (better) by assigning a class name to your new element and referencing that in the StyleSheet tiddler. /Poul On 14 Aug., 05:06, passingby wrote: > is it possible to have an ornamental border (something like flowers or a > custom design/image) around tiddlers when in view mode? -- 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: Flexigrid and TiddlyWiki
Thank you for the analysis - I guess I was just being lazy.
/Poul
On 13 Aug., 15:14, Eric Shulman wrote:
> > Although Tyler's version and Saq's version are named differently, and
> > Saq claims to be the author of his and documents it differently, it
> > does seem that they have an awful lot in common (not really having
> > reviewed the code, but judging from the examples [near identical] and
> > how they behave). Is it entirely fair of Saq to claim ownership of his
> > version..?
>
> Having actually *looked* at the code for SortableGridPlugin (SGP) and
> TableSortingPlugin (TSP), I can definitely see some similarities.
> However, there is a good reason for this: the code in *both* plugins
> seem to be based, in part, on the work of Stuart Langridge, who
> published a widely-reproduced solution for javascript-based sortable
> tables, back in 2003 (long before TiddlyWiki even existed).
>
> As a result of this common ancestry, both SGP and TSP share several
> key aspects that are inherited from Langridge's original
> implementation and documentation. For example, the contents in the
> sample tables (e.g., "Bloggs, Fred"... etc.) are "nearly identical"
> because both were apparently copied and adapted from the sample data
> shown in Langridge's 2003 original posting.
>
> In addition, both plugins use the same syntax for adding a CSS
> classname ("|sortable|k") to the table, as well as the syntax for
> designating a 'heading' row ("|foo|bar|baz|h"). This is because
> Langridge's code also uses the "sortable" CSS classname and the
> (table heading) element to specify and control sorting on the columns
> in a table.
>
> There are also similar 'code patterns' used in some funtions of both
> plugins. However, this would be the natural consequence of both
> plugin authors adapting Langridge's original implementation for use in
> TiddlyWiki, and I don't think it represents any illicit borrowing from
> each other.
>
> One major difference worth noting is the *size* of each plugin:
> SortableGridPlugin weighs in at 15986 bytes, while TableSortingPlugin,
> is only 5849 bytes. Given that both provide the same functionality,
> the obvious choice is for the smaller implementation.
>
> -e
--
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: Flexigrid and TiddlyWiki
Thanks everyone, Although Tyler's version and Saq's version are named differently, and Saq claims to be the author of his and documents it differently, it does seem that they have an awful lot in common (not really having reviewed the code, but judging from the examples [near identical] and how they behave). Is it entirely fair of Saq to claim ownership of his version..? /Poul On 12 Aug., 11:44, Eric Shulman wrote: > On Aug 11, 10:30 pm, Poul wrote: > > > I just discoveredhttp://rumkin.com/tools/tiddlywiki/#SortableGridPlugin > > > which, in the context of giewiki, should definitely be my first > > choice, being much more lightweight and not dependent on jQuery. > > See > http://tiddlywiki.squize.org/#[[New%3A%20TableSortingPlugin]] > and > http://www.TiddlyTools.com/#GridPlugin > > enjoy, > -e -- 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: Flexigrid and TiddlyWiki
I just discovered http://rumkin.com/tools/tiddlywiki/#SortableGridPlugin which, in the context of giewiki, should definitely be my first choice, being much more lightweight and not dependent on jQuery. /Poul http://giewiki.appspot.com | http://code.google.com/p/giewiki On Aug 9, 8:52 am, Poul wrote: > Hoping to pave the way for a future project of mine, I wondered if > anyone has tried to integrate Flexigrid (http://www.flexigrid.info) > with TiddlyWiki? > If so, Google hasn't noticed, as far as I can tell :-/. Although it > has noticed my interest in the subject :-). > > If not, there's still a chance that someone will beat me to it and > post their results here. > > /Poul -- 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] Flexigrid and TiddlyWiki
Hoping to pave the way for a future project of mine, I wondered if anyone has tried to integrate Flexigrid (http://www.flexigrid.info) with TiddlyWiki? If so, Google hasn't noticed, as far as I can tell :-/. Although it has noticed my interest in the subject :-). If not, there's still a chance that someone will beat me to it and post their results here. /Poul -- 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: Preview feature bug in giewiki
The easy fix of course turned out to be embarrassingly simple: Apply the viewer class in stead of inventing a new one. But thanks again to Bauwe for lending an eye. /Poul On Aug 1, 11:23 am, Poul wrote: > One of the bugs in giewiki that I'm painfully aware of is that the > preview feature in the edit template doesn't render everything > correctly. While I might eventually figure it out myself with the > excellent help of the built-in debugger in Chrome, I'm also tempted to > try prompt the CSS-savvy in the community for some help. If you can > point to someone somewhere who has gotten it perfectly right, please > do. I suspect it has to do with the CSS classes that are (or are not) > applied. > > As an aside, if anyone know of a better tool for the purpose than > Chrome, that's also a good reason to reply. > > :-) Poul > > http://giewiki.appspot.com|http://code.google.com/p/giewiki -- 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] Preview feature bug in giewiki
One of the bugs in giewiki that I'm painfully aware of is that the preview feature in the edit template doesn't render everything correctly. While I might eventually figure it out myself with the excellent help of the built-in debugger in Chrome, I'm also tempted to try prompt the CSS-savvy in the community for some help. If you can point to someone somewhere who has gotten it perfectly right, please do. I suspect it has to do with the CSS classes that are (or are not) applied. As an aside, if anyone know of a better tool for the purpose than Chrome, that's also a good reason to reply. :-) Poul http://giewiki.appspot.com | http://code.google.com/p/giewiki -- 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] What TW features do you find missing in giewiki
I'm sure TiddlyWiki power users could find several things (bug fixes, recent feature enhancements, etc...) that they find missing in giewiki. But, since giewiki admittedly has forked quite a bit from TiddlyWiki and since I'm reluctant to include jquery as a dependency, trying hard to keep the script size down, I'd like if interested parties would help me out in pointing out the things that they find most important in what has improved in TW since 2.4.1. In return, I'll try and carry them over. Eventually. I hope. Can't promiss. /Poul http://giewiki.appspot.com || http://code.google.com/p/giewiki -- 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: Giewiki: 5 questions for Poul (or anyone)
Deleting everything from the datastore will give you a clean giewiki, good as new. /Poul http://giewiki.appspot.com || http://code.google.com/p/giewiki On 10 Jul., 01:03, Ash wrote: > Can I delete the entire datastore to get rid of these insidious > incompatible plugins? CanGiewikicontinue to operate and rebuild a > datstore from scratch if there is absolutely no data or does the code > expect some data to begin operating? > > Thanks to your advice > athttp://giewiki.appspot.com/FeedBack#%5B%5BExporting%20from%20Giewiki%... > , I can safely export all my tiddlers to a downloaded TW and then > import them again (minus the plugins which I manually delete in the > offline version). > > thank you, > Ash > > On Jul 9, 7:53 pm, Poul wrote: > > > > > > > > > Oh, that's why: the root page cannot be deleted. > > > On 8 Jul., 11:23, Ash wrote: > > > > inline: > > > > On Jul 8, 7:00 am, Poul wrote: > > > > > Sorry, I don't scan this group regularly. > > > > > 1: Intra-site tiddler links the syntax [[text|/FeedBack#%5B%5BNice > > > > %20Job%5D%5D]] . You can easily find the link via the SiteMap, using > > > > your browser's feature for giving the exact link. > > > > > 2: I will have to look into this. > > > > > 3: Unless the PageProperties dialog is screwed up, you can delete the > > > > entire page that way. As for the plugin manager, I'll have to look > > > > into this. > > > > Thanks for all that. > > > > I can't see a way to delete a page using that dialog. > > > > This is the "root" page of myGieWikiand the Page Setup dialog > > > "works" (although it doesn't let me assign a group to the page for > > > some reason), however there is no "delete page" link or something > > > (what am I looking for?). The actual PageSetup tiddler itself only has > > > a "close" link above it and a "save" link at the bottom of the actual > > > dialog. > > > > Is my PageProperties "screwed up"? (If so how do I delete the tiddlers > > > via the GAE data viewer.) > > > > thanks, > > > Ash > > > > > 4. There currently is no support for exporting specific tiddler or the > > > > entire site, only pages. > > > > > 5. Use the MPTW template or tailor it to your taste. > > > > > On 1 Jul., 12:38, Ash wrote: > > > > > > I'm trying to useGiewikias an internal company wiki, but I have a > > > > > few things I'm very unclear about. > > > > > > 1. How do I link to tiddlers on other pages?Giewikiallows pages > > > > > (i.e. mygiewiki.appspot.com/project1#ATiddler) is there an expended > > > > > link syntax for linking to tiddlers on other pages? Tiddlyspace has > > > > > TiddlerInAnotherSpace@anotherspace syntax. > > > > > > 2. I'm having a lot of problems getting access permissions to actually > > > > > work. I have two people b...@mycompany.com (a Google Apps account) > > > > > and > > > > > j...@mycompany.com (also). I don't want joe to access (i.e. even view) > > > > > a certain page (e.g. the /project1 page) or any of the tiddlers within > > > > > it. I can set bob to a project1 group but these appear to be specific > > > > > to a page, not across pages. Whatever I do, it doesn't seem to work :( > > > > > > 3. I accidentally imported a whole (actually a tiddlyspace wiki, > > > > > funnily enough) wiki which includes a lot of incompatible plugins. I > > > > > managed to delete some unwanted tiddlers in bulk by directly managing > > > > > the datastore via GAE interface. I don't mind losing all the data and > > > > > starting again but I'm too nervous just to delete the whole datastore > > > > > as I bet it will be left in an inconsistent state. Trying to delete > > > > > the plugins via the PluginManager interface just reported an error > > > > > that it "needs a reason" so I can't delete them that way (even when I > > > > > deselect the "ask a reason when deleting" preference). > > > > > > 4. How do I export tiddlers, or the entire tiddlywiki? Is there any > > > > > way the versioning will be kept? > > > > > > 5. What's the simplest way to change the theme/skin to make it look > > > > > prettier? -- 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: History of Tiddlywiki
I remember reading Jeremy's own account, but I can't remember where. I
have, however followed it pretty much from the start, and I guess it's
safe to say that the release 1.x versions, that Jeremy published in
2004, were very experimental. It was sort-of a write-only web page in
that you could add content and the browser would hold it and present
an index, let you add hyperlinks, etc - but you couldn't actually save
anything permanently. Nevertheless, many people immediately recognized
it's potential. Release 2.0, which came in late 2005, was a big step
forward, with an architecture that was designed for extensibility,
allowing for the vast range of plugins, derivatives and applications.
- Poul
http://giewiki.appspot.com - http://code.google.com/p/giewiki
On Jul 20, 8:55 pm, Richard Niolon wrote:
> Hi All
> Maybe this is out there and I just can't find it... but I'm doing a
> presentation next week for teachers on using a TiddlyWiki for class
> websites. I wanted to just include a brief bit about the history of the
> Tiddlywiki project - when it started, how long before it "took off", why
> Jeremy started it, maybe what he was thinking when he went open source with
> it instead of making $oftware ("oh what the hell..." or "Fear me
> Microsoft!"... :)
>
> I just want a paragraph or so of that kind of information just to frame the
> background of it.
>
> Does anyone know where I might find this? (Or Jeremy, if you see this,
> maybe you could just write a quick paragraph on this :)
>
> Thanks
> Rich
--
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: Giewiki: 5 questions for Poul (or anyone)
Oh, that's why: the root page cannot be deleted. On 8 Jul., 11:23, Ash wrote: > inline: > > On Jul 8, 7:00 am, Poul wrote: > > > Sorry, I don't scan this group regularly. > > > 1: Intra-site tiddler links the syntax [[text|/FeedBack#%5B%5BNice > > %20Job%5D%5D]] . You can easily find the link via the SiteMap, using > > your browser's feature for giving the exact link. > > > 2: I will have to look into this. > > > 3: Unless the PageProperties dialog is screwed up, you can delete the > > entire page that way. As for the plugin manager, I'll have to look > > into this. > > Thanks for all that. > > I can't see a way to delete a page using that dialog. > > This is the "root" page of my GieWiki and the Page Setup dialog > "works" (although it doesn't let me assign a group to the page for > some reason), however there is no "delete page" link or something > (what am I looking for?). The actual PageSetup tiddler itself only has > a "close" link above it and a "save" link at the bottom of the actual > dialog. > > Is my PageProperties "screwed up"? (If so how do I delete the tiddlers > via the GAE data viewer.) > > thanks, > Ash > > > 4. There currently is no support for exporting specific tiddler or the > > entire site, only pages. > > > 5. Use the MPTW template or tailor it to your taste. > > > On 1 Jul., 12:38, Ash wrote: > > > > I'm trying to use Giewiki as an internal company wiki, but I have a > > > few things I'm very unclear about. > > > > 1. How do I link to tiddlers on other pages? Giewiki allows pages > > > (i.e. mygiewiki.appspot.com/project1#ATiddler) is there an expended > > > link syntax for linking to tiddlers on other pages? Tiddlyspace has > > > TiddlerInAnotherSpace@anotherspace syntax. > > > > 2. I'm having a lot of problems getting access permissions to actually > > > work. I have two people b...@mycompany.com (a Google Apps account) and > > > j...@mycompany.com (also). I don't want joe to access (i.e. even view) > > > a certain page (e.g. the /project1 page) or any of the tiddlers within > > > it. I can set bob to a project1 group but these appear to be specific > > > to a page, not across pages. Whatever I do, it doesn't seem to work :( > > > > 3. I accidentally imported a whole (actually a tiddlyspace wiki, > > > funnily enough) wiki which includes a lot of incompatible plugins. I > > > managed to delete some unwanted tiddlers in bulk by directly managing > > > the datastore via GAE interface. I don't mind losing all the data and > > > starting again but I'm too nervous just to delete the whole datastore > > > as I bet it will be left in an inconsistent state. Trying to delete > > > the plugins via the PluginManager interface just reported an error > > > that it "needs a reason" so I can't delete them that way (even when I > > > deselect the "ask a reason when deleting" preference). > > > > 4. How do I export tiddlers, or the entire tiddlywiki? Is there any > > > way the versioning will be kept? > > > > 5. What's the simplest way to change the theme/skin to make it look > > > prettier? -- 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: Giewiki: 5 questions for Poul (or anyone)
Sorry, I don't scan this group regularly. 1: Intra-site tiddler links the syntax [[text|/FeedBack#%5B%5BNice %20Job%5D%5D]] . You can easily find the link via the SiteMap, using your browser's feature for giving the exact link. 2: I will have to look into this. 3: Unless the PageProperties dialog is screwed up, you can delete the entire page that way. As for the plugin manager, I'll have to look into this. 4. There currently is no support for exporting specific tiddler or the entire site, only pages. 5. Use the MPTW template or tailor it to your taste. On 1 Jul., 12:38, Ash wrote: > I'm trying to use Giewiki as an internal company wiki, but I have a > few things I'm very unclear about. > > 1. How do I link to tiddlers on other pages? Giewiki allows pages > (i.e. mygiewiki.appspot.com/project1#ATiddler) is there an expended > link syntax for linking to tiddlers on other pages? Tiddlyspace has > TiddlerInAnotherSpace@anotherspace syntax. > > 2. I'm having a lot of problems getting access permissions to actually > work. I have two people b...@mycompany.com (a Google Apps account) and > j...@mycompany.com (also). I don't want joe to access (i.e. even view) > a certain page (e.g. the /project1 page) or any of the tiddlers within > it. I can set bob to a project1 group but these appear to be specific > to a page, not across pages. Whatever I do, it doesn't seem to work :( > > 3. I accidentally imported a whole (actually a tiddlyspace wiki, > funnily enough) wiki which includes a lot of incompatible plugins. I > managed to delete some unwanted tiddlers in bulk by directly managing > the datastore via GAE interface. I don't mind losing all the data and > starting again but I'm too nervous just to delete the whole datastore > as I bet it will be left in an inconsistent state. Trying to delete > the plugins via the PluginManager interface just reported an error > that it "needs a reason" so I can't delete them that way (even when I > deselect the "ask a reason when deleting" preference). > > 4. How do I export tiddlers, or the entire tiddlywiki? Is there any > way the versioning will be kept? > > 5. What's the simplest way to change the theme/skin to make it look > prettier? -- 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 can I use tiddlySpace? Where can I get installation guidelines?
I might add that if you are looking for a server-side, that supports adding comments to tiddlers, I believe giewiki (http:// giewiki.appspot.com) may suit you better. I may be wrong, but to my knowledge TiddlySpace does not. /Poul On 9 Maj, 07:11, Dani Zobin wrote: > Great explanation! > > > > > > > > On Mon, May 9, 2011 at 3:36 AM, Shavin wrote: > > Hi rroque. > > Tiddlyspace is already a usable website/platform. All you need is to > > create your own space herehttp://tiddlyspace.com/and get started > > right away. > > Now in addition to this the software which runs tiddlyspace is open > > source. This means that you can download that software from here > >https://github.com/TiddlySpace/tiddlyspaceand host it on your own > > server and run a website just like tiddlyspace.com. Of course you do > > not need to do that just to create a tiddly space for yourself because > > it would be an overkill, you can just create a space for yourself on > > tiddlyspace.com. > > Another thing, tiddlyspot is a separate website/platform. When > > tiddlywiki was created a website hosting was needed where people could > > created their own instances of tiddlywikis and for this tiddlyspot.com > > was created. On this website one can create one's own tiddlywiki. A > > tiddlywiki on tiddlyspot has its limitations. A tiddlywiki can only be > > downloaded and uploaded whole, in one full file. So that even if you > > have to update a single paragraph you'd have to upload and save the > > whole file. This is because the tiddlywiki file is treated as one > > single unit. > > Later on as tiddlywiki world developed a new model of tiddlyspace was > > developed in which a tiddler is treated as a unit and can be updated. > > Besides this a tiddlyspace can be included into other spaces. By doing > > this any public tiddlers of that site shall start showing up in the > > tiddlyspace they are included into. There are other features too. > > You can think of tiddlyspot as separate, standalone tiddlywiki files. > > On other hand tiddlyspace can be thought of as a web of spaces which > > can intermingle with each other to a certain degree. > > If you want to keep personal offline stuff in a tiddlywiki you can > > download a tiddlwiki file from tiddlywiki.com. If you want a > > tiddlywiki which has a copy offline as well as is hosted online, you > > can create one at tiddlyspot.com. If you want just an online thing > > then tiddlyspace should be your choice, cos it will be faster to save > > data. > > > On May 8, 6:27 pm, "rro...@renatoroque.com" > > wrote: > > > I installed Comment Plugin by Eric but it does not perform save on > > > server side. > > > > I reported this and Eric told me that "To save those tiddler changes > > > online, you need a "server-side" saving mechanism. See: > > > >http://tiddlywiki.org/#TiddlySpace%20Tiddlyspot > > > > I had a look at that URL and I was confused: > > > > It says:"TiddlySpace is a service for creating and curating small > > > packets of content on The Web. You may collaborate with others, > > > assemble content by including spaces, add cool features using plugins > > > and mix your content with other services using the API. TiddlySpace > > > is > > > Open Source software from Osmosoft so you're free to host your own > > > instance on your own domain and are encouraged to contribute to the > > > project. " > > > > How can I use TiddlySpace service? What must I install? Where is that > > > open source SW ? Must I use Tiddlyspot? Does it imply not using my > > > server location? > > > > Any guideline somewhere? > > > > Sorry for my basic ignorance but this TiddlySpace is complertely new > > > for me > > > > Regards > > > -- > > 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. -- 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: Pull GMail into a TiddlyWiki
Get a smartphone. The iPhone and, I'm sure, Androids should do fine. On 30 Mar., 21:02, Craig in Calgary wrote: > I have six (6) more months at a client site that has locked down > access to Gmail. I cannot accesshttp://mail.google.comor even an RSS > of my mail. Is it possible to configure a TiddlySpot or TiddlySpace TW > that could receive my Gmail email or at least display an RSS feed with > the email titles so I know what's waiting for me? The only non-TW > solution I can think of is to forward all my Gmail to the email > account my client has provided. I do not want to do this. But if a TW > can man-in-the-middle me then I can stay informed about my world > throughout the day. If a TW can digest something and generate tiddlers > or update a tiddler then I could even just monitor the TWs' RSS. -- 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] Lifting the ViewTemplate idea out of the story column
Hi all, I've been wondering if anyone has taken the ViewTemplate idea one step up (or back, if you will), and made it possible to have versions that render outside the story column. I was thinking of two alternatives: floating (Eric has the code for that, of course), and full-width, in an area between the titles and the the 3-column layout. But, to make myself clear, I'd like to be able to control the choice of presentation space at the tiddler level. If anyone has, I'd like very much to include it as an additional template in my next giewiki release, which makes template selection a simple dropdown menu and allows the use of external script libraries, including of course jQuery, to be specified at the page/template level, also via a dropdown menu. /Poul -- 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: Tutorial: Debugging with Google Chrome
When applied to a li or an ol as this case is, it does appear to be a
workaround:
It puts the marker box inline with the rest of the element, so it
doesn't flow over my image, but that's not quite what I wanted.
When an element floats to the left of a box, shouldn't everything
realign equally...?
On 19 Mar., 13:54, Jeremy Ruston wrote:
> I haven't had a chance to test it, but some googling suggests that
> this might possibly help:
>
> ul { list-style-position: inside; }
>
> Cheers
>
> Jeremy
>
>
>
>
>
>
>
>
>
> On Thu, Mar 17, 2011 at 6:10 PM, Poul wrote:
> > Hello everyone,
>
> > To assist in pinpointing the bugs that giewiki users experience, I put
> > together this turorial:http://giewiki.appspot.com/Tutorials/Debugging
> > I'm posting it here in the hope that it may be of use to others as
> > well, and to ask the CSS experts if they can pinpoint a rendering
> > error that I am seeing: When I use numbered lists in a place where it
> > gets rendered to the right of an image, the numbers are *not* aligned
> > with the surrounding text, but rather float over my image! It must be
> > said that I use my own image macro in stead of the TiddlyWiki feature,
> > because the latter does not allocate margins around the image. Both
> > Chrome and IE agree on how this should be rendered, and it isn't quite
> > what I had intended. So what's wrong?
>
> > --
> > 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
> > athttp://groups.google.com/group/tiddlywiki?hl=en.
>
> --
> 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] Tutorial: Debugging with Google Chrome
Hello everyone, To assist in pinpointing the bugs that giewiki users experience, I put together this turorial: http://giewiki.appspot.com/Tutorials/Debugging I'm posting it here in the hope that it may be of use to others as well, and to ask the CSS experts if they can pinpoint a rendering error that I am seeing: When I use numbered lists in a place where it gets rendered to the right of an image, the numbers are *not* aligned with the surrounding text, but rather float over my image! It must be said that I use my own image macro in stead of the TiddlyWiki feature, because the latter does not allocate margins around the image. Both Chrome and IE agree on how this should be rendered, and it isn't quite what I had intended. So what's wrong? -- 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] The Wikibook on TiddlyWiki
I didn't see a lot of response to my suggestion to adopt http://en.wikibooks.org/wiki/TiddlyWiki as a community project, so I'll give it a clean thread. I certainly understand Jeremy's reaction that TiddlyWiki is a more obvious form for educating about TiddlyWiki, and for reference material and detailed guidance, I agree. On the other hand, it could confuse the casual surfer who may be familiar with Wikipedia to find that while you can click view, you can't actually change anything on a web-hosted TW. Furthermore, the growing segment of "post-PC" readers with their tablet devices, is probably more reachable with something more akin to a book. Imagine, say * She in a deckchair with her Amazon Kindle * He in his armchair with his iPad (it's need for gravitational support is the main reason I don't have one). While they aren't likely to start writing blogs the next day, I feel that it's a worthwhile efford to try to convey the message that there are better alternatives for most one-way communication than Facebook on the one end and Microsoft Word on the other. A book on TW and it's derivatives, be it http://en.wikibooks.org/wiki/TiddlyWiki or other, should in my opinion have a broader focus than that which was probably intended by whoever started it. But that's also what in my opinion could make it fun to write. Particularly for those of us who buy into the original wiki concept of collaborative writing. After all, the book form allows more freedom to digress than web publishing in general. Anyway, to sort of get the ball rolling again, I've started by trying to give the introduction some more words for a broader reach and hopefully, a mental image that makes sense. Join me if you like, use the discussion page, or shoot it down if that's how you feel. I don't have a lot of time to put into it, but to me it's the sort of thing I might do late in the evening. Happy tiddling, Poul Staugaard http://giewiki.appspot.com || http://code.google.com/p/giewiki -- 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: Preparing for giewiki release 1.10
On Mar 10, 12:45 pm, Jeremy Ruston wrote: > > Absolutely. You may find, I admit, that I haven't been as dilligent in > > keeping strings separate, avoiding namespace pollution, etc. And > > obviously not bothered to preserve the codebase untouched. > > I wondered about that; it would certainly be cool if we could engineer > things so that giewiki is getting the latest tiddlywiki core. It //would// be nice, but I figured that tiddlywiki was approaching a sort-of steady-state where important fixes and enhancements could be ported over manually. I made it a fork in order to peel away all that I didn't need and make room for what I wanted to add. > I'm not such a fan of local storage for storing user data. I feel more > confident if I can see my data in a file, rather than hidden away in > an invisible cache that is tied to one browser. Your choice, but my creed is that you should keep your content in the cloud and only take it offline when you have to. It has tremendous advantages when you work on several different devices, local or remote, more or less at the same time. > So that would mean that applying a translation would be a build step? > That would constrain all users of a server to see the same language, > I'm not sure if that's an important limitation. Well, the content would typically be kept in one language anyway. I'm not a fan of sites that try to offer partial translations. If you want to offer multiple languages versions, install them separately on app engine. > > As for collaborative effords, I think it might be a good idea to try > > and create a book, in contrast to this rather nerdy forum, perhaps in > > the forum of the still very > > half-heartedhttp://en.wikibooks.org/wiki/Tiddlywiki > > -particularly now that tw.org is moving away from the familiar > > mediawiki form. > > You're proposing a collaborative effort to write a book about > TiddlyWiki? Interesting idea! I'm rather drawn towards eating my own > dogfood, and using TiddlyWiki rather than a conventional book, but > it's definitely an interesting idea. Rather than see someone else write the book for profit, we should write it for free. I'm not sure if it should lean towards the evangelical or the handbook - that'll mostly be up to those who volunteer. I also would be tempted to write in my own private environment, but once it's perfectly clear what a page or chapter is about, I believe wikibooks would be an excellent medium. It certainly has the advantage that professional-looking output can be generated by the built-in PDF engine - ready to print and pass around. Happy tiddling, Poul -- 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: Preparing for giewiki release 1.10
I'm not sure what you mean. It's a standard feature of giewiki, that can be removed by changing the ViewTemplate. If you mean how does it port to other TW dialects, that requires some work, both client- and server-side. Happy tiddling, Poul On Mar 10, 10:16 am, Tobbe wrote: > Hi, > > What do I need to do to get "add comment" "add message" and "add note" > under every tiddler? > > //Tobbe -- 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: Preparing for giewiki release 1.10
Hi Jeremy,
Absolutely. You may find, I admit, that I haven't been as dilligent in
keeping strings separate, avoiding namespace pollution, etc. And
obviously not bothered to preserve the codebase untouched. In stead
I've tried to focus on making it more accessible and familiar. I only
recently implemented the TW-based offline feature as a sort of short-
term solution, not really intending to worry about merge conflicts,
but handling renamed tiddler identity. Ultimately, I believe the right
approach is to use HTML5 for local storage, for security reasons. My
approach to client-server interface is classic HTTP posts with replies
in XML form. With a list-based mapping of Python methods to
JavaScript. As for translation, my idea which I haven't yet fully
implemented is to put all translatable strings in double-quotes, and
all other strings in single quotes. Then, in theory, you could easily
build a translation table and with a simple utility apply it to the
source code; with the advantage of more compact code.
I only just discovered interview.tiddlyspace.com, and I really like
it. The automatic transclusion idea is beginning to dawn on me.
Anyway, I'd like to suggest a few more questions: How often, in % of
time, do you work offline? How much of your tiddling is personal, how
much is collaborative, and how much is for publishing?
As for TiddlySpace, I do find a couple of features missing though:
* There is no patteren for discovering who the owner(s) of a space is.
* There is no obvious channel for feedback (comments, talk page, quick-
polls or other).
* There is no apparant way to make a private tiddler public.
* It would be nice if you could pull the content out in the familiar
XML structure of Tiddlywiki, but leaving out all the rest. It would
help importing into giewiki, which is handicapped by App Engine's 1MB
limit on HTTP requests.
And finally, the " saved succesfully" message looks to me
like an error ("negative") message, at least on a red background. If
the tiddler closes in response to clicking 'done', surely it should be
safe to assume that your edit //was// saved succesfully!
As for collaborative effords, I think it might be a good idea to try
and create a book, in contrast to this rather nerdy forum, perhaps in
the forum of the still very half-hearted http://en.wikibooks.org/wiki/Tiddlywiki
-particularly now that tw.org is moving away from the familiar
mediawiki form.
And finally, thanks to whoever for the link on TW.com - it seems to
have doubled the effective visiblity of giewiki. I must confess, I
haven't exactly been overwhelmed with feedback like you were, but I
take that only as a sign that the competition has toughened.
Cheers,
Poul
--
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: Preparing for giewiki release 1.10
Hi Måns, I've improved a bit on the DeploymentGuide at code.google.com/p/ giewiki, but it' still mainly about the other options: Window/Mac & cloud hosting. Linux users are expected to master the command line: http://code.google.com/intl/da-DK/appengine/docs/python/tools/devserver.html http://code.google.com/intl/da-DK/appengine/docs/python/tools/uploadinganapp.html Cheers, Poul On 9 Mar., 07:53, Måns wrote: > Hi Poul > > > Bear with me if you don't (care) - we all have our ways; giewiki is > > just my 'cloudy' way of tiddling. > > I really like your giewiki, - I've got to try to set it up locally on > a Linux-box... > Any hints for this? > > Cheers Måns Mårtensson -- 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] Preparing for giewiki release 1.10
Hi everyone who cares, giewiki development is now approaching release 1.10 - new features so far: * Page templates can now carry a set of predefined tags as a simple way to indicate a use pattern. * Tiddlers can be tagged isPrivate (by the page owner only). * More user-friendly tidler tagging process; with a separate menu of the special system-defined tags (called attributes); I never could remember excludeSearch & excludeLists. * Further enhancements to the page setup dialog (history available while editing). A plea to anyone who might be pulling the stuff directly from subversion: You could help improve the quality of releases by reporting any bugs that you find. If anyone thinks a presence on github would be conducive to doing so, also let me know. http://giewiki.appspot.com || http://code.google.com/p/giewiki Bear with me if you don't (care) - we all have our ways; giewiki is just my 'cloudy' way of tiddling. /Poul -- 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: Proposal: Move http://tiddlywiki.org to TiddlySpace
On 29 Jan., 01:36, Poul wrote: > All in all, I think the best route would be to leave the choice of > future platform to someone with an unbiased point of view. Let me qualify that last remark, at the risk of offending someone by unintentional (really) implication: I'll be perfectly happy to accept the decision of the community, if I feel that it has been made through an open, transparent process. -- 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: Proposal: Move http://tiddlywiki.org to TiddlySpace
On Jan 27, 6:24 pm, chris.d...@gmail.com wrote: > On Tue, 25 Jan 2011, Poul wrote: > > I - of course - must recommend giewiki as an alternative to > > tiddlyspace. > > I think it is great that there are plenty of options, but this > message seems like an invitation to respond with some compare and > contrast, perhaps so all systems can improve, so here goes: > > > The pros and cons executive summary goes something like: > > + Better revision control, including diff and revert > > This is a "simple matter of programming" at this point. Perhaps there > is code in giewiki that can be borrowed? TiddlyWeb (the guts > underneath TiddlySpace) stores revisions but does not provide in > itself tools for diff and doing revert. That's taken as the > obligation of the client side: TiddlyWeb provides the storage api. Of course, you are free to borrow my solution from giewiki. It's done server-side though. I probably don't understand TiddlyWeb well enough to say for sure, but my immediate reaction would be to observe that a web arcitecture that leaves all kinds of application-level duties to the client is going to be a very insecure one - just as you wouldn't expose SQL directly to the client. I'm not saying that giewiki scores high on security, but I am taking a more pragmatic approach when it comes to placing the detailed responsibilities. The main reason I did giewiki is that I felt that so much could be achieved by combining TiddlyWiki with a server-side, which wouldn't be appropriate to client-side. > > > + Recent changes, recent comments, tree structure, SiteMap, page > > templates, etc. > > Ditto on the above. TiddlyWeb lets you use whatever tools you want > for doing those kinds of things. If you have tiddlywiki plugins > which do those things, magic. > These are examples of features that are implemented server-side in giewiki, for reasons of security and performance. > > - It's currently a fork of TW 2.4.1 > > tiddlywebwiki, the package the includes the empty.html used with the > wiki serialization tracks the latest stable release. TiddlySpace > itself has functionality that allows a request to optionally use > whatever the latest beta TiddlyWiki is. > > > + It's only 320K before content, as compared to 770K for TiddlySpace > > Yeah, this is a big problem with TiddlySpace. On a plain > tiddlywebwiki it's 421K, which is still too much. > Which is one of the reasons that I chose to trim the TiddlyWiki code. The second was that my first attempt used unmodified TW 2.0.x code, only to find that later changes to TiddlyWiki broke my code. > > + It's cloud-based, which means Google will host it on redundant > > servers for little or nothing. > > TiddlyWeb can run on app engine[1] just fine, and it would be no big > deal to make TiddlySpace do the same. It's been useful thus far to > have it on its own server for the sake of tweakability. > > All that said I think the biggest win for TiddlyWeb (and excuse me > if giewiki has this stuff too, I had a look round the code but it > wasn't immediately obvious) is that it is explicitly designed to > make Tiddlers first class entities on the web. They have their own > URIs, can be represented in multiple (and extensible) content-types > (common ones are text, json, in-a-tiddlywiki, html and atom), can > contain any content (including images) not just wikitext, and > can be reused, by reference, across multiple wikis or other collections. Tiddlers in giewiki obviously also has their own (path#name) URI's (plus a GUID to allow stronger identification), although currently you cannot retrieve a single tiddler. I'm not saying that the currently available modes of retrieval are all that anyone could want, though. > > TiddlyWeb makes very few assumptions about how those tiddlers are > going to be used and who is going to use them. It's proven quite > remarkable, actually, taking the tiddler concept out of tiddlywiki > and thinking of them as free floating bits of content. This may be very powerful in theory, but if you want to to pull in twenty plugins from different servers, it's going to have an impact on performance. giewiki addresses this problem by caching copies of the content that you include, then builds a page template mechanism along the same lines. > > That makes it very flexible, but also means that it does not have > the level of focus that giewiki has: "giewiki tries to be a real > wiki". [3] > > In specific context of tiddlywiki.org, right now I think the winning > proposition for TiddlySpace is the inclusion functionality that allows > the content to be distributed across multiple spaces. I've already include > the tiddlywikidev space
[tw] Re: Proposal: Move http://tiddlywiki.org to TiddlySpace
On Jan 20, 2:18 pm, chris.d...@gmail.com wrote: > So I'd like to propose that we being a process of migrating the > content ofhttp://tiddlywiki.orgto a space or collection of spaces > onhttp://tiddlyspace.com/ > > If people have concerns, objections or encouragement, please post > here. This is not a done deal, just a proposal, but the benefits seem > a win: > I - of course - must recommend giewiki as an alternative to tiddlyspace. The pros and cons executive summary goes something like: + Better revision control, including diff and revert + Recent changes, recent comments, tree structure, SiteMap, page templates, etc. - It's currently a fork of TW 2.4.1 + It's only 320K before content, as compared to 770K for TiddlySpace + It's cloud-based, which means Google will host it on redundant servers for little or nothing. The one major piece still missing is server-side search (I have my eyes on Whoosh-AppEngine for that solution). I don't know what TiddlySpace has to offer in this department. -- 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: YouTubePlugin gains some support for iOS
Jeg er ikke nogen TW evangelist i "meatspace", men jeg har da brugt det lidt i mit arbejde og anbefalet det til kolleger. Men basalt set er jeg ikke specielt vild med TW's no-server-needed budskab. Min ide har været at lave en god general purpose wiki- platform til Google App Engine. Server platformen gør det muligt at tilføje en masse features. mvh Poul On 23 Jan., 20:05, Måns wrote: > Mojn Poul > > > Nice to see that I'm not the only dane who is into TW and willing to > > leave fingermarks on the net... > > Ye :-) > > > PS: Jeg er fra Aabenraa. Og jeg har rigeligt 'sjove' oplevelser med > > amerikansk software's mangler i forhold til ÆØ & Å. > > Lige præcis... Mit daglige styresystem er en variant af Puppy Linux > (PuppyStudio). Det egner sig IKKE til æ,ø og å. > Hvilke er dine erfaringer med TiddlyWiki og danske brugere? > Jeg har endnu ikke mødt nogen der er "bidt på" ... selvom jeg nok > synes jeg har gjort > mit:http://www.linux-abc.dk/phpBB3/viewforum.php?f=20&sid=dc18835b4f2c979...http://www.linux-abc.dk/phpBB3/viewforum.php?f=24&sid=dc18835b4f2c979...http://tw-abc.tiddlyspot.com/http://hootcourse.com/course/312/mhjfmj5vdsr/?type=minihttp://www.facebook.com/group.php?gid=121537204533733&v=wallhttp://tiddlywiki-da.posterous.com/lidt-om-hvad-tiddlywiki-er > Mvh Måns Mårtensson -- 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: YouTubePlugin gains some support for iOS
Mojn Måns, I've been thinking along the same lines, that is to enhance the options for rendering the subtitles and for user interaction with the player via the subtitles. But I must admit it wasn't Karaoke I was thinking of, but rather to make youtube a better tool for communication in general. However, as you can see from my site's front page, this plugin is just a minor part of my TiddlyWiki effords. Funny, I just noticed your name here this morning and went to check out måns.dk Nice to see that I'm not the only dane who is into TW and willing to leave fingermarks on the net... PS: Jeg er fra Aabenraa. Og jeg har rigeligt 'sjove' oplevelser med amerikansk software's mangler i forhold til ÆØ & Å. On Jan 23, 3:31 pm, Måns wrote: > Hi Poul > > > ..my YouTubePlugin (http://giewiki.appspot.com/lib/plugins/YouTubePlugin) > > ..the distinguishing feature of the plugin: support for adding subtitles. > > I just realized that this YouTubePlugin of yours actually turns a > TiddlyWiki into a veritable Karaoke machine :-) > I was wondering if you could work on that feature - like adding > templates for showing the text in a BIG container, maybe even in > lightbox kind of fashion, where the background gets darkened and the > text stands out? > Do you know Eric's > AnimationEffectsPlugin?http://www.tiddlytools.com/#AnimationEffectsPlugin > - It might add that last touch that you've come to expect from karaoke > subtitles.. > > Great work! Thanks for sharing it! > > Cheers Måns Mårtensson -- 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] YouTubePlugin gains some support for iOS
It has been bothering me that my YouTubePlugin (http:// giewiki.appspot.com/lib/plugins/YouTubePlugin) did not support iOS devices, when a simple link to youtube would get a long way. Well, problem solved, sort of. While you still can't embed youtube directly on web pages on iOS, at least now it does the best thing: insert a link to youtube if Flash isn't supported; this will launch the YouTube app on iPads, iPods and iPhones. They will not however benefit from the distinguishing feature of the plugin: support for adding subtitles. Android owners, please let me know if the page works at all on those devices. I suspect not, but hopefully the problem is solved by using this alternative rendering mode: http://giewiki.appspot.com/lib/plugins/YouTubePlugin?twd=twcomp.html If this helps I will make it the default mode. -- 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: Saving Tiddlers via http
I, of course, would recommend http://giewiki.appspot.com (see my recent post). On Jan 4, 8:30 pm, Måns wrote: > Hi again > If you have setup a TiddlyWiki at tiddlyspot.com, the welcomepage > tells you how to save back to the net:http://example.tiddlyspot.com/ > TiddlySpot:http://faq.tiddlyspot.com/http://tiddlyspot.blogspot.com/ > > Saving back from a standard space at TiddlySpace is automatic: > TiddlySpace:http://community.tiddlyspace.com/http://blog.tiddlyspace.com/ > > Cheers Måns Mårtensson > > On 4 Jan., 20:15, Måns wrote: > > > Hi Bill > > > > As I reread this, I thought maybe my question wasn't clear. I simply > > > want to have remote users be able to log and save information into the > > > wiki. Is there way to make tw do this? > > > Which hosted service are you using: > > TiddlySpot, ccTiddly, TiddlySpace or another? (there are several > > options you know)... > > > TiddlySpot is designed for single users, ccTiddly for several users > > and TiddlySpace is especially aimed at collaboration. > > > Cheers Måns Mårtensson -- 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: giewiki unplugged: Now supports offline editing and two-way sync TiddlyWiki style
Install Python 2.5 (2.6 or 2.7 will do), if you havent got it. Install the Google App Engine SDK. Fire up the Google App Engine SDK Launcher and choose to add an existing application. Point it to where you have giewiki unpacked. Start the app Hit the browser button. When you are ready do deploy in the Google cloud, consult http://code.google.com/p/giewiki/wiki/DeploymentGuide Or you can try out giewiki by logging in at giewiki.appspot.com with your google ID, clicking your login name and open My Profile. >From there, the My Projects part lets you create your own subdomain of giewiki.appspot.com. On 4 Jan., 12:13, Cyrill <2rig...@googlemail.com> wrote: > Hello Poul, > > can I find anywhere a step by step installguide of giewiki ?? > > Regards > > On 4 Jan., 11:36, Poul wrote: > > > > > Hi Chris, > > > giewiki saves content in tiddlers (app-engine 'expando' objects, > > keeping attributes & custom fields as separate fields), with the > > exception of SiteTitle & SiteSubtitle (that are saved as part of the > > page attributes for performance). > > > Logically, pages are stored hierachically as defined by the URL. Pages > > can be either leaf or folder, both can have tiddlers. > > Tiddlers, while belonging on a specific page, can be included in other > > pages using either of the following methods: > > > Adding the tag shadowTiddler to a tiddler on a folder page will copy > > it to all pages below it in the hierachy. > > The page object has a list of tiddlers included from other pages > > (defined via page properties). > > Pages can be defined as templates, giving a set of tiddlers to any > > page deriving from it. > > > I believe this set of mechanisms is easier to use/understand than the > > tiddlyweb model. > > > On 3 Jan., 11:47, "cd...@peermore.com" wrote: > > > > On Jan 2, 10:45 am, Poul wrote: > > > > > Tiddlyspot offers you - as far as I can tell - just one page, hosted > > > > at tiddlyspot. Giewiki lets you create any number of pages (using page > > > > templates), giving you an auto-generated sitemap, tiddler versioning, > > > > and much more. > > > > It sounds like giewiki has many of the same goals as tiddlyweb[1] and > > > tiddlyspace[2], but with a somewhat different approach to grouping > > > content. giewiki has "pages" whereas tiddlyweb has "bags" and > > > "recipes" and tiddlyspace has "spaces" (which are made from two > > > tiddlyweb recipes). > > > > In giewiki what is the fundamental element of content that gets saved? > > > Is it a tiddler or the tiddlywiki containing the tiddlers? If a > > > tiddler shows up in one page can the same one show up in another?- Skjul > > > tekst i anførselstegn - > > - Vis tekst i anførselstegn - -- 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: giewiki unplugged: Now supports offline editing and two-way sync TiddlyWiki style
Hi Chris, giewiki saves content in tiddlers (app-engine 'expando' objects, keeping attributes & custom fields as separate fields), with the exception of SiteTitle & SiteSubtitle (that are saved as part of the page attributes for performance). Logically, pages are stored hierachically as defined by the URL. Pages can be either leaf or folder, both can have tiddlers. Tiddlers, while belonging on a specific page, can be included in other pages using either of the following methods: Adding the tag shadowTiddler to a tiddler on a folder page will copy it to all pages below it in the hierachy. The page object has a list of tiddlers included from other pages (defined via page properties). Pages can be defined as templates, giving a set of tiddlers to any page deriving from it. I believe this set of mechanisms is easier to use/understand than the tiddlyweb model. On 3 Jan., 11:47, "cd...@peermore.com" wrote: > On Jan 2, 10:45 am, Poul wrote: > > > Tiddlyspot offers you - as far as I can tell - just one page, hosted > > at tiddlyspot. Giewiki lets you create any number of pages (using page > > templates), giving you an auto-generated sitemap, tiddler versioning, > > and much more. > > It sounds like giewiki has many of the same goals as tiddlyweb[1] and > tiddlyspace[2], but with a somewhat different approach to grouping > content. giewiki has "pages" whereas tiddlyweb has "bags" and > "recipes" and tiddlyspace has "spaces" (which are made from two > tiddlyweb recipes). > > In giewiki what is the fundamental element of content that gets saved? > Is it a tiddler or the tiddlywiki containing the tiddlers? If a > tiddler shows up in one page can the same one show up in another? -- 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: giewiki unplugged: Now supports offline editing and two-way sync TiddlyWiki style
I'm glad you asked. Tiddlyspot offers you - as far as I can tell - just one page, hosted at tiddlyspot. Giewiki lets you create any number of pages (using page templates), giving you an auto-generated sitemap, tiddler versioning, and much more. And you can try it out by creating your own subdomain site at giewiki.appspot.com, or host it for free in your own Google App Engine account, or run it locally on all OS's with the App Engine SDK. In short, the concept is the same as TiddlySpot and TiddlyWiki, except without the limitations. The next limitation that I hope to remove is offline editing on iOS Safari. Another ambition is to lower the barrier when it comes to finding and installing plugins, as many plugins need to be adapted for giewiki. The idea is to build a shared catalog at http://giewiki.appspot.com/lib/plugins/ - although there currently is nothing there except what is also in the standard distribution, namely the YouTubePlugin. On 2 Jan., 05:46, passingby wrote: > Hi Poul, > I did not understand the concept of geiwiki. As far I could tell the > features are same as Tiddlywiki. Does the difference lie in hosting? > If so, how is it different than lets say tiddlyspot? > > On Jan 1, 5:50 am, Poul wrote: > > > > > I am not aware of any other freely hosted solutions that offer this > > feature, but anyway, read the details and find the software > > athttp://giewiki.appspot.com > > > And a Happy New Year to everyone. Should I manage to put in the first > > post of 2011..? > > > /Poul- Skjul tekst i anførselstegn - > > - Vis tekst i anførselstegn - -- 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] giewiki unplugged: Now supports offline editing and two-way sync TiddlyWiki style
I am not aware of any other freely hosted solutions that offer this feature, but anyway, read the details and find the software at http://giewiki.appspot.com And a Happy New Year to everyone. Should I manage to put in the first post of 2011..? /Poul -- 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: Giewiki 1.1.0 announcement
Hi Tobias, Access rights to a page is controlled by the owner of the page, that is, by default, the user who created the page. This is done through the page properties dialog which is part of the edit menu. Pages are defined by their URL, you can create a page with any valid URL you might choose. The relationships between pages are loose, Wiki style: WikiWiki can refer to either a tiddler on the same page named WikiWiki, or to another pages named WikiWiki located in the same logical folder. Feedback is always welcome, particularly the feedback from potential users. /Poul On 2 Mar., 13:27, Tobias Beer wrote: > How is the process/workflow to set up rights&roles, e.g. "editors" for > tiddlers? > > Does giewiki allow for a kind of folder system (like "bags" in > tiddlyweb lingo) ...to arrange collections of different tiddler types > with which user rights can be associated? > > What do you mean by... > > "Unlike TW, it supports creating many different pages, and the > relationships between them." > > ? What kind of relationships are these? > > "In addition to having your own (free) App Engine account, you will > need Python 2.5 (or 2.6) and the App Engine SDK." > > As time allows, I should try that to give you better feedback. I hope > I didn't come off having too many rough edges on my first post. I just > often seem to turn out being the guy with the nagging questions ;o) > > 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] Re: Giewiki 1.1.0 announcement
Hi F, I'm certainly open to sharing, but I suppose it has to start with documenting the patterns and solutions that we develop to degree where it is possible to judge from documentation whether it is worthwhile to adapt existing code for your own use. I suppose the place to start is documenting the client/server interaction and the patterns used to implement it. Another issue is how this interacts with the user interface. /Poul On 2 Mar., 09:52, FND wrote: > This is good stuff, Poul - always great to see another addition to the > TiddlyWiki ecosystem! > > I've noticed you're using a customized version of the TiddlyWiki core. > That made me think we might share and evolve some common practices > regarding TiddlyWiki server-sides to promote interoperability and > general cross-pollination. For example, ccTiddly and TiddlyWeb* now > share a fair amount of code on the client-side. What do you think? > > -- F. > > * which happens to also work on > GAE:http://cdent.tumblr.com/post/278948050/smooth-tiddlyweb-on-app-enginehttp://cdent.tumblr.com/post/283065885/tiddlywebweb-to-app-engine -- 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: Giewiki 1.1.0 announcement
First of all, I agree that the sample site needs a lot more work. I find a server-based TW to be preferable to a stand-alone TW whenever you need to share the information with others, obviously. As for use-cases, my philosophy is to make it kind of a swizz army knife: It may not be the perfect tool for any particular application, but it should be able to solve many different needs, and knowing one powerful tool well is better than having ten diferent tools that you don't master. To some, it could be a classic wiki alternative, a message board, a tool for collecting information, etc. It is definitely more of a muli-user TW than a document management solution in that the versioning is only at the tiddler level: If you edit an existing tiddler, you get an (n prior versions) message next to the author+date; clicking on it brings in the revision history, where you can click on each version to see it. Editing tiddlers works just like in a classic TW, except that changes are saved immediately, and you have a preview button. Access to editing is controlled on a page by page basis, by the owner of the page. Users must authenticate with their Google account, of course. There is no user table. Unlike TW, it supports creating many different pages, and the relationships between them. The Feedback page is separate from the root/start page, but the sitemap makes it easy to navigate. I have not done a lot of work specifially to support customisation, except that if you make a tiddler with links (one per line) to other tiddlers anywhere on the site, and label it includes, the server will include those tiddlers the next time the page is requested. But again, I agree that the start page needs a lot more work. On Mar 1, 12:47 pm, Tobias Beer wrote: > Hello Poul, > > TW adaptations running on GAE invoke a certain interest in me, so I > have a few questions. > > In what situation would you find this kind of "specifically hosted > solution" to be beneficial over a "genuine" tiddlywiki? > > Running on GAE what would you think are workable use-cases of such a > system? > > Is this some kind of online-editable multiuser-tw-environment (with > admins,editors, users,guests) or is it's main addition some kind of > versioning? On the other hand, the version control features do not > seem to be accessible merely by looking at your demo ...or would that > be the "recent changes" list? > > In general, I guess you managed to > - store tiddlers in googles kind of "loose", object oriented database > format > - create a kind of interface to CRUD tiddlers within the GAE system > - while GAE provides some kind of automated versioning and possibly > commenting capabilities, too > > ? > > How do you go about editing tiddlers? ...and, related to that, how > does user management work? > > Well, I just found the login which unveils some commenting features. > Is all built around google accounts which provide any google user with > capabilities to write comments, personal notes on tiddlers and > messages to a tiddlers author (related to that tiddler?). > > When I click on "feedback", am I actually being forwarded to a kind of > "differently flavoured" sub-wiki? Or have you implemented a kind of > "context-sensitive" MainMenu? ...since that changes when openeing the > feedback system. The "feedback-wiki" also seems to provide different > user rights when it comes to commenting. > > Would that same differentiation allow for a kind of dynamic theming > capabilities? > > Would one load plugins on a "developers machine" and then deploy them > or would that simply be a 1) create a new tiddler, 2) post plugin code > and 3) hit refresh ...kind of process? > > All in all, I think it would facilitate getting started with giewiki > if you could provide some diagrams that show the workings / workflow / > abilities / relations within this GAE-serverside-TiddlyWiki flavour, > so that it were less of a trial and error process of getting to know > it. > > I also think that a sample "realworld-application" with "actual > content" might be far more useful and intuitive than a "demo" site > with some "lorem ipsum" and the standard "GettingStarted". > > Don't get me wrong, I think these are indeed interesting features: > - user management > - commenting > - personal notes > - "private messages" > - version control > > ...and they should jump right at you when you open that "sample site". > So, try to remove the noise from the demo and put either some "hard-" > or some "see-how-easy-this-works" kind of information in it. > > 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] Giewiki 1.1.0 announcement
Allow me to announce that giewiki 1.1.0, a hosted TW platform, now supports RSS and automatic links between pages. Try it out at http://giewiki.appspot.com, get it from http://code.google.com/p/giewiki/ -- 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: What's the best server-side implementation
On 27 Dec., 09:55, FND wrote: > > I've been working on an AppEngine-based server [...] > >http://iewikiwiki.appspot.com/SandBox/ > > Nice! > > Could the functionality to sync to your server be added to any > TiddlyWiki by way of plugins, or are you using a modified version of the > TiddlyWiki core? > > -- F. My first attempt used the standard TW 2.0.9 script, but I found that my extensions would't work with the newer TW. Also, I found that the that the newer TW had lots of code that I didn't need. Therefore, for this version, I've trimmed away everything that I didn't need, and I split the CSS and script from the content so that, in theory, a custom fronted could be written. So, while I suppose it wound be fairly easy to build an upload script, that has not been a priority. Basically, I'm not a fan of the self- contained TW concept, for the folowing reasons: a) It's fragile. b) It's vunerable to script viruses. c) It mixes code and data. d) There's just so much more you can do in a custom application. . For offline use, I would recommend the appengine SDK for now, but my master plan is to make a custom frontend that would sync with your appspot host transparently. -- 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: What's the best server-side implementation
On 26 Dec., 10:08, "cd...@peermore.com" wrote: > This is cool. I like the way you are handling logins from within the > TiddlyWiki document. I assume that's an iframe that's being managed? Yes, that happens in an Iframe. > Is the access control per tiddlywiki document, per tiddler, or per > some other mechanism? Access control is per page (document, if you will) or folder. > When a tiddler changes do you save just that tiddler, or the entire > document? I only save changes to the tiddler. The document text only exists as a set of tiddlers sharing a URL. > And what's the mechanism by which there are relationships between the > different wikis? The only relationships are the the shared tables of the site. I haven't made any automatic linking between pages, if that's what you mean. Site search is one of the major TODO's. As fa as I can tell, appEngine doesn't offer full text indexes, so I guess that I have to do that in code. -- 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: What's the best server-side implementation
I don't know which is the best, but I've been working on an AppEngine- based server which is fairly complete as far as access control is concerned. Multi-user support is provided by full access to all revisions of a tiddler; although there is not currently any edit locking mechanism. I can post the source code once I get home after new year. Try it out at http://iewikiwiki.appspot.com/SandBox/ On 23 Dec., 21:02, jrbast wrote: > I have a group of 12 sysadmin's that need to share commno documents, > most of them very small proceedures less that a page long. But nee > multi-user editing. I heard about a way to each have a master copy > of the wiki data dowloaded and when changes are made they get updated > to the master? Are there plug-ins to facilitate this? > > I have been looking for another wiki implementation that has server > side and login security, but none of them match what I see in > tiddlywiki > > Thanks, -- 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.
