<div dir="ltr">Yes, I think we need one single document for all developer guidelines, and I think the Developer's Handbook is the way to go. I think I can highlight the problem by confessing that I've never even seen ( or least didn't remember ) that Interface Patterns page before! We need a single source for developer rules and regulations simply so they don't get lost in the shuffle. Basically, if there is a rule or guideline that should affect how Koha developers plan and write their code, it should be in the Developer's Handbook<div><br></div><div>Kyle</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><a href="https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB" target="_blank"><img src="http://widgets.ch-or.us/badge/convio/cff/4715/2706639"></a><br></div><div><br></div><div><a href="http://www.kylehall.info" target="_blank">http://www.kylehall.info</a><br>ByWater Solutions ( <a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a> )<br>Meadville Public Library ( <a href="http://www.meadvillelibrary.org" target="_blank">http://www.meadvillelibrary.org</a> )<br>Crawford County Federated Library System ( <a href="http://www.ccfls.org" target="_blank">http://www.ccfls.org</a> )<br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Jun 1, 2016 at 2:13 AM, Marc Véron <span dir="ltr"><<a href="mailto:veron@veron.ch" target="_blank">veron@veron.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>+1 for 'Style guidelines' and 'GUI manager'</p>
<p>Regarding the Wiki:<br>
<a href="https://wiki.koha-community.org/wiki/Interface_patterns" target="_blank">https://wiki.koha-community.org/wiki/Interface_patterns</a><br>
<a href="https://wiki.koha-community.org/wiki/Developers_Handbook" target="_blank">https://wiki.koha-community.org/wiki/Developers_Handbook</a> (1.2 User
Interface)</p>
<p>Should this be consolidated in one document?<span class="HOEnZb"><font color="#888888"><br>
</font></span></p><span class="HOEnZb"><font color="#888888">
<p>Marc<br>
</p></font></span><div><div class="h5">
<br>
<div>Am 01.06.2016 um 02:43 schrieb Kyle
Hall:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I think you've summarized everything nicely. If
Owen were interested in taking some official mantel I would not
be opposed ; )
<div><br>
</div>
<div>I think we need to focus on expediency and uniformity
primarily. I think we basically have those two things, but
they could both be improved. I would be more than happy to
work on adding a UI guidelines section to the wiki. For those
interested, here is what I've done so far: <a href="https://wiki.koha-community.org/wiki/Developers_Handbook" target="_blank"></a><a href="https://wiki.koha-community.org/wiki/Developers_Handbook" target="_blank">https://wiki.koha-community.org/wiki/Developers_Handbook</a></div>
<div><br>
</div>
<div>It's a bit rough now because it's really guideline-centric,
but I think over time it will come into its own quite nicely.
Constructive criticism is welcome!<br>
<div><br>
</div>
<div>Kyle</div>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div><a href="https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB" target="_blank"><img src="http://widgets.ch-or.us/badge/convio/cff/4715/2706639"></a><br>
</div>
<div><br>
</div>
<div><a href="http://www.kylehall.info" target="_blank">http://www.kylehall.info</a><br>
ByWater Solutions ( <a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a>
)<br>
Meadville Public Library ( <a href="http://www.meadvillelibrary.org" target="_blank"></a><a href="http://www.meadvillelibrary.org" target="_blank">http://www.meadvillelibrary.org</a>
)<br>
Crawford County Federated Library System ( <a href="http://www.ccfls.org" target="_blank"></a><a href="http://www.ccfls.org" target="_blank">http://www.ccfls.org</a> )<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Tue, May 31, 2016 at 5:26 PM, Katrin
<span dir="ltr"><<a href="mailto:katrin.fischer.83@web.de" target="_blank">katrin.fischer.83@web.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> I like the idea of
having a role like 'GUI manager' and also the idea of
having style guidelines for the interfaces. Actually, I
think. we already have both of those, as Owen has been
working on writing documentation about existing patterns
on the wiki.<br>
<br>
I am not in favor of approving every change that would
change the screenshots, as that would make the clean-up
work much harder, that Owen, Aleisha and others have done
recently. For bigger changes I'd try sending links to
screenshots/bug reports to the mailing list to get some
opinions - if there is no clear direction, we can still
schedule an official discussion/vote at a meeting.<span><font color="#888888"><br>
<br>
Katrin</font></span>
<div>
<div><br>
<br>
<div>On 31.05.2016 23:54, Kyle Hall wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">Love it! I'd say this is a much better
idea!</p>
<p dir="ltr">Kyle</p>
<p dir="ltr">Sent from my phone. Please excuse my
brevity.</p>
<div class="gmail_quote">On May 31, 2016 4:25 PM,
"Eric Bégin" <<a href="mailto:eric.begin@inlibro.com" target="_blank">eric.begin@inlibro.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <font face="Verdana">I would rather have a
Interface guideline the same way we have
coding guidelines.<br>
<br>
I'm pretty sure that there are some UX
design patterns available somewhere.<br>
<br>
If we would like to have a rules, I would
suggest that something that changes the
screenshot used in the user documentation
should be approved, especially when it
doesn't add features.<br>
<br>
Eric<br>
</font><br>
<div>On 2016-05-31 15:49, Kyle Hall wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">I'm concerned that we are going
down a road where every patch submitted to
the Koha project will end up requiring a
community vote. I think it would be more
reasonable and efficient to add a
community UI manager role to the project.
Someone who is empowered to make executive
decisions on this matter. Either that or
accept that the way team rules on this
matter. The community votes them in after
all!</p>
<p dir="ltr">Kyle </p>
<p dir="ltr">Sent from my phone. Please
excuse my brevity.</p>
<div class="gmail_quote">On May 31, 2016
3:32 PM, "Christopher Davis" <<a href="mailto:cgdavis@uintah.utah.gov" target="_blank"></a><a href="mailto:cgdavis@uintah.utah.gov" target="_blank">cgdavis@uintah.utah.gov</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Owen,<br>
<br>
I think that Koha users should voice
their opinion/votes as that the<br>
Koha software, more or less, belongs to
them. Now, what vehicle should<br>
we use to collect everyone's
opinion/vote (like Survey Monkey, Google<br>
forms, IRC voting, etc.) and should
there be a committee formed for<br>
this purpose? Maybe decisions such as
this one should be voted on<br>
during Koha Devl IRC meetings?<br>
<br>
My $0.02 worth,<br>
<br>
Christopher Davis, MLS<br>
Systems & E-Services Librarian<br>
Uintah County Library<br>
<a href="mailto:cgdavis@uintah.utah.gov" target="_blank">cgdavis@uintah.utah.gov</a><br>
<a href="tel:%28435%29%20789-0091%20ext.261" value="+14357890091" target="_blank">(435)
789-0091 ext.261</a><br>
<a href="http://uintahlibrary.org" rel="noreferrer" target="_blank">uintahlibrary.org</a><br>
<a href="http://basinlibraries.org" rel="noreferrer" target="_blank">basinlibraries.org</a><br>
<a href="http://facebook.com/uintahcountylibrary" rel="noreferrer" target="_blank">facebook.com/uintahcountylibrary</a><br>
<a href="http://instagram.com/uintahcountylibrary" rel="noreferrer" target="_blank">instagram.com/uintahcountylibrary</a><br>
<br>
<br>
On Tue, May 31, 2016 at 1:01 PM, Owen
Leonard <<a href="mailto:oleonard@myacpl.org" target="_blank">oleonard@myacpl.org</a>>
wrote:<br>
>> Could the new features which
you are proposing be optional?<br>
><br>
> They're not really new features,
they're just changes to the way<br>
> existing features look. We can't
build options for every change we<br>
> want to make to the interface. We
need to make educated choices about<br>
> what we think is the best way for
things to work. We may not always<br>
> get it right, but it's our job to
make the choice.<br>
><br>
> -- Owen<br>
><br>
> --<br>
> Web Developer<br>
> Athens County Public Libraries<br>
> <a href="http://www.myacpl.org" rel="noreferrer" target="_blank">http://www.myacpl.org</a><br>
>
_______________________________________________<br>
> Koha-devel mailing list<br>
> <a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>
> <a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
> website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank"></a><a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a><br>
> git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
> bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Koha-devel mailing list
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a>
git : <a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a>
bugs : <a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Koha-devel mailing list
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a>
git : <a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a>
bugs : <a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Koha-devel mailing list
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a>
git : <a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a>
bugs : <a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br></blockquote></div><br></div>