New Sigil development blog

[Valloric]

Originally Posted by KevinH

The issue is that the ui will be slow until I cut up the one large xhtml file into smaller pieces. So my question is how do you envision the ui responding to the insertion of a Sigil Chapter Break tag?

1. Will it immediately split the file and then "two separate files" will show up in the sidebar on the left? Will you then handle on the fly, updating links, tocs, spine, entries, etc? That might be hard to do but that may be what you have in mind.

This first option. It will be hard to do, but as you've said, the other option is not user-friendly.

[Valloric]

The longest post I've written for the blog is now online. It's fairly important since I'm talking about Sigil's new long-term focus. Anyone interested should read it.

[Guns4Hire]

Hey great to see some of the new developments you are working on.

[Valloric]

I just posted a detailed analysis of the loading process and why it's taking so long in 0.1.x. I also present how this has been improved in the upcoming 0.2.0 version. The post cites hard numbers so you can compare the two.

Anyone interested in Sigil's performance should check it out.

[Godzil]

Thanks valoric for all of your dev!

[abdul_ms]

Dear Valloric,

I have an question.

I need to use my own TOC which i used in the epub, but whenever i update the epub in the sigil(without editing the TOC), it removes the TOC from the epub file(I have not used heading tag for TOC).

How can i retain the TOC without using the heading tag.

Please reply.

Thanks,
Abdul MS

[Valloric]

Originally Posted by abdul_ms

How can i retain the TOC without using the heading tag.

Currently, you have to use the heading tags since the original NCX file is not preserved. Original NCX preservation is a planned feature.

[abdul_ms]

Dear Valloric,

Thanks for the reply.

I will be very happy, if the patches come soon.

Thanks,
Abdul MS

[arg]

Originally Posted by Valloric

Currently, you have to use the heading tags since the original NCX file is not preserved. Original NCX preservation is a planned feature.

I'm sure there's a way around this but the restriction creating TOC entries from heading tags is extremely inconvenient: it changes fonts I don't want changed; I want to link to images which have no text associated with them; I want to use different text to the actual header (yes i can edit the ncx directly but it's a pain). At worst i'd like a nice little 'Insert TOC Entry' with a dialog to label the entry.

Thanks

[theducks]

Originally Posted by arg

I'm sure there's a way around this but the restriction creating TOC entries from heading tags is extremely inconvenient: it changes fonts I don't want changed; I want to link to images which have no text associated with them; I want to use different text to the actual header (yes i can edit the ncx directly but it's a pain). At worst i'd like a nice little 'Insert TOC Entry' with a dialog to label the entry.

Thanks

You CAN write a style for any H# tag that appears just as it was text... including using the standard paragraph text style. That style must be contain all the attributes that normally get used in a H# tag.


<h3 class="calibre2">Chapter 1</h3>
<p class="calibre2">It was a dark and... </p>

can be made to appear visually the same (Not sure Why..But then I am not an Artiste )

[Jellby]

... and if you want the text in the NCX file to be different than in the XHTML, you can use the title attribute. This works for images too:

<h3 title="1. The Beginning">Chapter 1: The Beginning</h3>

<h3 title="Chapter X"><img src="chapter-10.jpg" alt="chapter 10"/></h3>

or so I believe, since I don't use Sigil

[theducks]

Originally Posted by Jellby

... and if you want the text in the NCX file to be different than in the XHTML, you can use the title attribute. This works for images too:

<h3 title="1. The Beginning">Chapter 1: The Beginning</h3>

<h3 title="Chapter X"><img src="chapter-10.jpg" alt="chapter 10"/></h3>

or so I believe, since I don't use Sigil

100% correct (with the Image wrapped in a h tag as shown)

[Thasaidon]

The Sigil Development blog has not been updated for a long time. Any chance of an quick update on how things are going with Sigil v0.6?

From the my haunting the Sigil website it appears that v0.6 will include a hangar load (there is more than a shed load) of new features, bug fixes and updates.

[Dillinquent]

Originally Posted by Thasaidon

The Sigil Development blog has not been updated for a long time. Any chance of an quick update on how things are going with Sigil v0.6?

From the my haunting the Sigil website it appears that v0.6 will include a hangar load (there is more than a shed load) of new features, bug fixes and updates.

Yes, it's all gone quiet over there in the Sigil dev camp! Last full release was 6 months ago.
I have been using Sigil 5.902 (V6 beta) for a while and it has some really useful enhancements but also a lot of really annoying bugs which I'm looking forward to having fixed.

I think the dev team have been spending all their efforts on Calibre, which seems to be updated every other day - <off-topic>its nice to know that Calibre is being actively worked on but a right royal pain that it has to be updated every time you use it.</off-topic>

[DiapDealer]

Originally Posted by Dillinquent

Yes, it's all gone quiet over there in the Sigil dev camp! Last full release was 6 months ago.
I have been using Sigil 5.902 (V6 beta) for a while and it has some really useful enhancements but also a lot of really annoying bugs which I'm looking forward to having fixed.

I think the dev team have been spending all their efforts on Calibre, which seems to be updated every other day - <off-topic>its nice to know that Calibre is being actively worked on but a right royal pain that it has to be updated every time you use it.</off-topic>

A quick look at the Source->Changes section of Sigil's Google Code site shows that multiple commits are happening daily. So while it's fair to say that the devs might not be keeping the general public apprised of exactly what they're working on ... it's quite clear from the active commit log that a lot of work is going on. They're not idle or applying all their efforts elsewhere.