Hi Richard, In my experience, there are serious performance difficulties before 10 megs with TW, especially on devices. So a 6 meg Bible will take 18 seconds to load. Once it's loaded it doesn't work too bad for *reading*. Saving may be another matter. A particular problem is that on Android devices, if you go away from an app and come back, it may arbitrarily decide to reload the page. It has to do with how Android manages memory. I wonder if the i-products suffer from the same condition?
I took a similar approach to the data, except I compressed data wherever possible. I used the spreadsheets with various formulas to massage the data. There was a lot of by-hand work to fix it up. The problem is that the source document was mostly concerned with actual speakers, but when you're importing everything, including stage directions needs to be assigned a value that says what it does and where it goes. To reduce overhead, each line is given a 5 part id: play.act.scene.speech.line. "Speech" is a number that indicates which speech (set of lines) this is. With a js macro containing an embedded list of actor names/speech part, it would be possible to extract actor name if that was desirable. I suppose it wouldn't add too much overhead to put in a hex code or something to identify the speaker (just looked it up -- there's about 1200 speaking characters in all Shakespeare's works) . The question is, is anyone other than an occasional english major doing a dissertation all that interested in TW versions of Shakespeare? That IOS page came up very fast. I downloaded it. The entire thing with images is only about 1 meg. Maybe I'm not looking at the right page? Thanks! Mark On Monday, June 20, 2016 at 9:16:23 PM UTC-7, RichardWilliamSmith wrote: > > Hi Mark, > > It looks great. When I did similar with Macbeth, I was able to use the > spreadsheet (and a lot of futzing) to add several fields to each line of > the play - which might seem like overkill but it means that you can, for > example, extract all the lines spoken by a particular character etc. > > > <https://lh3.googleusercontent.com/-0DtqN8d_zPY/V2i99P4A_oI/AAAAAAAABo0/ojWKFQg2XG0FXJAYM55-VNd3Uo5AVy8ZACLcB/s1600/Screen%2BShot%2B2016-06-21%2Bat%2B2.04.08%2BPM.png> > > The primary key here is as simple as possible - every piece of dialog and > direction gets a sequential integer. > > As for the total size of the finished document, my advice would be "don't > panic!" - most of the web pages we load every day are much bigger than even > a fully-stuffed tiddlywiki. I was reading this slide-deck just the other > day which you might be interested in; > http://idlewords.com/talks/website_obesity.htm > > "Let's take a look at the Apple page that explains iOS on the iPad Pro >> <http://www.apple.com/ipad-pro/ios9/>. How big do you think this page >> is? >> Would you believe that it's bigger than the entire memory capacity of the >> iconic iMac? (32 MB) >> In fact, you could also fit the contents of the Space Shuttle Main >> Computer. Not just for one Shuttle, but the entire fleet (5 MB). >> And you would still have room for a tricked out Macintosh SE... (5MB). >> ...and the collected works of Shakespeare... (5 MB) >> With lots of room to spare. The page is 51 megabytes big." > > > So, you see, if our file is only 10 or 20 times the size of our actual > content, we are really doing quite well ;) > > Regards, > Richard > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b8424c47-6ca7-43c9-9a98-2c584df81aee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
