User story #12740
Make conditions visible in the Technique editor
I already suggested this a few times, and you also agreed times it would be useful. But probably there's no story for it so far which might be why it never happened:
If in the NCF editor a condition is set for method, there's no visual way to tell so if the "conditions" area is folder.
This is a workflow issue - there is not enough space on the screen, so we need to usually keep it folded.
But we might not be aware of the conditions we got until we unfold it.
If you got a few methods in the technique you need to go through all of them, etc.
I would be ieasiest if there was a somewhat-subtle-but-not-too-subtle color coding on the conditions/classes area if one is set (other than "any").
I suppose that is a 15 minute hack that would immediately help all users.
A smart bonus would be to scan all those conditions and then also flag in colour all return classes that are currently used somewhere.
(need to update on technique save, and now it's not a 15 min hack anymore. but you'd be 1/3 way to a full dependency graph though all of NCF)
Updated by François ARMAND over 2 years ago
- Tracker changed from User story to Bug
- Assignee set to Raphael GAUTHIER
- Target version set to 4.1.13
- Suggestion strength deleted (
Want - This would make my life a lot easier but I can manage without)
- Priority set to 0
I ok with it being called a bug because I'm pretty sure we already did something to make non default filter be immediatly visable, and it seems to not have worked out as expected.
Updated by Florian Heigl almost 2 years ago
From my end, already overkill. just give it a slighly different colour. The screen estate management of NCF is already pretty "challenged", your change increases use by 30%, meaning 30% less fits. Try around some more and imagine how to make it help you.
Updated by Vincent MEMBRÉ almost 2 years ago
Thanks for you feedback Florian !
Yes I also want to try some colors on condition/parameter, I think on the small 'title', don't yet which one ( I think some blue )
I'm also thinking of having the value on the same line than the 'title'
What still need to be done (but should be ok as v1, if v2 comes soon):
- Add a way to expand the value at will (not display 4k value by default ... )
Things that have changes you can't see in a picture:
- Fix the fact that you couldn't copy/paste the parameter ( and the new condition, they follow the same scheme) (js/css hell to make it selectable ...)
- But on counterpart you can only drag/drop with left side (the ::: part), which is a common/basic way to indicate a draggable element, so i guess it's better (it was messing with the click action)
Next steps (this week, in another issue):
- Remove some icons on the central part( up/down arrow which are useless since can drag/drop, windows/cog icons ... )
- Add clone action to clone a generic method
- I need to think about the way we select/edit a generic method, The arrow may be replaced by a pen "button"
- Filter on generic methods
Updated by François ARMAND almost 2 years ago
@florian: I think it's important to see the condition because one use case that is extremelly itchy right now is: I need to change the condition for that technique from "condA" to "condA.condB" (and then it happens it's more like "(condA.condB | condC).condD etc") and I need to be able, with just a glance, to see if al the cond are consistant or if I still messed up some of them".
Perhaps I'm more enclined to other to miss a copy and paste or forget if I changed something in three or the whole four methods (and on which), but it's extremelly important for me. And for that, I need to be able to see them all at once.
That being said, and to concure with @Vincent, we need to simplify the displaying of a technique so that the list of generic let the logic be much more apparent.
Idea: write nothing when no condition ; if a condition is present, add a "if: cond" before the method name, pehaps with some visual parenthesing (a border of color with the same color than the if ?)
Updated by Florian Heigl almost 2 years ago
@fanf I understand your reasoning, and it would be helpful.
But: I keep trying to get this simple change for 3 years now. The way I suggested takes away no screen estate.
Now you're suggesting to build it in a way that will get us A (but not in a highly visual way but one that requires a lot more reading and does NOT do the one main thing this was about: "highlight where it matters") but on the other end, B, you increase the amount of screen estate used meaning NCF will be even less usable as it is now.
This will NOT be an improvement.