Tweet
This little 1/3 of the screen on the side makes it extremely difficult to do real editing of a formula; that model popup needs to be full screen
-
-
really? I never had problems with that. Do you format your formulas or let them get spaghettied?-
my other colleague isn't a programmer so i get a spaghetti mess
but even apart from that its just too short for a lot of code, especially as the Espo formula is fairly long-winded
i guess you don't do very complex formulas? we regularly do 5 pages plus and that tiny window is just too small
i see you don't have a problem but for me its a rather major source of annoyance and every time i have to do work in it i have to change out the css
would be a simple change that would improve my life, but then there seems to be not a lot of care about developers here -
the complexity of a formula is mirrored in very long lines of code? Strange point of view honestly.
I try to help. Although you having the holy grail of everything, no need to be offensive to the developers, which I got to know over my six years journey with espoCRM as attentive, willing to help and before all very skilled.
If you would pay attention to the mood in this forum, perhaps you already would have perceived (perhaps not), that here you will find helpful people. And friendly. Why then your reaction is always as if all the others are idiots, but you?
-
-
I think there’s been a slight misunderstanding in how my comment is being interpreted.
I’m not suggesting that anyone else is doing things incorrectly, or that their workflows are invalid. I’m saying that in my case, I’m still running into the same problem, regardless of how others have adapted to the current behaviour, and i find it to be unnecessary, whereas a simple number change in the CSS will enable a much better developer experience
It’s great that some users have developed effective workarounds and are happy with the system as it is. However, those approaches don’t address the issue I’m facing, and therefore don’t solve the requirement I’m raising.
What I’m proposing is a small change that would improve usability for users in my situation, particularly around making the interface more flexible and reducing friction when working with longer or variable-length data. From my perspective, even a relatively simple UI adjustment could significantly improve the experience.
I fully appreciate the feedback and alternative approaches being shared, but not adopting those workflows doesn’t mean they’re wrong — it just means my requirements are different.
The intent here is not to dismiss existing usage patterns, but to highlight an area where the current design doesn’t fully meet all use cases, particularly for programmers or enterprise contexts.
so in summary, you might be happy to work around a bad ux desinge, but as someone who's been doing this for over 20 years i will propose improvements where i see a gap, and i really don't expect much response as developers seem not to really care about user experience
Comment
-
rabii in particular the before save, but really any where i have to enter a formula, the box is only good for small things but our company has (probably) way too much logic in there and having such a small box just makes it harder to develop and debug for no reason
Comment
Comment