[tw] innards of modern browsers?
Hi Folks, Since this is pretty central to TiddlyWiki, I figure someone here might be able to point me at documentation (presentation form would be nice) about the innards of modern browsers. I'm particularly looking for information about some of the newer HTML5 storage and webapp functionality - and even more specifically what gets stored, and how, if one edits the content of an active page via JavaScript - what state can be saved, and how does it happen (and which of this is dictated by standards vs. by specific browser designs). Thanks Very Much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- 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] innards of modern browsers?
Hi Miles This is quite a good starting point for finding out more about how browsers work: http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ I think though that your specific questions might be answered by the HTML 5 specs. Basically, all the storage features are exposed as JavaScript APIs, and things only get stored explicitly. So, if one edits the contents of an active page then nothing will get stored unless JS code explicitly does so. In terms of caching, the caching mechanisms in browsers are at the network level. So they cache the results of particular network requests, rather than caching the state of the document as it changes. Best wishes Jeremy -- Jeremy Ruston jeremy.rus...@gmail.com On 7 May 2012, at 16:11, Miles Fidelman mfidel...@meetinghouse.net wrote: Hi Folks, Since this is pretty central to TiddlyWiki, I figure someone here might be able to point me at documentation (presentation form would be nice) about the innards of modern browsers. I'm particularly looking for information about some of the newer HTML5 storage and webapp functionality - and even more specifically what gets stored, and how, if one edits the content of an active page via JavaScript - what state can be saved, and how does it happen (and which of this is dictated by standards vs. by specific browser designs). Thanks Very Much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- 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] innards of modern browsers?
Hi Jeremy, Thanks! And... Jeremy Ruston wrote: Hi Miles This is quite a good starting point for finding out more about how browsers work: http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ Unfortunately, it doesn't really talk about how JavaScript interacts with things. However.. it contains a list of references that point to: http://www.vineetgupta.com/2010/11/how-browsers-work-part-1-architecture/ which does, at least a little. I think though that your specific questions might be answered by the HTML 5 specs. Basically, all the storage features are exposed as JavaScript APIs, and things only get stored explicitly. So, if one edits the contents of an active page then nothing will get stored unless JS code explicitly does so. As far as I can tell, the HTML5 spec days very little about HTTP interactions. In terms of caching, the caching mechanisms in browsers are at the network level. So they cache the results of particular network requests, rather than caching the state of the document as it changes. Right... but think about things like HTTP PUT, POST, DELETE and interactions with AppCache. As far as I can tell, there is nothing in the HTML5 documents, or anywhere else, that talks about this. And it gets just that much trickier, when talking about executing a page headless, say with node.js. Sigh... Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- 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: wanted: endless nested slider loop
Thanks, that works great!! I'm going to try to use it to build some process flow/loop diagrams (e.g. the nutritional approach to cancer prevention) that people can follow by clicking on the sliders, obviously in a linear fashion, but as the process unfolds the looping becomes apparent. If I get one working the way I'm envisioning I'll post it here for interest. On May 5, 8:59 pm, Eric Shulman elsdes...@gmail.com wrote: On May 5, 12:03 pm, Dave cedar...@telus.net wrote: Hi, just wondering if there's a way to disable the loop limitations on this: [[EndlessLoop2]] this is EndlessLoop2 +++[click for loop 3]tiddler EndlessLoop3=== [[EndlessLoop3]] this is EndlessLoop3 +++[click for loop 2]tiddler EndlessLoop2=== If I refer two or three tiddlers to each other in this way, the progression stops after 3 or 4 iterations. Is there a way to allow looping to continue indefinitely? The loop limit is necessary to prevent run-away recursion, which would cause the parser to never finish processing, and thus lock up your browser. However, there is a little trick that WILL allow you to infinitely nest the sliders by using the NestedSlidersPlugin deferred rendering feature (aka, lazy sliders). By adding ... following the closing ] of ALL the slider labels, slider *content* will not actually be rendered until you click to open that slider, which then only renders the current slider content since any nested sliders are also lazy, so no recursion occurs, and the parser will not lock up. Give this a try: [[EndlessLoop2]] this is EndlessLoop2 +++[click for loop 3]...tiddler EndlessLoop3=== [[EndlessLoop3]] this is EndlessLoop3 +++[click for loop 2]...tiddler EndlessLoop2=== Note: I also used an optional (blockquote) syntax, so that the slider content display will be indented for each nested level, so that you can really see how deep you've gone. enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios WAS THIS ANSWER HELPFUL? IF SO, PLEASE MAKE A DONATION http://www.TiddlyTools.com/#Donations note: donations are directly used to pay for food, rent, gas, net connection, etc., so please give generously and often! 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: Trying to get the AutoTagger plug-in to work
Thanks, Eric. AutoTagger *does* work with a handmade Tiddler, incrementing the Dropbox and Linux tags in the normal way. It looks like the problem is indeed with TiddlySnip. Roger -- 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/-/6ytb12abjvEJ. 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] calendar
Hi, We are trying to use the calendar plugin - all we want is a display of the calendar and to create events associated with particular days but don't want people to follow onto a tiddler? Thanks Philippe -- 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/-/cC4yQRXvEJ4J. 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] popups in chrome?
Hi All I have a TW that has a Youtube video embedded in the default tiddler. And a header that contains navegation panels that open in popups. In FF it all works well, but in Chrome... the popup panels open behind the embedded video, while in FF they open on top of the video. Obviously with the popups sitting behind the video the navegation is not possible. Anyway to get the popup to open on top of the video 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.
