Mobileread
sigil 0.2.0
#1  bobcdy 02-22-2010, 10:58 PM
I just read the Feb 03 post about the upcoming v. 0.2.0; am I interpreting it correctly in that the new version will no longer have a single file with both book and code views, and instead will have numerous files like an unzipped epub and that each one will need to be edited individually?


Bob
Reply 

#2  Valloric 02-23-2010, 07:03 AM
Yes, that's it. The first beta will not have support for search&replace across files, but the final version will.

This tabbed-based approach is better than the single-flow one. When you edit the book, you move from chapter to chapter. Here you'll just move from tab to tab. Also, in a single flow system, if you're looking at chapter 19 and want to edit something in chapter 8, you have to lose your current place, scroll up, find chapter 8, do what you want, then find chapter 19 again.

With tabs, this is all much quicker since each chapter is a separate tab. And if you need to perform some operations on all files, well then you just use S&R and select "Search/replace in all files" (or whatever I end up calling that).

In this new model, you don't lose anything except the slowness and the bugs that come with the single-flow approach.
Reply 

#3  bobcdy 02-23-2010, 04:34 PM
V. 0.2.0 seems like there will be many advantages, chiefly in speed. However, I must admit I appreciate editing an epub like a simple, single html file rather than editing chapter by chapter, etc. It is similar in that respect to working with a mobi file using mobi creator. Having to worry about all the files involved in an epub is a bit daunting to a beginner like me!

Of course I'll try it but I've saved an install file of v. 0.1.9 and will revert back to that if it seems advisable. Although v. 0.1.9 is a bit slow, at least for a text only with one cover image it is not really that much of a problem on my 2.4 gH dual core. I also have access to a 3 gH quad core if necessary. However, if there were many images, tables, etc. in the epub then speed might be a serious impediment to v. 0.1.9.

Anyway, having access to a program like Sigil has certainly helped me learn to create and edit an epub using my own css styles. The only thing I'd really like to see added someday is a log that indicates where and what css and html errors are present in the file.
Bob
Reply 

#4  Valloric 02-23-2010, 04:54 PM
Quote bobcdy
However, I must admit I appreciate editing an epub like a simple, single html file rather than editing chapter by chapter, etc.
Personally, I like that approach too. I has it's downsides, but it's intuitive and simple. Sadly, it's also slow. There are other technical peculiarities with the epub format, Qt framework etc. that make this approach a not-so-great idea.

Quote bobcdy
Of course I'll try it but I've saved an install file of v. 0.1.9 and will revert back to that if it seems advisable.
Actually you don't have to save it. All the older versions of Sigil are up on the site in the "Downloads" tab. Just change "Current downloads" to "All downloads" in the drop-down and click on Search.

Google Code has this policy where they prevent project administrators from removing files from the site after a certain (very short) amount of time, or a certain (single digit) number of downloads. Effectively, when you upload something to GC, it's there for good.

So I couldn't remove the older versions of Sigil even if I wanted to. You will always be able to download them.

Quote bobcdy
Anyway, having access to a program like Sigil has certainly helped me learn to create and edit an epub using my own css styles. The only thing I'd really like to see added someday is a log that indicates where and what css and html errors are present in the file.
Bob
This is currently the highest rated issue on the tracker. It's a huge subproject, so you won't see it for quite some time.
Reply 

#5  bobcdy 02-24-2010, 12:08 AM
Thanks for the info. You've done such a great job with the 0.1.9 that I expect I'll get used to and really like the new version! I suspect it might be more difficult for beginners to use, but then again, perhaps not so.
Bob
Reply 

#6  Shieko 02-24-2010, 12:30 AM
Well I'm quite excited about the release of 0.2.0.

I have no experience with html or xml whatsoever, (though I can clumsily figure stuff out as I change things that already exist) so to find a WYSIWYG editor has been very handy. Have been using it since 0.1.6.

Edit: just figured something mind-numbingly simple out! All good...
Reply 

#7  Valloric 02-24-2010, 11:35 AM
Quote Shieko
Well I'm quite excited about the release of 0.2.0.

I have no experience with html or xml whatsoever, (though I can clumsily figure stuff out as I change things that already exist) so to find a WYSIWYG editor has been very handy.
You really have nothing to worry about. Honestly.

Let's say you don't know (and don't want to know) anything about XHTML, CSS etc. that actually makes up your book. Let's call these technologies magic.

So in 0.1.x, you would open an epub file and do your editing in the Book View, and if you switch to Code View you would see the magic. But you don't care about that so you just remain in Book View. That's fine. The content of the original files that made up the epub are all presented in this one "flow", one screen with a scrollbar and a double red line separates these out (the "chapter break" line).

In 0.2.0, the only thing that changes (from your perspective) is that you don't have one large "flow" anymore, but several. There is no red line demarcating chapters, they are now in separate files. You click on one of these files, and you see the "chapter" displayed in a new tab. Every tab has Book/Split/Code View. You don't care about the magic, so you remain in Book View.

No new knowledge is required from you as the user. You just edit the way you used to before, but now you get to "see" the different "chapters" of the book individually, not all at once.

That's it. You have nothing to be afraid of. The people who know and care about the magic can still work with it (and more effectively), and you get an faster/better/easier workflow since you don't have to scroll around as much.
Reply 

#8  theducks 02-24-2010, 12:39 PM
Quote Valloric
You really have nothing to worry about. Honestly.

Let's say you don't know (and don't want to know) anything about XHTML, CSS etc. that actually makes up your book. Let's call these technologies magic.

So in 0.1.x, you would open an epub file and do your editing in the Book View, and if you switch to Code View you would see the magic. But you don't care about that so you just remain in Book View. That's fine. The content of the original files that made up the epub are all presented in this one "flow", one screen with a scrollbar and a double red line separates these out (the "chapter break" line).

In 0.2.0, the only thing that changes (from your perspective) is that you don't have one large "flow" anymore, but several. There is no red line demarcating chapters, they are now in separate files. You click on one of these files, and you see the "chapter" displayed in a new tab. Every tab has Book/Split/Code View. You don't care about the magic, so you remain in Book View.

No new knowledge is required from you as the user. You just edit the way you used to before, but now you get to "see" the different "chapters" of the book individually, not all at once.

That's it. You have nothing to be afraid of. The people who know and care about the magic can still work with it (and more effectively), and you get an faster/better/easier workflow since you don't have to scroll around as much.
What happens if I make a "Sigil Chapter break" in 2.0? A new tab is generated after the current tab?
Reply 

#9  Valloric 02-24-2010, 02:40 PM
Quote theducks
What happens if I make a "Sigil Chapter break" in 2.0? A new tab is generated after the current tab?
That's what I'm currently working on. It's one of the last features that needs to be done before you see the first beta of 0.2.0 (hopefully in a few days).

What you said is the general idea. But it's remarkably tricky to do while keeping respectable performance. Both tabs would need to render, and I'm trying to avoid it for at least one of them. There are a few other complications as well.
Reply 

#10  gwynevans 02-24-2010, 04:20 PM
Quote Valloric
That's what I'm currently working on. It's one of the last features that needs to be done before you see the first beta of 0.2.0 (hopefully in a few days).

What you said is the general idea. But it's remarkably tricky to do while keeping respectable performance. Both tabs would need to render, and I'm trying to avoid it for at least one of them. There are a few other complications as well.
It's probably not needed, but I'd throw in a caution against premature optimisation, in that this, at least, doesn't sound to be something that'd happen that often (compared with opening the files, etc). Are you sure you're not spending time fixing things that wouldn't really matter - i.e. if both tabs did re-render would it be so bad, especially if it kept the code simpler?
Reply 

  Next »  Last »  (1/2)
Today's Posts | Search this Thread | Login | Register