[OPEN-ILS-DEV] GSoC Proposition

[Joseph Lewis]

I've added the suggestion in to the time-line, the updated version is at the
same URL.

Joe

--
Public Key: [0xF8462E1593141C16]<http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF8462E1593141C16>

Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system
which can be mass-produced by unskilled labor.
- NASA



On Wed, Mar 30, 2011 at 11:19 AM, Jason Boyer <jasonb at myjclibrary.org>wrote:

> I do like the idea of a "see also" style pointer (er, link) to related
> groups or settings. That might satisfy both the labeling strategy and
> keeping settings within a single main group, as long as it's not
> overcrowded.
>
> Jason
>
> --
> Jason Boyer, IT Specialist
> Jackson County Public Library
> 303 W Second St
> Seymour, IN 47274
>
> jasonb at myjclibrary.org
> p (812) 522-3412 ext. 227
> f (812) 522-5456
>
>
> On Wed, Mar 30, 2011 at 11:51 AM, Joseph Lewis <joehms22 at gmail.com> wrote:
>
>> I can see that this might be useful if settings pages were generated
>> on-demand, then "recipes" could be created where you told the software which
>> settings to show to the user; but there is another merit to the tagging from
>> what I see: hints could be given based upon relationships, like the "you
>> might also be interested in" that now shows up in Windows control-panels.
>> Another possible feature is if users are changing many tags in a row that
>> have a similarity the program could check if they might have "missed" one by
>> mistake.
>>
>> Under the current structure it would still probably make sense to have a
>> top down approach with logical sectioning, but labels could add some extra
>> aids to the developers.
>>
>> What do you think?
>>
>> - Joe
>>
>>
>> --
>> Public Key: [0xF8462E1593141C16]<http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF8462E1593141C16>
>>
>> Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system
>> which can be mass-produced by unskilled labor.
>> - NASA
>>
>>
>>
>> On Wed, Mar 30, 2011 at 8:47 AM, Jason Boyer <jasonb at myjclibrary.org>wrote:
>>
>>> Do you mean that the same setting might be visible in more than one place
>>> on the settings page? That seems like it would get confusing fast,
>>> especially if changing it in one location didn't immediately update all of
>>> the other instances. I think having a "settings group" field would be
>>> helpful for building a better UI, but restricting a setting to 1 group would
>>> be easier for admins (who are not necessarily software developers or
>>> database admins!) to use, and for software devs/db admins to implement.
>>> That's the way the labels work in Gmail, and precious few people here
>>> understand how that all works. (And Google did eventually have to add a
>>> "Move To" button for users, which just dumbs them back down to simple
>>> 1-label-per-email "folders" ...)
>>>
>>> Jason
>>>
>>> --
>>> Jason Boyer, IT Specialist
>>> Jackson County Public Library
>>> 303 W Second St
>>> Seymour, IN 47274
>>>
>>> jasonb at myjclibrary.org
>>> p (812) 522-3412 ext. 227
>>> f (812) 522-5456
>>>
>>>
>>>
>>> On Wed, Mar 30, 2011 at 10:15 AM, Mike Rylander <mrylander at gmail.com>wrote:
>>>
>>>> On Tue, Mar 29, 2011 at 4:31 PM, Joseph Lewis <joehms22 at gmail.com>
>>>> wrote:
>>>> > Hello everyone,
>>>> >
>>>> > I have posted a draft here of what I plan to do (if I'm accepted)
>>>> during
>>>> > GSoC for you all, if you could reply with some comments that would be
>>>> great:
>>>> >
>>>> https://docs.google.com/document/pub?id=1z-LX9O9BDzMZwuwMDz6dZ_7CjdRuXUmIlwU9qExrwJI
>>>> >
>>>>
>>>> Thanks, Joe.
>>>>
>>>> A further idea that is perhaps worth evaluation is the addition of
>>>> "tagging" to settings for the purpose of grouping them into logical
>>>> sets.  This would be a many-to-many relationship as opposed to a
>>>> simple many-to-one grouping as settings may be usefully viewed in more
>>>> than one context.  This would increase the complexity of the task by
>>>> involving more layers (in the least, database changes) and therefore
>>>> may be less appropriate for a GSoC project (IMO, it's still quite
>>>> do-able), but would pay large dividends in terms of flexibility and
>>>> future maintenance if the UI was driven primarily by settings-grouping
>>>> tags.
>>>>
>>>> --
>>>> Mike Rylander
>>>>  | VP, Research and Design
>>>>  | Equinox Software, Inc. / Your Library's Guide to Open Source
>>>>  | phone:  1-877-OPEN-ILS (673-6457)
>>>>  | email:  miker at esilibrary.com
>>>>  | web:  http://www.esilibrary.com
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20110330/4b1f678b/attachment.htm