Hi,
My guess it is the early Qt builds stored as Frameworks inside the app. Right now Qt 5 is up to version 5.3.1 and it seems to be much more stable than earler versions although the macdeployqt program stills seems to have issues with missing dependencies in some of the plug-ins.
I agree not having an open bug / issue tracker is a major hurdle. The only one I could find was in Googlecode and it has posts up to March and April of this year when it was closed. There are in fact many Mac OS X keeps crashing style bug reports there that duplicate what Carrigboy reported. I am hoping the updating to a newer Qt will help him.
As for Epub3 support, that can could come in stages ...
1. duplicate and modify the toc.ncx code to become the new nav.html
2. move guide info from content.opf to nav.html landmarks
3. modify the metadata code to grok the new metadata types while remembering the current metadata as well
4. Replace the entire Flightcrew with a simple interface to the standard epub 2 and 3 checkers
5. add plugin support for python based plugins similar to what calibre has done
The remainder can come with time and in small changes.
It is a lot of work but the actual code beyond the GUI is quite straight forward and easy to read. Having Qt familiarity is probably the single most important skill as Qt data types and structures/Strings are being used everyplace.
Anyway, as I said the bones/code are really good so I hate to see it go.
Take care,
KevinH
Quote:
Originally Posted by radius
Just wanted to say that I have been running 0.7.4 on Mavericks for quite a while, so it works in general. There must be something specific to Carrigboy's setup that is causing the crash. From what has been posted in the thread, there isn't enough information to guess what that might be.
Regarding continued development, I think the issue to me is that there isn't an active bug database right now (and nobody to triage it even if it existed) so new developers don't have small bits to work on as they learn Sigil's code. The only big feature I can think of to add would be epub3 support and that is complicated enough to add that it would be very helpful to be already familiar with the code, how it works, and how epub3 needs to be supported and has time to do it. That is probably a very small pool of people.
|