May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19783) Users have problems finding the 'Parent' button in Batch diagram editor

by Tomáš Milata (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19783?page=com.atlassian.jira.plugi... ] Tomáš Milata updated JBIDE-19783: --------------------------------- Attachment: class.png > Users have problems finding the 'Parent' button in Batch diagram editor > ----------------------------------------------------------------------- > > Key: JBIDE-19783 > URL: https://issues.jboss.org/browse/JBIDE-19783 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Priority: Minor > Attachments: class.png > > > When editor content is changed to a nested flows, some users cannot find an appropriate way to return back. > Ideal would be to move the button to the left in the title bar, as Max Andersen said here https://github.com/jbosstools/jbosstools-javaee/pull/326 in the comments. But that is, in my opinion not possible in Sapphire. Or does anybody know a way to achieve that? > Other options for navigation could be: > - action in diagram's context (right click) > - to populate the job xml file in Package explorer with additional children representing subflows (in the same way as java class fields are displayed) > Does anybody have suggestions? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19783) Users have problems finding the 'Parent' button in Batch diagram editor

by Tomáš Milata (JIRA)

Tomáš Milata created JBIDE-19783: ------------------------------------ Summary: Users have problems finding the 'Parent' button in Batch diagram editor Key: JBIDE-19783 URL: https://issues.jboss.org/browse/JBIDE-19783 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: batch Affects Versions: 4.3.0.Beta1 Reporter: Tomáš Milata Priority: Minor When editor content is changed to a nested flows, some users cannot find an appropriate way to return back. Ideal would be to move the button to the left in the title bar, as Max Andersen said here https://github.com/jbosstools/jbosstools-javaee/pull/326 in the comments. But that is, in my opinion not possible in Sapphire. Or does anybody know a way to achieve that? Other options for navigation could be: - action in diagram's context (right click) - to populate the job xml file in Package explorer with additional children representing subflows (in the same way as java class fields are displayed) Does anybody have suggestions? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19781) Open 'Properties' view together with the Batch diagram editor

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19781?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19781: ----------------------------------------------- On the other hand, Tree tab has forms that make Properties view unnecessary when it is selected. So, maybe, the prompt should be not right on editor opening, but postponed to the first selecting of Diagram tab. > Open 'Properties' view together with the Batch diagram editor > ------------------------------------------------------------- > > Key: JBIDE-19781 > URL: https://issues.jboss.org/browse/JBIDE-19781 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.0.Beta1 > > > Users have problems to find where to edit properties like item readers or batchlet refs. > If the Properties view is not open when editor is started, they do not have the idea to use it. > So I suggest to open it always when diagram is opened or changes its inner model element. Or do you have a better idea? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19781) Open 'Properties' view together with the Batch diagram editor

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19781?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-19781 at 5/8/15 10:23 PM: ------------------------------------------------------------------------ org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor Method createPages() in the end calls checkPalette(). It is implemented so that it opens Palette in this forced way only once ever for the workspace. As soon as user closes Palette view, it should be opened manually. I think the same approach would be consistent for Batch Editor + Properties. Though, there is one difference. Palette is shown in the section to the right of the editor which it shares with only Outline. Properties is shown in the bottom section shared by a lot of views, so that it is quite probably that another view in the bottom is selected. Maybe, on making sure that Properties is not selected, we can show dialog asking 'Properties view is very useful for Batch Diagram, would you like to open it now?', and of course with check box 'Never show this dialog again' or 'Remember my choice'. was (Author: scabanovich): org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor Method createPages() in the end calls checkPalette(). It is implemented so that it opens Palette in this forced way only once ever for the workspace. As soon as user closes Properties view, it should be opened manually. I think the same approach would be consistent for Batch Editor + Properties. Though, there is one difference. Palette is shown in the section to the right of the editor which it shares with only Outline. Properties is shown in the bottom section shared by a lot of views, so that it is quite probably that another view in the bottom is selected. Maybe, on making sure that Properties is not selected, we can show dialog asking 'Properties view is very useful for Batch Diagram, would you like to open it now?', and of course with check box 'Never show this dialog again' or 'Remember my choice'. > Open 'Properties' view together with the Batch diagram editor > ------------------------------------------------------------- > > Key: JBIDE-19781 > URL: https://issues.jboss.org/browse/JBIDE-19781 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.0.Beta1 > > > Users have problems to find where to edit properties like item readers or batchlet refs. > If the Properties view is not open when editor is started, they do not have the idea to use it. > So I suggest to open it always when diagram is opened or changes its inner model element. Or do you have a better idea? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19780) Confusing <id> placeholder in Batch Diagram editor

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19780?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19780: ----------------------------------------------- Can we implement generating new id that user can change for the new element? It is better when new element is created making correct xml. > Confusing <id> placeholder in Batch Diagram editor > -------------------------------------------------- > > Key: JBIDE-19780 > URL: https://issues.jboss.org/browse/JBIDE-19780 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.0.Beta1 > > > Currently, when no id of an element is entered, the "<id>" label is displayed in the node. > This caused issues during usability testing. User for some reason thought the "<>" characters have some meaning and edited the value to "<myId>" and then was confused why he sees "&lt" and "&gt" sequences in the XML. > Note that sapphire does not have placeholders, so this is just a workaround (when id is null, the <id> text is shown). > This approach is has also disadvantage that if user double click the <id> of empty id, presses an arrow and then enter, the whole <id> value originally meant as a placeholder is now the literal value of the property. > I suggest keeping the place for label just empty. User can be still notified by a validation marker and the label inline editor is still accessible by double click. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19781) Open 'Properties' view together with the Batch diagram editor

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19781?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-19781 at 5/8/15 9:50 PM: ----------------------------------------------------------------------- org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor Method createPages() in the end calls checkPalette(). It is implemented so that it opens Palette in this forced way only once ever for the workspace. As soon as user closes Properties view, it should be opened manually. I think the same approach would be consistent for Batch Editor + Properties. Though, there is one difference. Palette is shown in the section to the right of the editor which it shares with only Outline. Properties is shown in the bottom section shared by a lot of views, so that it is quite probably that another view in the bottom is selected. Maybe, on making sure that Properties is not selected, we can show dialog asking 'Properties view is very useful for Batch Diagram, would you like to open it now?', and of course with check box 'Never show this dialog again' or 'Remember my choice'. was (Author: scabanovich): org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor Method createPages() in the end calls checkPalette(). It is implemented so that it opens Palette in this forced way only once ever for the workspace. As soon as user closes Properties view, it should be opened manually. I think the same approach would be consistent for Batch Editor + Properties. > Open 'Properties' view together with the Batch diagram editor > ------------------------------------------------------------- > > Key: JBIDE-19781 > URL: https://issues.jboss.org/browse/JBIDE-19781 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.0.Beta1 > > > Users have problems to find where to edit properties like item readers or batchlet refs. > If the Properties view is not open when editor is started, they do not have the idea to use it. > So I suggest to open it always when diagram is opened or changes its inner model element. Or do you have a better idea? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19781) Open 'Properties' view together with the Batch diagram editor

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19781?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19781: ----------------------------------------------- org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor Method createPages() in the end calls checkPalette(). It is implemented so that it opens Palette in this forced way only once ever for the workspace. As soon as user closes Properties view, it should be opened manually. I think the same approach would be consistent for Batch Editor + Properties. > Open 'Properties' view together with the Batch diagram editor > ------------------------------------------------------------- > > Key: JBIDE-19781 > URL: https://issues.jboss.org/browse/JBIDE-19781 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.0.Beta1 > > > Users have problems to find where to edit properties like item readers or batchlet refs. > If the Properties view is not open when editor is started, they do not have the idea to use it. > So I suggest to open it always when diagram is opened or changes its inner model element. Or do you have a better idea? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19782) Validation markers in Batch diagram seem like delete buttons to users

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19782?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19782: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Validation markers in Batch diagram seem like delete buttons to users > --------------------------------------------------------------------- > > Key: JBIDE-19782 > URL: https://issues.jboss.org/browse/JBIDE-19782 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Fix For: 4.3.0.Beta1 > > > I guess moving the markers from right to left should help i little. Left is the usual location for validation markers in eclipse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19770) linux distro not tracked reliable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19770?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19770: ---------------------------------------- There is no any universal way to get the linux distro name. It depends on the distro. I added more distro specific detectors for some popular previously untracked distros: Arch, Mageia, Puppy, openSUSE (might be tracked as SUSE). Also improved detection for distro we have already been tracked. If no any specific distro detected then we now try to get the name from *os-release* file (if exists): http://www.freedesktop.org/software/systemd/man/os-release.html I hope it will help to improve the linux distro detection. > linux distro not tracked reliable > --------------------------------- > > Key: JBIDE-19770 > URL: https://issues.jboss.org/browse/JBIDE-19770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > user defined value is not set in ~50% of cases of linux users. > https://www.google.com/analytics/web/?hl=en#report/content-pages/a1764536... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19782) Validation markers in Batch diagram seem like delete buttons to users

by Tomáš Milata (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19782?page=com.atlassian.jira.plugi... ] Tomáš Milata updated JBIDE-19782: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/334 > Validation markers in Batch diagram seem like delete buttons to users > --------------------------------------------------------------------- > > Key: JBIDE-19782 > URL: https://issues.jboss.org/browse/JBIDE-19782 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > > I guess moving the markers from right to left should help i little. Left is the usual location for validation markers in eclipse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2015