Took more than expected to find time to work on th...
# jewel
s
Took more than expected to find time to work on this, but here is how you can use Jewel in 243 & 251 once we release the next version, 0.28 https://github.com/rock3r/jewel-ijp-template/tree/243-and-251-compat The example for now uses 0.27 on IJP 243, which has some significant differences from what’s on 251. 251 also doesn’t have all the 0.28 APIs and fixes available. I'm hoping they make it into 251.1, but the review and approval processes are taking longer than anticipated and are entirely internal to JetBrains, so I can't guarantee anything.
🙏 4
t
So IntelliJ 251 is already released. When i use this template would it already work for the current stable IntelliJ IDE? Or do we have to wait for the new version of Jewel. But when it is integrated into IntelliJ than we can not use a newer version of it. So we are tied to the version integrated into IntelliJ right?
s
If I understand what you're asking, the answer is "please hold off until 251.1 is out".
t
Ok i see. So we will not be able to support 251.0 Thank you for clarification. It is just i got today a mail from Jetbrains that my plugin should prepare for 252 😄
s
As I wrote above, this is only a proof of concept using what's out there today. 0.27, the latest available on 243 still, is quite different from what's on 251.0, which in turn is missing quite a lot of stuff compared to what we call 0.28. Moreover, 0.27 and what's on 251 today are not necessarily binary compatible; it might work for a simple example like the one in the repo, but it'll likely break for more complex stuff
🆗 1
That's why I'm trying to get 0.28 out ASAP, as that is binary compatible between 243 and 251.1
👌 1
Sadly things didn't line up to have this all done in 251.0; moving to the IJP uncovered a myriad issues in processes and infrastructure that delayed the release to this point
Things will get ironed out over time; doing releases like these across major IJP versions is unheard of at JetBrains and it's a lot more complex and time consuming that anyone imagined
The good news is that for 252 you shouldn't have to change anything from 251.1+, at least :D
t
Thank you very much for your effort. I know in the repo from Jewel it says clearly that it should not be used for production code. But i as an Android developer was not able to resist to use Compose for the UI for my Plugin 😄
plus1 1
s
I completely understand! This whole things exists pretty much because I also feel this way, and many others are also happy this is a possibility
Fwiw we're using Jewel in production in Studio, but that's a much more controlled environment than a 3p plugin needs to deal with
❤️ 1
f
Thanks for this @seb. We haven't updated since 0.25.0 ... at this point should we wait until 0.28 comes out or what upgrade path would you recommend (since we support both AS and IJ clients)?
s
Probably worth waiting for 0.28 at this point 🙂
thank you color 1