<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>On a separate note I would like to suggest adding some videos of how digiKam works.</div><div>If something simple will do (record screen, add some text comments and background music) I can help with that.</div><div>I guess we would need to determine the top 5-10 features first.</div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Pat David <patdavid@gmail.com> </div><div>Date: 2017-04-01 6:56 AM (GMT-07:00) </div><div>To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org> </div><div>Subject: Re: New digikam website source available from KDE's git server </div><div><br></div></div><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 31, 2017 at 11:19 PM Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">On the download section, there are too much text to read to find the right version.</div></blockquote><div><br></div><div>Agreed! This is one of the pages I was hoping to rewrite soon to be a little clearer. I had written some small OS detection script I use on <a href="http://www.gimp.org">www.gimp.org</a> to show the most likely relevant download to users when they visit the page - I could possibly re-use that here if you wanted.</div><div><br></div><div>Either way, the page is on the to-do list to re-write to be more direct and clear. :)</div><div><br></div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">To resume :</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">- screenshots stored in local or not ?</div><div class="gmail_msg">- If stored in local (git), this is acceptable by KDE team to overload the repository with this kind of huge data ?</div></div></blockquote></div></div></div></blockquote></div><div><br></div><div>Re: Screenshots</div><div><br></div><div>I know that historically you've hosted your photos on Flickr. This is fine, but I would personally suggest hosting them locally if possible.<br></div><div><br></div><div>The reason is that if Flickr, for any reason, goes dark - then you'll have a huge amount of dead images across your site. I'd hate for that to happen! Even worse, if the images aren't stored anywhere else then there's a chance you'll lose the mapping of what those images should be. :(</div><div><br></div><div>In git, we'll have them and won't have to worry about it (and we don't have to worry about a database not liking them on the backend anymore).</div><div><br></div><div>I don't think there's a _huge_ amount of files/sizes to worry about, but I guess it's up to Ben to let us know if that'll be ok.</div><div><br></div><div>pat</div></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr"><a href="https://patdavid.net">https://patdavid.net</a><br>GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC</div></div>
</body></html>