<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="text-align:left; direction:ltr;">
<div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
I'm enjoying the better / smoother functionality of this vs the Eclipse Plugin. One tiny issue I just ran into just now: it would be nice for the event log to indicate which environment it communicated with. I just finished up something new that I had been
testing on devel. I thought I hit the upload button to go to prod, but that didn't happen. So when I went to validate in prod, it wasn't working. And the fact that I went from devel to prod in about a minute, the timestamp didn't help. So I think this would
be a nice quality of life improvement for those of us that frequently and quickly change environments.</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
<br>
</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
The other nice thing would be to know which intent I'm operating on in a long resource. I don't know how you would do it, as it isn't an attribute of the top level element of concern.</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
<br>
</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
I haven't had any issues in the approximately month I have been using it. Just the couple of nice to haves listed above are what I can identify. Thanks for all of the awesome work.</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
<br>
</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
Richard</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
<br>
</div>
<div style="font-family: monospace; font-size: 17.33333396911621px; width: 71ch;">
<br>
</div>
</div>
<div>On Thu, 2020-11-12 at 11:26 +0100, Radovan Semancik via midPoint wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p>Dear midPoint community,</p>
<p>MidPoint may have started as a humble identity management tool, yet it has evolved into identity
<i>platform</i>. MidPoint is comprehensive, flexible and customizable. MidPoint configurations can be quite complex and it may be a challenge to manage them. Therefore we have prepared an integrated development environment (IDE) to make this work easier:
<a href="https://docs.evolveum.com/midpoint/studio/">MidPoint Studio</a>. We have just released its “beta” version.<span id="more-7028"></span></p>
<p>The idea of midPoint IDE is not a new one. There was an unofficial midPoint plugin for Eclipse IDE for quite some time. However, this plugin originated as a side project of one of midPoint developers. It was an experiment that somehow escaped the laboratory.
The Eclipse-based IDE became quite popular. Yet, to code was quite “experimental” and it was difficult to maintain. Moreover, midPoint development migrated away from Eclipse IDE towards a more convenient IntelliJ IDEA. The Eclipse plugin was never officially
and it started to fall apart. Yet the community wanted (and needed) an IDE tool. Therefore it was high time to do something about it.</p>
<p>New IDE was based on newer midPoint concepts. It was also based on a different IDE platform. We have chosen IntelliJ platform over Eclipse. IntelliJ is much more convenient and polished platform. Similarly to Eclipse,
<a href="https://www.jetbrains.com/opensource/idea/">IntelliJ platform is open source</a>. We have used IntelliJ as a foundation for
<a href="https://docs.evolveum.com/midpoint/studio/">MidPoint Studio</a>, an integrated development environment to develop and maintain midPoint configurations.</p>
<p>We have just released a beta-quality version of MidPoint Studio (4.2-150). The Studio is pretty much feature-complete at this point. There may be some bugs and glitches, which is also the reason that we are releasing it to the community. We would like to
gather community feedback before our first official release. If you are interested, please navigate to the
<a href="https://docs.evolveum.com/midpoint/studio/">Studio page at docs.evolveum.com</a> and give it a try. Please share your feedback on
<a href="https://docs.evolveum.com/community/mailing-lists/">midPoint mailing list</a>. We would like to hear whether you like the Studio, if it works for you and what can be improved. You are welcome to report bugs
<a href="https://wiki.evolveum.com/display/midPoint/Creating+a+Bug+Report">using the usual procedure</a>. Just make sure you set the component field to “Studio” and include Studio version number in your report.</p>
<p>We plan to release production-quality MidPoint Studio after we gather the community feedback. The plan is to maintain and officially support the Studio starting with that release. MidPoint Studio will become the official IDE for midPoint.</p>
<p>(Reposted from <a moz-do-not-send="true" href="https://evolveum.com/midpoint-studio-beta-blog/">
Evolveum blog</a>)</p>
<pre>-- </pre>
<pre>Radovan Semancik</pre>
<pre>Software Architect</pre>
<pre>evolveum.com</pre>
<pre>_______________________________________________</pre>
<pre>midPoint mailing list</pre>
<pre><a href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a></pre>
<pre><a href="https://lists.evolveum.com/mailman/listinfo/midpoint">https://lists.evolveum.com/mailman/listinfo/midpoint</a></pre>
<pre><br></pre>
</blockquote>
</body>
</html>