zlacker

>>Tomte+(OP)
this site comes up often and it usually sparks conversations about shoelaces, but i want to see the algorithms(o) and database schema

the consistency in the images, and the seemingly exhaustive quantity, implies they were algorithmically generated

i would love if each image had a build array that documented how to draw the laces using a minimalist(i) notation representing connections and nodes

this paired with simple client side code could have the images created dynamically with less work for the server and less data being sent across wire.. a random photo(ii) from the 'dis' method(iii) was 2.7K

instead it seems the server either stores or creates html with the images hard coded and serves up the images associated with the method, though the image file names are encouraging of a meticulously normalised underlying abstraction

i think an appreciation, either conscious or unconscious, for this underlying abstraction is part of the attraction to this project

(o) http://www.fieggen.com/shoelace/2trillionmethods.htm

(i) http://www.fieggen.com/software/info.htm

(ii) http://www.fieggen.com/la/ya-d+.png

(iii) http://www.fieggen.com/shoelace/displayshoelacing.htm

>>justif+2l2
Like you, I'd love to pass a simple minimalist string to a Javascript code to render images client-side. My more recent "Create-a-Lace" does just that, dynamically generating all the .svg images using client-side Javascript. However, I've yet to see browsers correctly render shadows, without which the diagrams lose depth. When that hurdle is overcome, I may well extend this concept to all lacing methods.

In the meantime, I do indeed need to resort to some 600+ individual .png images in order to render each of the 50+ lacing methods with their many variations and multiple numbers of eyelet pairs.