Talk:Sierpinski triangle: Difference between revisions
Content added Content deleted
m (→Variations) |
m (added a section header for the 1st talk section to put the TOC in the proper place.) |
||
Line 1: | Line 1: | ||
== JavaScript version == |
|||
I'm confused about the algorithm in the JavaScript version. Could we get more descriptive variable names for u and t or maybe a pseudocode algorithm that everyone can use? --[[User:Mwn3d|Mwn3d]] 16:29, 14 March 2008 (MDT) |
I'm confused about the algorithm in the JavaScript version. Could we get more descriptive variable names for u and t or maybe a pseudocode algorithm that everyone can use? --[[User:Mwn3d|Mwn3d]] 16:29, 14 March 2008 (MDT) |
||
== Graphics lib == |
== Graphics lib == |
||
Line 8: | Line 11: | ||
:: I think converting it into graphics would be rather simple, even without a really existing function. It is enough to advance x on every space, and set pixel on every *, and advance y on every "\n" or similar... Anyway... what about languages (like Postscript, Metafont...) which have a "natural" graphics nature? Or what about using the codes in the [[Raster graphics operations]] for languages that implemented that, and —also?— a certain common library/package for the others, if (easily) available? --[[User:ShinTakezou|ShinTakezou]] 10:54, 2 May 2009 (UTC) |
:: I think converting it into graphics would be rather simple, even without a really existing function. It is enough to advance x on every space, and set pixel on every *, and advance y on every "\n" or similar... Anyway... what about languages (like Postscript, Metafont...) which have a "natural" graphics nature? Or what about using the codes in the [[Raster graphics operations]] for languages that implemented that, and —also?— a certain common library/package for the others, if (easily) available? --[[User:ShinTakezou|ShinTakezou]] 10:54, 2 May 2009 (UTC) |
||
== Variations == |
== Variations == |