My progress was recently stymied for a while by a server related
issue, but I've got that sorted now.
Minor hiccup with the addition of the validation code. After its
introduction, the policies table (assuming sqlstore) is expected to
have the new 'accept' column. But when using an older sqlstore
I didn't know about S5, but this is awesome.
On Jun 17, 8:48 pm, Scott Elcomb wrote:
> On Tue, Jun 16, 2009 at 7:00 PM, cd...@peermore.com
> wrote:
> > This evening FND encouraged me to make an S5 serializer for TiddlyWeb.
> > This makes it possible to use a set of tiddlers hosted by TiddlyWeb
On Jun 15, 5:19 pm, Oveek wrote:
> When you open it in your browser you may want to check
> these plugins are listed under the systemConfig tag :
Just to be clear, when I said "open it in your web browser" I meant
open the imported tiddlywiki and make sure you can see thos
On Jun 15, 2:25 pm, tony wrote:
> Unfortunately I could not save to an imported tiddlywiki both from
> plain text and sqlite store.
>
> Also when I open a recipe from an imported tw, the
> chkHttpReadOnly=True and I have to go into Advanced Options to reset,
> reload and retest if I could save.
On Jun 14, 8:23 pm, "cd...@peermore.com" wrote:
> Unfortunately the stuff that is working just fine for mysql and
> postgres is not working just fine for sqlite. sqlite has its own
> special connection pooling class because it get confused in multi-
> threaded environments. After a few request
On Jun 13, 12:18 am, "cd...@peermore.com"
wrote:
> Oveek, have a look at this commit:
>
> http://github.com/tiddlyweb/tiddlyweb/commit/8c3c8371718df8275350b3c3...
>
> and install Tiddlyweb 0.9.39 (just released) and see if that changes
> the behavior at all.
Dis
Okay I've been doing some testing. I think your latest commit in the
StoreSet has hit the problem at its source, but I'm seeing some things
that still aren't making sense.
Going back to the earlier posts first...
On Jun 11, 8:38 pm, "cd...@peermore.com" wrote:
> One option would be for the wsg
he connection
closing code.
Doing it in the store (the way I did for testing purposes) has some
problems...
but I don't have time to finish this right now, I'll come back later
on and pick up where I left off.
On Jun 11, 12:41 am, Oveek wrote:
> On Jun 10, 1:58 am, tony wrote
connections differently so that might account
for it. Either that or your server has a lot of memory and the
incremental increase in memory usage hasn't had an effect yet. If you
are getting new connections on each request you may be in for an
unpleasant surprise somewhere down the line.
I hit another Postgre foreign key related store problem.
It happens when twanager is used to add an user with a role. The
problem is with the order stuff is committed to the database.
Currently an user's role is committed to the database before the
actual user is.
The roles table has a foreign k
Internet Explorer strikes again...
Ticket 825 (http://trac.tiddlywiki.org/ticket/825) is about IE
reporting HTTP response code 1223 when it receives a 204.
The patch in the ticket solves the problem in TiddlyWiki core, but it
needs to be handled in the TiddlyWebAdaptor as well. Under IE 7 saving
On Jun 8, 9:00 pm, "cd...@peermore.com" wrote:
> Just out of curiosity, why does the sqlstore change the work
> situation?
That's really due to one of my assumptions about performance. If the
text store gets very large with many tiddlers and revisions, I guess
its performance becomes tied to how
ould be added to users in practice,
but I think having the user's password reset each time is going to be
troublesome.
I ought to warn you what I wrote is not (yet) based on real world
experience, just speculation :)
On Jun 8, 2:24 pm, tony wrote:
> On Jun 7, 9:22 pm, Oveek wrote:
>
Knocking things down one by one. With the sqlstore available I feel
like I can create a test instance of TiddlyWeb at work. I think it's
going to be pretty awesome once all the pieces come together.
By the way I tried posting this as a comment on TiddlyWeb at peermore,
but the comment didn't get
I'm glad you started working on this when you did, because I was
thinking about it as well. To use TiddlyWeb seriously--my intended use
case is as a collaboration tool in a corporate environment--I think a
database backend becomes necessary.
Before I plunge in I just wanted to find out what the s
Been trying to get around to replying...
On May 23, 10:52 pm, "cd...@peermore.com"
wrote:
>By the way, if you haven't already done it, it's probably best to make
>your fork for tiddlyweb-plugins have tiddlyweb/tiddlyweb-plugins as
>its upstream, not cdent/tididlyweb-plugins.
Yea I later realize
Late reply here...
On May 23, 10:52 pm, "cd...@peermore.com"
wrote:
>By the way, if you haven't already done it, it's probably best to make
>your fork for tiddlyweb-plugins have tiddlyweb/tiddlyweb-plugins as
>its upstream, not cdent/tididlyweb-plugins.
Yea I later realized most of the commit a
By the way, I think dynamic loading is a good umbrella term for lazy
loading, on demand loading, and any other variation that may come up.
On May 18, 12:21 am, FND wrote:
> So, now that we've outlined the issues, where does this leave us - what
> could/should we start with to create a simple pro
On May 18, 12:01 am, FND wrote:
> As discussed, I think that distinction is correct and important.
> Even though one might argue about the semantics of "lazy" vs.
> "on-demand" loading, let's just stick to those labels for now and use
> "dynamic" loading for the more general concept.
>
> I've tri
This post became pretty big, hope you guys can stay awake :)
> In this use case do you assume that the server is always going to be
> available; available for at least the initial load time, but maybe not
> later; or server availability is an unknown. The first option is
> clearly the easiest.
T
I'm following up a quick chat with Chris, and FND, on #tiddlyweb,
about delayed loading of tiddlers. The aim is to discuss possible
implementations in TiddlyWeb and get started working on one or more of
them.
This is by no means a new topic and FND pointed me at a thread
summarizing an experiment
I started playing with filters a bit, testing on URLs.
Does searching the entire datastore with /search work using the new
filter syntax?
On May 10, 6:30 am, "cd...@peermore.com" wrote:
> On May 8, 10:40 pm, "cd...@peermore.com" wrote:
>
> > Sometime over the weekend I will push out the new c
I started playing with filters a bit, testing on URLs.
Does searching the entire datastore with /search work using the new
filter syntax?
On May 10, 6:30 am, "cd...@peermore.com" wrote:
> On May 8, 10:40 pm, "cd...@peermore.com" wrote:
>
> > Sometime over the weekend I will push out the new c
Okay, committed the plugin.
> On May 9, 1:27 am, "cd...@peermore.com" wrote:
>
> > On May 8, 5:20 pm, Oveek wrote:
>
> > > Nice timing. I copied the methodhack plugin, renamed it to
> > > pathinfohack, and substituted in a method that copies
Cool! Glad it's working.
Sure I'll go ahead and fork it, add the try, and check it in. This
will give me a chance to jump in and try using github.
On May 9, 1:27 am, "cd...@peermore.com" wrote:
> On May 8, 5:20 pm, Oveek wrote:
>
> > Nice timing. I copied the
On May 9, 1:27 am, "cd...@peermore.com" wrote:
> Awesome! I've taken a slightly modified version of it and installed it
> on tiddlyweb.peermore.com and it seems to do the trick:
>
> http://tiddlyweb.peermore.com/wiki/recipes/editor/tiddlers/I'am%20a%2...
>
>My change was simply to wrap a try aro
On May 9, 1:27 am, "cd...@peermore.com" wrote:
> Awesome! I've taken a slightly modified version of it and installed it
> on tiddlyweb.peermore.com and it seems to do the trick:
>
> http://tiddlyweb.peermore.com/wiki/recipes/editor/tiddlers/I'am%20a%2...
>
>My change was simply to wrap a try aro
> If you have a look at the methodhack code plugin I check in yesterday
> I think you'll see a good model for how to add your own request filter
> that does the right thing.
>
> That's at:
>
> http://github.com/tiddlyweb/tiddlyweb-plugins/blob/master/methodhack/...
Nice timing. I copied the metho
Oops that should be:
PATH_INFO = REQUEST_URI.replace(SCRIPT_NAME, "", 1)
On May 7, 11:45 pm, Oveek wrote:
> Hey all, fell off the map for quite a while; but I've been keeping
> tabs on TiddlyWeb, watching things progress nicely. I'm still using
> TiddlyWeb and
Hey all, fell off the map for quite a while; but I've been keeping
tabs on TiddlyWeb, watching things progress nicely. I'm still using
TiddlyWeb and MonkeyGTD regularly, and have been meaning to give
feedback for a long time.
Recently I undertook to switch from using TiddlyWeb via CherryPy to
usi
nding something though. Would be great
if there's an easy solution.
On Feb 11, 4:19 pm, Reenen Laurie wrote:
> Try setting the environment variable http_proxy to http_proxy
> =http://myusername:mypassw...@myproxyaddress
>
> On 2/11/09, Oveek wrote:
>
>
>
>
>
>
I think I'm right in saying that it's currently not possible to use
TiddlyWiki's import function (the one accessed through the backstage)
under TiddlyWeb.
Since TiddlyWikis accessed via TiddlyWeb are served by the CherryPy
server, and viewed over http, they are affected by the infamous cross
doma
I've been working on using these two excellent tools together. Out of
the box there are a few issues with running MonkeyGTD under TiddlyWeb.
I think the same issues apply to using MonkeyGTD under any TW
serverside that uses TiddlyWiki's adaptor mechanism.
First, sorry this post is so long, I actu
33 matches
Mail list logo
