Hi guys, this is a bit about how I feel on the current state of Amber Smalltalk development experience: https://medium.com/@sebastianconcpt/improving-the-amber-experience-26764d5d578 and some issues:
thanks for letting me know You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Hello Sebastian, thanks for writing down your thoughts. But after reading your article it is still not clear to me what issues you are having with Helios. Your statement about 'lower productivity' is not a very concrete meassure :-) Maybe it would make sense to address concrete issues and improve Helios in that direction (I am pro Helios). Overall, I don't think that it is possible to support two IDE's with the current amount of contributors. Best, Manfred On Sat, Jan 31, 2015 at 2:19 PM, Sebastian Sastre <[hidden email]> wrote:
You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Manfred Kröhnert wrote: > Hello Sebastian, > > thanks for writing down your thoughts. > But after reading your article it is still not clear to me what issues > you are having with Helios. > Your statement about 'lower productivity' is not a very concrete > meassure :-) > > Maybe it would make sense to address concrete issues and improve Helios > in that direction (I am pro Helios). > Overall, I don't think that it is possible to support two IDE's with the > current amount of contributors. Agree with points of making Helios better. OTOH, if someone feels like legacy IDE has potential (I was hesitating long time to move to Helios, because legacy IDE with its minimalism was really easy to use still is stronger in search - https://github.com/amber-smalltalk/helios/issues/5 and of course https://github.com/amber-smalltalk/helios/issues/14), I would not stop him. Having two IDEs can bring one plus: isolating generic reflection service into Amber itself and having only IDE-related things in IDE. > Best, > Manfred > > > On Sat, Jan 31, 2015 at 2:19 PM, Sebastian Sastre > <[hidden email] <mailto:[hidden email]>> wrote: > > Hi guys, > > this is a bit about how I feel on the current state of Amber > Smalltalk development experience: > https://medium.com/@sebastianconcpt/improving-the-amber-experience-26764d5d578 > > and some issues: > > * > * Typography issues > * Poor contrast issues > * Focus issues > * Lack of search keyboard shortcut > * Tab close area too small > * SUnit button alignment > * Horizontal arrow keys should change the pane in focus (on > Browser and SUnit) > * Vertical arrow keys should change the selected list item when > focus is in a list pane > * Save button disabled on pristine > * Class browse shortcut > * Drag and drop to categorise methods > * Marking changed packages > * Select and change theme easily and persist the preference on > localStorage > * Change theme to be dark by default > > and main question being: I'm alone in this (should I fork and do) or > not (should I commit to official repo)? > > thanks for letting me know -- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by Manfred Kröhnert
Ah well.. if you are asking for a scientific study with data to prove it, I don’t owe you one but we could talk about funding one if you really have that interest :)
Lower productivity gets concrete really fast when is you who pay for it. That is persuasive enough to me. So as I said in the article, I have the clear impression that fixing the Legacy IDE (or Classic IDE as Philippe suggested to call it) is way easier than fixing Helios. Even fixing the main Helios issues would not convert me as opening one IDE versus the other is comparing something with a sub-second response versus a pop-up that makes a full load of an extra amber application. That’s a deal-breaker to me. That doesn’t mean that I wouldn’t enjoy seeing people improving Helios, it only means that I (sebastian) decided to route any effort about IDE to the legacy/classic IDE. If you or anyone wants to make Helios better, he/she has my (passive) support
You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Hi Sebastian On Sun, Feb 1, 2015 at 3:24 PM, sebastian <[hidden email]> wrote:
Interesting answer. But I won't go into details about such 'counter arguments'... You asked about feedback and now you are bashing the feedback? Please stay constructive. In my last email I was only saying that arguments like "this is wrong!" are very mood if you don't provide some backup for a statement.
Okay, but what is it that makes you less productive? Is it about too many clicks you have to perform, too many keystrokes to remember, too much lag in the UI, cursing about finding the right information? We can only improve Helios if we know what makes it less productive.
Right, but what needs to be improved in Helios to make it usable to you? That is the only thing I am asking. Actually, I support your ideas for improving Classic IDE. But it would be even greater if Helios were be brought to a point where it is equally usable to you.
Cool, this is a concrete example about what makes Helios less usable to you. For me, it doesn't make a huge difference, since the IDE is only opened once during startup. However, making Helios load faster and/or in-frame seems to be something worth investigating if this is of concern to you and other IDE users.
Best, Manfred
You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Ah. That would be me :-) I want a search box in Helios anyway. Phil You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by Manfred Kröhnert
Yes I don’t want to inhibit your feedback with my answers. We shouldn’t confuse bashing with provocation :) I found provocation stimulating. For me the widely positive output is more important than being constructive locally.
Helios would gain a second chance to try for me if it becomes as friendly to the mouse as it is to keyboard and instant opening. Also those sequences of keypresses, if they are the only way to do things that’s a big no-no. Check the list I’ve made for legacy and you’ll certainly have more concrete examples of what doesn’t make Helios work for me. This is something I can’t even understand. In my experience too often any app needs to reload page during the development cycle. Dozens of times per session.
-- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
On Sun, Feb 1, 2015 at 8:54 PM, sebastian <[hidden email]> wrote:
Don't confuse poor argumentation with provocation.
Now we are getting somewhere. Why not provide such an answer in the first place? Best, Manfred
You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
On Sunday, February 1, 2015 at 7:09:40 PM UTC-2, MKroehnert wrote:
Well you see.. the "poor argumentation" was enough to make the point and, as already mentioned, there are economic reasons that show that the strategy was good enough. The really good part is the attitude on how it was received here because you and others showed interest in improving Helios. That's great. I'm looking forward to the outcome of that.
It was public right from the beginning but we needed "to talk about it" to connect the dots :D Thanks again for your feedback and a great discussion. seb o/
You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Free forum by Nabble | Edit this page |