Template talk:Ele

I would like to change this template to accept the opacity value passed in to it...any objections?--David Yamakuchi 15:57, 6 April 2008 (CDT)

Yeah, but if you add an opacity value you have to include it in every functional call on the {{periodic}} page. Also, the periodic template needs some logic in there to allow you to select one of the ele units to "highlight" it. I'm not sure how to accomplish that yet.--Robert W King 15:58, 6 April 2008 (CDT)

I'm on it :-)--David Yamakuchi 16:38, 6 April 2008 (CDT)

Basically, the command should be {{periodic|highlight=thiscoordinate or thiselement}} or something like that. --Robert W King 17:07, 6 April 2008 (CDT)

Check it out...[1]--David Yamakuchi 21:01, 7 April 2008 (CDT)

Cell Width

When does the b field ever get used in the context of "border:{{{b}}}px solid #000;"? It seems that the addition of a border here causes each cell to become wider. Chris Day 13:12, 8 April 2008 (CDT)

I put a hook in so that we can resize the "element" if needed. I left the border setting in place so that if you want to have an ele that has a border, theoretically you should be able to declare it to be a smaller size and compensate. I haven't tested this of course, we don't need the functionality...for _this_ table :-)--David Yamakuchi 13:38, 8 April 2008 (CDT)

There's a problem with each ele cell border I discovered early on (shoulda said something, apologies). Remember when you add a border to all sides, it adds 1 pixel width to every little ele cell, so in effect something 6 pixels wide becomes 8. Multiply that times how many ele cells there are and... you get the idea. Also you'll end up with double-thick lines if you border all eles which look really unsightly. --Robert W King 13:45, 8 April 2008 (CDT)

I guessed the double line, judging from the white space, and was testing to see what a dark gray double line would look like. I have not really delved into the code too much. Are all these cell elements part of a table? If so, why couldn't a cellspacing=0 parameter be used to prevent a double line? Chris Day 13:52, 8 April 2008 (CDT)

They're part of a table yes, and the only way to get a single line around any individual element would be to specificy a style sheet for every little ele. Otherwise, to define the lines within the entire table would result in table lines being drawn even around the blank entries (which we don't want). --Robert W King 14:00, 8 April 2008 (CDT)

Changes

Watch out, it may look normal but now look on lead. Careful with changes. I just reverted two versions because it seriously tampered with the appearance of the template. Everything that's in there is there on purpose in order to make it look correct on all browsers. --Robert W King 15:45, 8 April 2008 (CDT)

OK, I'll just pull out the conditional resize and see how much diff...--David Yamakuchi 16:00, 8 April 2008 (CDT)

I don't think documentation in this case makes a difference in size considering it's rendered from another template. Could be mistaken though. --Robert W King 16:03, 8 April 2008 (CDT)

Also I think the bulk of the code size will be in {{periodic}}. We might need "smarter" logic, or some other way of specifying which ele to highlight. --Robert W King 16:06, 8 April 2008 (CDT)

Maybe, but when I pulled out the documentation the number that Chris Day looks at went from 1058kB to 743kB. Remember ele is called a hunderd times. My browser (ie) sseems to count the thing 100x including documentation!--David Yamakuchi 16:54, 8 April 2008 (CDT)

Isn't it called more than once for each element? Just because it is not used does not mean it will not count to the pre=expand size. So it might be called up to three or four hundred times. Obviously, from your experiment, it does make a significant difference. Chris Day 17:00, 8 April 2008 (CDT)

again, watch what is cut out because it wrecks formatting. --Robert W King 21:22, 8 April 2008 (CDT)