[JBoss JIRA] (DROOLS-4647) Update History (undo & redo actions) to support Background grid
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4647?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4647:
--------------------------------
Description:
The current incorrect behavior of undo for background tabs is shown in the video [^undo.webm]
h2. Acceptance criteria
The undo/redo action should be taken on the correct tab.
> Update History (undo & redo actions) to support Background grid
> ---------------------------------------------------------------
>
> Key: DROOLS-4647
> URL: https://issues.jboss.org/browse/DROOLS-4647
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Fix For: 7.6.0.Final
>
> Attachments: undo.webm
>
>
> The current incorrect behavior of undo for background tabs is shown in the video [^undo.webm]
> h2. Acceptance criteria
> The undo/redo action should be taken on the correct tab.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-4619:
-------------------------------------
[~manstis] Question about version b) would be the dropdown still hidden below canvas or would be there and html element for it? Asking because of selenium tests.
> Hard to figure out how to select what type of expression the DMN decision will be
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-4619
> URL: https://issues.jboss.org/browse/DROOLS-4619
> Project: Drools
> Issue Type: Enhancement
> Reporter: Alexandre Bakos
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png, dropdown-new.png, icon-new.png, icon-only.png, icon_introtip.png, mock1.png
>
>
> I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table.
> I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression.
> A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4662) Resources added through KieHelper get interpreted using the default character set
by Max Zerzouri (Jira)
[ https://issues.jboss.org/browse/DROOLS-4662?page=com.atlassian.jira.plugi... ]
Max Zerzouri updated DROOLS-4662:
---------------------------------
Affects Version/s: 7.28.0.Final
7.20.0.Final
7.10.0.Final
> Resources added through KieHelper get interpreted using the default character set
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-4662
> URL: https://issues.jboss.org/browse/DROOLS-4662
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.10.0.Final, 7.20.0.Final, 7.28.0.Final
> Environment: Windows. Can be reproduced on other OSes using "-Dfile.encoding=latin1".
> Reporter: Max Zerzouri
> Assignee: Mario Fusco
> Priority: Major
> Attachments: Test.java
>
>
> When a resource is added using {{KieHelper.addResource}}, any specified encoding is ignored when it is added to the {{MemoryFileSystem}} by {{KieFileSystemImpl.write(Resource)}} (effectively assuming the {{InputStream}} is already encoded in UTF-8).
> Additionally, when the resource is read again by {{AbstractKieModule.getResource}}, it constructs a {{Resource}} object with no encoding specified, whereas it should probably specify an encoding of UTF-8, since it seems that sources are considered to be UTF-8 already at least in the case of the {{MemoryKieModule}}.
> I've attached a fairly minimal test case where the rules bytes are passed in UTF-8 with the encoding explicitly specified. This currently produces an error when the default file encoding is not UTF-8 (eg, by passing {{-Dfile.encoding=latin1}} as a JVM argument, or by using the default arguments on Windows).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4662) Resources added through KieHelper get interpreted using the default character set
by Max Zerzouri (Jira)
Max Zerzouri created DROOLS-4662:
------------------------------------
Summary: Resources added through KieHelper get interpreted using the default character set
Key: DROOLS-4662
URL: https://issues.jboss.org/browse/DROOLS-4662
Project: Drools
Issue Type: Bug
Environment: Windows. Can be reproduced on other OSes using "-Dfile.encoding=latin1".
Reporter: Max Zerzouri
Assignee: Mario Fusco
Attachments: Test.java
When a resource is added using {{KieHelper.addResource}}, any specified encoding is ignored when it is added to the {{MemoryFileSystem}} by {{KieFileSystemImpl.write(Resource)}} (effectively assuming the {{InputStream}} is already encoded in UTF-8).
Additionally, when the resource is read again by {{AbstractKieModule.getResource}}, it constructs a {{Resource}} object with no encoding specified, whereas it should probably specify an encoding of UTF-8, since it seems that sources are considered to be UTF-8 already at least in the case of the {{MemoryKieModule}}.
I've attached a fairly minimal test case where the rules bytes are passed in UTF-8 with the encoding explicitly specified. This currently produces an error when the default file encoding is not UTF-8 (eg, by passing {{-Dfile.encoding=latin1}} as a JVM argument, or by using the default arguments on Windows).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months