LDraw.org Discussion Forums › LDraw Programs › LDraw File Processing and Conversion v
LDraw to Web

LDraw to Web


Jamie B. Offline
Provisional LDrawer *
Posts: 3
Threads: 1
Joined: Oct 2011
Re: that solution will also work for pad computers
#11
2011-11-04, 19:20
On the parts angle, I don't think it would be that bad. Parts are already HTTP accessible from LDraw.org, although I doubt it's set-up to handle this kind of load.

An app can cache the parts using one of the several HTML5 storage options, as well as using HTTP caches. Additionally, parts average 10k each and subparts average 5k (very compressible). Include procedurally-generated subparts (a la LDView), and I would consider this reasonable downloads.

As for the speed of JavaScript, Chrome and Firefox are both JIT compiling now, so it should be comparable in speed to Java.
Find
Reply
« Next Oldest | Next Newest »



Messages In This Thread
LDraw to Web - by Nick McBride - 2011-09-09, 19:32
Re: LDraw to Web - by Roland Melkert - 2011-09-09, 21:32
Re: LDraw to Web - by Nick McBride - 2011-09-11, 15:22
Re: LDraw to Web - by Roland Melkert - 2011-09-11, 17:21
Re: LDraw to Web - by Nick McBride - 2011-09-11, 20:11
Re: LDraw to Web - by Nick McBride - 2011-09-13, 15:58
Re: LDraw to Web - by Jim DeVona - 2011-09-17, 14:37
why not use JavaScript ? - by Steffen - 2011-09-27, 17:44
Re: that solution will also work for pad computers - by Jamie B. - 2011-11-04, 19:20

Forum Jump:


Users browsing this thread: 1 Guest(s)