> Perhaps with things like OwnCloud and personal NAS devices being widely
> available now, [WebDAV] might be more attractive today.
FWIW, a colleague pointed out to me that Subversion repositories (in the
usual Apache combo anyway) are often configured to include WebDAV
support - which means you g
> Hmmm would there be any way for a page served from it to know its own
> ETag?
I don't think so. However, a quick HEAD request on startup should
suffice - the risk of race conditions should be negligible in most
scenarios?
> Pretty cool if Apache could be configured to pass the ETag in a
> cooki
>> Have you tried it with any other WebDAV server implementations?
>
> Not that exact code, but it's based on my own tiny SPA. That sits on my
> Synology NAS, which uses Apache IIRC.
I just checked: My NAS does indeed use Apache. That implementation also
supports ETags, including checking the If-M
> Wow. So it really is pretty amazingly simple.
I know, right! After the aborted effort to implement a WebDAV store for
TiddlyWeb, I never expected the client side to be that easy.
> Have you tried it with any other WebDAV server implementations?
Not that exact code, but it's based on my own tin
> The one that is used for saving to TiddlySpot is pretty close already
I've hacked that UploadSaver to work for WebDAV:
https://gist.github.com/FND/b3e969f5ed471b55c831
(using jsDAV for easy testing: `npm install; ./server`)
It's very primitive because I have no idea what I'm
>> WebDAV allows regular GET, PUT and DELETE
>
> I hadn't realised that, very interesting.
Glad I'm not the only one who was surprised by that.
> BidiX created a WebDAV saving plugin for TWC quite some time ago
I'm aware, but looking at the code gave me mego... (Modern JavaScript
developers are
Hi all,
The other day I realized that WebDAV allows regular GET, PUT and DELETE
without worrying about the horrors of its protocol extensions. Thus it's
trivial to write a JavaScript application which is served via WebDAV and
stores its data (including itself) there.
This seems like such an obvio
> Note that `text/x-tiddler` on PUT would make sense if the HTTP
> Content-Type header didn't end up as the respective tiddler's `type`
> attribute - but that's a different, probably unhelpful discussion.
Correction (my tests last nights were misleading): The representation's
`type` actually takes
> So, it sounds like the only change on the TW5 side would be to change
> the content type for PUTs
Well, actually...
I've had some scenic train time to think about this today, or perhaps it
was the wind tunnel clearing my pathways - either way, I've come to the
conclusion that a tiddler's `type`
> FND, I don't understand the difference between the two things you
> mentioned
Basically, I was trying to say that creating a generic diagram editor
(like Visio, Gliffy etc.) is very challenging and time-consuming.
However, if you're content with a specific visualization - in
Hi Yakov,
Do you want to visualize arbitrary data (e.g. relationships between
tiddlers) or allow the user to craft diagrams (e.g. mind maps, flow charts
etc.)?
The latter is non-trivial to implement. For the former, it should be pretty
simple to adapt existing prototypes
like http://bl.ocks.o
Hi all,
While Eric's offer is admirable, I'm somewhat concerned about unintended
side-effects: Such direct communication channels leave casual observers
without easily accessible artifacts. Consider how many TiddlyWiki users
have learned a ton of stuff simply by reading people discussing their
iss
FWIW, this is a well-known issue:
While Markdown encourages[1] the use of line breaks to format (only) the
source, GFM[2] argues that line breaks in the source should translate to
line breaks in the output.
Personally, I *strongly* prefer the former. However, I understand that
in certain contexts
> By the way, you guys are amazing and I am really enjoying this thread,
> but should I start a new thread since I am no longer looking for a
> rewrite in C, or should the whole context of the discussion be preserved
> to enlighten anyone else who might consider this in the future?
Threads evolvin
> You might have a look at the following for a bit of existing python code
> that reads tiddlywiki files:
> https://github.com/tiddlyweb/tiddlywebplugins.twimport
FWIW, there's also this:
https://github.com/FND/tiddlywiki-svn-mirror/blob/master/tools/TiddlyPy/main.py
It'
For the sake of completeness, this might also be of interest:
https://github.com/rogerwang/node-webkit
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe f
>> So still suck.
>
> Freudian slide there. Meant "stuck".
I totally wuv u man.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to tiddlywikidev@googlegroups.com.
To unsubscribe from this group, send email to
> There is the luakit brwoser framework, which imo does all the stuff
> you want to create.
FWIW, this reminded me of another avenue worth exploring: uzbl
(http://uzbl.org)
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to thi
> there seems to be no interest in this
I don't think there isn't any interest, it just seems like a *very*
ambitious undertaking.
> I will (from scratch) build an [sandboxed] html parser in C [...]
> I will (from scratch) build a JS interpreter, again sandboxed [...]
Out of curiosity: Why rewri
Other than my previously expressed dislike for "vnd", I very much agree
with cdent that what you have here are two different content types.
The fact that there's common history and just because a client can
render both classic and new TiddlyWiki markup doesn't mean they should
be conflated - both
> One possibility might be to use text/x-tiddlywiki5 for the new format,
> and text/x-tiddlywiki for the old, but to deprecate the latter in
> favour of text/x-tiddlywiki2. Then we could declare that at some
> future coordinated release of TiddlyWiki and TiddlyWeb we'll switch
> the default interpr
>> the Dolphin creator had the same idea before you.
>> Menu, bookmark, history are accessible with a left slide, and tools
>> are accessible with a right slide.
>
> Ha! Does the right hand side of the screen have a similar function
> defined?
As I understood Phil, sliding on the right-hand side
> Is there a way to "overload" the built-in macros without "shadowing"
> them?
Yes:
http://oldwiki.tiddlywiki.org/wiki/Dev:Hijacking
Given your example:
(function() {
var onClick = config.macros.newTiddler.onClickNewTiddler;
config.macros.newTiddler.onClickNewTiddler = function() {
MyPreFun
> https://github.com/Hugheth/preso2
> [...]
> http://janne.aukia.com/zoomooz/
Thanks, this looks useful. I'll play with it over the next few weeks and
report back if(!) I come up with anything useful.
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWi
Is Cecily[1]'s functionality available as a stand-alone library? I seem
to recall Hugh worked on this, but can't find any evidence of it.
If done right, this would enable arbitrary SPAs to apply Cecily's ZUI to
any number of scenarios (TiddlyWeb/-Space revisions as well as front-
and backlinks is
> raise an issue in github
I've started to get the ball rolling:
https://github.com/TiddlyWiki/tiddlywiki/issues/55
https://github.com/TiddlyWiki/tiddlywiki/pull/56
(note the pull request's message though)
-- F.
--
You received this message because you are subscribed to the Google Groups
"Tid
A recent post[1] made me aware that TiddlyWiki's `saveTiddler` method
does not currently merge `config.defaultCustomFields`.
However, I seem to recall that we'd agreed it should do that a long time
ago (can't find the thread/ticket/conversation now, unfortunately).
Can anyone enlighten me what th
> So, is this correct that getTiddlerText method should be used every
> time _instead of_ direct changing of tiddler.text?
Generally speaking, TiddlyWiki (and/or its community) has never been
very clear about accessor methods; while they're often present, they're
frequently ignored.
Having said t
> Also, what does a construction in [1] means:
> (function ($) {
> ...
> }) (jQuery);
http://oldwiki.tiddlywiki.org/wiki/Dev:Best_Practices#Creating_Aliases
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send em
> I think it's worth picking out the enhancements and dangers to
> existing plugins that the new version of TiddlyWiki brings.
Thanks for providing that overview, Jon!
> * upgrade to jquery 1.6.1
I'd recommend to upgrade to jQuery 1.6.2 before the final release.
-- F.
--
You received this me
>> However the getMissingLinks function won't ever need to sort via a
>> field because it just returns an array of strings not a collection
>> of tiddler objects so there isn't anything to sort on.
>
> Not exactly true. [...] Thus, there is already work being done to
> retrieve tiddler data associ
> Maybe someone can help me. I am looking for a tool which reads in all
> the tiddlywiki javascript files and automatically creates a list of
> variables, functions etc. (preferably as browsable cross-linked
> html). I think javadoc does something similar for java.
This kinda thing is generally
> My plan is to write a simple website that syncs to dropbox, serves up
> my Tiddly.html file, and somehow saves back to the website, which
> would then write the changes back into Dropbox.
Why not submit the data to Dropbox directly? I guess authentication is
an issue with your proxy solution as
>> Aloha tiddlers would be tagged with a special tag, which would
>> trigger the editor when the tiddler is clicked. They would only
>> contain HTML, no wikimarkup.
>
> That sounds like a reasonable constraint.
FWIW, I always imagined a content-type field to trigger this sort of
thing (my origina
ain
(as much as the current framework allowed):
https://github.com/FND/tiddlywebwiki/blob/adaptor/src/TiddlyWebAdaptor.js
This work - along with the core's sync rewrite - is still very much
incomplete (and currently on hold, as I understand it), but it might
provide some insights, as I made a
> To get back to what I took as FND's original point, the issue here is
> not this one bug about jQuery, but rather how long it is taking it,
> as an example of many bugs, to get resolved. A healthy open source
> project "should move more rapidly and be more responsive".
That was indeed my main
As of today, the TiddlyWiki core (v2.6.2) is lagging two releases behind
jQuery (v1.4.3 vs. v1.5.0), with jQuery 1.5 being a major release.
Late last year, there seemed to be universal agreement that core
development should move more rapidly and be more responsive.
Unfortunately, I don't see any e
> One of the reasons I'm in favour of not importing the history into git
> is that a clean repository is in some ways attractive to new users.
> I'm in particular thinking of a friend of Paul's who was interested in
> doing some work on TiddlyWiki, but didn't bother in the end because
> the reposit
> To get things started I went ahead and today created a cooker repo
> and imported the existing cooker "stuff" into it.
Looks good - thanks Chris!
> Presumably a next step with cook and ginsu would be to package them
> in a proper Ruby way
+1
> I thought we'd decided *not* to import the histo
> I've seen this phrase "short-term priorities at Osmosoft" bounced
> around this thread a few times. The implication is that Osmosoft is
> making all the core decisions and core commits.
> Since that is considered a problem let me restate one of the reasons
> for a move to github:
> Make it p
> we'd like to move the management of the core TiddlyWiki code from
> http://svn.tiddlywiki.org/ to a to be determined location on GitHub
That'd be great. In fact, it almost seems like a necessary (if not
sufficient) step in order to bring about some reinvigoration.
FWIW, I registered https://gi
> I'm afraid that this was a change that accidentally went through to
> production without adequate discussion and notice.
While a bit unfortunate in this case, I understand the motivation to
keep up the momentum with rapid development (permission vs. forgiveness
etc.). Either way, I reckon it's n
> A possible issue here.
> There are vast numbers of people who are forced to use older browsers
Sorry, I should have been more explicit; when I said "use LocalStorage
where available", I fully expected that cookies would continue to be
used as fallback for older browsers.
So we'd have a simple st
xtMainTab:"Recent" txtMoreTab:"moreTabAll"
txtMaxEditRows:"30" txtFileSystemCharSet:"UTF-8" txtTheme:""
txtUserName:"GUEST" chkPrivateMode:"false" chkBackstage:"true"
chkViewDiffText:"true" chkViewDi
> FND also worked on a parsing library at some point, but for some
> reason I can't find it.
That's probably because it's in SVN:
http://svn.tiddlywiki.org/Trunk/tools/TiddlyPy/
It hasn't been used/maintained in recent months though, so I'm not sure
how use
> FND also worked on a parsing library at some point, but for some
> reason I can't find it.
That's probably because it's in SVN:
http://svn.tiddlywiki.org/Trunk/tools/TiddlyPy/
It hasn't been used/maintained in recent months though, so I'm not sure
how usef
> I am trying to use http://chef.tiddlywiki.org/ , but I get errors
> [...]
> Is the online cook still supported?
I'm afraid Saq doesn't maintain this anymore.
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send
> So the question now is, does anyone know how to auto-detect the
> operating system and then set the fields accordingly?
if(navigator.appVersion.indexOf("Win") != -1) {
// Windows
} else {
// Unix OS (Linux, MacOS, etc.), or perhaps some mobile platform
}
-- F.
--
You received this me
>> I don't think the core should provide support for this seemingly
>> specific use case
>
> I don't think, that this is a specific usecase. Every, third party,
> existing and future inline formatters have these problems.
> [...]
> What I want is a nice vanilla tw fallback, if there is no formatter
It seems we're getting way off-topic here...
> [syntaxhighlighter] needs
>
> code goes here
> which is not rendered by a vanilla tw.
If you have some flexibility (which I suspect you don't, but some
monkey-patching might do it), you could use custom classes:
{{brushjs{
...
}}}
N
> 1) I love having images in a slider format, I've been manually putting
> links of images into a tiddler, then using sliders pointing to those
> tiddlers, but I'd love if that function would be in either the slider
> function or img function.
Sounds like perhaps you want Eric's NestedSlidersPlugi
> There was some descussion about the default private/public value for
> new tiddlers.
That story is still pending - details here:
http://tiddlyspace.tiddlyspace.com/#%5B%5BSave%20Tiddlers%20as%20Public%20by%20Default%5D%5D
-- F.
--
You received this message because you are subscribed to the G
> maybe the user object returned by getUserInfo would do good with an
> additional flag, e.g. a user.status[string] or a watered down
> user.member[boolean]
While I understand the impulse, I'm not keen on this - it seems to
conflate different concerns.
Your use case of distinguishing between visit
> where does this peculiar 'anon' have its origin? Never heard of this
> before. Does that simply stand for anonymous?
That's right.
> Would you think, too, that it made sense to turn this into a global
> utility function in the TiddlySpace core? ...returning the visitor
> status with respect to
> identify [...] the current visitor
var callback = function(user) {
// user's an object with members anon and name
// user.anon is true if the current user is not logged in
};
config.extensions.tiddlyweb.getUserInfo(callback);
Combined with the recent snippet about re
> To begin with, I would much prefer, if onTiddlerKeyPress would only
> act in EditMode! There are cases where CTRL+CLICK, for example, would
> be quite useful in viewmode, but since there's onTiddlerKeyPress it
> makes it quite hard to ensure that we're not going into edit mode.
Can you elaborate
> Are there some more links + timeline to early versions
http://tiddlywiki.com/archive/
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to tiddlywiki...@googlegroups.com.
To unsubscribe from this group
> Would there be a technical breakage if I were to add a few paragraph
> parsers for my plugin? Since I'm writing a new parser, I have little
> concern for backwards compatability.
If you're not concerned about compatibility with existing tiddler
contents (i.e. TiddlyWiki markup), you can pretty
> tiddlers output s where one would expect 's [...]
> Is there a reason for this implementation?
The reasons for this are historic - unfortunately, it doesn't seem like
we can change this now without breaking backwards compatibility:
http://trac.tiddlywiki.org/ticket/34
-- F.
--
You received t
> There'd be some trickiness with editing a tiddler to add a tag that is
> removed on the next edit - essentially the last change would have to add
> the appropriate tags and the person doing the boilerplate updates would
> have to keep chasing the tag.
True - perhaps you could use a paramifier*,
> temporarily hide a tiddler in the timeline
That's an interesting approach, thanks for sharing.
I assume you're familiar with excludeLists*, but did not want to require
user to manually remove this tag? One could imagine a saveTiddler hijack
that removes excludeLists if another tag (e.g. "boilerp
> Another approach that might suit some people is to use a browser
> extension that lets you edit a in an external editor.
Indeed, I frequently use Vimperator's built-in functionality for this to
shove tiddler contents into Vim and back - works quite well, and better
still if you have some simple
> * I want to edit and save my TiddlyWiki plugin in my preferred editor
> * then I go to my browser hit reload and - bang - my plugin is loaded
As you probably know, the standard method is to use Cook (which
basically just concatenates a bunch of files, both HTML and JavaScript,
to create a Tiddly
> In your or other's experience, do plugins/themes work as expected
> [with TinyTiddly]?
There should be no difference between regular TiddlyWiki and TinyTiddly;
it's essentially the same code.
> I'm working with a couple tiddly's at once [...] I am concerned
> about the waste of having the same
I've just simplified the ck wrapper for Cook:
http://trac.tiddlywiki.org/changeset/12410
I've always hated the process of creating a customized copy of ck and
messing with PATH - now I can just use a simple wrapper in ~/bin instead.
Let me know if this raises any unforseen issues.
-- F.
--
Yo
> do you have any suggestions for measuring performance?
Use Firebug (or WebKit's/Chrome's dev tools):
http://getfirebug.com/javascript
TiddlyWiki also has built-in instrumentation (see AdvancedOptions >
unknown options > chkDisplayInstrumentation):
http://trac.tiddlywiki.org/browser/Trunk/co
> I think it were beneficial if tag buttons would indicate whether a tag
> is being used or not...
> [...]
> function createTagButton(place,tag,excludeTiddler,title,tooltip)
> [...]
> addClass(btn,store.getTaggedTiddlers(tag).length>0?'hastags':'hasnotags');
Two concerns:
a) performance - we'd ne
le
They are indeed mutable - some samples can be found here:
http://svn.tiddlywiki.org/Trunk/contributors/MartinBudden/formatters/
http://svn.tiddlywiki.org/Trunk/contributors/FND/formatters/
A simple example might be this one:
http://svn.tiddlywiki.org/Trunk/contributors/FND/formatters/ParagraphForma
> I'm the project lead of UberStudent,http://uberstudent.org
Cool!
> As I have a very overfilled plate already, I'm wondering if someone
> might be interested in making a debian package for TiddlyWiki
Unfortunately, I have no experience creating Debian packages. I don't
suppose a Python package
Saq and I created an adaptor along with some views and lists to save
tiddlers in and generate TiddlyWiki documents from CouchDB:
http://github.com/saqimtiaz/TiddlyCouch#readme
http://saq.couchone.com/tiddlydb/_design/tiddlycouch/_list/tiddlywiki/tiddlers
It's the result of a quick hacking session,
> Can you explain the reason for the last line in Popup.show() ?
> else window.scrollTo(0,ensureVisible(curr.popup));
Popup.show ensures that the newly-created popup is actually visible in
the viewport - if animations are disabled by the user, the less smooth
method is used.
> This seems to make
http://github.com/TiddlyWiki/tiddlywiki
Since my local Git clone of the SVN repo only goes back to September
(due to The Incident), I was sometimes missing easy access to history
(Subversion's got nothing on Git's log, diff or blame commands).
So I finally got around to creating a new, full clone
jQuery's documentation is pretty good start for this:
http://api.jquery.com/submit/
> the browser wouldn't redirect to some php server response
So you want to suppress the standard browser handling of form
submissions and manually perform an XHR instead. Here's some sample code
that should he
> no problems
While I could reliably reproduce this issue on my other machine, I
cannot do so now after reinstalling Ubuntu (and Firefox).
Instead, I now get a "tiddler is undefined" exception in
config.macros.sync.doSync for _some_ tiddlers (updating MainMenu from
master worked fine, but updatin
te [draft] mechanism.
IMO, the draft mechanism is primarily for content - so developers should
either manually create a private tiddler of the same name or create a
separate space ("foo" and foo-dev" perhaps?).
Also, I tend not to use the install-only-once wrapper anymore:
http://trac.
It appears there's a pretty significant bug in the FileAdaptor: When
sync'ing to update local tiddlers from a master copy, the server.host
field is blanked and the tiddler body is not updated.
test case:
* create master document with a sample tiddler Foo (I used a fresh
TiddlyWiki 2.6.0)
* creat
I created a tiddlybutton, but I'd really like just a normal link to a
tiddler which behaves like a normal tiddlerlink
createTiddlyLink:
http://trac.tiddlywiki.org/browser/Trunk/core/js/Utilities.js?rev=11445#L63
Sounds like you want to Wikify the text?
Personally, I think invoking wikify sho
those WikiWords under 'options>>' are just dead and confusing links
You're right, we should fix that in 2.6.2:
http://trac.tiddlywiki.org/ticket/1240
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send emai
I was just wondering if it's possible to change the timestamps used
for "created" and "modified", which is now: MMDDHHMM to the more
accurate: MMDDHHMMSSMMM?
Based on your suggestion the other day, we added support for more
accurate timestamps to the core:
http://trac.tiddlywiki.org/ti
We are pleased to announce the first beta of TiddlyWiki 2.6.1:
http://www.tiddlywiki.com/beta/
This is a maintenance release, containing a variety of bugfixes and
enhancements:
http://trac.tiddlywiki.org/wiki/History
As usual, help testing this release would be greatly appreciated -
pleas
var t = store.createTiddler("foo");
t.text="bar";
I don't think you want to use that low-level method - saveTiddler is
probably more appropriate:
http://trac.tiddlywiki.org/browser/Trunk/core/js/TiddlyWiki.js?rev=12238#L309
anyone know how hard/easy it would be to make TW save more accurate
something which concerns me is including someone else's space and then
putting myself at risk of someone being able to override the shadow
tiddlers, plugins and icons so I've created a "system" space which you
may include after including a space to reapply the default tiddlers
I reckon that all
I'm interested in doing the ajax event when people mouseover a
tiddler. Should I then hijack the
"Story.prototype.onTiddlerMouseOver" function?
You might wanna take advantage of jQuery instead:
jQuery(".tiddler").live("hover", enterHandler, exitHandler);
I'm seeing that everytime I mouse
I don't know of any *actual* conflicts between the two plugins [...]
a 'flag' goes up in my mind to make sure that the compatibility
issues are being considered carefully.
I'm glad you're being vigilant!
When I'm not quite as busy (when is that? :-), I'll definitely take a
closer look at how
it's important to ensure that TiddlyWeb's BinaryTiddlersPlugin can properly
co-exist with my current plugin, by hijacking the formatters, rather
than overwriting them.
BinaryTiddlersPlugin does not override any formatters, but rather hooks
into config.macros.view.views.wikified - plus it is onl
The problem was in the twFileDemo.html file on line 397:
var textarea = $("").css({
Excellent work uncovering that! Should be fixed now.
-- F.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to tiddlywiki..
Actually, use of sections to deliver a 'payload' of CSS, HTML, etc.
that is then dynamically loaded as needed, was something that I
developed shortly after sections were first implemented in the core.
I had a feeling this was an Ericism - my apologies!
Also note that, in addition to directly s
Many plugin authors[1] these days use sections within their plugins'
documentation block[2] to embed CSS code:
/***
!StyleSheet
body {
color: #F00;
}
!Code
***/
//{{{
var name = "StyleSheetFoo";
config.shadowTiddlers[name] = store.getTiddlerText(tiddler.title +
"##StyleSheet");
store.add
For anyone interested I have built an Android app to allow local save
TiddlyWiki's.
First test version @ http://mgsimon.de/android/andtidwiki ... :-)
That sounds pretty neat (though I don't have an Android device to
actually give it a try).
You might wanna provide a short description in Engli
you can type a space separated list of tags. What function is used
to convert that list into an array of tags?
That's readBracketedList:
http://trac.tiddlywiki.org/browser/Trunk/core/js/Strings.js?rev=10112#L170
-- F.
--
You received this message because you are subscribed to the Google Grou
yes I'll get the source code out as soon as I can figure out how to
do that intelligently. I think I need to go and learn how to use
GitHub properly, finally!
That would be great. Should you run into any issues with Git, we're
happy to help.
-- F.
--
You received this message because you ar
In summary: I don't see *any* net advantage to hiding attachment data
in custom fields. It seems contrary to the 'open information' nature
of TiddlyWiki, and makes it harder to share that information across
the entire TiddlyVerse
I understand where you're coming from, and coming from a TiddlyWi
I plan to use your jquery.twFile.js for another project.
Excellent!
Out of curiosity, how did you learn about this plugin? Also, can you
elaborate on what kind of application you're working on?
What do I have to consider to use your code?
The jQuery plugins are triple-licensed under the BS
My apologies for the late response, Lyall - I'm still rather busy at the
moment, so I didn't get around to replying...
After a bit of looking, I am unsure as to what is fundamentally
different between your demo and my old plugin
I now realize this isn't obvious at all - mainly due to the fact
I've been thinking about using the Tiddlywiki as the basis for a
generic RPG character generator. The idea being that tiddlies are used
to fill in the blanks of an SVG character sheet "template"
Sounds interesting.
We're making use of SVG in TiddlySpace, using Jon's macro:
http://svn.tiddlywiki
Would you mind commenting up a version for me and making it available?
I'd be happy to do so - unfortunately, I'm currently swamped, so it
might have to wait a week or two.
By the way, I can get your demo to 'encrypt' a tiddler, on the net,
but I can't seem to convince it to pop up a passwor
I hope you don't mind, I will be using your example as a starting point
Quite the opposite - I was hoping it would be used that way!
I am playing around with your example, but I am using TiddlyWiki 2.6.0
and I have horrible flickering on the edit buttons
I can't recall having experienced thi
# Save changes doesn't seem to do what it's name suggests it ought to
do. That is, saving changes and opening up the same site (http://
markpea.tiddlyspace.com/) in another browser (Flock) reveals that
nothing actually got saved.
Changes should be saved automatically when you edit a tiddler. I e
I will have a look at what you have done.
Thanks Lyall - much appreciate it!
Any chance you could point me to some docs on coding for the new
TiddlyWiki way?
I'm not sure what you mean by "new way" here. TiddlyWiki's APIs haven't
changed much in a long time - except that you now have access
I GOT IT
** slice values are cached **
That's excellent, Eric - thanks a lot!
This makes perfect sense now, of course, and I'm a bit annoyed with
myself for not having thought of it. Luckily, the TiddlyWiki community
can always count on Eric to go the extra mile...
-- F.
--
You receive
1 - 100 of 418 matches
Mail list logo
