[tw] Re: manipulating the dom using jQuery
I understand what's happening but what I want to know is why. Because I expect it work one way, and it works another. Therefore, if I can understand the underlying concept, I won't assume a logical conclusion that is incompatible with javascript (because there is surely a difference in mental model between javascript and the other languages I've used). I can and will study information and tutorials available about javascript, BUT, I always try to do something useful with what I'm learning early on, as I can retain it better. But useful stuff often builds upon an complete understanding of the subject. The problem with only reading the documentation or current tutorials is the bleeding edge is always changing the paradigm. Don't you think javascript programming is changing rapidly with the advent of html5? (or rather, is javascript changing html?) Also I want to make unobtrusive javascript code, but the tutorials and beginner information is usually old and obtrusive examples. (the better stuff is more conceptual and less likely to be demonstrated to a beginner audience). /rhetoric rant Bottom line, what I'm asking is, I know the two work differently-- but _why_. is this because of objects? I'm used to thinking that using a variable is only a shortcut, it just functions the same as the text that it was defined with. (does that make sense?) ` newP = document.createElement(p); Is newP a variable, an object, or both? Is this because it's a different variable *type*? Is this behavior part of object-oriented programming (my experience in programming is limited to basc perl/cgi--therefore my understanding of variables is different/limited) I just want to conceptualize javascript code in the correct (or most productive) mindset... And I want to apply javascript to what I already understand. Does that clarify my intentions?? (sorry for sounding overly zealous) --~--~-~--~~~---~--~~ 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: using variables when manipulating the dom
fair enough, but the one-liner version still does not work correctly. if I don't capture the createElement method first in a variable, it will append the only the text to the body. compare the difference: http://jksjs.s3.amazonaws.com/ce1.html and http://jksjs.s3.amazonaws.com/ce2.html --~--~-~--~~~---~--~~ 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] using variables when manipulating the dom
Is it alright to ask general questions about javascript here?
I'm trying to understand the mental model(s) of the dom.
I'm experimenting with adding and removing elements from the page.
I got this to work:
` function addParagraph() {
` var newP = document.createElement(p);
` var newT = document.createTextNode(hello, world!);
` newP.appendChild(newT);
` document.getElementsByTagName('body')[0].appendChild(newP);
` }
my question is, if the above works, why doesn't this?
(replaced variable `newP`):
` function addParagraph() {
` var newT = document.createTextNode(hello, world!);
` document.createElement(p).appendChild(newT);
` document.getElementsByTagName('body')[0].appendChild(newP);
` }
What's at work here? does the variable capture something being passed
from the method?
why can't I use appendChild and createElement within the same
statement? I guess I thought that variables were mostly a shortcut, so
it seemed to me you COULD write the above example in one line, without
variables. (note: I can subsitute the var `newT` in the sample above
with no issues.)
admittedly, my knowledge of javascript is slim, but I find it hard to
learn it without also understanding its application to the dom. the
tutorials at w3schools.com are so dated.
--~--~-~--~~~---~--~~
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: style to override the header gradient?
Thank's for everyone's replies! I don't expect tiddlywiki to radically change. I want to tiddlywiki to modularize its functions, and maybe I can copy them in designing my own wiki. I want to dismantle tiddlywiki, and reconstruct my own wiki with aesthetics in mind from the get go (and interaction on small devices). I'll be happy if jQuery makes this easier by standardizing the feature set of tiddlywiki. maybe there is room for a tiddlywiki 2, where we could demonstrate some radical new changes for modern browsers (without worrying about breaking support/compatibility). but I don't expect this. (just out of curiosity, other than jQuery, what sort of features/goals are in the roadmap for the current tiddlywiki build that is backwards- compatible?) I'm trying to find where html is lacking in designing an interactive application such as tiddlywiki. Is html5 sufficient as it is?--is it is enough to cleanly redefine tiddlywiki? I want to be able design with meaningful markup and progressive css. Markup has become so convoluted with container elements such as div and span that are added only in concern for styling. These are typically used to create complex, fragile layouts and user interactions with css. But I don't think these layouts nor the complicated markup used to create them are necessary to build well-designed websites/applications. Tiddlywiki has a 3-column layout designed with the desktop in mind. Instead of redesigning tiddlywiki for a mobile setting, why not build it so that is usable to everyone and perhaps progressively enhanced for people with more screen real-estate? I don't expect the tiddlywiki crew to answer all these questions. But I do hope you all working on it continue to modularize it. I hope that I can build a tiddlywiki someday (soon) as easily as I build conceptual templates with html and css: by progressively adding modularized javacript functionality to recreate tiddlywiki's functionality transparently with any design. If only these concepts were demo'd somewhere (i.e. an html file demonstrating the javascript for opening and closing tiddlers-- probably trivial). I did notice the save plugin was demo'd at http://jquery.tiddlywiki.org/, and I think this is a step in the right direction. Learning javascript from the bottom is hard when you know when what your trying to recreate is already very evolved and sophisticated. Once I can build designs more rapidly without working _around_ tiddlywiki, I will quickly discover which design is best. Tobias, good luck to what your working on! containing core css definitions to nullify any default browser styles I never go this far when creating stylesheets, but I might try it someday. --~--~-~--~~~---~--~~ 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: style to override the header gradient?
You can over ride the PageTemplate gradient with this in the
StyleSheet.
.headerShadow {color:#000;background:#f00}
Using this method, a margin of the macro will still be seen, as the
shadow is offset top left 1px.
--~--~-~--~~~---~--~~
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: style to override the header gradient?
analysed this quite awhile and here are my results.
afaik the macro appends layers of div's with gradiating backgrounds
after .headerForeground and .headerShadow. (try firebug or safari's
web inspector)
so I concocted this to disabled the macro completely:
.header {background:inherit}
.header div+div+div {display:none}
furthermore, to disable the shadow:
.headerShadow {visibility:hidden}
a less elegant but shorter way:
body,.headerForeground {background:#fff;width:100%}
You can over ride the PageTemplate gradient with this in the
StyleSheet.
.headerShadow {color:#000;background:#f00}
Using this method, a margin of the macro will still be seen, as the
shadow is offset top left 1px.
--~--~-~--~~~---~--~~
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: style to override the header gradient?
analysed this quite awhile and here are my results.
afaik the macro appends layers of div's with gradiating backgrounds
after .headerForeground and .headerShadow. (try firebug or safari's
web inspector)
so I concocted this to disabled the macro completely:
.header {background:inherit}
.header div+div+div {display:none}
furthermore, to disable the shadow:
.headerShadow {visibility:hidden}
a less elegant but shorter way:
body,.headerForeground {background:#fff;width:100%}
You can over ride the PageTemplate gradient with this in the
StyleSheet.
.headerShadow {color:#000;background:#f00}
using this method, a margin of the macro will still be seen, as the
shadow is offset top left 1px.
--~--~-~--~~~---~--~~
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: style to override the header gradient?
it's nice how tiddlywiki provides several measures of hackability, but when it comes down to it styling it is very difficult. it's hard to measure what is the best way to achieve a look if you didn't write the markup itself or all the default styles. I find tiddlywiki's default look convoluted and distracting (I'm spatially-oriented and dogmatic about aesthetics). I conceptualize a wiki where design disappears, rather than drawing attention to itself. (BTW hacked-up special effects like gradients and text-shadow do not make it any more usable, and barely more attractive. adding complexity to markup for achieving a style effect is a bad idea. CSS3 provides a text-shadow property AND gradients.) I've been trying to design it from the inside-out to be more usable and its a nightmare. if I but more than dabbled in javascript perhaps I would achieve a better understanding of tiddlywiki's guts and it wouldn't be quite such an undertaking. all I know is I spend more time considering how to make tiddlywiki more usable then I do using tiddlywiki. I'm trying to catch up. the use of jQuery in recent versions is exciting, and the idea of modularization of functions. Its important for people to construct their own tools. will I one day be able to rapidly construct a tiddlywiki using a pre-existing, modularized library of rich javascript functions? is tiddlywiki backporting some of its features to jQuery itself, rewriting some of its original features using jQuery, or both? (sorry to get off-topic) --~--~-~--~~~---~--~~ 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: style to override the header gradient?
analysed this quite awhile and here are my results.
afaik the macro appends layers of div's with gradiating backgrounds
after .headerForeground and .headerShadow. (try firebug or safari's
web inspector)
so I concocted this to disabled the macro completely:
.header {background:inherit}
.header div+div+div {display:none}
furthermore, to disable the shadow:
.headerShadow {visibility:hidden}
a less elegant but shorter way:
body,.headerForeground {background:#fff;width:100%}
You can over ride the PageTemplate gradient with this in the
StyleSheet.
.headerShadow {color:#000;background:#f00}
using this method, a margin of the macro will still be seen, as the
shadow is offset top left 1px.
--~--~-~--~~~---~--~~
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: style to override the header gradient?
(cont..) ...it's nice how tiddlywiki provides several measures of hackability, but when it comes down to it styling it is very difficult. it's hard to measure what is the best way to achieve a look if you didn't write the markup itself or all the default styles. I find tiddlywiki's default look convoluted and distracting (I'm spatially-oriented and dogmatic about aesthetics). I conceptualize a wiki where design disappears, rather than drawing attention to itself. (BTW hacked-up special effects like gradients and text-shadow do not make it any more usable, and barely more attractive. adding complexity to markup for achieving a style effect is a bad idea. CSS3 provides a text-shadow property AND gradients.) I've been trying to design it from the inside-out to be more usable and its a nightmare. if I but more than dabbled in javascript perhaps I would achieve a better understanding of tiddlywiki's guts and it wouldn't be quite such an undertaking. all I know is I spend more time considering how to make tiddlywiki more usable then I do using tiddlywiki. I'm trying to catch up. the use of jQuery in recent versions is exciting, and the idea of modularization of functions. Its important for people to construct their own tools. will I one day be able to rapidly construct a tiddlywiki using a pre-existing, modularized library of rich javascript functions? is tiddlywiki backporting some of its features to jQuery itself, rewriting some of its original features using jQuery, or both? (sorry to get off-topic) --~--~-~--~~~---~--~~ 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: style to override the header gradient?
(also...) it's nice how tiddlywiki provides several measures of hackability, but when it comes down to it styling it is very difficult. it's hard to measure what is the best way to achieve a look if you didn't write the markup itself or all the default styles. I find tiddlywiki's default look convoluted and distracting (I'm spatially-oriented and dogmatic about aesthetics). I conceptualize a wiki where design disappears, rather than drawing attention to itself. (BTW hacked-up special effects like gradients and text-shadow do not make it any more usable, and barely more attractive. adding complexity to markup for achieving a style effect is a bad idea. CSS3 provides a text-shadow property AND gradients.) I've been trying to design it from the inside-out to be more usable and its a nightmare. if I but more than dabbled in javascript perhaps I would achieve a better understanding of tiddlywiki's guts and it wouldn't be quite such an undertaking. all I know is I spend more time considering how to make tiddlywiki more usable then I do using tiddlywiki. I'm trying to catch up. the use of jQuery in recent versions is exciting, and the idea of modularization of functions. Its important for people to construct their own tools. will I one day be able to rapidly construct a tiddlywiki using a pre-existing, modularized library of rich javascript functions? is tiddlywiki backporting some of its features to jQuery itself, rewriting some of its original features using jQuery, or both? (sorry to get off-topic) --~--~-~--~~~---~--~~ 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] style to override the header gradient?
can the header gradient macro be overidden with a style rule?
I tried
.header {background:#f00!important}
but no luck. I know I could modify the PageTemplate, but I'm trying to
implement a theme using only the stylesheet tiddler.
It's easier to maintain and distribute this way.
--~--~-~--~~~---~--~~
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: cname to tiddlyspot
well are there any services that'll host a tiddlywiki that can be cname'd to? imagine: 1. create tw at tiddlyspot.com 2. buy a domain, and add a cname for tiddlyspot 3. modify the tiddlywiki to deploy as a (bare bones) website * any additional content can be linked (flickr, wordpress, twitter etc.) easily created, easily deployed, from any browser. easy to modify by someone with no technical experience, without sacrificing the control of css/html/js. the domain makes it feasible for a small business or organization (maybe just as a draft or proof-of-concept). and although tiddlywiki does rely on javascript, i'm sure it could be made accessible in no-javascript solutions, if just to display basic information. the point is having content linked to a meaningful/useful uri as quickly and with as low overhead as possible. is this a good idea, or am i too zealous? On May 17, 6:06 pm, Simon Baird simon.ba...@gmail.com wrote: I don't think it would work. On Mon, May 18, 2009 at 7:34 AM, jk emailo...@gmail.com wrote: Would it be possible to create a cname record to tiddlyspot hosted wiki? -- simon.ba...@gmail.com --~--~-~--~~~---~--~~ 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] cname to tiddlyspot
Would it be possible to create a cname record to tiddlyspot hosted wiki? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
