Learn from Mu editor

[almarklein]

I'm impressed with the Mu editor. We could learn a thing or two from it. Further, I wonder if an IDE can be designed so it grows along with the user; start real simple like Mu, and then expose more features as the user progresses and becomes something like Pyzo/Spyder.

• Hide stuff that cannot be used (e.g. debug buttons)
• Toolbar. I've always been against it, but I now also see how it's important for newcomers. But would only do this in a way that can "grow".

[kelsa-pi]

Hi,

Toolbar. I've always been against it, but I now also see how it's important for newcomers. But would only do this in a way that can "grow".

Can you expand on "grow"?

Best

[almarklein]

I meant that it should initially be simple, like Mu, but users should be able to add and remove items easily. In a more general way, I mean that I don't simply want to add a toolbar. It must be an integral part of the IDE, and also e.g. help users adopt using keyboard shortcuts. It definitely needs more thought than I've given it so far :)

[CAM-Gerlach]

FWIW, a big focus for Spyder 5, which should be out next month, was a comprehensive plugin architecture such that everything, from the toolbar to the editor to the console to the many different panes, is actually a modular plugin and can be enabled/disabled as the user wishes, while external/third party plugins have the same power as built-in IDE components. So, you could create a stripped-down Spyder that only exposed the very basics, or a tricked out one with advanced third party features, depending on your needs. There was already basic plugin and pane support in earlier versions, but it was much more limited and not customizable. Not sure if that's something you're interested in or something Pyzo would want to emulate, but just wanted to mention that.