Hello everybody.
I'm curious about how the confirmation messages are managed. This has
become important since TW acquired the auto save option.
During the Hangout 42 Jeremy asked about a tiddler I was working on (some
kind of agenda). He asked: Why don''t you put a delete button? And I
El miércoles, 9 de abril de 2014 00:42:41 UTC-7, Jeremy Ruston escribió:
The plan is to add optional automatic backup maintenance to TW5, similar
to TW Classic.
That sounds nice.
What about asking for confirmation in every deletion event?
--
You received this message because you are
Hi Danielo
At the moment you'll only get the confirmation message when you delete a
draft tiddler.
Best wishes
Jeremy
On Wed, Apr 9, 2014 at 9:42 AM, Danielo Rodríguez rdani...@gmail.comwrote:
El miércoles, 9 de abril de 2014 01:16:26 UTC-7, Jeremy Ruston escribió:
Hi Danielo
What
On Wednesday, April 9, 2014 11:10:29 AM UTC+2, Danielo Rodríguez wrote:
Are there plans to change this behaviour?
Deleting a tiddler is deleting a tiddler, no matter the type of it.
:) +1
I did encounter a second confimation issue some time ago. ...
If you edit a tiddler and hit the Cancel
On Wednesday, April 9, 2014 11:32:24 AM UTC+2, PMario wrote:
I think I'll create a ticket.
done
https://github.com/Jermolene/TiddlyWiki5/issues/544
-m
--
You received this message because you are subscribed to the Google Groups
TiddlyWikiDev group.
To unsubscribe from this group and stop
I personally think, that the base layout and the base CSS needs tweaking
anyway.
I did create a small pull request [1] that modifies the right sidebar DOM
structure.
It removes the unnecessary p tags, without changing the overall layout.
At the moment I try to simplify the base CSS, to make
Your code is working for me in Chrome. I copied your tiddler text into a
new tiddler in editions/tw5.com/tiddlers, and then rebuilt index.html. On
opening it in the browser, I saw:
jscolor.js invoked $:/plugins/skeeve/jscolor.js:15
Leaving jscolor.js $:/plugins/skeeve/jscolor.js:21
EditTextWidget
On Wed, Apr 9, 2014 at 10:10 AM, Danielo Rodríguez rdani...@gmail.comwrote:
Are there plans to change this behaviour?
Deleting a tiddler is deleting a tiddler, no matter the type of it.
I think the current behaviour of only requesting confirmation for deleting
drafts was accidental. I've
Tested with a fresh download and it works as expected.
It did not work with the node.js version. I'm going to update that and test
again.
--
You received this message because you are subscribed to the Google Groups
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails
Updated to 5.0.9prerelease and No! No EditTextWidget PostRender Called
message at all :(
--
You received this message because you are subscribed to the Google Groups
TiddlyWikiDev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Thank you Jeremy!
Fixed for the next release!! Wow. Will this small tweaks postpone the
delivery date of the new awesome version?
El miércoles, 9 de abril de 2014 03:32:28 UTC-7, Jeremy Ruston escribió:
On Wed, Apr 9, 2014 at 10:10 AM, Danielo Rodríguez
rdan...@gmail.comjavascript:
On Tue, 8 Apr 2014, chris.d...@gmail.com wrote:
All I need is a reliable way to read the text and fields of a tiddler,
regardless of its content type.
I think the best thing is going to be to set the 'type' field to
something different. There's already the unholy freaking of content
types in
Fixed for the next release!! Wow. Will this small tweaks postpone the
delivery date of the new awesome version?
It's done. It took about 10 minutes.
Best wishes
Jeremy
El miércoles, 9 de abril de 2014 03:32:28 UTC-7, Jeremy Ruston escribió:
On Wed, Apr 9, 2014 at 10:10 AM, Danielo
Updated to 5.0.9prerelease and No! No EditTextWidget PostRender Called
message at all :(
I ran my experiments against 5.0.9, too. Weird.
Best wishes
Jeremy
On Wed, Apr 9, 2014 at 1:11 PM, Stephan Hradek stephan.hra...@gmail.comwrote:
Updated to 5.0.9prerelease and No! No EditTextWidget
So I've managed to get jscolor to display the picker for the color fields
now.
The disadvantage is: The changes are not reflected in TW as jscolor is (of
course) overwriting the focus and input events and I'm not understanding
how I could solve that issue properly :(
--
You received this
I tried to call handleInputEvent alas I have no idea how to get it.
I tried this:
jscolor.color( domNode, { hash : true, onImmediateChange :
EditTextWidget.prototype.handleInputEvent } );
But this gives me JavaScript errors.
I gues I need to get the handler somehow from my domNode…
Hi Chris
Two is that, despite the above, it makes semantic sense that a
tiddler which has as content JSON but is expected to be manipulated
as a tiddler (that is the text attribute of a tiddler is JSON) should
have a content type that is distinct from straight
application/json.
This is the
Hi Stephan
You'd have to pass a reference to the implementation of handleInputEvent.
Something like this:
var self = this;
...
jscolor.color( domNode, { hash : true, onImmediateChange :
self.handleInputEvent
} );
Best wishes
Jeremy
On Wed, Apr 9, 2014 at 3:42 PM, Stephan Hradek
On Wed, 9 Apr 2014, Jeremy Ruston wrote:
This is the bit that I still struggle with. There's still entirely special
behaviour for application/json tiddlers. From the point of view of
TiddlyWiki these tiddlers really are application/json, and not some special
TW variant implied by the special
Hi Chris
Strictly speaking in neither case are they getting text/html nor
application/json, they are getting tiddlers which _contain_ text/html
and application/json. I think this is important.
That's a useful distinction. So, TW5 wants to PUT/GET a representation of
tiddlers that is always
On Wed, 9 Apr 2014, Jeremy Ruston wrote:
This rule works fine for everything _but_ application/json which is
why I've suggested this change:
But doesn't that add up to the rule *not* being followed because of the
inconsistent treatment of tiddlers that contain application/json?
That's what
Hi Chris
Yes, if/when that change is made the content type for PUTting a JSON
container of _any_ type of tiddler will be as above, and you can set
the 'type' to whatever you want.
So, it sounds like the only change on the TW5 side would be to change the
content type for PUTs here:
Hi Stephan
I don't get it :(
the handleInputEvent is attached to the domNode, right? So this is what I
*thought* should work:
No, the handleInputEvent is a method on the edit-text widget.
EditTextWidget.prototype.postRender = function() {
var domNode = this.domNodes[0];
I think I have it:
EditTextWidget.prototype.postRender = function() {
var domNode = this.domNodes[0];
var self = this;
if($tw.browser this.document !== $tw.fakeDocument
domNode.getAttribute(type) === color) {
jscolor.color( domNode, { hash : true, onImmediateChange :
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`
Hi FND
I've had some scenic train time to think about this today, or perhaps it
was the wind tunnel clearing my pathways
Wind tunnel?!? Sounds like that could be helpful for my occasional mental
befuddlement.
- either way, I've come to the
conclusion that a tiddler's `type` refers
26 matches
Mail list logo
