<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi all<br>
</p>
<p>I agree with Dave. The default setting being as it is means that
less computer-savvy worship leaders still send me useful orders of
service, even if they've added a new song or image. Making this
not the default, even if it was still a separate option on the
file menu, would cause us a lot of frustration and undermine the
perception of OpenLP as a solution that 'just works'. You only
have to wreck one service before users will want to switch. Disk
space is cheap these days, and bandwidth is plentiful - so my plea
is to leave the defaults as they are, with great thanksgiving for
the foresight of the developers who set it up this way.</p>
<p>Grace and peace</p>
<p>Adam<br>
</p>
<br>
<div class="moz-cite-prefix">On 30/11/17 11:40, David Warnock wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANHtGrL3wgz5ji0xyBxkEtPf1PORQYLCPpqnsmuG2f5G9-NZ8w@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>
<div>Hi,<br>
<br>
</div>
We have a team of about 6 people who prepare services. All
services are always prepared at their homes and this is a
key selling point for OpenLP.<br>
<br>
</div>
Please do not change this behaviour! I use a team whose
computer skills would not be up to copying files around
manually. The chances of ending up without a complete
service would be high. We do not have all the custom slides,
images or videos on the Church Computer.<br>
<br>
</div>
So again please don't change this.<br>
<br>
</div>
Dave<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 30 November 2017 at 08:43, Philip
Ridout <span dir="ltr"><<a
href="mailto:phill.ridout@gmail.com" target="_blank"
moz-do-not-send="true">phill.ridout@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I have been looking at how OpenLP saves and
loads its service files as part of my pathlib and cross
platform file handling refactors. I would like to make a
few changes.
<div><br>
</div>
<div>Currently:</div>
<div>OpenLP defaults to packing all the service item files
in to a zip file, the actual service is saved as a json
in a file that is also packaged. There is an option of
saving a 'lite' service, which is just the json file
zipped.</div>
<div><br>
</div>
<div>I have the following issues with the current system:</div>
<div>The default save method (packaged) is very slow if
lots of / large files are used.</div>
<div>Packaging the json file of a 'lite' service in to a
zip file seems a bit pointless.</div>
<div>Its not very obvious that there is a choice between
packaged and light</div>
<div><br>
</div>
<div>My proposed solution:</div>
<div>Packaging files in a zip file is great if somebody
prepares a service at home. However, in my experience
(10 years) this has never happened! Lets make the 'lite'
option the default, this would make OpenLP faster saving
files which are not going to be transported.</div>
<div>Lets make the option to package a service file more
visible, and place a separate menu item for it next to
save in the file menu.</div>
<div>When saving a 'lite' service, lets just save the json
in a text file and not worry about zipping it up. While
were at it, it might make sense to change the extension.
'.olp'?</div>
<div><br>
</div>
<div>Compatability:</div>
<div>OpenLP 3.0 will continue to be able to open
'packaged' and 'lite' files saved in 2.2 and later.</div>
<div>Packaged files saved with 3.0 will be able to be
opened in 2.4.x, The 'new lite' (.olp?) files will not.</div>
<div>Some users may be caught out by the change to saving
a lite file by default, so when they use the save as
dialog we could display a message box about the changes.</div>
<div><br>
</div>
<div>Are you guys happy with my proposal? Any other ideas
/ suggestions?</div>
<div><br>
</div>
<div>God Bless,</div>
<div>Phill</div>
</div>
<br>
______________________________<wbr>_________________<br>
openlp-dev mailing list<br>
<a href="mailto:openlp-dev@openlp.io" moz-do-not-send="true">openlp-dev@openlp.io</a><br>
<a
href="https://lists.openlp.io/mailman/listinfo/openlp-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openlp.io/<wbr>mailman/listinfo/openlp-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Dave Warnock: <a
href="http://42.blogs.warnock.me.uk" target="_blank"
moz-do-not-send="true">http://42.blogs.warnock.me.uk</a>
<div>Cycling Blog: <a href="http://42bikes.warnock.me.uk"
target="_blank" moz-do-not-send="true">http://42bikes.warnock.me.uk</a></div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
openlp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:openlp-dev@openlp.io">openlp-dev@openlp.io</a>
<a class="moz-txt-link-freetext" href="https://lists.openlp.io/mailman/listinfo/openlp-dev">https://lists.openlp.io/mailman/listinfo/openlp-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>