<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><div><div><div>I just tried it and it still loads in the latest 3770 image. You need to load in sequence: FFI (from the main Cuis repo Packages/System directory), 3DTransform (from the OpenGL repo link you used) and finally OpenGL (also from the OpenGL repo.)<o:p></o:p><o:p> </o:p>Okay.<o:p></o:p><o:p> </o:p>Do we have a way to manage package dependencies in Cuis? Getting the order right could become very time-consuming.<o:p></o:p><o:p> </o:p> Anyone using the OpenGL stuff regularly?<o:p></o:p><o:p> </o:p><o:p> </o:p>I did that port over a decade ago and used it until about 5-ish years ago. When I last used it, the core OpenGL stuff worked fine but the code was getting a bit crusty:<o:p></o:p><o:p> </o:p>1) I originally pulled it from a Croquet image back before anyone would admit to having OpenGL support in Squeak (this was 2009 or so) and ported it back to Squeak then later to Cuis. So the code is quite old.<o:p></o:p><o:p> </o:p>2) As a result of the bit-rot due to 1, it only supports OpenGL 1.x I think (along with some early VBO and shader extensions) and immediate mode rendering.<o:p></o:p><o:p> </o:p>3) It *might* need some minor modifications to run on 64-bit images... I don't remember if the FFI package updates handled everything or not on that front.<o:p></o:p><o:p> </o:p>So it's a good starting point showing how to do OpenGL via FFI, but probably not much more than just a starting point these days. (i.e. I'm not actively working with/on that code anymore)<o:p></o:p><o:p> </o:p>Right. Thanks for the background.<o:p></o:p><o:p> </o:p>I have my own framework in VW. It’s very specialized, and I don’t really want to port it. Was hoping to find something shader-based and working. Is Woden too fat for Cuis? Will it be ported/streamlined? How does the Cuis community determine what, if any, of Pharo gets ported, and what sorts of changes/minimalizings must happen if something is ported? <o:p></o:p><o:p> </o:p>Along the same line, must we do without buttons with icons in the debugger?<o:p></o:p><o:p> </o:p><o:p> </o:p>Shaping<o:p></o:p><o:p> </o:p></div></div></div></div></body></html>