I am really glad that there is so much to love about Logos 7 because the sermon editor is a poor excuse for a helpful tool. I can do things faster with powerpoint and Word.
Faithlife are working on some enhancements to the Sermon Editor - some currently in beta testing.
Are there any specific enhancements you would like to see?
I can do things faster with powerpoint and Word.
Can't we all do things faster in familiar tools than in new tools? Putting that aside and recognizing that the sermon editor has some integration features that PowerPoint and Word do not, what would you want in the sermon editor to make it worth your time to learn?
I can't even find the sermon editor. I have Logos Now, and see sermon starter, which has a different icon than the video shows for sermon editor. It also has different tabs/panels, etc. How do you find it?
Len
I can't even find the sermon editor. I have Logos Now, and see sermon starter, which has a different icon than the video shows for sermon editor. It also has different tabs/panels, etc. How do you find it? Len
Try poking about here...
and here
Logos 7 sermon editor is a poor excuse for a helpful tool. I can do things faster with powerpoint and Word.
Agreed. Or Keynote.
And where in the fine print does it mention this is an online only tool for generating output. When backgrounds for slides are configured they are not pulled down off the internet and stored locally on you computer so you have to be online to export the sermon slides.
Thanks Mike. This was helpful.
Graham Criddle,
Thanks for the response. Here's my wish list so far....
1. Make sure the term is consistent. Is it "sermon editor" or what is currently listed as "sermon." 2. If this is a top feature/function, place it in a more prominent place. It is not actually a document, but that is where it is listed. If I want to start a fresh sermon editor, I don't consider it a currently existing document.
3. The copy & paste functions are very glitchy and not consistent. Sometimes it automatically creates a slide. Other times it doesn't. I don't know the logic, only that I do the same actions on my end.
4. The font sizing needs to be adjusted to fit a typical screen display for an audience. The default mode is for someone who is nearly blind, and takes 12 -15 verses and parses them int o 9 slides.
5. Somehow, please, please, please, make it possible to copy clippings and notes with their original sources into the sermon. The sermon starter guide is "nice" but isn't a place to keep relevant findings. Neither is the sermon editor as I will only use a few citations. But when I copy and paste from Clippings and Notes, all citations are lost. Unless I click on the link, which is an extra step and opens yet another panel (my subconscious mind freaks out thinking "NOOO, IF ANOTHER PANEL OPENS, I'M GONNA NEED A STRAIGHT JACKET!" LOL).
I'm sure I'll have more suggestions, perhaps on how the outline, bold print, different fonts function, but at this point, I have given up on every attempt to use it. I keep encountering glitches, and at that point in my preparation, I just don't have time to mess around. This is also a reason why I think Logos needs to keep working on this- it can save us a LOT of time come end of the week- when we're doing things like powerpoint, and copying things without wanting to type source citations.
Thanks a bunch. Oh, do you work for Logos? If not, I think I just wasted my time!
1. Make sure the term is consistent. Is it "sermon editor" or what is currently listed as "sermon."
There is a "sermon editor" which is used to create "sermon documents"
2. If this is a top feature/function, place it in a more prominent place. It is not actually a document, but that is where it is listed. If I want to start a fresh sermon editor, I don't consider it a currently existing document.
The results of using the sermon editor is to create a sermon document - in a similar way to using the functionality of creating a new Reading Plan creates a Reading Plan document. So, from an architectural perspective it makes sense - but I agree there are some usability questions that need to be looked at
In general, copying something into a blank line will create associated slides - copying into a line that already contains text will not. Are you seeing behaviour different to that?
I agree there ought to be some controls in this area - I believe it is being worked on
5. Somehow, please, please, please, make it possible to copy clippings and notes with their original sources into the sermon.
That would be nice but - as in my response to your other post on this https://community.logos.com/forums/p/133507/867564.aspx#867564 - it would be inconsistent with how the application currently works in other areas. Certainly something to be considered.
Oh, do you work for Logos? If not, I think I just wasted my time!
No I don't work for Logos - I'm just a fellow-user of the software.
But hopefully you won't find this is time wasted. The forums provides an opportunity - among other things - to explore ideas and ways of working and discussions are often picked up and commented on by Faithlife employees.
Thanks Graham!
Can't we all do things faster in familiar tools than in new tools?
True. And I can testify that after a couple of months of using the sermon editor I'm now much more proficient than at first.
I do agree that there are many things that need improvement, but I'm confident that Faithlife are listening and will continue to develop a really excellent tool to help those who preach.
I've found the same, and am appreciating the benefits of not having to turn my sermons into Personal Books to get them into Logos, as well as the ease of getting Bible passages into sermons and having at least the basics of a Powerpoint display produced as a by-product of my sermon preparation. I grant that there are some features that are underdeveloped, but am encouraged that each new release of Logos every six weeks seems to improve, tidy up and add more functionality to this feature. I think it was taken out of the oven and put on the table before it was fully cooked, but can see it becoming increasingly useful as time passes. I also appreciate the way in which requests from users are being built into the product release by release.
