[OPEN-ILS-DEV] Make craftsman the default catalogue skin in...Evergreen 1.6?
Cynthia Williamson
crwbookgirl at gmail.com
Sat May 30 07:02:46 EDT 2009
We'd love to see Craftsman as the default OPAC - it is indeed very good
looking. Frankly anything will look better than what we're currently using
(old catalogue of the mythical beast variety) but I'd love to impress
students and faculty with Craftsman in September! We'd love to go live with
1.6 - if we can do it by the end of June. Being a college library that
gives us the quietish time in July and August to get used to everything and
to help you folks find any bugs.
Cheers, Cynthia
Mohawk College.
On Fri, May 29, 2009 at 12:00 PM, <
open-ils-dev-request at list.georgialibraries.org> wrote:
> Send Open-ils-dev mailing list submissions to
> open-ils-dev at list.georgialibraries.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://libmail.georgialibraries.org/mailman/listinfo/open-ils-dev
> or, via email, send a message with subject or body 'help' to
> open-ils-dev-request at list.georgialibraries.org
>
> You can reach the person managing the list at
> open-ils-dev-owner at list.georgialibraries.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Open-ils-dev digest..."
>
>
> Today's Topics:
>
> 1. Make craftsman the default catalogue skin in Evergreen 1.6?
> (Dan Scott)
> 2. Fixing the mixed-content warnings in My Account (Dan Scott)
> 3. Re: Make craftsman the default catalogue skin inEvergreen
> 1.6? (Grant Johnson)
> 4. Re: Make craftsman the default catalogueskin inEvergreen 1.6?
> (Grant Johnson)
> 5. Re: Fixing the mixed-content warnings in My Account
> (Mike Rylander)
> 6. Re: Fixing the mixed-content warnings in My Account (Jeff Godin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 28 May 2009 23:50:27 -0400
> From: Dan Scott <denials at gmail.com>
> Subject: [OPEN-ILS-DEV] Make craftsman the default catalogue skin in
> Evergreen 1.6?
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <fbb0d11d0905282050y1454cc6ap3844801949607212 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> How crazy would it be to make craftsman the default skin for the 1.6
> release?
>
> I think that it would make sense for two reasons:
>
> 1) It would put the best face forward for new Evergreen installs.
> First impressions matter.
> 2) It would help us shake out any bugs that might remain in the
> craftsman skin at this point.
>
> I would hate to see the investment in this very nice facelift to the
> catalogue fall by the wayside. I was happy to see that my serials
> display code "just works" with craftsman, but it's visually jarring
> because it uses the legacy skin classes for its styling at the moment.
>
> --
> Dan Scott
> Laurentian University
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 29 May 2009 00:38:57 -0400
> From: Dan Scott <denials at gmail.com>
> Subject: [OPEN-ILS-DEV] Fixing the mixed-content warnings in My
> Account
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <fbb0d11d0905282138x44613b29o4fe8ed98908ea130 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> If I understand correctly, some browsers (hello IE!) throw up warnings
> when patrons enter "My Account" in the OPAC because there are some
> hard-coded HTTP requests mixed in with the HTTPS session. When patrons
> opt to not allow the browser to load mixed content, hilarity (or some
> miserable facsimile thereof) ensues. This is bad. Apaprently things
> are even worse in IE8.
>
> It looks like the mixed content is due to
> Open-ILS/var/web/opac/skin/default/xml/setenv.xml:
>
> setenv.xml:<!--#set var="OILS_BASE"
> value="http://${SERVER_NAME}/${OILS_OPAC_BASE}"-->
> setenv.xml: <!--#set var="OILS_OPAC_JS_HOST"
> value="http://${OILS_OPAC_JS_HOST}"-->
> setenv.xml: <!--#set var="OILS_OPAC_CSS_HOST"
> value="http://${OILS_OPAC_CSS_HOST}"-->
>
> Setting these to the following alleviates the problem:
>
> setenv.xml:<!--#set var="OILS_BASE" value="${OILS_OPAC_BASE}"-->
> setenv.xml: <!--#set var="OILS_OPAC_JS_HOST" value=""-->
> setenv.xml: <!--#set var="OILS_OPAC_CSS_HOST" value=""-->
>
> The win from having a non-scary default configuration seems to, in my
> mind, outweigh the possible balancing of JS and CSS across different
> hosts. Would there be any objection to my merging a commit that resets
> each offending var to a non-scary default value, along with a comment
> that explains what in the wide world of sports is going on?
>
> --
> Dan Scott
> Laurentian University
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 29 May 2009 07:22:13 -0300
> From: "Grant Johnson" <fgjohnson at upei.ca>
> Subject: Re: [OPEN-ILS-DEV] Make craftsman the default catalogue
> skin
> inEvergreen 1.6?
> To: "Evergreen Development Discussion List"
> <open-ils-dev at list.georgialibraries.org>
> Message-ID: <4A1F8D25.5AB7.007F.0 at groupwise.upei.ca>
> Content-Type: text/plain; charset=US-ASCII
>
> If the bug's aren't extraordinary...
> We'd be pleased to use the Craftsman skin (he says without consulting
> anyone else!)
>
> As you say it looks really nice and "just works" with most things.
>
>
>
> F. Grant Johnson
> Systems Coordinator
> Robertson Library
> University of Prince Edward Island
>
>
> >>> On Fri, May 29, 2009 at 12:50 AM, in message
> <fbb0d11d0905282050y1454cc6ap3844801949607212 at mail.gmail.com>, Dan Scott
> <denials at gmail.com> wrote:
> > How crazy would it be to make craftsman the default skin for the 1.6
> release?
> >
> > I think that it would make sense for two reasons:
> >
> > 1) It would put the best face forward for new Evergreen installs.
> > First impressions matter.
> > 2) It would help us shake out any bugs that might remain in the
> > craftsman skin at this point.
> >
> > I would hate to see the investment in this very nice facelift to the
> > catalogue fall by the wayside. I was happy to see that my serials
> > display code "just works" with craftsman, but it's visually jarring
> > because it uses the legacy skin classes for its styling at the moment.
> >
> > --
> > Dan Scott
> > Laurentian University
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 29 May 2009 08:12:02 -0300
> From: "Grant Johnson" <fgjohnson at upei.ca>
> Subject: Re: [OPEN-ILS-DEV] Make craftsman the default catalogueskin
> inEvergreen 1.6?
> To: "Evergreen Development Discussion List"
> <open-ils-dev at list.georgialibraries.org>
> Message-ID: <4A1F98D2.5AB7.007F.0 at groupwise.upei.ca>
> Content-Type: text/plain; charset=US-ASCII
>
> And to help with what we can of course...
>
>
>
> F. Grant Johnson
> Systems Coordinator
> Robertson Library
> University of Prince Edward Island
>
>
> >>> On Fri, May 29, 2009 at 7:22 AM, in message
> <4A1F8D25.5AB7.007F.0 at groupwise.upei.ca>, "Grant Johnson" <
> fgjohnson at upei.ca>
> wrote:
> > If the bug's aren't extraordinary...
> > We'd be pleased to use the Craftsman skin (he says without consulting
> anyone
> > else!)
> >
> > As you say it looks really nice and "just works" with most things.
> >
> >
> >
> > F. Grant Johnson
> > Systems Coordinator
> > Robertson Library
> > University of Prince Edward Island
> >
> >
> >>>> On Fri, May 29, 2009 at 12:50 AM, in message
> > <fbb0d11d0905282050y1454cc6ap3844801949607212 at mail.gmail.com>, Dan Scott
> > <denials at gmail.com> wrote:
> >> How crazy would it be to make craftsman the default skin for the 1.6
> > release?
> >>
> >> I think that it would make sense for two reasons:
> >>
> >> 1) It would put the best face forward for new Evergreen installs.
> >> First impressions matter.
> >> 2) It would help us shake out any bugs that might remain in the
> >> craftsman skin at this point.
> >>
> >> I would hate to see the investment in this very nice facelift to the
> >> catalogue fall by the wayside. I was happy to see that my serials
> >> display code "just works" with craftsman, but it's visually jarring
> >> because it uses the legacy skin classes for its styling at the moment.
> >>
> >> --
> >> Dan Scott
> >> Laurentian University
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 29 May 2009 07:32:02 -0400
> From: Mike Rylander <mrylander at gmail.com>
> Subject: Re: [OPEN-ILS-DEV] Fixing the mixed-content warnings in My
> Account
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <b918cf3d0905290432l45f6fe17sda7fe4d9157a9744 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, May 29, 2009 at 12:38 AM, Dan Scott <denials at gmail.com> wrote:
> > If I understand correctly, some browsers (hello IE!) throw up warnings
> > when patrons enter "My Account" in the OPAC because there are some
> > hard-coded HTTP requests mixed in with the HTTPS session. When patrons
> > opt to not allow the browser to load mixed content, hilarity (or some
> > miserable facsimile thereof) ensues. This is bad. Apaprently things
> > are even worse in IE8.
> >
> > It looks like the mixed content is due to
> > Open-ILS/var/web/opac/skin/default/xml/setenv.xml:
> >
> > setenv.xml:<!--#set var="OILS_BASE"
> > value="http://${SERVER_NAME}/${OILS_OPAC_BASE}"-->
> > setenv.xml: ? ?<!--#set var="OILS_OPAC_JS_HOST"
> > value="http://${OILS_OPAC_JS_HOST}"-->
> > setenv.xml: ? ?<!--#set var="OILS_OPAC_CSS_HOST"
> > value="http://${OILS_OPAC_CSS_HOST}"-->
> >
> > Setting these to the following alleviates the problem:
> >
> > setenv.xml:<!--#set var="OILS_BASE" value="${OILS_OPAC_BASE}"-->
> > setenv.xml: ? ?<!--#set var="OILS_OPAC_JS_HOST" value=""-->
> > setenv.xml: ? ?<!--#set var="OILS_OPAC_CSS_HOST" value=""-->
> >
> > The win from having a non-scary default configuration seems to, in my
> > mind, outweigh the possible balancing of JS and CSS across different
> > hosts. Would there be any objection to my merging a commit that resets
> > each offending var to a non-scary default value, along with a comment
> > that explains what in the wide world of sports is going on?
>
> How about we do that /AND/ supply https: versions of those three,
> having the code that deals with (and makes up) the My OPAC stuff use
> those. Perhaps even make that explicit in the name by putting MYOPAC
> in there:
>
> setenv.xml:<!--#set var="OILS_MYOPAC_BASE"
> value="https://${SERVER_NAME}/${OILS_OPAC_BASE}"-->
> setenv.xml:<!--#set var="OILS_MYOPAC_JS_HOST"
> value="https://${OILS_OPAC_JS_HOST}"-->
> setenv.xml:<!--#set var="OILS_MYOPAC_CSS_HOST"
> value="https://${OILS_OPAC_CSS_HOST}"-->
>
> Then My OPAC is happy in tin-foil browsers, and those sites that need
> a separate content server (at least the 2 largest production sites,
> that I recall OTTOMH) don't have to jump through any more hoops than
> anyone else at upgrade time -- it stays as config settings. Do you
> see any issues with that modification to your plan?
>
> --
> Mike Rylander
> | VP, Research and Design
> | Equinox Software, Inc. / The Evergreen Experts
> | phone: 1-877-OPEN-ILS (673-6457)
> | email: miker at esilibrary.com
> | web: http://www.esilibrary.com
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 29 May 2009 11:10:35 -0400
> From: Jeff Godin <jeff at tcnet.org>
> Subject: Re: [OPEN-ILS-DEV] Fixing the mixed-content warnings in My
> Account
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Message-ID:
> <835ee5a80905290810n72aba787n4a3f8e5f16f3430a at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I had a few discussions with people at eg09 regarding this, and I'm
> glad that Dan brought it up!
>
> Inspired by both ideas in this thread, I tried something else. Seems
> to work here.
>
> The following suggested patch should fix the mixed content warnings
> "out of the box" without breaking sites that use static servers for
> CSS and Javascript.
>
> This sets OILS_PROTOCOL based on the environment variable HTTPS (which
> Apache sets to "on" for https:// requests).
>
> Thus, a page loaded via https:// gets https:// urls, and a page loaded
> via http:// gets http:// urls.
>
> To accommodate sites with static servers that can not support https,
> there's a new OILS_OPAC_STATIC_PROTOCOL variable in eg_vhost.conf
> which can be set to "http" to force JS/CSS to be loaded over http://
> (you'll get the same warnings that you got before).
>
> Not addressed yet: OILS_OPAC_IMAGES_HOST, or Craftsman.
>
> If I'm on the right track here, I'd also like to add the ability for
> sites with static servers that have no https support on the static
> servers to fall back to loading JS/CSS from the https servers -- some
> performance loss, but allows them to avoid the mixed-content warnings
> also.
>
> Feedback? Testing from someone with a static server setup?
>
> -jeff
> -------------- next part --------------
>
> Developer's Certificate of Origin 1.1
>
> By making a contribution to this project, I certify that:
>
> (a) The contribution was created in whole or in part by me and I
> have the right to submit it under the open source license
> indicated in the file; or
>
> (b) The contribution is based upon previous work that, to the best
> of my knowledge, is covered under an appropriate open source
> license and I have the right under that license to submit that
> work with modifications, whether created in whole or in part
> by me, under the same open source license (unless I am
> permitted to submit under a different license), as indicated
> in the file; or
>
> (c) The contribution was provided directly to me by some other
> person who certified (a), (b) or (c) and I have not modified
> it.
>
> (d) I understand and agree that this project and the contribution
> are public and that a record of the contribution (including all
> personal information I submit with it, including my sign-off) is
> maintained indefinitely and may be redistributed consistent with
> this project or the open source license(s) involved.
>
> Signed-off-by: Jeff Godin <jeff at tcnet.org>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: fix-https-mixed-content.diff
> Type: text/x-diff
> Size: 2250 bytes
> Desc: not available
> Url :
> http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090529/9af3b9f5/attachment-0001.diff
>
> End of Open-ils-dev Digest, Vol 38, Issue 23
> ********************************************
>
--
Afoot and light-hearted I take to the open road,
Healthy, free, the world before me,
The long brown path before me leading wherever I choose.
Henceforth I ask not good-fortune, I myself am good-fortune,
Henceforth I whimper no more, postpone no more, need nothing,
Done with indoor complaints, libraries, querulous criticisms,
Strong and content I travel the open road.
Walt Whitman, Song of the Open Road
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090530/afd53ed0/attachment-0001.htm
More information about the Open-ils-dev
mailing list