Hi
V7 is really a great platform with a lot of improvements and enhancements has been done without any doubt. I am trying to use V7 but in a few hours of my try, I noticed some RAD functionality which is either missing in V7 or I have missed them. This is not an exhaustive list but thought to share when I have come across.
When I add a new field to an Entity:
1a) V6: when the entity is saved, automatic prompt to add the new field to screen helps in rapid development
1b) in V7, there is no such automatic option, needs to be added manually
When modifying an existing Enum, I do not see the visual designer anymore in V7
Deployment UI to Jelastic is confirmed removed in a separate thread. I use this frequently and believe some of us are using, recommended to keep in V7. We should rather enlarge the scope e.g bring the same for other cloud platforms.
The left-side panel for selecting a different element was much more user-friendly and stable than in v7 from my point of view. For example, when I am displaying DataModel especially when it is a large project where i need to scroll up-down to select specific Entity I can directly easily go to Project property without scroll-up action unline in V7. Can we use Accordion component here in V7 like V6?
5. Generating DB script is way too slow in V7 than v6. It keeps showing the following window for ages (especially when I have a lot of entities e.g. >700)
and finally got the following error:
java.lang.IllegalArgumentException: Argument for @NotNull parameter 'scriptText' of com/haulmont/studio/intellij/ui/dbupdate/tabs/CodeBrowserTab. must not be null See log file for details (/Users/mak/Library/Logs/CubaStudio2018.3/idea.log)
I shall add later as soon as I come across if any but the response from CUBA team is appreciated.
In Studio 7.0 there is no UI for this functionality. You can do it by @Index and @UniqueConstraint in Entity source code.
As an example: @Index(name = "IDX_SOME_NEW_ENTITY", columnList = "NAME, VERSION")
I see more things in terms of lost RAD functionality in V7. Here is some of them
When I search and select a screen in V6, the location of the file is expanded and selected in the file navigation pan on the left as below which is very convenient as switching to the controller or relevant browser/Editor files become very handy.
Whereas in V7, the search option brings a lot of files (more than required and irrelevant mostly e.g. files in “out” directory…) and after selecting it navigation pan remains unchanged and the location is not opened, though the controller file is opened if we click on any event.
When I start or restart the Application Server, V7 starts generating DB Scripts first even there is nothing to create and takes a long time especially when it is a large project it takes a few minutes. It was faster in V6 for some reason (it seems DB script generation is not triggered in this case). Can we make it optional to generate DB scripts in this case?
When I make any changes in a file, there is are some buttons like OK, Apply etc. When we save it deploys the update automatically however since there are no such buttons I am not sure how it is working to deploying any changes.
In v6, I used to specify focus t specific component e.g. field in a screen by updating the id name in the designer
However, in V7, even if i have updated the field ID in the designer I don’t see it in for selection, only container type components are there. Am I missing anything here to get that?
I love those RAD features of STUDIO 6x! here is one more that I don’t see in V7.
In v6.x we could select the appComponents from the list of combo as below
But that combo field is no more existing in v7. This was very useful.
I am sorry that I am bringing missing v6 RAD functionalities which are something I have been using regularly and appreciate they are productive.
In v6 studio, there was an option to modify/create view in screen design mode as follows:
But it is missing in V7 Studio, I can only select an existing.
After going through all the above, I am switching back to v6 studio temporarily with a hope that v7 will get it’s maturity in near future when I shall migrate my project to the new platform 7.