<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Tariq,<div><br></div><div><div><blockquote type="cite"><div>On 4 Nov 2025, at 4:09 am, Dale Henrichs via Glass <glass@lists.gemtalksystems.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div>Many developers develop in Pharo and deploy in GemStone and again I would defer to others in the community to explain the Seaside development process that they use.</div></div></div></blockquote></div></div><div><br></div><div><div>My understanding is that it’s possible to load metacello projects in GemStone 3.7.x with the devkit extent, and to configure Jadeite4Pharo to be able to connect in a limited way (ie. Rowan projects will obviously not work) so you have an UI to write code outside of Topaz.</div><div><br></div><div>That said, I’ve not been able to make everything work yet… but I’ve had very limited time to experiment. A couple of months back, Dale mentioned the “DevKit” development workflow was to get some priority, so things may have changed.</div><div><br></div><div>I believe we will see “rowan” packaged versions of all the greatest hits eventually, but for now we have a stop-gap solution that could soon (or is currently) getting some love.</div><div><br></div><div>The most exciting option moving forward looks like develop in GT (<a href="https://gtoolkit.com/">https://gtoolkit.com/</a>) and deploy in GS, but right now that’s dependent on Rowan, so seaside isn’t yet an option.</div><div><br></div><div><font color="#000000"><span style="caret-color: rgb(255, 255, 255);">If there’s anyone working with Seaside (and other metacelllo stuff) in GS 3.7.x, can you share your experience?</span></font></div><div><font color="#000000"><span style="caret-color: rgb(255, 255, 255);"><br></span></font></div><div>Cheers,</div><div><br></div><div>J</div></div></body></html>