[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment.h2. Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*.h4. Closed selector !Styleguide.closed-box.png|thumbnail! - Set the left margin to approx.16px.  The goal should be to *left-align the combobox value with the dialog and tab titles*.- Choose the *dark green color palette for the value*: text color <31>, hover color <32>.The hover color only needs to slightly tint the base text color. It's about giving visual feedback, not about readability or good contrast.h4. Open selector  !Styleguide.open *Positioning* -  *Open the box  above (not below) the selected value*, at the approx . sizes  same position as the value itself . png|thumbnail!   *Padding and widths*- Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.- Set *left + right* inner paddings to *10px* (includes the 1px border).- Set *top + bottom* inner paddings to *8px* (includes the 1px border). *Positioning*- *Open the box above (not below) the selected value*, at the approx. same position as the value itself.  !Styleguide.open-box. colors sizes .png|thumbnail!   !Styleguide.open-box.fonts.png|thumbnail!*Colors and fonts*- Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.   !Styleguide.open-box.colors.png|thumbnail!  !Styleguide.open-box.fonts.png|thumbnail!   
 

  
 
 
 
 

 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment. h3 h2 . Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*.h4. Closed selector- Set the left margin to approx.16px.  The goal should be to *left-align the combobox value with the dialog and tab titles*.- Choose the *dark green color palette for the value*: text color <31>, hover color <32>.The hover color only needs to slightly tint the base text color. It's about giving visual feedback, not about readability or good contrast.h4. Open selector*Padding and widths*- Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.- Set *left + right* inner paddings to *10px* (includes the 1px border).- Set *top + bottom* inner paddings to *8px* (includes the 1px border).*Positioning*- *Open the box above (not below) the selected value*, at the approx. same position as the value itself.*Colors and fonts*- Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment.h2. Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*.h4. Closed selector  !Styleguide.closed - box.png|thumbnail! -  Set the left margin to approx.16px.  The goal should be to *left-align the combobox value with the dialog and tab titles*.- Choose the *dark green color palette for the value*: text color <31>, hover color <32>.The hover color only needs to slightly tint the base text color. It's about giving visual feedback, not about readability or good contrast.h4. Open selector  !Styleguide.open-box.sizes.png|thumbnail!  *Padding and widths*- Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.- Set *left + right* inner paddings to *10px* (includes the 1px border).- Set *top + bottom* inner paddings to *8px* (includes the 1px border).*Positioning*- *Open the box above (not below) the selected value*, at the approx. same position as the value itself.  !Styleguide.open-box.colors.png|thumbnail!  !Styleguide.open-box.fonts.png|thumbnail!  *Colors and fonts*- Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
   

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment.h2. Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*.h4. Closed selector !Styleguide.closed-box.png|thumbnail! - Set the left margin to approx.16px.  The goal should be to *left-align the combobox value with the dialog and tab titles*.- Choose the *dark green color palette for the value*: text color <31>, hover color <32>.The hover color only needs to slightly tint the base text color. It's about giving visual feedback, not about readability or good contrast.h4. Open selector * h5. Positioning * - *Open the box above (not below) the selected value*, at the approx. same position as the value itself. * h5. Padding and widths *  !Styleguide.open - box.sizes.png|thumbnail! -  Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.- Set *left + right* inner paddings to *10px* (includes the 1px border).- Set *top + bottom* inner paddings to *8px* (includes the 1px border). h5. Colors and fonts  !Styleguide.open-box. sizes colors .png|thumbnail!  *Colors and   !Styleguide.open-box.  fonts * .png|thumbnail!  - Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.  !Styleguide.open-box.colors.png|thumbnail!  !Styleguide.open-box.fonts.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment. h3. Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*.*Closed selector*- Set the left margin to approx.16px.  The goal should be to left-align the combobox value with the dialog and tab titles.- Choose the dark green color palette for the value: text color <31>, hover color <32>.*Open selector*- Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.- *Open the box above (not below) the selected value*, at the approx. same position as the value itself.- Set *left + right* paddings to *10px*.- Set *top + bottom* paddings to *8px*.- Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment.h3. Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*. * h4. Closed selector * - Set the left margin to approx.16px.  The goal should be to left-align the combobox value with the dialog and tab titles.- Choose the dark green color palette for the value: text color <31>, hover color <32>.*Open selector*- Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.- *Open the box above (not below) the selected value*, at the approx. same position as the value itself.- Set *left + right* paddings to *10px*.- Set *top + bottom* paddings to *8px*.- Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The *language switcher in dialogs should be more subtle*. While we may use standard comboboxes with forms, we use a text-only variant in headers, footers and filters. This will improve the overall appearance of dialogs and allows to better align the main buttons and the switcher.Please change the language switcher to:* be a text-only in Magnolia green, followed by an arrow (see attachments)* use our dark grey for text and icon, use white on hover* use the subtle popup for showing the valuesIf creating a popup like this seems like too much off the standard component, let's have a look together. Note that the bottom padding is wrong in the popup shown in the attachment.h3. Visual design for language/variant selectorSo far, we've had mainly comboboxes on green, black and white backgrounds. Here's how *language and variant selector look and work on gray backgrounds and in dialogs*.h4. Closed selector- Set the left margin to approx.16px.  The goal should be to  *  left-align the combobox value with the dialog and tab titles * .- Choose the  *  dark green color palette for the value * : text color <31>, hover color <32>. * The hover color only needs to slightly tint the base text color. It's about giving visual feedback, not about readability or good contrast.h4. Open selector  * Padding and widths* - Ensure a *minimum width of 120px*. There's no minimum height, although the screenshot seems to suggest so.-  Set  * left + right* inner paddings to *10px* (includes the 1px border).- Set *top + bottom* inner paddings to *8px* (includes the 1px border).*Positioning*- * Open the box above (not below) the selected value*, at the approx. same position as the value itself. - Set *left + right* paddings to *10px*.  - Set  * top + bottom Colors and fonts *  paddings to *8px*. - Background color of the *box is white*, the *border color is <13>*.- *Highlight color is <16>*.- The font is *Verdana regular 12px*, font color is black.The screenshot shows DIN regular, but this doesn't apply here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Attachment: 
 Styleguide.closed-box.png  
 
 
Attachment: 
 Styleguide.open-box.colors.png  
 
 
Attachment: 
 Styleguide.open-box.fonts.png  
 
 
Attachment: 
 Styleguide.open-box.sizes.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail 

[magnolia-dev] [JIRA] (MGNLUI-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
 Raised this to major as this is a bug the article editor depends upon.  
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-83) Ensure CLI works on Windows

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-83  
 
 
  Ensure CLI works on Windows   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Summary: 
 templateScript path uses backslash Ensure CLI works on Windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3547) Fix the tab order in backend forms

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3547  
 
 
  Fix the tab order in backend forms   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Epic Name: 
 AX:  Good  tab order in forms  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3508) Streamline form field attributes handling (i18n, default values, required/read-only states)

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3508  
 
 
  Streamline form field attributes handling (i18n, default values, required/read-only states)   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Epic Colour: 
 ghx-label- 3 6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3547) Fix the tab order in backend forms

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3547  
 
 
  Fix the tab order in backend forms   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Epic Name: 
 AX: Good tab order in forms  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3910) Usability improvements in the "move" chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3910  
 
 
  Usability improvements in the "move" chooser dialog   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Epic Name: 
 AX: "Move" dialog  improvements  imprv  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (CFGUI-59) Extend the definitions app with more features and to show definitions from all sources

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Definitions app /  CFGUI-59  
 
 
  Extend the definitions app with more features and to show definitions from all sources   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Epic Colour: 
 ghx-label- 1 5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (CFGUI-59) Extend the definitions app with more features and to show definitions from all sources

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Definitions app /  CFGUI-59  
 
 
  Extend the definitions app with more features and to show definitions from all sources   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Summary: 
 Extend the definitions app  with more features and  to show definitions from all sources  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (CFGUI-59) Extend the definitions app to show definitions from all sources

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Definitions app /  CFGUI-59  
 
 
  Extend the definitions app to show definitions from all sources   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 

  
 
 
 
 

 
 The current Definitions app already provides a rounded set of features. We're also lacking a couple of functions and features. In addition, we're not yet showing definitions from all possible sources (e.g. Blossom). This epic collects all such stories.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (CFGUI-59) Extend the definitions app to show definitions from all sources

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Definitions app /  CFGUI-59  
 
 
  Extend the definitions app to show definitions from all sources   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Summary: 
 Follow-up stories that conclude Extend  the definitions app  to show definitions from all sources  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (CFGUI-59) Extend the definitions app to show definitions from all sources

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Definitions app /  CFGUI-59  
 
 
  Extend the definitions app to show definitions from all sources   
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Epic Name: 
 Definitions:  next steps  show more  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (CFGUI-59) Follow-up stories that conclude the definitions app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Definitions app /  CFGUI-59  
 
 
  Follow-up stories that conclude the definitions app   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 13/Jan/17 10:25 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Andreas Weder  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-112) Slightly rework the preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Slightly rework the preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Summary:
 
 Rework Slightly rework the  preview of pages 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Priority:
 
 Neutral Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 The page preview on tablet and smartphone [looks dated due to the (old) iPhone and iPad frames|^3 Preview.current.png] we show it in. It's also disorienting as switching between two previews causes the page to start at a different location inside the viewport. We've heard it several time that the page preview should be reworked. We're going to *rework the page preview* like this  (see [attachment 1|^2 Reworked preview.png] and [attachment 2|^2 Reworked preview.png]) :* We *no longer show the frames* of a tablet or a smartphone.* We *top-align* a page preview with the black preview bar.* When switching, we *only change the width* of the page, but always use the *full available height*.* We have two options per mobile preview in the combobox in the preview bar, *one for "landscape", one for "portrait"*.* We *expose the current resolution* of the iframe in the status bar at the bottom.Note that the main goal of this issue has been to remove the main pain points, and remove them quickly. We've thus designed *a solution which we expect is somewhat easy to implement* with the current means.h4. Widths to useTo remain aligned with how the current preview works, we'll stick with the widths of the original 1x resolutions of an iPad and an iPhone.* Desktop: width of the viewport available for the iframe* Tablet (landscape): 1024px* Tablet (portrait): 768px* Smartphone (landscape): 480px* Smartphone (portrait): 320pxThe plan is to eventually move to a preview allowing you to *actually pick from multiple, typical resolutions for each mobile device type*. See [attachment 4|^4 Choose resolution.future.png] for an example from Mozilla Firefox's built-in web developer tools. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
   

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 The page preview on tablet and smartphone  [  looks dated due to the (old) iPhone and iPad frames |^3 Preview.current.png]  we show it in. It's also disorienting as switching between two previews causes the page to start at a different location inside the viewport. We've heard it several time that the page preview should be reworked. We're going to *rework the page preview* like this:* We *no longer show the frames* of a tablet or a smartphone.* We *top-align* a page preview with the black preview bar.* When switching, we *only change the width* of the page, but always use the *full available height*.* We have two options per mobile preview in the combobox in the preview bar, *one for "landscape", one for "portrait"*.* We *expose the current resolution* of the iframe in the status bar at the bottom.Note that the main goal of this issue has been to remove the main pain points, and remove them quickly. We've thus designed *a solution which we expect is somewhat easy to implement* with the current means.h4. Widths to useTo remain aligned with how the current preview works, we'll stick with the widths of the original 1x resolutions of an iPad and an iPhone.* Desktop: width of the viewport available for the iframe* Tablet (landscape): 1024px* Tablet (portrait): 768px* Smartphone (landscape): 480px* Smartphone (portrait): 320pxThe plan is to eventually move to a preview allowing you to *actually pick from multiple, typical resolutions for each mobile device type*.  See [attachment 4|^4 Choose resolution.future.png] for an example from Mozilla Firefox's built-in web developer tools. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
  

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 4 Choose resolution.future.png 
 
 
 

Attachment:
 
 3 Preview.current.png 
 
 
 

Attachment:
 
 2 Reworked preview.png 
 
 
 

Attachment:
 
 1 Reworked preview.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 The page preview on tablet and smartphone looks dated due to the (old) iPhone and iPad frames we show it in. It's also disorienting as switching between two previews causes the page to start at a different location inside the viewport. We've heard it several time that the page preview should be reworked. We're going to *rework the page preview* like this:* We *no longer show the frames* of a tablet or a smartphone.* We *top-align* a page preview with the black preview bar.* When switching, we *only change the width* of the page, but always use the *full available height*.* We have two options per mobile preview in the combobox in the preview bar, *one for "landscape", one for "portrait"*.* We *expose the current resolution* of the iframe in the status bar at the bottom.Note that the main goal of this issue has been to remove the main pain points, and remove them quickly. We've thus designed *a solution which we expect is somewhat easy to implement* with the current means. h4. Widths to useTo remain aligned with how the current preview works, we'll stick with the widths of the original 1x resolutions of an iPad and an iPhone.* Desktop: width of the viewport available for the iframe* Tablet (landscape): 1024px* Tablet (portrait): 768px* Smartphone (landscape): 480px* Smartphone (portrait): 320pxThe plan is to eventually move to a preview allowing you to *actually pick from multiple, typical resolutions for each mobile device type*. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 
 
Attached a PDF prototype to allow you to preview the experience of the reworked page preview. 
In OS X: 
 

Open in Preview.app
 

Switch "View" to "Single page"
 

Click on red link areas to cycle through all five previews
 
 
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 Reworked mobile preview.pdf 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To 

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 The page preview on tablet and smartphone looks dated due to the (old) iPhone and iPad frames we show it in. It's also disorienting as switching between two previews causes the page to start at a different location inside the viewport. We've heard it several time that the page preview should be reworked  a bit .     We're going to *rework the page preview* like this:* We *no longer show the frames* of a tablet or a smartphone.* We *top-align* a page preview with the black preview bar.* When switching, we *only change the width* of the page, but always use the *full available height*.* We have two options per mobile preview in the combobox in the preview bar, *one for "landscape", one for "portrait"*.* We *expose the current resolution* of the iframe in the status bar at the bottom. Note that the main goal of this issue has been to remove the main pain points, and remove them quickly. We've thus designed *a solution which we expect is somewhat easy to implement* with the current means. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-112) Rework preview of pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-112 
 
 
 
  Rework preview of pages  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 08/Dec/16 4:48 PM 
 
 
 

Labels:
 

 ux usability 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
The page preview on tablet and smartphone looks dated due to the (old) iPhone and iPad frames we show it in. It's also disorienting as switching between two previews causes the page to start at a different location inside the viewport. We've heard it several time that the page preview should be reworked a bit. 
We're going to rework the page preview like this: 
 

We no longer show the frames of a tablet or a smartphone.
 

We top-align a page preview with the black preview bar.
 

When switching, we only change the width of the page, but always use the full available height.
 

[magnolia-dev] [JIRA] (MGNLUI-3994) Sponsored development of Drag and Drop support in Grid and TreeGrid

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3994 
 
 
 
  Sponsored development of Drag and Drop support in Grid and TreeGrid  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Assignee:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-4088) Favorites: only works when the app is not open already and on top

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4088 
 
 
 
  Favorites: only works when the app is not open already and on top  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.5.1 
 
 
 

Labels:
 
 usability 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-4088) Favorites: only works when the app is not open already and on top

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4088 
 
 
 
  Favorites: only works when the app is not open already and on top  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-103) Components can't be pasted across pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-103 
 
 
 
  Components can't be pasted across pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Environment:
 
 Found with snapshot: magnolia-enterprise-pro-demo-bundle-5.5-20161030.091240-342-tomcat-bundle Firefox 49.0.2 on Mac OS X 10.11.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-103) Components can't be pasted across pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-103 
 
 
 
  Components can't be pasted across pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-103) Components can't be pasted across pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-103 
 
 
 
  Components can't be pasted across pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Account:
 
 null (null) 
 
 
 

Environment:
 
 Found with snapshot: magnolia-enterprise-pro-demo-bundle-5.5-20161030.091240-342-tomcat-bundle 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-103) Components can't be pasted across pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-103 
 
 
 
  Components can't be pasted across pages  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 31/Oct/16 6:01 PM 
 
 
 

Labels:
 

 usability page-editor ux 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
I've verified the mechanisms for copying and pasting components in the page editor. I can't copy a component on one page, then paste it on a duplicate of the same page. It seems, actually, that I can't c of components to work across pages in general. 
Steps to reproduce 
 

In the Travel demo, duplicate the page /travel/about/company. This leads to the creation of the page /travel/about/company0.
 

Copy the text/image component on the /travel/about/company.
 

Open the page /travel/about/company0 (the duplicate), and try to paste the copied text/image component into the "Main" area.
 
 
The "paste component(s)" action is not enabled, but I actually expect it to. 
 
 
 
 

[magnolia-dev] [JIRA] (PAGES-103) Components can't be pasted across pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-103 
 
 
 
  Components can't be pasted across pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Priority:
 
 Neutral Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-103) Components can't be pasted across pages

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-103 
 
 
 
  Components can't be pasted across pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 I've verified the mechanisms for copying and pasting components in the page editor. I *can't copy a component on one page, then paste it on a duplicate of the same page*. It seems, actually, that I can't c of components to work across pages in general.h4. Steps to reproduce# In the Travel demo, duplicate the page /travel/about/company. This leads to the creation of the page /travel/about/company0.# Copy the text/image component on the /travel/about/company.# Open the page /travel/about/company0 (the duplicate), and try to paste the copied text/image component into the "Main" area.The "paste component(s)" action is not enabled, but I actually expect it to. Note that copy+paste of components within the same page, but different areas works fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3767) Use resources (fonts, images) from core module in defaultMagnoliaLoginForm

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3767 
 
 
 
  Use resources (fonts, images) from core module in defaultMagnoliaLoginForm  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Labels:
 
 estimate-pm-5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 1.3.2 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 New icon for GA app.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 New CSS stmt.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We've designed a new icon for the Google Analytics app to be released as part of Magnolia 5.5. Please replace the existing "eye" icon with this new icon.I have *attached a new version of our icon font (V18)*, which contains the new icon and should be fully compatible with the existing font (e.g. it should use the same unicode character ranges).To add the new icon:* Copy the font files in the archive ( [^ MagnoliaIcons.V18.160906.zip ] ) to the Vaadin theme* Add the new CSS statement to the end on the MagnoliaIcons.css file in the Vaadin theme (see  [^  New  css stmts  CSS stmt .png ] ). The CSS file is also contained in the archive mentioned above. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 MagnoliaIcons.V18.160906.zip 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We've designed a new icon for the Google Analytics app to be released as part of Magnolia 5.5. Please replace the existing "eye" icon with this new icon.I have  *  attached a new version of our icon font (V18) * , which contains the new icon and should be fully compatible with the existing font (e.g. it should use the same unicode character ranges).  Please note that the work on the installation screens, which should be finished by now. To add the new  icons  icon :  * Copy the font files in the archive (MagnoliaIcons. v17 V18 . 160727 160906 .zip) to the Vaadin theme * Add  a couple of  the  new CSS  statements  statement  to the end on the MagnoliaIcons.css file in the Vaadin theme (see New css stmts.png). The CSS file is also contained in the archive mentioned above. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We've designed a new icon for the Google Analytics app to be released as part of Magnolia 5.5. Please replace the existing "eye" icon with this new icon. To I have attached a new version of our icon font (V18), which contains the new icon and should  be  continued  fully compatible with the existing font (e . g .  it should use the same unicode character ranges) .  Please note that the work on the installation screens, which should be finished by now.To add the new icons:Copy the font files in the archive (MagnoliaIcons.v17.160727.zip) to the Vaadin themeAdd a couple of new CSS statements to the end on the MagnoliaIcons.css file in the Vaadin theme (see New css stmts.png). The CSS file is also contained in the archive mentioned above. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLGA-22) Install new app icon for Google Analytics app

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-22 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 06/Sep/16 6:35 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
We've designed a new icon for the Google Analytics app to be released as part of Magnolia 5.5. Please replace the existing "eye" icon with this new icon. 
To be continued... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
  

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*.We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image (see [attachment 1|^1 No selection (default view).png]). We might want to make the rows a bit higher - we'll have to check several sizes. The column can be configured to not appear. * Every asset chooser has a *Preview bar on the right* (similar to the Action bar), which can be collapsed and extended. By default, it the Preview bar is extended.** If a single item is selected, a larger preview is shown in the Preview bar (see [attachment 3|^3 Single item selected.png] and [attachment 4|^4 Single item selected 2.png]).** If multiple items are selected, the Preview bar is empty (see [attachment 5|^5 Multiple item selected.png]).** The Preview bar remembers its collapsed/expanded state (see  [  attachment 2|^2 Preview bar collapsed.png].* The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*. The following may be desirable, but are not required:# The Preview bar could be available in every chooser dialog.If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type.# The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*.We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image (see [attachment 1|^1 No selection (default view).png]). We might want to make the rows a bit higher - we'll have to check several sizes. The column can be configured to not appear. * Every asset chooser has a *Preview bar on the right* (similar to the Action bar), which can be collapsed and extended. By default, it the Preview bar is extended.** If a single item is selected, a larger preview is shown in the Preview bar (see [attachment 3|^3 Single item selected.png] and [attachment 4|^4 Single item selected 2.png]).** If multiple items are selected, the Preview bar is empty (see [attachment 5|^5 Multiple item selected.png]).** The Preview bar remembers its collapsed/expanded state (see attachment 2|^2 Preview bar collapsed.png].* The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*.  It  The following  may be desirable, but  is  are  not required: * #  The Preview bar could be available in every chooser dialog.If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type. * #  The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*.We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image  (see [attachment 1|^1 No selection (default view) .  This will likely png]). We might want to  make the rows a bit higher - we'll have to check several sizes. The column can be configured to not appear.     * Every asset chooser has a *Preview bar on the right* (similar to the Action bar), which can be collapsed and extended. By default, it the Preview bar is extended.** If a single item is selected, a larger preview is shown in the Preview bar  (see [attachment 3|^3 Single item selected . png] and [attachment 4|^4 Single item selected 2.png]). ** If multiple items are selected, the Preview bar is empty  (see [attachment 5|^5 Multiple item selected . png]). ** The Preview bar remembers its collapsed/expanded state  (see attachment 2|^2 Preview bar collapsed . png]. * The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*. It may be desirable, but is not required:* The Preview bar could be available in every chooser dialog.If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type.* The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*.   We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image. This will likely make the rows a bit higher - we'll have to check several sizes. The column can be configured not to appear.* Every asset chooser has a *Preview bar on the right* (similar to the Action bar), which can be collapsed and extended. By default, it the Preview bar is extended.** If a single item is selected, a larger preview is shown in the Preview bar.** If multiple items are selected, the Preview bar is empty.** The Preview bar remembers its collapsed/expanded state.* The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*. It may be desirable, but is not required:* The Preview bar could be available in every chooser dialog.If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type.* The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*.We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image. This will likely make the rows a bit higher - we'll have to check several sizes. The column can be configured  not  to  not  appear.* Every asset chooser has a *Preview bar on the right* (similar to the Action bar), which can be collapsed and extended. By default, it the Preview bar is extended.** If a single item is selected, a larger preview is shown in the Preview bar.** If multiple items are selected, the Preview bar is empty.** The Preview bar remembers its collapsed/expanded state.* The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*. It may be desirable, but is not required:* The Preview bar could be available in every chooser dialog.If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type.* The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*.We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image. This will likely make the rows a bit higher - we'll have to check several sizes. The column can be configured to not appear.  * Every asset chooser has a *Preview bar on the right* (similar to the Action bar), which can be collapsed and extended. By default, it the Preview bar is extended.** If a single item is selected, a larger preview is shown in the Preview bar.** If multiple items are selected, the Preview bar is empty.** The Preview bar remembers its collapsed/expanded state.  * The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*. It may be desirable, but is not required:* The Preview bar could be available in every chooser dialog.If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type.* The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 5 Multiple item selected.png 
 
 
 

Attachment:
 
 4 Single item selected 2.png 
 
 
 

Attachment:
 
 3 Single item selected.png 
 
 
 

Attachment:
 
 2 Preview bar collapsed.png 
 
 
 

Attachment:
 
 1 No selection (default view).png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Our current *asset chooser doesn't offer any previews*. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision.There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for. We would thus like to *offer dedicated previews in the Tree view of an asset chooser*. We've *discussed and estimated several options* we currently have and would like to try the following:# We offer a *dedicated column* showing tiny, HTML-rendered image previews.# We add an bar similar to the Action bar on the right, which shows a *larger preview of the currently selected item*.h4. Acceptance criteria* Every asset chooser offers a *configurable "previews" column*, which shows a tiny preview, if the asset is an image. This will likely make the rows a bit higher - we'll have to check several sizes. The column can be configured not to appear.* Every asset chooser has a  *  Preview bar  on the right*  (similar to the Action bar)  on the right , which can be collapsed and extended. By default, it the Preview bar is extended.* *  If a single item is selected, a larger preview is shown in the Preview bar.* *  If multiple items are selected, the Preview bar is empty.* *  The Preview bar remembers its collapsed/expanded state.* The solution should be *in a state so that we can ship it to customers for testing*. It doesn't have to be of production-grade quality yet, but should be stable enough so that customers can rate the solution and test it with setups featuring many assets.Note that we *focus mainly on the asset chooser*. It may be desirable, but is not required:* The Preview bar could be available in every chooser  dialog .If we implement this, it must be configurable whether the Preview bar should be shown or not (not only collapsed or expanded), as previews don't make sense for every chooser type.* The "previews" could configurable in views of apps as well.Please do not invest, however, in solving issues that come from this, as the focus is mainly to focus on the problem of missing previews in the asset chooser. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Affects Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-4001) Build a first solution for showing previews in the asset chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4001 
 
 
 
  Build a first solution for showing previews in the asset chooser dialog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 26/Aug/16 3:08 PM 
 
 
 

Labels:
 

 ux usability support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Our current asset chooser doesn't offer any previews. If your assets are many and use similar titles, you only realize after picking a specific asset that it was the wrong one, which forces you to click many times again to just make a second, possibly equally wrong decision. 
There's a thumbnail view, of course, but the current implementation behind it still has performance issues for customers with many assets, offers no filters and doesn't show any information alongside the thumbs currently, which would help you in identififying the asset you're looking for.  
We would thus like to offer dedicated 

[magnolia-dev] [JIRA] (MGNLUI-3994) Sponsored development of Drag and Drop support in Grid and TreeGrid

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3994 
 
 
 
  Sponsored development of Drag and Drop support in Grid and TreeGrid  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Summary:
 
 Sponsored development of Drag and Drop  support  in Grid and TreeGrid 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3994) Sponsored development of Drag and Drop in Grid and TreeGrid

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3994 
 
 
 
  Sponsored development of Drag and Drop in Grid and TreeGrid  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Aug/16 5:00 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3993) Sponsored development of TreeGrid component

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3993 
 
 
 
  Sponsored development of TreeGrid component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Assignee:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3993) Sponsored development of TreeGrid component

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3993 
 
 
 
  Sponsored development of TreeGrid component  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Aug/16 5:00 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3995) Replace our existing with the new Grid-based components

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3995 
 
 
 
  Replace our existing with the new Grid-based components  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Aug/16 5:01 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3992) Replace Vaadin's Table and TreeTable with new Grid-based components

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3992 
 
 
 
  Replace Vaadin's Table and TreeTable with new Grid-based components  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 framework, vaadin integration 
 
 
 

Created:
 

 18/Aug/16 4:56 PM 
 
 
 

Labels:
 

 usability ux 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Vaadin have released a new implementation of a list and matrix component called "Grid". This component solves many performance and usability problems we have in our views. It will also allow us to add improvements (e.g. inline detail views) and new features (e.g. small image previews in rows and checkboxes in headers to select all items), making views more useful and also increasing their usability. 
However, "Grid" does not support and drag and drop operations nor the hierarchical display of data. Our intention is thus to sponsor Vaadin for the development of both features. Once these features will be available, we'll replace our 

[magnolia-dev] [JIRA] (MGNLUI-3992) Replace Vaadin's Table and TreeTable with new Grid-based components

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3992 
 
 
 
  Replace Vaadin's Table and TreeTable with new Grid-based components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Labels:
 
 blocked usability ux 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3992) Replace Vaadin's Table and TreeTable with new Grid-based components

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3992 
 
 
 
  Replace Vaadin's Table and TreeTable with new Grid-based components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Assignee:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3992) Replace Vaadin's Table and TreeTable with new Grid-based components

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3992 
 
 
 
  Replace Vaadin's Table and TreeTable with new Grid-based components  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Vaadin have released a  *  new implementation  of  for  a list and  a  matrix  component  of items  called  the  "Grid" * component . This component solves many performance and usability problems we have in our views. It will also allow us to add improvements (e.g. inline detail views) and new features (e.g. small image previews in rows and checkboxes in headers to select all items), making views more useful and also increasing their usability.However, "Grid"  *  does not support and drag and drop operations  *  nor the hierarchical display of data. Our intention is thus to  *  sponsor Vaadin for the development of both features * . Once these features will be available, we'll replace our existing Table component with Grid and TreeTable with TreeGrid. That  *  will set us up to finally tackle many of our long-standing problems *  we've had.This story allows us, our partners and our customers to track our progress on this matter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3988) After "Publish deletion" the view jump at the beginning of the pages tree and don't stay at the selected item

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3988 
 
 
 
  After "Publish deletion" the view jump at the beginning of the pages tree and don't stay at the selected item  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3988) After "Publish deletion" the view jump at the beginning of the pages tree and don't stay at the selected item

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3988 
 
 
 
  After "Publish deletion" the view jump at the beginning of the pages tree and don't stay at the selected item  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Labels:
 
 usability 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3467) A duplicated item should be selected and visible

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Just re-opening it in order to close it as "fixed" instead of "duplicate" as I need it to appear on a list of UX things done. 
 
 
 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3467 
 
 
 
  A duplicated item should be selected and visible  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Resolution:
 
 Duplicate 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3910) Usability improvements in the "move" chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3910 
 
 
 
  Usability improvements in the "move" chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Epic Colour:
 
 ghx-label-6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3910) Usability improvements in the "move" chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3910 
 
 
 
  Usability improvements in the "move" chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3910) Usability improvements in the "move" chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3910 
 
 
 
  Usability improvements in the "move" chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Assignee:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3910) Usability improvements in the "move" chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3910 
 
 
 
  Usability improvements in the "move" chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3896) Adjust column widths in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3896 
 
 
 
  Adjust column widths in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3897) Open the move dialog where the move action started

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3897 
 
 
 
  Open the move dialog where the move action started  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3910) Usability improvements in the "move" chooser dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3910 
 
 
 
  Usability improvements in the "move" chooser dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Project:
 
 Backlog Magnolia UI 
 
 
 

Key:
 
 BL MGNLUI - 361 3910 
 
 
 

Security:
 
 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3682) Find a way to group form fields to properly structure forms

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3682 
 
 
 
  Find a way to group form fields to properly structure forms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We currently *lack any type of structuring element in dialogs* apart from tabs. If you e.g. look at the "edit asset" dialog, we just have a large sequence, a "flood of fields". We can do better than that, e.g. by separating core asset properties (it's name, media blog) from meta data sections.One of the basic things we need in order to properly design and structure forms is *a way to group fields*. Other useful structural elements would be accordions and tabs in forms. This issue, however, is only about a way to group fields.Such a group of fields:* can be associated with a *name and/or an id* so that we refer to it* may feature an *optional title* We should make sure that we *don't simply introduce additional hierarchy levels in the already quite nested dialog definitions*, unless we find no other meaningful way to group elemens. Technically, this would properly be rendered using an HTML "fieldset" element, so that we can take advantage of built-in browser support such as a way to disable or hide the entire group, or to mark it as read-only. We have to discuss if we also want to allow such a group of fields to be used in lieu of a regular field, i.e. in switchable or multi-value fields. This issue is part of an initiative to improve the author experience in forms by adding missing elements, which allow us to better structure forms. It also allows us to switch to better forms once we improve our content pool story further. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3682) Find a way to group form fields to properly structure forms

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3682 
 
 
 
  Find a way to group form fields to properly structure forms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Field sets are an important We currently *lack any type of structuring  element  to structure forms  in dialogs* apart from tabs .  They group together related fields  If you e .  A field set has some typical attributes which g. look at the "edit asset" dialog,  we  just have a large sequence ,  at least partially  a "flood of fields". We can do better than that ,  also know  e.g. by separating core asset properties (it's name, media blog)  from  the HTML fieldset element  meta data sections .  They:  One of the basic things we need in order to properly design and structure forms is * a way to group fields  * . Other useful structural elements would be accordions and tabs in forms. This issue, however, is only about a way to group  fields.Such  a  set  group  of fields * : *  have  can be associated with  a *name and/or  an  id*  so that  we  can use to  refer to  them  it * may  have  feature  an *optional title* Technically, this would properly be rendered using an HTML "fieldset" element, so that we can take advantage of built-in browser support such as a way to disable or hide the entire group, or to mark it as read-only. We have to discuss if we also want to allow  field sets  such a group of fields  to be used in  complex fields such as  lieu of  a  regular field, i.e. in  switchable or multi-value fields.  It'd support an approach which would *treat field sets just like regular fields*.   This would also mean I could:  * *disable* field sets* mark them as *read-only** *hide* a field set This issue is part of an initiative to improve the author experience in forms by adding missing elements, which allow us to better structure forms.  It also allows us to switch to better forms once we improve our content pool story further. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 

[magnolia-dev] [JIRA] (MGNLUI-3682) Find a way to group form fields to properly structure forms

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3682 
 
 
 
  Find a way to group form fields to properly structure forms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 Field sets are an important element to structure forms. They group together related fields. A field set has some typical attributes which we, at least partially, also know from the HTML fieldset element. They:* *group a set of fields**  *  have a *name and/or id* we can use to refer to them* may have an *optional title*We have to discuss if we also want to allow field sets to be used in complex fields such as a switchable or multi-value fields. It'd support an approach which would *treat field sets just like regular fields*. This would also mean I could:* *disable* field sets* mark them as *read-only** *hide* a field setThis issue is part of an initiative to improve the author experience in forms by adding missing elements, which allow us to better structure forms. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3682) Find a way to group form fields to properly structure forms

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3682 
 
 
 
  Find a way to group form fields to properly structure forms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Summary:
 
 Add Find  a  new field  way  to  specify a field set in dialogs  group form fields to properly structure forms 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3105) Keyboard focus should only move the focus, not the selection

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3105 
 
 
 
  Keyboard focus should only move the focus, not the selection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Labels:
 
 accessibility estimate-pm-5.5 is-expected  pain-point team-priority  usability ux 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 1 Selected root folder.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 It is *currently not clear how to move an item to the top-most folder* in the hierarchy (the root folder). The "move" dialog doesn't show the root folder and requires to deselect any folder in order to "select" the root folder. The latter point is also confusing, as the dialog mentions that "no item is selected", but has the "move inside" button enabled.To fix this, we're going to *expose the root folder* in any "move" dialog:* The root folder is marked with a *root folder icon*.* The root folder is *always open* and can't be closed.* As a result of this, the icon *doesn't show an arrow*.* The  title/  node name of the root folder is *"root folder"*.  It does not have a title (show "-"). The root folder acts like any other potential destination for the "move" operation: it can be selected and moved into. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 1 Selected root folder.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 It is *currently not clear how to move an item to the top-most folder* in the hierarchy (the root folder). The "move" dialog doesn't show the root folder and requires to deselect any folder in order to "select" the root folder. The latter point is also confusing, as the dialog mentions that "no item is selected", but has the "move inside" button enabled.To fix this, we're going to *expose the root folder* in any "move" dialog:* The root folder is marked with a *root folder icon*.* The root folder is *always open* and can't be closed.* As a result of this, the icon *doesn't show an arrow*.* The title/name of the root folder is *" (top-most root  folder ) "*. This should be verified with an English-native speaker (we could just use "root folder", but it could be a technical term).   The root folder acts like any other potential destination for the "move" operation: it can be selected and moved into. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 1 Selected root folder.png 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 31/May/16 2:42 PM 
 
 
 

Labels:
 

 estimate-pm-5.5 ux usability working-with-items 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We'd like to *show the item you're currently moving* in the "move" dialog in order to avoid having the user to re-orient herself when the dialog opens (see rationale below).The *item currently moved* is shown like this (see [attachment 1|^1 How to reveal item being moved.png]):* The item *has the mouse hover highlighting* (light gray). It's not selected, but has the keyboard focus.* The item actually *can't be selected*.* Its icon is replaced with a *placeholder icon* (the dotted rectangle in the wireframe)Note that the  *  wireframe actually shows an even more advanced state *  of the "move" dialog, which also reveals the root node, offers to duplicate instead of moving the item and features menu buttons to cover all way to move an item (inside, above or below another item). Those are  *  handled in separate tasks *  (see linked issues).h4. Design rationale behind this decisionWe show the "move" dialog when a user clicks on a "move item" action. This is a rupture in a user's flow, but one we accept as the "move" dialog is the one option that works across devices. We can mitigate the effect of such a rupture by aligning the view presented by the "move" dialog and the view the user had when clicking on the "move" action. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We'd like to *show the item you're currently moving* in the "move" dialog in order to avoid having the user to re-orient herself when the dialog opens (see rationale below).The *item currently moved* is shown like this  (see [attachment 1|^1 How to reveal item being moved.png]) :* The item *has the mouse hover highlighting* (light gray). It's not selected, but has the keyboard focus.* The item actually *can't be selected*.* Its icon is replaced with a *placeholder icon* (the dotted rectangle in the wireframe)Note that the wireframe actually shows an even more advanced state of the "move" dialog, which also reveals the root node, offers to duplicate instead of moving the item and features menu buttons to cover all way to move an item (inside, above or below another item). Those are handled in separate tasks (see linked issues).h4. Design rationale behind this decisionWe show the "move" dialog when a user clicks on a "move item" action. This is a rupture in a user's flow, but one we accept as the "move" dialog is the one option that works across devices. We can mitigate the effect of such a rupture by aligning the view presented by the "move" dialog and the view the user had when clicking on the "move" action. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 2 Example of selected target.png 
 
 
 

Attachment:
 
 1 How to reveal item being moved.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We'd like to *show the item you're currently moving* in the "move" dialog in order to avoid having the user to re-orient herself when the dialog opens (see rationale below).The *item currently moved* is shown like this:*  its icon is replaced with a *placeholder icon* (the dotted rectangle in the wireframe)* the  The  item *has the mouse hover highlighting* (light gray) ; it . It 's not selected , but has the keyboard focus. *  the  The  item actually *can't be selected*. * Its icon is replaced with a *placeholder icon* (the dotted rectangle in the wireframe)   Note that the wireframe actually shows an even more advanced state of the "move" dialog, which also reveals the root node, offers to duplicate instead of moving the item and features menu buttons to cover all way to move an item (inside, above or below another item). Those are handled in separate tasks (see linked issues).h4. Design rationale behind this decisionWe show the "move" dialog when a user clicks on a "move item" action. This is a rupture in a user's flow, but one we accept as the "move" dialog is the one option that works across devices. We can mitigate the effect of such a rupture by aligning the view presented by the "move" dialog and the view the user had when clicking on the "move" action. Showing a dialog for a move action already represents quite a rapture in a user's flow. We can alleviate some of the pain that causes by presenting the users with a view he saw before the dialog was opened. When starting a "move item" action, we currently open the "move" dialog at the root node. To *avoid forcing the user to re-orient himself, we should actually open the dialog at the exact same location* where the "move item" action was started. h4. Rationale behind this design decisionShowing a dialog for a move action already represents quite a rapture in a user's flow. We can alleviate some of the pain that causes by presenting the users with a view he saw before the dialog was opened. h4. A set of changes that work togetherApart from opening the "move" dialog at the same location you left off from, we're also going to show the item you're actually moving (to help in recreating the same image after the dialog opens) and to expose the root node (to make it clearer how you move things to the top of the hierarchy).Both these changes are already shown in the [attached wireframe|^2 View when move dialog opens.png], but will be added in separate steps (see linked issues). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 31/May/16 2:12 PM 
 
 
 

Labels:
 

 estimate-pm-5.5 ux usability working-with-items 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We'd like to show the item you're currently moving in the "move" dialog in order to avoid having the user to re-orient herself when the dialog opens (see rationale below). 
The item currently moved is shown like this: 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3897) Open the move dialog where the move action started

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3897 
 
 
 
  Open the move dialog where the move action started  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 1 View before move starts.png, 2 View when move dialog opens.png 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 31/May/16 12:03 PM 
 
 
 

Labels:
 

 estimate-pm-5.5 ux usability working-with-items 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3896) Adjust column widths in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3896 
 
 
 
  Adjust column widths in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 In the Tree view of the "Move" chooser dialog, the most important bit of information shown is the hierarchy of nodes in the first column (named "Page", "Asset name", "Node name" or the like). Often however, this *column is too narrow to allow for easy browsing of hierarchies*. We should thus adjust its width the maximize the amount of space available to navigate hierarchies.To *maximize the width of the first column*:# *Remove the empty column* or space to the left of the first column.# Ensure that the *second column occupies at most 30% of the width* available to the Tree view ("Title" in [Pages|^1 Pages app.png] and [Assets|^2 Assets app.png], "Tour operator" in Tours) .Note that this will *have to be adjusted in several apps* and on a as-needed basis. In some cases (e.g. Assets or Tours), the column width is already fine and needs no adjustment.For an examples how this will then look in the Pages app, see [^5 Adjusted columns.png].h4. More than two columns. 3.  If there's more than two columns, (e.g. "Value" and "Type" in [Configuration|^4 Config app.png]), we leave column widths how they currently are. Here, we can only reduce widths, if we also truncate or shorten values shown. The ideal way to truncate the value depends on the value, and should thus probably be customizable. E.g.* For Java class names, we would truncate in-line (show three, four characters of the package name, then an ellipsis, then the class name): "ch.livelife...AbstractStorageSpace"* For people's names, the abbreviation could be "A. Weder" instead of "Andreas Weder".However, this last bit should be the topic of a separate issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3896) Adjust column widths in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3896 
 
 
 
  Adjust column widths in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 In the Tree view of the "Move" chooser dialog, the most important bit of information shown is the hierarchy of nodes in the first column (named "Page", "Asset name", "Node name" or the like). Often however, this *column is too narrow to allow for easy browsing of hierarchies*. We should thus adjust its width the maximize the amount of space available to navigate hierarchies.To *maximize the width of the first column*:# *Remove the empty column* or space to the left of the first column.# Ensure that the *second column occupies at most 30% of the width* available to the Tree view ("Title" in [Pages|^1 Pages app.png] and [Assets|^2 Assets app.png], "Tour operator" in Tours) .Note that this will *have to be adjusted in several apps* and on a as-needed basis. In some cases (e.g. Assets or Tours), the column width is already fine and needs no adjustment. # For an examples how this will then look in the Pages app, see [^5 Adjusted columns.png].h4. More than two columns.3.  If there's more than two columns, (e.g. "Value" and "Type" in  [  Configuration |^4 Config app.png] ), we leave column widths how they currently are. Here, we can only reduce widths, if we also truncate or shorten values shown. The ideal way to truncate the value depends on the value, and should thus probably be customizable. E.g.* For Java class names, we would truncate in-line (show three, four characters of the package name, then an ellipsis, then the class name): "ch.livelife...AbstractStorageSpace"* For people's names, the abbreviation could be "A. Weder" instead of "Andreas Weder".However, this last bit should be the topic of a separate issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3896) Adjust column widths in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3896 
 
 
 
  Adjust column widths in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 In the Tree view of the "Move" chooser dialog, the most important bit of information shown is the hierarchy of nodes in the first column (named "Page", "Asset name", "Node name" or the like). Often however, this *column is too narrow to allow for easy browsing of hierarchies*. We should thus adjust its width the maximize the amount of space available to navigate hierarchies.To *maximize the width of the first column*:# *Remove the empty column* or space to the left of the first column.# Ensure that the *second column occupies at most 30% of the width* available to the Tree view ("Title" in [Pages|^1 Pages app.png] and [Assets|^2 Assets app.png], "Tour operator" in Tours) .Note that this will *have to be adjusted in several apps* and on a as-needed basis. In some cases (e.g. Assets or Tours), the column width is already fine and needs no adjustment. For an examples how this will then look in the Pages app, see [^5 Adjusted columns.png].h4. More than two columns. If there's more than two columns, (e.g. "Value" and "Type" in [Configuration|^4 Config app.png]), we leave column widths how they currently are.  For an examples how this will then look in the Pages app, see [^5 Adjusted columns.png].h4. More than two columnsIf a "move" dialog has more than three columns, we leave things as they are. Here, we can only  reduce  optimize column  widths ,  if we also truncate or shorten values shown. The ideal way to truncate the value depends on the value, and should thus  probably  be customizable. E.g.* For Java class names, we would truncate in-line (show three, four characters of the package name, then an ellipsis, then the class name): "ch.livelife...AbstractStorageSpace"* For people's names, the abbreviation could be "A. Weder" instead of "Andreas Weder".However, this  last bit  should be the topic of a separate issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was 

[magnolia-dev] [JIRA] (MGNLUI-3896) Adjust column widths in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3896 
 
 
 
  Adjust column widths in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 In the Tree view of the "Move" chooser dialog, the most important bit of information shown is the hierarchy of nodes in the first column (named "Page", "Asset name", "Node name" or the like). Often however, this *column is too narrow to allow for easy browsing of hierarchies*. We should thus adjust its width the maximize the amount of space available to navigate hierarchies.To *maximize the width of the first column*:# *Remove the empty column* or space to the left of the first column.# Ensure that the *second column  occupies at most 30% of the width *  giving more details  available to the Tree view  ("Title" in [Pages|^1 Pages app.png] and [Assets|^2 Assets app.png], "Tour operator" in Tours)  occupies *at most 30% of the width* available to the Tree view . ##  Note that this will *have to be adjusted in several apps* and on a as-needed basis. ##  In some cases (e.g. Assets or Tours), the column width is already fine and needs no adjustment.# If there's more than two columns, (e.g. "Value" and "Type" in Configuration), we leave column widths how they currently are. Here, we can only reduce widths, if we also truncate or shorten values shown. The ideal way to truncate the value depends on the value, and should thus probably be customizable. E.g.* For Java class names, we would truncate in-line (show three, four characters of the package name, then an ellipsis, then the class name): "ch.livelife...AbstractStorageSpace"* For people's names, the abbreviation could be "A. Weder" instead of "Andreas Weder".However, this last bit should be the topic of a separate issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
  

[magnolia-dev] [JIRA] (MGNLUI-3896) Adjust column widths in the "move" dialog

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3896 
 
 
 
  Adjust column widths in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 4 Config app.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: