Quote:
Originally Posted by garbanzo
that kind of defeats the purpose of a WYSIWYG editor, no?
i'm also experiencing problems. the app is slow to the point that it is absolutely unusable. it takes around 20 seconds to load a file if i'm lucky - half the time it just stops responding. once i get an epub to load, i can't even scroll without having to wait another 10 seconds for a refresh, let alone edit anything.
if i switch to code view everything is fine.
tried on half a dozen epub files, no luck at all.
Windows 7 x86
|
I feel for you. Believe me, I do. On the files I edit, I basically get the same user experience. Makes me infinitely sad and frustrated. Pissed off, as well.
Wait for 0.2.0. It'll be out in about three weeks, and it's a joy to use: loading huge files takes about 2 seconds, and since the XHTML files are not concatenated into one large one but left separate, you merely open the one you want to edit in a tab and it works reasonably fast. Several times faster than before, actually. This is because the smaller the flow loaded, the faster WebKit can respond. It gets slower exponentially depending on the size.
And since content files are now separate, I can multi-thread the loading process: every XHTML file needs to go through Tidy, and for each one a functor "task" is created. So 50 different content files, 50 different "tasks". These are then handed off to a thread pool that munches them in parallel until they are all done. The number of threads in the thread pool is equal the number of
logical CPUs (cores and HT count) on your machine. So if you have a quad-core with HT (8 logical CPUs), it's going to get the loading done 8 times faster than some single-core machine. And it scales linearly. But even on my measly old Core 2 Duo, it loads large files in 2 seconds, not 20.
There's a great amount of MT optimizations that can be employed in this kind of architecture. A few (like the one I mentioned) will be used in the first release in the 0.2.0 branch, and more will follow later.
Until then, use Code View for large files.
EDIT: Oh if current Sigil "stops responding" during the loading procedure, it's actually still doing work. Just let it finish, it will return GUI control when it's done.