February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1569) Forge dialogs do not obtain focus on launch

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/FORGE-1569?page=com.atlassian.jira.plugin... ] Koen Aers commented on FORGE-1569: ---------------------------------- I have actually looked into this. It only happens on Linux so I had to rely on a VM to reproduce it (quite annoying, /me needs more hardware). The bad news is that I didn't really figure out the reason as to why the wizard doesn't get the focus. The 'New Wizards' get focus so it should be possible but I haven't found any clue (yet) as to why the Forge wizards behave differently... > Forge dialogs do not obtain focus on launch > ------------------------------------------- > > Key: FORGE-1569 > URL: https://issues.jboss.org/browse/FORGE-1569 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.0.0.Final > Environment: Fedora 17, Eclipse Kepler > Reporter: Vineet Reynolds > Priority: Minor > Fix For: 2.x Future > > > When I launch a new Forge dialog in Eclipse, it does not automatically obtain focus. For a keyboard user, this is slightly frustrating, as this requires Alt-Tabbing back and forth to Eclipse for the dialog to obtain eventually focus. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1571) Shell UISelect options are set with partial values when auto-completing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1571?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1571. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Cannot Reproduce Bug Fixed in FORGE-1537 > Shell UISelect options are set with partial values when auto-completing > ----------------------------------------------------------------------- > > Key: FORGE-1571 > URL: https://issues.jboss.org/browse/FORGE-1571 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Priority: Critical > > FORGE-1537 introduced a validation for invalid values in UISelectOne/Many components. However, during auto-completion, the shell implementation attempts to set the partial value (correctly converted to null, because it is not present in the value choices) > Eg: > {code} > jpa-setup --container JB<TAB> > {code} > The validation in https://github.com/forge/core/blob/master/ui/api/src/main/java/org/jboss/... is the culprit. Removing it, the value is correctly set to null, however it breaks FORGE-1537. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1537) Able to create a constraint on a non existing field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1537?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1537. ---------------------------------- Resolution: Done Removed default value for onProperty input > Able to create a constraint on a non existing field > --------------------------------------------------- > > Key: FORGE-1537 > URL: https://issues.jboss.org/browse/FORGE-1537 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > I've created a few fields on an entity and add some constraints to those fields. Everything is ok. But when I add a constraint to a field that doesn't exit, then it adds the constraint to the last created field (looks a bit random actually). > So if I type : > {code} > [Artist.java]$ constraint-add --onProperty dummy --constraint NotNull > ***SUCCESS*** Constraint NotNull successfully configured > {code} > dummy doesn't exist, so it adds NotNull to other attributes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1571) Shell UISelect options are set with partial values when auto-completing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1571?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1571: ----------------------------------- Description: FORGE-1537 introduced a validation for invalid values in UISelectOne/Many components. However, during auto-completion, the shell implementation attempts to set the partial value (correctly converted to null, because it is not present in the value choices) Eg: {code} jpa-setup --container JB<TAB> {code} The validation in https://github.com/forge/core/blob/master/ui/api/src/main/java/org/jboss/... is the culprit. Removing it, the value is correctly set to null, however it breaks FORGE-1537. was: FORGE-1537 introduced a validation for invalid values in UISelectOne/Many components. However, during auto-completion, the shell implementation attempts to set the partial value (correctly converted to null, because it is not present in the value choices) Eg: {code} jpa-setup --container JB<TAB> {code} The validation in https://github.com/forge/core/blob/master/ui/api/src/main/java/org/jboss/... is the culprit. Removing it, the value is correctly set to null, however it breaks FORGE-1537. > Shell UISelect options are set with partial values when auto-completing > ----------------------------------------------------------------------- > > Key: FORGE-1571 > URL: https://issues.jboss.org/browse/FORGE-1571 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > FORGE-1537 introduced a validation for invalid values in UISelectOne/Many components. However, during auto-completion, the shell implementation attempts to set the partial value (correctly converted to null, because it is not present in the value choices) > Eg: > {code} > jpa-setup --container JB<TAB> > {code} > The validation in https://github.com/forge/core/blob/master/ui/api/src/main/java/org/jboss/... is the culprit. Removing it, the value is correctly set to null, however it breaks FORGE-1537. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1537) Able to create a constraint on a non existing field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1537?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1537: ------------------------------------ Reopening this issue, since some collateral effects were found > Able to create a constraint on a non existing field > --------------------------------------------------- > > Key: FORGE-1537 > URL: https://issues.jboss.org/browse/FORGE-1537 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > I've created a few fields on an entity and add some constraints to those fields. Everything is ok. But when I add a constraint to a field that doesn't exit, then it adds the constraint to the last created field (looks a bit random actually). > So if I type : > {code} > [Artist.java]$ constraint-add --onProperty dummy --constraint NotNull > ***SUCCESS*** Constraint NotNull successfully configured > {code} > dummy doesn't exist, so it adds NotNull to other attributes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1571) Shell UISelect options are set with partial values when auto-completing

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1571: -------------------------------------- Summary: Shell UISelect options are set with partial values when auto-completing Key: FORGE-1571 URL: https://issues.jboss.org/browse/FORGE-1571 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Final Reporter: George Gastaldi Priority: Critical Fix For: 2.x Future FORGE-1537 introduced a validation for invalid values in UISelectOne/Many components. However, during auto-completion, the shell implementation attempts to set the partial value (correctly converted to null, because it is not present in the value choices) Eg: {code} jpa-setup --container JB<TAB> {code} The validation in https://github.com/forge/core/blob/master/ui/api/src/main/java/org/jboss/... is the culprit. Removing it, the value is correctly set to null, however it breaks FORGE-1537. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1570) Introduce UICommandEnricher to the UI API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1570?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1570. ---------------------------------- Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done > Introduce UICommandEnricher to the UI API > ----------------------------------------- > > Key: FORGE-1570 > URL: https://issues.jboss.org/browse/FORGE-1570 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > A {{UICommandEnricher}} provides an extension point for the UI API to allow a UICommand to be modified before executing. > Implementations may, but not limited to: > - add security features to it; > - Add Pre/post steps to a UIWizard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1570) Introduce UICommandEnricher to the UI API

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1570: -------------------------------------- Summary: Introduce UICommandEnricher to the UI API Key: FORGE-1570 URL: https://issues.jboss.org/browse/FORGE-1570 Project: Forge Issue Type: Feature Request Components: UI - API Affects Versions: 2.0.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.x Future A {{UICommandEnricher}} provides an extension point for the UI API to allow a UICommand to be modified before executing. Implementations may, but not limited to: - add security features to it; - Add Pre/post steps to a UIWizard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1537) Able to create a constraint on a non existing field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1537?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1537. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done It was a bug in the UI addon. Now the output is as follows: {code} [demo]$ constraint-add --onProperty dummy --constraint Max --value 10 Exception when parsing/running: constraint-add --onProperty dummy --constraint Max --value 10, Error while creating parser: 'dummy' is not a valid value for onProperty {code} > Able to create a constraint on a non existing field > --------------------------------------------------- > > Key: FORGE-1537 > URL: https://issues.jboss.org/browse/FORGE-1537 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > I've created a few fields on an entity and add some constraints to those fields. Everything is ok. But when I add a constraint to a field that doesn't exit, then it adds the constraint to the last created field (looks a bit random actually). > So if I type : > {code} > [Artist.java]$ constraint-add --onProperty dummy --constraint NotNull > ***SUCCESS*** Constraint NotNull successfully configured > {code} > dummy doesn't exist, so it adds NotNull to other attributes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1569) Forge dialogs do not obtain focus on launch

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1569: -------------------------------------- Summary: Forge dialogs do not obtain focus on launch Key: FORGE-1569 URL: https://issues.jboss.org/browse/FORGE-1569 Project: Forge Issue Type: Feature Request Components: UI - Eclipse Affects Versions: 2.0.0.Final Environment: Fedora 17, Eclipse Kepler Reporter: Vineet Reynolds Priority: Minor Fix For: 2.x Future When I launch a new Forge dialog in Eclipse, it does not automatically obtain focus. For a keyboard user, this is slightly frustrating, as this requires Alt-Tabbing back and forth to Eclipse for the dialog to obtain eventually focus. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014