[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ] Gabriele Cardosi edited comment on DROOLS-3154 at 10/26/18 3:21 AM: -------------------------------------------------------------------- [~uxdlc] About Index/Description header: Maybe it is possible, but surely it is not just a "delete one line" operation; so, for the moment being I would keep them there. /----/ About this header menu: Liz, please, *I'm* asking you what to do. I just underlined to you what (from my point of view) could be a little un-consistence. Please tell me, without keeping asking, what do you prefer the interaction to be, I'm not in love with any of those menu, I can live without. If you want them to be removed, I remove. If you want them to be renamed, I rename. If you want a different interaction, I'll implement. About that document you keep referring to, it can not be considered final by any mean. It is only using the real software while is developed that you may understand what is actually needed, what needs to be changed, and so on and so forth. I'm using it all the day, and whatever doubt or objection I raise is due to the actual usage, being myself not only a "developer" but also a "user". And that drive to my last consideration: if you were able to use a real instance of the scenario is *great*, but now we need a way so that you may look at what I'm currently doing: my last PR (3095), the multi-instance, has a huge impact and implications, and it is taking a lot of time: to wait for you to see it until is merged in master would be a big waste of time, because surely I'm doing things with "developer" eye, that has never matched, in historical reports, UX one :). was (Author: gabriolo): [~uxdlc] About Index/Description header: Maybe it is possible, but surely it is not just a "delete one line" operation; so, for the moment being I would keep them there. /----/ About this header menu: Liz, please, *I'm* asking you what to do. I just underlined to you what (from my point of you) could be a little un-consistence. Please tell me, without keeping asking, what do you prefer the interaction to be, I'm not in love with any of those menu, I can live without. If you want them to be removed, I remove. If you want them to be renamed, I rename. If you want a different interaction, I'll implement. About that document you keep referring to, it can not be considered final by any mean. It is only using the real software while is developed that you may understand what is actually needed, what needs to be changed, and so on and so forth. I'm using it all the day, and whatever doubt or objection I raise is due to the actual usage, being myself not only a "developer" but also a "user". And that drive to my last consideration: if you were able to use a real instance of the scenario is *great*, but now we need a way so that you may look at what I'm currently doing: my last PR (3095), the multi-instance, has a huge impact and implications, and it is taking a lot of time: to wait for you to see it until is merged in master would be a big waste of time, because surely I'm doing things with "developer" eye, that has never matched, in historical reports, UX one :). -- This message was sent by Atlassian Jira (v7.12.1#712002)