Uploaded image for project: 'Samigo'
  1. Samigo
  2. SAM-894

Reduce confusion over core, published, inactive by using Javascript tabbed display

    Details

    • Type: Feature Request Feature Request
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0
    • Component/s: Authoring
    • Labels:
      None
    • Previous Issue Keys:

      Description

      The problem we hear from clients: instructors do not understand the difference between core, published, and inactive. Having one screen with the three distinct types of assessment is confusing.

      Additional issue raised by some instructors: the more T&Q is used, the more cluttered the interface becomes. They would like some sort of visual separation to make the assessment categories distinct.

      Proposal: use jQuery UI tabs to separate the three categories into dynamic tabs (no page load).

      Mockup attached. We will submit a patch if there is interest from the Samigo team.

        Gliffy Diagrams

        1. SAM-894-spec.rtf
          0.8 kB
          Jacqueline Mai
        2. SAM-894-v3.patch
          47 kB
          Sam Ottenhoff
        3. SAMigoMainPagePublishedCopies.psd
          791 kB
          Jacqueline Mai
        4. SAMigoMainPageWorkingCopies.psd
          773 kB
          Jacqueline Mai
        1. screenshot-1.jpg
          108 kB
        2. screenshot-2.jpg
          211 kB

          Issue Links

            Activity

            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            Is there a test or dev instance where I could review this proposed change?

            Thanks,
            Jackie
            User Experience Designer
            Stanford University

            Show
            Jacqueline Mai added a comment - Hi Sam, Is there a test or dev instance where I could review this proposed change? Thanks, Jackie User Experience Designer Stanford University
            Hide
            Sam Ottenhoff added a comment -

            Hi Jackie,

            No, this is only a proposed change right now. We have not started development on the modification. We are looking for feedback from you and others to get a sense of whether this modification would be welcome.

            The tabs functionality could be implemented using jQuery UI (instant tab switching, no page loading):

            http://jqueryui.com/demos/tabs/

            If there is interest in this modification, we will setup a development instance for testing.

            Thanks,
            Sam

            Show
            Sam Ottenhoff added a comment - Hi Jackie, No, this is only a proposed change right now. We have not started development on the modification. We are looking for feedback from you and others to get a sense of whether this modification would be welcome. The tabs functionality could be implemented using jQuery UI (instant tab switching, no page loading): http://jqueryui.com/demos/tabs/ If there is interest in this modification, we will setup a development instance for testing. Thanks, Sam
            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            Re-working the main page of T&Q (instructor view) is something that I was planning to work on for SAMigo 2.8 release. Have you begun to put together specifications (form and function) for what you have in mind?

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - Hi Sam, Re-working the main page of T&Q (instructor view) is something that I was planning to work on for SAMigo 2.8 release. Have you begun to put together specifications (form and function) for what you have in mind? Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            Hi Jackie,

            We have no specifications, only a provided, admittedly-rough mockup on the direction we would like to see instructor UI go in based on end-user comments. We are not attempting a radical redesign of the instructor UI; we think large advances in new instructor comprehension could be gained with a few small changes.

            The stated problem we have heard from new users of Sakai is that the concept of Core, Inactive, and Published is confusing. We are attempting to solve that with two primary changes:

            1) Subtle rewording around "Core" and "Assessment Types".

            2) Visually breaking up the sections (proposed with JavaScript tabs)

            Other issues that our mockup addresses:

            3) The instructor dropdown hides the possibilities of the tool.

            We would like to help in this effort. Please let us know what you would like from us as a next step, and we will do our best.

            --Sam

            Show
            Sam Ottenhoff added a comment - Hi Jackie, We have no specifications, only a provided, admittedly-rough mockup on the direction we would like to see instructor UI go in based on end-user comments. We are not attempting a radical redesign of the instructor UI; we think large advances in new instructor comprehension could be gained with a few small changes. The stated problem we have heard from new users of Sakai is that the concept of Core, Inactive, and Published is confusing. We are attempting to solve that with two primary changes: 1) Subtle rewording around "Core" and "Assessment Types". 2) Visually breaking up the sections (proposed with JavaScript tabs) Other issues that our mockup addresses: 3) The instructor dropdown hides the possibilities of the tool. We would like to help in this effort. Please let us know what you would like from us as a next step, and we will do our best. --Sam
            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            The main problem we hear over and over from our users is that it is confusing to have 3 lists (Pending, Published -Active, Published-Inactive) and the same assessment showing up in more than one list. Confusion tends to arise when people forget which assessment they last made changes to - was it under 'Core' or 'Published'? I myself have been frustrated by this when I had to verify something against a 'core' assessment but mistakenly did it against the published version.

            Ideally, users should see only one list and only one copy/version of an assessment. My instinct tells me that this is the way to go although I have yet to fully flesh out the details and I've yet to check with our developers to find out what the implications would be at the pipes and plumbing level.

            Other areas of confusion include the following but I don't foresee these being difficult to implement with your proposed tabbed view approach.
            -inability to export a published assessment. Instructors who've made significant changes to published assessments would want to re-use the published version when they next teach the class but they currently can't - they can't export or import published assessment (via Worksite Setup or Site Info > import from sites). Can only do so to pending assessments
            -label of 'Pending' is unclear
            -Inactive 'no student access' is not accurate - retracted assessments with feedback enabled is accessible to students who have submitted prior to the retraction; it would be more accurate to say 'unavailable for students to take'

            In any case, the Stanford UX team is meeting tomorrow to review and evaluate open JIRA issues to address in SAMigo 2.8. We'll have a better idea of where your request stands relative to other requests/bugs in the queue. We'd love it if you're able to work with us towards a solution. I'll keep you posted

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - Hi Sam, The main problem we hear over and over from our users is that it is confusing to have 3 lists (Pending, Published -Active, Published-Inactive) and the same assessment showing up in more than one list. Confusion tends to arise when people forget which assessment they last made changes to - was it under 'Core' or 'Published'? I myself have been frustrated by this when I had to verify something against a 'core' assessment but mistakenly did it against the published version. Ideally, users should see only one list and only one copy/version of an assessment. My instinct tells me that this is the way to go although I have yet to fully flesh out the details and I've yet to check with our developers to find out what the implications would be at the pipes and plumbing level. Other areas of confusion include the following but I don't foresee these being difficult to implement with your proposed tabbed view approach. -inability to export a published assessment. Instructors who've made significant changes to published assessments would want to re-use the published version when they next teach the class but they currently can't - they can't export or import published assessment (via Worksite Setup or Site Info > import from sites). Can only do so to pending assessments -label of 'Pending' is unclear -Inactive 'no student access' is not accurate - retracted assessments with feedback enabled is accessible to students who have submitted prior to the retraction; it would be more accurate to say 'unavailable for students to take' In any case, the Stanford UX team is meeting tomorrow to review and evaluate open JIRA issues to address in SAMigo 2.8. We'll have a better idea of where your request stands relative to other requests/bugs in the queue. We'd love it if you're able to work with us towards a solution. I'll keep you posted Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            Hi Jackie,

            Yes, I agree that one list would be really nice, but my guess is that the devs would see that as a huge modification!

            Is there anything to report out of the Stanford UX team meeting?

            Is there a direction that you would like us to work in next? A more refined mockup or a demo?

            --Sam

            Show
            Sam Ottenhoff added a comment - Hi Jackie, Yes, I agree that one list would be really nice, but my guess is that the devs would see that as a huge modification! Is there anything to report out of the Stanford UX team meeting? Is there a direction that you would like us to work in next? A more refined mockup or a demo? --Sam
            Hide
            Sam Ottenhoff added a comment -

            First revision of patch. Still looking for feedback. I will attach a few screenshots.

            Note that this patch uses the existing jQuery UI JS and CSS included in samigo-app (I believe for the timer).

            Show
            Sam Ottenhoff added a comment - First revision of patch. Still looking for feedback. I will attach a few screenshots. Note that this patch uses the existing jQuery UI JS and CSS included in samigo-app (I believe for the timer).
            Hide
            Jacqueline Mai added a comment - - edited

            Hi Sam,

            I'm wondering why you have the tabs at the top, above create assessment? The lists would not be available until assessments are created so the placement of the tabs should be below the create section.

            On my end, I put together some mockups (attached: SAMigoMainPagePublishedCopies.gif and SAMigoMainPageWorkingCopies.gif) and ran them by a few of our end users as well as our User Experience team. Attached is a redesign proposal based on their collective feedback and optimized for the most likely usage scenarios.

            What's new with this mockup:

            UI Changes
            Goals:
            -to de-clutter UI when there are many assessments
            -to help alleviate some confusion with existing labeling

            -'New Assessements' renamed to 'Create and Assessment'
            -The 2 create options are made more visually distinct
            -'Pending' renamed to 'Working Copies' and 'Published' to 'Published Copies.'
            -Under 'Published Copies,'
            -present users option to view all assessments as well as ability to view just Active or Inactive ones.
            -provide more accurate labels of what Active and Inactive mean
            -introduce a 'Status' column that allows users to see at a glance Active vs. Inactive assessments since default view is view all.

            Desired Interaction

            Working Copies:
            -Default view when user clicks on tool
            -After user publishes an assessment, redraw page and make Published Copies the active tab so users could see where the published copy has landed.

            Published Copies:
            -Default view is 'All'
            -Primary sort is 'Status' whereby all 'Active' assessments would appear on top of list

            The visual design is not finished but I wanted to give you feedback on the proposed revised layout and interaction changes.
            BTW, the mockups are based on the Stanford's local implementation of Sakai and we refer to 'assessments' as 'assignments'.

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - - edited Hi Sam, I'm wondering why you have the tabs at the top, above create assessment? The lists would not be available until assessments are created so the placement of the tabs should be below the create section. On my end, I put together some mockups (attached: SAMigoMainPagePublishedCopies.gif and SAMigoMainPageWorkingCopies.gif) and ran them by a few of our end users as well as our User Experience team. Attached is a redesign proposal based on their collective feedback and optimized for the most likely usage scenarios. What's new with this mockup: UI Changes Goals: -to de-clutter UI when there are many assessments -to help alleviate some confusion with existing labeling -'New Assessements' renamed to 'Create and Assessment' -The 2 create options are made more visually distinct -'Pending' renamed to 'Working Copies' and 'Published' to 'Published Copies.' -Under 'Published Copies,' -present users option to view all assessments as well as ability to view just Active or Inactive ones. -provide more accurate labels of what Active and Inactive mean -introduce a 'Status' column that allows users to see at a glance Active vs. Inactive assessments since default view is view all. Desired Interaction Working Copies: -Default view when user clicks on tool -After user publishes an assessment, redraw page and make Published Copies the active tab so users could see where the published copy has landed. Published Copies: -Default view is 'All' -Primary sort is 'Status' whereby all 'Active' assessments would appear on top of list The visual design is not finished but I wanted to give you feedback on the proposed revised layout and interaction changes. BTW, the mockups are based on the Stanford's local implementation of Sakai and we refer to 'assessments' as 'assignments'. Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            > I'm wondering why you have the tabs at the top, above create assessment? The lists would not be available
            > until assessments are created so the placement of the tabs should be below the create section.

            I think the original idea of having the create assessment functionality in the first tab was that assessment creation was most directly associated with the the pending section of assessments (and to separate out results completely).

            I like your mockups a lot. I think the visual separation of creation and results is excellent. I also like the visual separation of import.

            Please let us know how we can help going forward. We are glad to implement any chunks of the final mockups your team produces. Is it an appropriate time to start creating sub-tasks / sub-tickets to represent the changes that need to be implemented?

            Show
            Sam Ottenhoff added a comment - > I'm wondering why you have the tabs at the top, above create assessment? The lists would not be available > until assessments are created so the placement of the tabs should be below the create section. I think the original idea of having the create assessment functionality in the first tab was that assessment creation was most directly associated with the the pending section of assessments (and to separate out results completely). I like your mockups a lot. I think the visual separation of creation and results is excellent. I also like the visual separation of import. Please let us know how we can help going forward. We are glad to implement any chunks of the final mockups your team produces. Is it an appropriate time to start creating sub-tasks / sub-tickets to represent the changes that need to be implemented?
            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            If you're able to implement in full, then this will have a good chance of making the SAMigo 2.8 release. Is this possible? I can finish the visual treatment this week. What do you need from me in order to get started?

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - Hi Sam, If you're able to implement in full, then this will have a good chance of making the SAMigo 2.8 release. Is this possible? I can finish the visual treatment this week. What do you need from me in order to get started? Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            Hi Jackie,

            Yes, I can work on it in full. I have time this week if you are able to provide me with a final mockup. If you have a PSD, I would appreciate it, but if not, I can work from the GIF.

            Thanks,
            Sam

            Show
            Sam Ottenhoff added a comment - Hi Jackie, Yes, I can work on it in full. I have time this week if you are able to provide me with a final mockup. If you have a PSD, I would appreciate it, but if not, I can work from the GIF. Thanks, Sam
            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            GReat to hear you'll be able to implement in full!! .psd images are attached. I experimented with some other visual treatments but didn't like any of them. Just made minor tweak to the mockups I sent originally. I also included specification on desired behavior. Please let me know if you need anything else.

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - Hi Sam, GReat to hear you'll be able to implement in full!! .psd images are attached. I experimented with some other visual treatments but didn't like any of them. Just made minor tweak to the mockups I sent originally. I also included specification on desired behavior. Please let me know if you need anything else. Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            Attaching latest patch. Work is not done yet but core functionality is complete. I should have a complete patch ready in next three days.

            Show
            Sam Ottenhoff added a comment - Attaching latest patch. Work is not done yet but core functionality is complete. I should have a complete patch ready in next three days.
            Hide
            Sam Ottenhoff added a comment -

            Attaching screenshot of my local instance

            Show
            Sam Ottenhoff added a comment - Attaching screenshot of my local instance
            Hide
            Sam Ottenhoff added a comment -

            Attaching version of patch with all functionality implemented:

            1) Separation of create from scratch vs. Import

            2) Two tabs: Working Copies and Published Copies

            3) New Status column in Published Copies

            4) Removal of Inactive published assessments table

            5) Addition of jQuery limiter for All, Active, Inactive

            The only item I need help with is the possibilities for the Status column. What are the possible Status values? 1= Active, .....??

            Jackie, do you need me to bring up a test instance with this functionality? Or do you have a local instance you can use for testing?

            Show
            Sam Ottenhoff added a comment - Attaching version of patch with all functionality implemented: 1) Separation of create from scratch vs. Import 2) Two tabs: Working Copies and Published Copies 3) New Status column in Published Copies 4) Removal of Inactive published assessments table 5) Addition of jQuery limiter for All, Active, Inactive The only item I need help with is the possibilities for the Status column. What are the possible Status values? 1= Active, .....?? Jackie, do you need me to bring up a test instance with this functionality? Or do you have a local instance you can use for testing?
            Hide
            Sam Ottenhoff added a comment -

            New screenshot attached showing new column and new switcher functionality.

            Show
            Sam Ottenhoff added a comment - New screenshot attached showing new column and new switcher functionality.
            Hide
            Sam Ottenhoff added a comment -

            Can a Samigo Team member review this patch? We're hoping to get this merged into trunk so we don't need to run an independent branch of this patch.

            Thanks,
            Sam

            Show
            Sam Ottenhoff added a comment - Can a Samigo Team member review this patch? We're hoping to get this merged into trunk so we don't need to run an independent branch of this patch. Thanks, Sam
            Hide
            Sam Ottenhoff added a comment -

            This patch is now running in production at some institutions.

            A trunk branch is available here:

            https://source.sakaiproject.org/svn/msub/longsight.com/SAM-894/

            Show
            Sam Ottenhoff added a comment - This patch is now running in production at some institutions. A trunk branch is available here: https://source.sakaiproject.org/svn/msub/longsight.com/SAM-894/
            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            Before our developer merges your code, do you have a test instance on your end where I could take a look at the patch? In the event the patch needs to be tweaked, it would be better for our developer to just merge the final version.

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - Hi Sam, Before our developer merges your code, do you have a test instance on your end where I could take a look at the patch? In the event the patch needs to be tweaked, it would be better for our developer to just merge the final version. Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            Hi Jackie,

            Here is a trunk instance running the SAM-894 patch:

            http://sakaitrunk.longsight.com/portal/

            Login is stanford/stanford.

            Feel free to add additional guest users from Site Info

            --Sam

            Show
            Sam Ottenhoff added a comment - Hi Jackie, Here is a trunk instance running the SAM-894 patch: http://sakaitrunk.longsight.com/portal/ Login is stanford/stanford. Feel free to add additional guest users from Site Info --Sam
            Hide
            Jacqueline Mai added a comment -

            Hi Sam,

            My findings:

            UI Issues (please refer to screenshots)

            -Missing
            Page title: 'Assessments'
            'Create an Assessment' title below page title
            'Choose assignment type (optional)' and pull-down menu after 'Create using markup text' in Create from Scratch box

            Import box
            actual: Import assessment (from XML of zip file)
            desired per spec: Import from file (XML or zip)

            Published Copies
            -View options
            actual: Active (open to students)
            desired per spec: Active (open to students to take)

            actual: Inactive (not open to students)
            desired per spec: Inactive (not open to students to take)

            User Interaction Issues (please refer to spec document)
            actual: -After user publishes an assessment, page redrawn and Working Copies is still active tab.
            desired: -After user publishes an assessment, redraw page and make Published Copies the active tab so users could see where the published copy has landed.

            Could not make an active item inactive so could not test desired behavior of Published Copies

            Show
            Jacqueline Mai added a comment - Hi Sam, My findings: UI Issues (please refer to screenshots) -Missing Page title: 'Assessments' 'Create an Assessment' title below page title 'Choose assignment type (optional)' and pull-down menu after 'Create using markup text' in Create from Scratch box Import box actual: Import assessment (from XML of zip file) desired per spec: Import from file (XML or zip) Published Copies -View options actual: Active (open to students) desired per spec: Active (open to students to take) actual: Inactive (not open to students) desired per spec: Inactive (not open to students to take) User Interaction Issues (please refer to spec document) actual: -After user publishes an assessment, page redrawn and Working Copies is still active tab. desired: -After user publishes an assessment, redraw page and make Published Copies the active tab so users could see where the published copy has landed. Could not make an active item inactive so could not test desired behavior of Published Copies
            Hide
            Sam Ottenhoff added a comment -

            Okay, I committed the text changes as requested to the SAM-894 branch. I need 10 minutes of help from a Samigo developer to work on redrawing the page to land on the Published Copies. Can you ask a developer to give guidance on where this location can be modified? I can do the JavaScript work.

            Show
            Sam Ottenhoff added a comment - Okay, I committed the text changes as requested to the SAM-894 branch. I need 10 minutes of help from a Samigo developer to work on redrawing the page to land on the Published Copies. Can you ask a developer to give guidance on where this location can be modified? I can do the JavaScript work.
            Hide
            Karen Tsao added a comment -

            Sam,

            When an assessment is published or republished, samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/PublishAssessmentListener.java or samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/RepublishAssessmentListener.java is called from publishAssessment.jsp. You can set some flag there to switch the active tab. Is this what you are looking for?

            Thanks,
            Karen

            Show
            Karen Tsao added a comment - Sam, When an assessment is published or republished, samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/PublishAssessmentListener.java or samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/RepublishAssessmentListener.java is called from publishAssessment.jsp. You can set some flag there to switch the active tab. Is this what you are looking for? Thanks, Karen
            Hide
            Jacqueline Mai added a comment - - edited

            Hi Sam,

            One comment on the visual display of the tabs:

            Per the spec, the active tab should not have a bottom border. In actuality, the active tab has a bottom border and the top border has a different thickness (1px) than the bottom border that spans the remainder of the tabs navigation bar (2px).
            Could you please fix this?

            Preferable thickness of border is 2px.

            Thanks,
            Jackie

            Show
            Jacqueline Mai added a comment - - edited Hi Sam, One comment on the visual display of the tabs: Per the spec, the active tab should not have a bottom border. In actuality, the active tab has a bottom border and the top border has a different thickness (1px) than the bottom border that spans the remainder of the tabs navigation bar (2px). Could you please fix this? Preferable thickness of border is 2px. Thanks, Jackie
            Hide
            Sam Ottenhoff added a comment -

            Okay, I have checked in two more commits to the SAM-894 branch:

            1) Change border to 2px. Make sure no border on bottom of active tab.

            2) New boolean in AuthorBean.java gets set after publishing an assessment. Jump directly to published tab if the boolean is set (we set the default jquery-ui tab index)

            Show
            Sam Ottenhoff added a comment - Okay, I have checked in two more commits to the SAM-894 branch: 1) Change border to 2px. Make sure no border on bottom of active tab. 2) New boolean in AuthorBean.java gets set after publishing an assessment. Jump directly to published tab if the boolean is set (we set the default jquery-ui tab index)
            Hide
            Karen Tsao added a comment -

            svn commit -m "SAM-894"
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/bundle/AuthorFrontDoorMessages.properties
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/bean/author/AuthorBean.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/ActionSelectListener.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/AuthorActionListener.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/PublishAssessmentListener.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/RepublishAssessmentListener.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/SortCoreAssessmentListener.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/SortInactivePublishedAssessmentListener.java
            Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/SortPublishedAssessmentListener.java
            Sending samigo-app/src/webapp/css/tool_sam.css
            Sending samigo-app/src/webapp/css/ui-lightness/jquery-ui-1.7.2.custom.css
            Sending samigo-app/src/webapp/jsf/author/authorIndex.jsp
            Sending samigo-app/src/webapp/jsf/author/confirmAssessmentRetract.jsp
            Sending samigo-services/src/java/org/sakaiproject/tool/assessment/facade/PublishedAssessmentFacade.java
            Transmitting file data ..............
            Committed revision 84254.

            Show
            Karen Tsao added a comment - svn commit -m " SAM-894 " Sending samigo-app/src/java/org/sakaiproject/tool/assessment/bundle/AuthorFrontDoorMessages.properties Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/bean/author/AuthorBean.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/ActionSelectListener.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/AuthorActionListener.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/PublishAssessmentListener.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/RepublishAssessmentListener.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/SortCoreAssessmentListener.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/SortInactivePublishedAssessmentListener.java Sending samigo-app/src/java/org/sakaiproject/tool/assessment/ui/listener/author/SortPublishedAssessmentListener.java Sending samigo-app/src/webapp/css/tool_sam.css Sending samigo-app/src/webapp/css/ui-lightness/jquery-ui-1.7.2.custom.css Sending samigo-app/src/webapp/jsf/author/authorIndex.jsp Sending samigo-app/src/webapp/jsf/author/confirmAssessmentRetract.jsp Sending samigo-services/src/java/org/sakaiproject/tool/assessment/facade/PublishedAssessmentFacade.java Transmitting file data .............. Committed revision 84254.
            Hide
            Hudson CI Server added a comment -
            Show
            Hudson CI Server added a comment - Integrated in samigo trunk #296 (See http://builds.sakaiproject.org:8080/job/samigo%20trunk/296/ ) SAM-894
            Hide
            Karen Tsao added a comment -

            Further UI tuning:

            svn commit -m "SAM-894"
            Sending samigo-app/src/webapp/css/tool_sam.css
            Sending samigo-app/src/webapp/css/ui-lightness/jquery-ui-1.7.2.custom.css
            Sending samigo-app/src/webapp/jsf/author/authorIndex.jsp
            Transmitting file data ...
            Committed revision 85812.

            Show
            Karen Tsao added a comment - Further UI tuning: svn commit -m " SAM-894 " Sending samigo-app/src/webapp/css/tool_sam.css Sending samigo-app/src/webapp/css/ui-lightness/jquery-ui-1.7.2.custom.css Sending samigo-app/src/webapp/jsf/author/authorIndex.jsp Transmitting file data ... Committed revision 85812.
            Hide
            Stephen Marquard added a comment -

            The UI code here is not resizing the iframe correctly if the published list is longer than the working list. See screenshot.

            Show
            Stephen Marquard added a comment - The UI code here is not resizing the iframe correctly if the published list is longer than the working list. See screenshot.
            Hide
            Stephen Marquard added a comment -

            Double scroll bars in tool.

            Show
            Stephen Marquard added a comment - Double scroll bars in tool.
            Hide
            Sam Ottenhoff added a comment -

            Hi Stephen,

            Can you create a new ticket to help reduce confusion?

            Show
            Sam Ottenhoff added a comment - Hi Stephen, Can you create a new ticket to help reduce confusion?
            Hide
            Sam Ottenhoff added a comment -

            Resolving SAM-894. I will create new tickets for any enhancements (the Stephen issue regarding heights).

            Show
            Sam Ottenhoff added a comment - Resolving SAM-894 . I will create new tickets for any enhancements (the Stephen issue regarding heights).
            Hide
            Andrea Schmidt added a comment -

            Tested on QA3-US: sakai-2.9.0-a01 (Kernel 1.3.0-a01)- Server qa3-us
            Seems to be working as expected

            Show
            Andrea Schmidt added a comment - Tested on QA3-US: sakai-2.9.0-a01 (Kernel 1.3.0-a01)- Server qa3-us Seems to be working as expected

              People

              • Assignee:
                Karen Tsao
                Reporter:
                Sam Ottenhoff
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development