Re: Question | mGSD 3.1.8b -Exclude Sub-Projects from Active Projects
oh wow, that's awesome. Works like a charm! -- You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To view this discussion on the web visit https://groups.google.com/d/msg/gtd-tiddlywiki/-/HW2kDg7v5iQJ. To post to this group, send email to gtd-tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
Re: [tw] Re: TiddlyWiki Development News
I've been doing a lot of research and playing around in the tools that transform markup space recently, and would **implore** you to consider choosing one of the more mainstream cross-platform syntaxes rather than re-implementing a proprietary TWmarkup, even if it may be based on one of them. The primary constraint I am embracing is to retain compatibility as far as possible with existing TiddlyWIki markup. I think that that rules out the wholesale adoption of a standard format - for instance, TiddlyWiki gets [[pretty|links]] the wrong way round from most wikis. To get around the limitations imposed by that constraint, we have the idea of pluggable parsers and renderers, so that it is possible to adopt other formats, and intermingle them and so on. If you can find a JavaScript parser for it, then hopefully you'll be able to use it. Markdown is a popular choice, lots of active development in the Pandocs project - their extensions may be a bit proprietary, but since the focus of the whole project is interoperability, it's for a good cause. Adopting MarkDown in its entirety is a bit troublesome from my perspective; it's not very formally defined, and the only implementations that I've seen are even hairier balls of regexps than the old TiddlyWIki wikifier. It also lacks what I'd have thought of as basic features, like tables, arguing that users should write HTML tags for them. Other candidates are txt2tags and reST/Sphinx, with the former having the edge in a huge number of output formats currently supported. Both of these are implemented in Python, while Pandocs is Haskell, if that means anything. I need JavaScript code, obviously. There may be bits and pieces worth taking from those projects, but a brief glance shows that they take in concerns that don't entirely match TiddlyWiki, so I don't see a way to wholesale adopt those syntaxes. IMO the key is to **not** pick and choose bits and pieces, but to take on an entire **syntax spec as a whole**. I only see that as feasible if there was a spec out there that was (a) compatible with TiddlyWiki and (b) did everything that TiddlyWiki needs and (c) didn't include lots of features that aren't relevant for TiddlyWiki and (d) had usable JavaScript code. This would enable plugging TW into a standardized toolchain so that it can be either a publishing and distribution target, along with say EPUB, AsciiDoc and HTMLhelp, or perhaps even the location where the master source text is edited, to then be able to output and transform to such formats. NB I consider TW's forte to be the former rather than the latter, but something like Pandocs would give the flexibility to go in either direction. As I say, the ability to have pluggable parsers and renderers should give you the capabilities you want. For you, the native TiddlyWiki format might just be what gets used for the application plumbing, with all your content being in other formats. But please **please** don't just throw another proprietary wikiMarkup syntax set into the mix, this is an historic opportunity to contribute to the idea of open data in the larger ecosystem rather than continuing to view tiddlers as an isolated silo needing custom coding to extract inline markup semantics. I'm not planning to throw another proprietary wiki markup into the mix. I'm planning to improve TiddlyWiki's existing markup so that it isn't broken with respect to paragraphs, and to introduce some alternative syntaxes for some simple formatting. Thanks in advance for at least considering these ideas. . . As I say, I think the kinds of things you're interested in are enabled by the parsing/rendering architecture. I would very much appreciate feedback on the improvements to the wikitext. Best wishes Jeremy /rant -- 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.
Re: [tw] Re: TiddlyWiki Development News
I concur with HansBKK that you should adopt a standard wiki markup for TW 5. I differ from in that I think you should adopt WikiCreole see: http://www.wikicreole.org/wiki/Creole1.0 and http://www.wikicreole.org/wiki/CreoleAdditions The main reason for this recommendation is the WikiCreole markup is *very* similar to TW markup. The main differences being the handling of bold, headings and links. WikiCreole even recommends using double angle brackets for plugins. Since TW 5 is going to break compatibility, then I think it should also take the opportunity to move to a standard wiki format. I know text compatibility and code compatibility are different things, but nevertheless I believe this is the correct way forward. Note TW 5 could support standard TW wikiformat using a plugin, and also could provide a converter so that people can easily move their text from TW format to WikiCreole format. Since the formats are so similar, conversion would be fairly straightforward. Martin On 15 December 2011 09:22, Jeremy Ruston jeremy.rus...@gmail.com wrote: I've been doing a lot of research and playing around in the tools that transform markup space recently, and would **implore** you to consider choosing one of the more mainstream cross-platform syntaxes rather than re-implementing a proprietary TWmarkup, even if it may be based on one of them. The primary constraint I am embracing is to retain compatibility as far as possible with existing TiddlyWIki markup. I think that that rules out the wholesale adoption of a standard format - for instance, TiddlyWiki gets [[pretty|links]] the wrong way round from most wikis. To get around the limitations imposed by that constraint, we have the idea of pluggable parsers and renderers, so that it is possible to adopt other formats, and intermingle them and so on. If you can find a JavaScript parser for it, then hopefully you'll be able to use it. Markdown is a popular choice, lots of active development in the Pandocs project - their extensions may be a bit proprietary, but since the focus of the whole project is interoperability, it's for a good cause. Adopting MarkDown in its entirety is a bit troublesome from my perspective; it's not very formally defined, and the only implementations that I've seen are even hairier balls of regexps than the old TiddlyWIki wikifier. It also lacks what I'd have thought of as basic features, like tables, arguing that users should write HTML tags for them. Other candidates are txt2tags and reST/Sphinx, with the former having the edge in a huge number of output formats currently supported. Both of these are implemented in Python, while Pandocs is Haskell, if that means anything. I need JavaScript code, obviously. There may be bits and pieces worth taking from those projects, but a brief glance shows that they take in concerns that don't entirely match TiddlyWiki, so I don't see a way to wholesale adopt those syntaxes. IMO the key is to **not** pick and choose bits and pieces, but to take on an entire **syntax spec as a whole**. I only see that as feasible if there was a spec out there that was (a) compatible with TiddlyWiki and (b) did everything that TiddlyWiki needs and (c) didn't include lots of features that aren't relevant for TiddlyWiki and (d) had usable JavaScript code. This would enable plugging TW into a standardized toolchain so that it can be either a publishing and distribution target, along with say EPUB, AsciiDoc and HTMLhelp, or perhaps even the location where the master source text is edited, to then be able to output and transform to such formats. NB I consider TW's forte to be the former rather than the latter, but something like Pandocs would give the flexibility to go in either direction. As I say, the ability to have pluggable parsers and renderers should give you the capabilities you want. For you, the native TiddlyWiki format might just be what gets used for the application plumbing, with all your content being in other formats. But please **please** don't just throw another proprietary wikiMarkup syntax set into the mix, this is an historic opportunity to contribute to the idea of open data in the larger ecosystem rather than continuing to view tiddlers as an isolated silo needing custom coding to extract inline markup semantics. I'm not planning to throw another proprietary wiki markup into the mix. I'm planning to improve TiddlyWiki's existing markup so that it isn't broken with respect to paragraphs, and to introduce some alternative syntaxes for some simple formatting. Thanks in advance for at least considering these ideas. . . As I say, I think the kinds of things you're interested in are enabled by the parsing/rendering architecture. I would very much appreciate feedback on the improvements to the wikitext. Best wishes Jeremy /rant -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To
[tw] Re: Suggestion for better WARNING when you delete a tiddler that tags...
Nice. Thanks Mans, that is really helpful. i think those suggstions will solve this Dickon -- 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/-/h6I37IL9OS0J. 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] New user can't register on Tiddlyspace
I am trying to help a couple of new (non technical) users to register on TiddlySpace, but we are struggling - type in username, type in passwords, click Create your space, and nothing happens! What am I doing wrong? dickon -- 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/-/1-TnvMZIMLUJ. 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: New user can't register on Tiddlyspace
On Dec 15, 1:53 pm, dickon dickon.beving...@gmail.com wrote: I am trying to help a couple of new (non technical) users to register on TiddlySpace, but we are struggling - type in username, type in passwords, click Create your space, and nothing happens! What am I doing wrong? Not your fault. When the backstage was updated some code was moved from the tiddlyspace bag to the common bag, but the frontpage code was not updated to reflect this change. Now it has been. Things should work now. Please shout it not. Thanks for the report. -- 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.
Re: Question | mGSD 3.1.8b -Exclude Sub-Projects from Active Projects
ok, looked a bit into the code, and mGSD makes no apparent distinction between projects and subprojects, subprojects just get an extra tag in the form of the it's mother-project. No simple workaround this. You'd need to rename all project-tags into SubProject. And change the mGSD macro so that it will still show up in the mother projects. + a new button 'add Sub-Project' similar to the 'new dependent' button.' -- You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To view this discussion on the web visit https://groups.google.com/d/msg/gtd-tiddlywiki/-/2TFsJRj3tokJ. To post to this group, send email to gtd-tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
Re: Question | mGSD 3.1.8b -Exclude Sub-Projects from Active Projects
Actually, you're in luck. There's a filter clause that checks for the
existence of a parent project:
where:tiddler.hasParent('Project')
or the lack of one:
where:tiddler.!hasParent('Project')
If you change the Active Projects macro as follows, you should see only
projects that are not subprojects:
mgtdList title:'Active Projects' startTag:Project tags:'Active !
Complete' view:ProjectArea mode:global
newButtonTags:'Project Active'
where:!tiddler.hasParent('Project')
--
Stephanie Butler
--
You received this message because you are subscribed to the Google Groups GTD
TiddlyWiki group.
To post to this group, send email to gtd-tiddlyw...@googlegroups.com.
To unsubscribe from this group, send email to
gtd-tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/gtd-tiddlywiki?hl=en.
Re: Question | mGSD 3.1.8b -Exclude Sub-Projects from Active Projects
Argh. I left out a bracket. It should be:
mgtdList title:'Active Projects' startTag:Project tags:'Active !
Complete' view:ProjectArea mode:global
newButtonTags:'Project Active'
where:!tiddler.hasParent('Project')
On Thu, Dec 15, 2011 at 6:27 AM, Stefi Butler quarterd...@gmail.com wrote:
Actually, you're in luck. There's a filter clause that checks for the
existence of a parent project:
where:tiddler.hasParent('Project')
or the lack of one:
where:tiddler.!hasParent('Project')
If you change the Active Projects macro as follows, you should see only
projects that are not subprojects:
mgtdList title:'Active Projects' startTag:Project tags:'Active !
Complete' view:ProjectArea mode:global
newButtonTags:'Project Active'
where:!tiddler.hasParent('Project')
--
Stephanie Butler
--
Stephanie Butler
--
You received this message because you are subscribed to the Google Groups GTD
TiddlyWiki group.
To post to this group, send email to gtd-tiddlyw...@googlegroups.com.
To unsubscribe from this group, send email to
gtd-tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/gtd-tiddlywiki?hl=en.
[tw] Re: TiddlyWiki Development News
Hello all, ' hope everyone is having a good day. Although much of this thread goes over my head, I am glad that Jeremy is again working on Tiddliwiki. As a regular Joe, however, I would like to state that if indeed one were to go with a syntax change I would concur with Martin above. I would definitely be able to adapt to the Creole syntax for the same reason he stated...it's very similar to Tiddlywiki. I do have a question: * If indeed this were to be the case, can one adapt Creole yet keep some syntax that would be unique to Tiddlywiki without the use of plugins or converters? * Or would that be too much work for development? Just trying to educate myself here. This probably should be discussion for another thread. I thought I'd just throw the question out there while it's still fresh in my mind. Thanks all, Julio On Dec 15, 6:15 am, Martin Budden mjbud...@gmail.com wrote: I concur with HansBKK that you should adopt a standard wiki markup for TW 5. I differ from in that I think you should adopt WikiCreole see: http://www.wikicreole.org/wiki/Creole1.0 andhttp://www.wikicreole.org/wiki/CreoleAdditions The main reason for this recommendation is the WikiCreole markup is *very* similar to TW markup. The main differences being the handling of bold, headings and links. WikiCreole even recommends using double angle brackets for plugins. Since TW 5 is going to break compatibility, then I think it should also take the opportunity to move to a standard wiki format. I know text compatibility and code compatibility are different things, but nevertheless I believe this is the correct way forward. Note TW 5 could support standard TW wikiformat using a plugin, and also could provide a converter so that people can easily move their text from TW format to WikiCreole format. Since the formats are so similar, conversion would be fairly straightforward. Martin On 15 December 2011 09:22, Jeremy Ruston jeremy.rus...@gmail.com wrote: I've been doing a lot of research and playing around in the tools that transform markup space recently, and would **implore** you to consider choosing one of the more mainstream cross-platform syntaxes rather than re-implementing a proprietary TWmarkup, even if it may be based on one of them. The primary constraint I am embracing is to retain compatibility as far as possible with existing TiddlyWIki markup. I think that that rules out the wholesale adoption of a standard format - for instance, TiddlyWiki gets [[pretty|links]] the wrong way round from most wikis. To get around the limitations imposed by that constraint, we have the idea of pluggable parsers and renderers, so that it is possible to adopt other formats, and intermingle them and so on. If you can find a JavaScript parser for it, then hopefully you'll be able to use it. Markdown is a popular choice, lots of active development in the Pandocs project - their extensions may be a bit proprietary, but since the focus of the whole project is interoperability, it's for a good cause. Adopting MarkDown in its entirety is a bit troublesome from my perspective; it's not very formally defined, and the only implementations that I've seen are even hairier balls of regexps than the old TiddlyWIki wikifier. It also lacks what I'd have thought of as basic features, like tables, arguing that users should write HTML tags for them. Other candidates are txt2tags and reST/Sphinx, with the former having the edge in a huge number of output formats currently supported. Both of these are implemented in Python, while Pandocs is Haskell, if that means anything. I need JavaScript code, obviously. There may be bits and pieces worth taking from those projects, but a brief glance shows that they take in concerns that don't entirely match TiddlyWiki, so I don't see a way to wholesale adopt those syntaxes. IMO the key is to **not** pick and choose bits and pieces, but to take on an entire **syntax spec as a whole**. I only see that as feasible if there was a spec out there that was (a) compatible with TiddlyWiki and (b) did everything that TiddlyWiki needs and (c) didn't include lots of features that aren't relevant for TiddlyWiki and (d) had usable JavaScript code. This would enable plugging TW into a standardized toolchain so that it can be either a publishing and distribution target, along with say EPUB, AsciiDoc and HTMLhelp, or perhaps even the location where the master source text is edited, to then be able to output and transform to such formats. NB I consider TW's forte to be the former rather than the latter, but something like Pandocs would give the flexibility to go in either direction. As I say, the ability to have pluggable parsers and renderers should give you the capabilities you want. For you, the native TiddlyWiki format might just be what gets used for the application plumbing, with all your content being
[tw] Re: Hijacking saveTiddler
I should also say take care when hijacking where you don't completely
know what you are doing. If you do it wrong you could break the
function. In this situation that means it would be impossible to save
any tiddlers... so take backups :)
On Dec 15, 1:47 am, skye riquelme riquelme.s...@gmail.com wrote:
Ooopa..now thats exactly what I wanted to know. now to work to
see if I can get it woring as I want.
Thanks
Skye
On 14 dez, 08:18, rakugo jdlrob...@gmail.com wrote:
Hijack does seem to be the right word. The idea with hijacking is
// cache the old value of the function
var _cache = TiddlyWiki.prototype.saveTiddler;
// override the existing value
TiddlyWiki.prototype.saveTiddler =
function(title,newTitle,newBody,modifier,modified,tags,fields,clearChangeCo
unt,created,creator)
{
// do something new
alert(!);
// apply the old value
return _cache.apply(this, arguments);
};
Hope this helps...
Jon
On Dec 14, 4:00 am, skye riquelme riquelme.s...@gmail.com wrote:
Hi All
Not sure if Hijacking ids the right term in this case. Basically I
want to modify the saveTiddler macro so that when a student saves a
tiddler. the saveTiddler also does something else...in this case
executes another macro that sends a message to my server..and
maybe emails me a message. ths would be for specific
tiddlers...not ALL!
So how to hijack the saveTiddler macro to my ends...where is it
in the core?
Thanks
Skye
--
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: New user can't register on Tiddlyspace
Brilliant. Thanks Chris. momentary panic as tomorrow I have a whole room full of therapists (known for their munificent patience with the glitches and crashes that occur in the interpersonal sphere, but not for the same in their relation to IT) to train about TiddlySpace in relation to the slowly crescendoing AMBIT project (see @tiddlymanuals and @ambit)... this will now be OK! PS keep an eye out for Jon Lister and Josh Bradley's ambit theme v3 which will be unleashed very soon - tiddlywiki in excelsis. Dickon -- 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/-/mnq_LLvjX4YJ. 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: Hijacking saveTiddler
...thanks even more so for the advice...obviously Ill play around with
a simple non-importante test TW first!!!
and thanks for the warning/advice
Skye
On 15 dez, 12:36, rakugo jdlrob...@gmail.com wrote:
I should also say take care when hijacking where you don't completely
know what you are doing. If you do it wrong you could break the
function. In this situation that means it would be impossible to save
any tiddlers... so take backups :)
On Dec 15, 1:47 am, skye riquelme riquelme.s...@gmail.com wrote:
Ooopa..now thats exactly what I wanted to know. now to work to
see if I can get it woring as I want.
Thanks
Skye
On 14 dez, 08:18, rakugo jdlrob...@gmail.com wrote:
Hijack does seem to be the right word. The idea with hijacking is
// cache the old value of the function
var _cache = TiddlyWiki.prototype.saveTiddler;
// override the existing value
TiddlyWiki.prototype.saveTiddler =
function(title,newTitle,newBody,modifier,modified,tags,fields,clearChangeCo
unt,created,creator)
{
// do something new
alert(!);
// apply the old value
return _cache.apply(this, arguments);
};
Hope this helps...
Jon
On Dec 14, 4:00 am, skye riquelme riquelme.s...@gmail.com wrote:
Hi All
Not sure if Hijacking ids the right term in this case. Basically I
want to modify the saveTiddler macro so that when a student saves a
tiddler. the saveTiddler also does something else...in this case
executes another macro that sends a message to my server..and
maybe emails me a message. ths would be for specific
tiddlers...not ALL!
So how to hijack the saveTiddler macro to my ends...where is it
in the core?
Thanks
Skye
--
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: New user can't register on Tiddlyspace
On Dec 15, 3:29 pm, dickon dickon.beving...@gmail.com wrote: Brilliant. Thanks Chris. momentary panic as tomorrow I have a whole room full of therapists (known for their munificent patience with the glitches and crashes that occur in the interpersonal sphere, but not for the same in their relation to IT) to train about TiddlySpace in relation to the slowly crescendoing AMBIT project (see @tiddlymanuals and @ambit)... this will now be OK! Yay! I assume you are aware of the forthcoming downtime for tiddlyspace.com[1]? This is looking like it will be Wednesday afternoon. PS keep an eye out for Jon Lister and Josh Bradley's ambit theme v3 which will be unleashed very soon - tiddlywiki in excelsis. Yeah, I've been watching that evolve. Very snazzy looking stuff. I'm hoping to be able to benefit from some of their skillz soon. [1] http://groups.google.com/group/tiddlyspace/browse_frm/thread/be3d22d0073185c8 -- 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 Development News
Hi folks, I did re/search a bit for nicely documented wikitext grammers lately. I only found one for wiki creole. The good thing is, that it imo is a good subset of the TW grammar. There is a short article from: Authors: Martin Junghans, Dirk Riehle, Rama Gurram, Matthias Kaiser, Mário Lopes, Umit Yalcinalp at: http://dirkriehle.com/2008/07/19/a-grammar-for-standardized-wiki-markup/ that links to: (see available as a PDF file) http://dirkriehle.com/wp-content/uploads/2008/07/ws2008-wiki-creole-grammar-final-for-web.pdf which talks about there intentions. = Searching Dirk Riehle's site a bit more I found: http://dirkriehle.com/publications/2008-2/wiki-creole/ and http://dirkriehle.com/wp-content/uploads/2008/01/creole10_with_extension.g Which is a full EBNF grammar description for wiki Creole. (using some ANTLR specific commands). Since the source (see: creole10_with_extension.g link) is copyrighted, I did contact Mr. Riehle to get a less restrictive license (just to be sure). Since the creole project is CreativeCommons, I did get an emailed permission to use the most open CC-BY - http://creativecommons.org/licenses/by/3.0/ license to use with TW. @Jeremy Just linking some resources, that may be usefull. -m -- 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] Date confusion
Hi All
A quick question to resolve some confusion about date formats.
If I use Erics QuickNotePlugin like this - quickNote tiddler:Skye-
dateformat:0MM0DD-0hh:0mm:0ss taglist:Nota..the note is
created with the title in the format specified...as you would expect
from Eric's work!!!
Now when I use almost the same date format in a very similar bit of
coding part of a similar input form, like -
input type=button value=submit onclick=
this.form.materia.value=config.options.txtMateria;
this.form.topico.value=config.options.txtTopico;
this.form.subtopico.value=config.options.txtSubTopico;
this.form.nota.value=config.options.txtNota;
var text=this.form.comment.value;
var when=new Date().formatString('0MM0DD-0hh:0mm:0ss');
this.form.when.value=when;
var who=config.options.txtUserName;
this.form.who.value=who;
var title=who+'-'+when;
this.form.title.value=title;
var etiquetas='comment '+who;
store.saveTiddler(title,title,text,who,when,etiquetas,null);
autoSave();
story.displayTiddler(null,title);
the tiddler is not created, and in fact the TW freezes up with a
message saying it cant save the tiddler because -
Erro ao guardar tiddler 'Skye-20111215-16:47:03':
TypeError: b.convertToMMDDHHMM is not a function
Why is this happeningwhy doesnt my date format work in my code??
I´d rather use my code (than Erics) as I plan to have it send the
comment to a MySQL database and generate a message by email.blah.
blah and would rather not mess around too much with Erics work
(mainly cause I´d most likely just break it!)
Thanks
Skye
--
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: Date confusion
var when=new Date().formatString('0MM0DD-0hh:0mm:0ss');
...
store.saveTiddler(title,title,text,who,when,etiquetas,null);
...
TypeError: b.convertToMMDDHHMM is not a function
Why is this happeningwhy doesnt my date format work in my code??
The 'when' variable you define is a date, **formatted as text**. But
the saveTiddler() function expects a Date **object**. Try these
changes:
var now=new Date()
var when=now.formatString('0MM0DD-0hh:0mm:0ss');
...
store.saveTiddler(title,title,text,who,now,etiquetas,null);
enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
TiddlyTools needs YOUR financial support...
Help ME to continue to help YOU...
make a generous donation today:
http://www.TiddlyTools.com/#Donations
Professional TiddlyWiki Consulting Services...
Analysis, Design, and Custom Solutions:
http://www.TiddlyTools.com/#Contact
--
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: New user can't register on Tiddlyspace
Thanks for pointing out the downtime - I hadn't reaised that, and will warn the new users. From tomorrow there will be 17 separate use instances (locally-adapted versions) of the @ambit tiddlymanual in teams across the UK - not bad. Have some chapters in books and a paper coming out next year, too, so things are looking good. What I'd really like is for a surgeon or a midwife, or a district nurse to have a look and say I wanna bit of that! Best wishes and Happy Christmas, Dickon -- 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/-/FQ_CpA7Ndj0J. 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: Date confusion
Thanks...that works, although not sure why. I can see that var now is
a dateas store.saveTiddler expects..but why is var now
formatted into the right format, when the code formated var now as var
when. seems to me the formated date is in when,not now!!!
Anyway, back on the road...now just have to get it to write the note
to mysqland then later have php build the sorted notes into a
text, stored into pureStore format Phew!!!
Thanks
Skye
On 15 dez, 17:12, Eric Shulman elsdes...@gmail.com wrote:
var when=new Date().formatString('0MM0DD-0hh:0mm:0ss');
...
store.saveTiddler(title,title,text,who,when,etiquetas,null);
...
TypeError: b.convertToMMDDHHMM is not a function
Why is this happeningwhy doesnt my date format work in my code??
The 'when' variable you define is a date, **formatted as text**. But
the saveTiddler() function expects a Date **object**. Try these
changes:
var now=new Date()
var when=now.formatString('0MM0DD-0hh:0mm:0ss');
...
store.saveTiddler(title,title,text,who,now,etiquetas,null);
enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
TiddlyTools needs YOUR financial support...
Help ME to continue to help YOU...
make a generous donation today:
http://www.TiddlyTools.com/#Donations
Professional TiddlyWiki Consulting Services...
Analysis, Design, and Custom Solutions:
http://www.TiddlyTools.com/#Contact
--
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] Not all tabs showing up in backstage
I am familiar with tiddlyspot, but I have just started testing tiddlyspace. Currently, when I go to backstage, I get the following tabs: search tiddlers plugins batch tweaks import/export I think I'm missing a few, such as members and include. Can anyone offer advice as to why these are missing? -- 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.
