schooltool-developers team mailing list archive

[Alan Elkner <aelkner@xxxxxxxxx>]

Hey Guys,

I attached some more screenshots reflecting the changes I made to the
section_linkage.html view as well as the three new views, two for
confirmation of extending and unlinking and one for the
link_existiing.html view.  In the section_linkage view, you can now
see that extending or linking backwards in time is now supported.
Also, Ithere is an additional link below the section link for
unlinking the section.

The two confirmation views are self-explanatory.  I understand that we
don't want the user to regret hitting a link that takes an important
action to change the data.  In the case of the link_existing view,
correct me if I'm wrong, but since the user clicks a radio button
followed by clicking the Link button, I assumed that I wouldn't need a
confirmation step for that action, like when a user chooses a teacher
or student to add to a section and then clicks Add.

I also attached a screenshot of the error message the shows when the
user tries to click Link without choosing a section target.  With this
view, as with all the other views, any suggestions for changing
something are welcome.

Also, please review the code changes before finishing for the week so
that I can make any adjustments between now and next Monday's meeting.

Thanks,
Alan



On Mon, Apr 11, 2011 at 9:11 AM, Tom Hoffman <tom.hoffman@xxxxxxxxx> wrote:
> On Mon, Apr 11, 2011 at 3:43 AM, Justas <justas@xxxxxx> wrote:
>> Hey,
>>
>> On 04/11/2011 08:16 AM, Alan Elkner wrote:
>
>>> I added CSS classes to schooltool.css that make the table follow the
>>> guidelines laid out on page 27 of the Ubuntu style guide.  That
>>> includes the dotted line as border-bottom of table cells.  I chose
>>> 220px as column width rather than 140px because it seemed too narrow,
>>> and people will rarely use more than four terms.
>>
>>  Umm.. why 220px?  Just couldn't figure out the reasoning behind this
>> number.
>>
>>  Page 26 also says "Table width: 100%. Table should use the whole width of
>> the content area."  This of course works pretty well when your content area
>> is 544px (as in the guidelines), and may look quirky when it is whole page
>> width, like we have now.  So no objections, just curious.
>
> Given that there could be an arbitrarily large number of terms, making
> the page arbitrarily wide seems better than allowing the columns to
> become arbitrarily narrow.
>
>>  As a compromise, maybe we could have "link existing section" in all
>> unlinked terms, and "extend to term" only in terms after the last linked
>> one?  Get the best of both worlds - soft hint what user should do +
>> possibility to fix mistakes.
>
> That would probably be best.  Also, maybe an "unlink" option too?
>
>>  I'd also like if ExtendTermView had a confirmation button.  In my
>> experience, links that create content without confirmation bite users hard
>> (in javascripty implementations you usually have to use at least two mouse
>> clicks, see assigning a developer to a bug in Launchpad).
>
> Yes, we probably should.
>
> --Tom
>
> _______________________________________________
> Mailing list: https://launchpad.net/~schooltool-developers
> Post to     : schooltool-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~schooltool-developers
> More help   : https://help.launchpad.net/ListHelp
>

Attachment: section_linkage.png
Description: PNG image

Attachment: extend.png
Description: PNG image

Attachment: unlink_section.png
Description: PNG image

Attachment: link_existing.png
Description: PNG image

Attachment: link_error.png
Description: PNG image