<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
I mean, should it be possible to load FFI-Kernel and FFI-Pools at once -- without loading FFI-Win32 etc., too? A package includes all class categories after a dash. That's why "FFI-PoolsTests" is not called "FFI-Pools-Tests": to be able to load "FFI-Pools" without loading "FFI-PoolsTests".<div><br></div><div>Here is an idea for the FFI package hierarchy:</div><div><br></div><div>FFI (incl. FFI-Kernel and FFI-Pools)</div><div>FFITests (incl. FFITests-Kernel and FFITests-Pools)</div><div>FFITools</div><div>FFIExamples (incl. FFIExamples-Win32 and FFIExamples-Unix etc.)</div><div><br></div><div>I suppose we could start putting important bridge classes -- the ones that are not just toy examples -- into another package, not FFI*. FFI might be important but it should rarely leak into higher-level abstractions such as by package name. Maybe we should start a "Platform" package?</div><div><br></div><div>Looking at the primitive calls in "Files" and "Graphics" and "Kernel" (i.e. EventSensor), maybe something like this:</div><div><br></div><div>Platform-Graphics</div><div>Platform-Events</div><div>Platform-Files</div><div><br></div><div>A viable goal could be to keep the layer in the "Platform" package as thin as possible to then quickly dispatch to other, higher-level packages. Such as "Files" and "Graphics". :-)</div><div><br></div><div>Such a distinction would render the "Kernel" package and the "Platform" package the two most basic things in the image. And "Collections", of course. :-D</div><div><br></div><div>...or we add "Kernel-Platform" and make that entry point for platform-specific graphics, events, files, etc. as part of the Kernel package. Not sure whether "Kernel" should (eventually) depend on the FFI package. Sounds unpleasant.<br><div><br></div><div>Best,</div><div>Marcel</div></div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 03.06.2020 01:02:59 schrieb Eliot Miranda <eliot.miranda@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite" style="min-width: 500px">On Jun 2, 2020, at 11:41 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br><br></blockquote></div><blockquote type="cite" style="min-width: 500px"><div dir="ltr"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
<span style="font-size: 13.3333px">Hi Eliot.</span><div style="font-size: 13.3333px"><br></div><div style="font-size: 13.3333px">> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">So combine them.</span></div><div style="font-size: 13.3333px"><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div style="font-size: 13.3333px"><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">This would mean combining all of them. Including "FFI-Win32", "FFI-Unix", etc. Hmm... Or we add "FFIWin32" etc. (without the dash) ...</span></div></div></div></blockquote><div><br></div>wouldn’t it just mean moving the win32-specific FFIExternalSharedPool subclasses to FFI-Win32 and the Unix-specific ones into FFI-Unix?<div><br><blockquote type="cite" style="min-width: 500px"><div dir="ltr"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000"><div style="font-size: 13.3333px"><br></div><div style="font-size: 13.3333px"><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div style="font-size: 13.3333px"><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 02.06.2020 20:39:28 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Eliot.<div><br></div><div>> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">So combine them.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">This would mean combining all of them. Including "FFI-Win32", "FFI-Unix", etc. Hmm... Or we add "FFIWin32" etc. (without the dash) ...</span></div><div><br></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 02.06.2020 20:36:05 schrieb Eliot Miranda <eliot.miranda@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">Marcel,<br><br><br>> On Jun 2, 2020, at 11:17 AM, commits@source.squeak.org wrote:<br>> <br>> Marcel Taeumel uploaded a new version of FFI-Pools to project FFI:<br>> http://source.squeak.org/FFI/FFI-Pools-mt.19.mcz<br>> <br>> ==================== Summary ====================<br>> <br>> Name: FFI-Pools-mt.19<br>> Author: mt<br>> Time: 2 June 2020, 8:17:16.425853 pm<br>> UUID: b602902a-6f8f-9549-adc7-d0cd5313cbf7<br>> Ancestors: FFI-Pools-mt.18<br>> <br>> Hmpf. Having "FFI-Kernel" and "FFI-Pools" in two separate packages is really annoying. ;-)<br><br>So combine them. The pool functionality is essential core support for accessing external defines in a cross-platform way. I for one have no objection to you combining these for ease of development.<br><br>> <br>> =============== Diff against FFI-Pools-mt.18 ===============<br>> <br>> Item was changed:<br>> ----- Method: ExternalPoolReadWriter class>>initialize (in category 'class initialization') -----<br>> initialize<br>> <br>> + "self initializeAtomicTypesExtra."!<br>> - self initializeAtomicTypesExtra.!<br>> <br>> <br><br></div></blockquote>
</div></div></blockquote></div><span></span><br></div></blockquote></div></div></blockquote></div>