petalslink / petals-studio Goto Github PK

Instead of 1.6.

In fact, values are suppsoed to be predefined but are not displayed in the wizards.
And they are not set in the final result. 💢

The wizard and the editor need to be completed.

It seems we miss some plugin.

java.lang.ClassNotFoundException: org.eclipse.jgit.lfs.BuiltinLFS cannot be found by org.eclipse.egit.core_5.0.0.201806131550-r

There are still few things to do for the editor.

The (c) mentions have been updated several years ago.
But the module names have not changed. com.ebmwebsourcing.* 🔜 com.linagora.*

Clicking a tab makes a scroll bar appear (while it is not necessary).

Simple text fields were much better.

Add screenshots, among other things.

Currently, there are two bundles that embed JAR files (...).
This issue is about...

• ... removing these files. Or at least, add them to the .gitignore.
• ... updating the build to download them.

We will rewrite the Git history later.

Once we have done the next release, remove all the JAR files from the history.
That will make the Git repo lighter. Do not forget to prune the repository to remove orphan commits.

Links are outdated.

Currently, we have two wizards for service units, one for service providers and one for service consumers. Each wizard has its own choice page, that gathers Petals components by use case (communication protocols, service composition, etc). This page also allows to select the component version to use.

This page is ugly.
That makes the studio look like... its real age. I also think we should rely on the idea users know what is an engine and what is a connector. JBI concepts adds too much complexity. So, maybe we should hide this. Anyway, let's just keep a single wizard for service units, and let's update the choice page: connectors VS. engines, a description of the use case (provides or consumes), plus the choice of the version. That's it.

Or make it open the source editor when one clicks on it.