Followup: Should we expect a more fleshed out ui f...

# amper

[arve]

Followup: Should we expect a more fleshed out ui for the IntelliJ plugin further down the line? Hoping for something similar to the Gradle pane (sync, build, clean, publish, other tasks, run for specific module etc. )
I understand we are in very early stage so this isn’t impatience, I just think this will be very important for team adoption.

[joffrey]

This is interesting, because so far we actually have been striving for adding IDE features in the places they are needed instead of an independent pane. To cite a few of these:
• running specific modules is already possible with automatically created run configurations
• run/test in general can be done with gutter icons in front of main / @Test functions, or with shortcuts in different places
• we're working on making explicit sync unnecessary (auto-sync / very fast re-sync)
• we hope that clean is unnecessary either (if caches don't have bugs)
Nevertheless, it would be quite interesting to know what you would want to use it for.

For build, could you please clarify what you use it for? There usually is the Build project action in the IDE, but it was not really implemented for Amper so far, for lack of demand.

For publish, this is usually done from CI/CD machines, but it would be good to have other use cases. Do you publish often from your local machine? Is mostly for publishing to maven local and going to another project?

For running arbitrary tasks, this is a topic we'll definitely look into as part of extensibility. Maybe for this we'll have to actually bring a dedicated Amper tool window.

[arve]

Sorry for late reply 😅

Maybe just a case of old habits die slow but after years of using Gradle I’m very used to having “the build system” in a pane on one side.

In my mental model there is a clear distinction between the editors project-model and the build system’s project-model. (lack of trust i guess?)


It’s very comfortable to have a pane for gradle which visualizes gradle’s world view and lets me perform whatever actions on whatever modules are possible. I noticed i am missing something similar with Amper

I.e. in a multimodule project maybe i want to publish this one package, run tests on that other package, etc