0.5.902 (0.6.0 beta) avaliable

[jbacelar]

Originally Posted by theducks
I take it that this will re-enable the Sigilsplit button in BV? (The #1 most used feature of BV that I use.)

I'm in the same situation.

I have uploaded the issue 1467 (Chapter Break disabled in view book), and user_none has responded: This is by design because it currently does not work properly.

The truth is that I have never had any problems with this function.

[exaltedwombat]

Can we establish whether, when everything is working to design:

-Chapter Break will work again in Page View
-There will at least be the option to synch cursor position between Page and Code view? (I would find it very inconvenient if this remained broken.)

Thanks.

[meme]

Originally Posted by jbacelar

I'm in the same situation.

I have uploaded the issue 1467 (Chapter Break disabled in view book), and user_none has responded: This is by design because it currently does not work properly.

The truth is that I have never had any problems with this function.

Chapter Break worked fine in 0.5.3, but the major changes for 0.6.0 mean that it no longer works in the Beta.

Originally Posted by exaltedwombat

Can we establish whether, when everything is working to design:

-Chapter Break will work again in Page View
-There will at least be the option to synch cursor position between Page and Code view? (I would find it very inconvenient if this remained broken.)
.

The intention is to get Chapter Break to work again in Book View.

Syncing between Code View and Book View is no longer supported and not planned.

[exaltedwombat]

Originally Posted by meme

The intention is to get Chapter Break to work again in Book View.

That's great!

Syncing between Code View and Book View is no longer supported and not planned.

That's not so great :-( My first reaction is that it's quite a big step backwards. But perhaps I'm missing something. Could you tell me what was the thinking behind this change?

[theducks]

Originally Posted by Danger

And here I always thought they were the same thing. Of course I can't remember what a keyboard said on it 26 years ago when I first was learning DOS 1.0 and I know my keyboard currently says "Enter" but I've always made the assumption that Return/Enter did the same exact thing. Damn now I have to go and change my shortcut as well. Funny it was working just fine right up to the point I read this post and them blammo it just stopped working for me.
......

Sorry theducks. It's early morning here and I just couldn't resist

I have been to your town. There is this Whirlpool there that tried to eat my dad boat

Windows enter is CRLF where there is CR or LF on ASCII Terminals (and other OS). Ducks goes back BEFORE MSDOS.

[JoHunt]

Originally Posted by meme

There is no syncing of the cursor between views anymore.

The plan is to leave the cursor where you left it in the specific view (if possible). So if you edit in CV and then switch to BV and move around, when you switch to CV again your cursor should be where you left it.

Just reading through this again. Does no cursor syncing mean that I have to actually search for my cursor position from the top (or bottom) of the document every time I want to switch between code/book view? Or something else?

If it's the former, as much as I like the new features of 0.6 and unless I've misunderstood this issue, I'm sticking with Sigil 0.5.3, which allows me to quickly make and check changes between views.

[exaltedwombat]

Originally Posted by joehunt

Just reading through this again. Does no cursor syncing mean that I have to actually search for my cursor position from the top (or bottom) of the document every time I want to switch between code/book view? Or something else?

If it's the former, as much as I like the new features of 0.6 and unless I've misunderstood this issue, I'm sticking with Sigil 0.5.3, which allows me to quickly make and check changes between views.

That's what's worrying me too. When I see a problem in Book view that requires code-level correction, I highlight the offending section and press F11. I'm immediately directed to the relevant code. I can't see much point in being taken to the PREVIOUS bit of code I'd worked on!

This wouldn't be a showstopper preventing me from using 0.6 - some of the other features seem excellent! But it would certainly seem an inconvenience.

The inline TOC feature is a nice touch. It's essential to have this when publishing on Amazon and using the "Look inside" feature. However much, or little, of the book you choose to reveal, it's surely essential to provide a Contents page as an overview. No longer having to use an external application to construct one is very helpful. The stylesheet linker will be a boon to those of us who don't ALWAYS plan ahead fully before splitting into chapters! And the hyperlink support looks very promising.

But would it be impossible to give us back positioning sync between the two views?

[soulafein]

Beta Linux please on my laptop Linux version is much more stable and fast

[elibrarian]

Originally Posted by exaltedwombat

But would it be impossible to give us back positioning sync between the two views?

One could stick a line of

{ name: 'document', items: ['Source'] },

to get a menuitem, that will allow you to edit the sourcecode in CKEditor directly.

That will probably result in other problems ...

in the CKEditors config.js (on Windows it seems, that you have to edit the original config.js - sticking a ckeditor_config.js in C:\Users\USERNAME\AppData\Local\sigil-ebook\sigil\ just give you CKEditor's default menu, whatever you do put in it (haven't experimented much).

Anyway, the direction, Sigil is taking presently compells me to stick with 5.3. The CKEditor may not be so good an idea after all? Seems to be creating more problems than the opposite ...

Regards

Kim

[DiapDealer]

Beta Linux please on my laptop Linux version is much more stable and fast

You'll need to build the Linux beta version from source if you want to try it.

[mesquite]

Originally Posted by meme

Chapter Break worked fine in 0.5.3, but the major changes for 0.6.0 mean that it no longer works in the Beta.

So a suggestion would be to digress back to 0.5.3 then?

Has there been an explanation for why say a title page image will disappear when editing? Like I will open a book and as standard, it will open with titlepage.xhtml as the first portion open but it won't display the cover image.

I might have missed it going through 8 pages of the first beta thread.

[Toxaris]

The complete BookView has been rewritten due to a lot of issues with it. As a result, certain things don't work anymore, either by design or due to being a beta.

[Jabby]

Originally Posted by elibrarian

Anyway, the direction, Sigil is taking presently compells me to stick with 5.3. The CKEditor may not be so good an idea after all? Seems to be creating more problems than the opposite ...

I have to agree with you on this.

If it becomes a choice between this editor and BV/CV cursor sync my vote would be to pitch the editor. Having to search for your place every time you switch between CV and/or BV is too time consuming and these switches are needed many, many times in the creation or editing of a book.

Regards - John

[exaltedwombat]

Originally Posted by Jabby

I have to agree with you on this.

If it becomes a choice between this editor and BV/CV cursor sync my vote would be to pitch the editor. Having to search for your place every time you switch between CV and/or BV is too time consuming and these switches are needed many, many times in the creation or editing of a book.

Regards - John

I guess there must be over-riding advantages in the new editor that made the programmers decide it was worth ditching cursor synch between views? Are they discussed anywhere?

[DiapDealer]

Originally Posted by Jabby

Having to search for your place every time you switch between CV and/or BV is too time consuming and these switches are needed many, many times in the creation or editing of a book.

I realize I probably don't represent the majority of Sigil users, but it's important to keep in perspective that different people use it differently. I don't really use Book View for much of anything—Split View, not at all—so all this talk of syncing between the views is mostly lost on me. But I accept the fact that it seems to be important to others.