-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Below is the class hierarchy diagram for Flow 3a. There is no
particular reason to expect it to change before release. If you are
having line wrap issues, it will probably look better pasted into a
Workspace.
Testing to confirm none of my refactorings broke anything is under way.
The next step will be to file out in such a way that it can be filed
into a 3.2 stock image. The tricky part will be identifying Flow's
dependencies on changes in non-Flow classes. I plan to make filing in
work for all target stock images (Squeak 3.2, 3.6, 3.7, 3.8 and 3.9)
before releasing any of the changesets, in hopes that the code named
Flow 3a can be & work as similarly as possible in all the target images.
Brenda
- --
ProtoObject
Object
Collection
SequenceableCollection
OrderedCollection
FlowPathSegmentCollection
TestCase
FlowTestURI
InterpreterPlugin
Flow
Exception
Error
FlowStreamingError
FlowExhaustion
FlowExternalResourceError
FlowConnectionRefused
FlowEncodingMismatch
FlowFailedReadingAttempt
FlowFailedWritingAttempt
FlowFilesystemError
FlowFileNotFound
FlowInvalidPositioningAttempt
FlowInvalidReadingAttempt
FlowInvalidWritingAttempt
FlowTimeout
FlowUnresolvableHostname
FlowOverflow
FlowIllegalURI
FlowCorrespondent
FlowClient
FlowIncomingClient
FlowIncomingHTTPClient
FlowOutgoingClient
FlowOutgoingHTTPClient
FlowOutgoingPOPClient
FlowServer
FlowHTTPServer
FlowTransport
FlowSerialTransport
FlowIP4Transport
FlowStream
FlowPositionableStream
FlowWritableStream
FlowDiscardingStream
FlowExternalStream
FlowFileStream
FlowAppendingFileStream
FlowAppendingFileStreamWriter
FlowRemoteFileStream
FlowNetStream
FlowHardwareStream
FlowAudioStream
FlowIEEE1394Stream
FlowParallelPortStream
FlowSerialPortStream
FlowIP4Stream
FlowTCPStream
FlowUDPStream
FlowNetMessage
FlowHTTPMessage
FlowHTTPRequest
FlowHTTPResponse
FlowNewsMessage
FlowURIStream
FlowExternalResource
FlowFile
FlowNetResource
FlowHardwarePort
FlowAudioPort
FlowIEEE1394Port
FlowInfraredPort
FlowParallelPort
FlowSerialPort
FlowUSBPort
FlowIP4Socket
FlowTCPSocket
FlowClientTCPSocket
FlowIncomingClientTCPSocket
FlowOutgoingClientTCPSocket
FlowServerTCPSocket
FlowUDPSocket
FlowIP4AddressResolver
FlowSpeechRelay
FlowHostPlatform
FlowMacintosh
FlowRiscOS
FlowUnix
FlowWin32
FlowURI
FlowHierarchicalURI
FlowOpaqueURI
FlowAuthority
FlowRegisteredAuthority
FlowPeerAccessAuthority
FlowIP4Address
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEurZULgS0DKtN84oRAkOjAKC8dMkiw0AkyN8sy+bmoMW+lOOzxQCgoR6I
6u3a+gRJS5SPziL72CnQhM4=
=H/Nb
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As I think a few of you know, I am putting together a new release of
Flow based on Craig's current code. Craig is still Flow's owner; I am
mostly providing release management assistance.
Craig did some significant refactoring (go, Craig!) since Flow 2a, so we
will be calling this Flow 3a. It is planned to work on Squeak 3.2, 3.6,
3.7, 3.8 and 3.9. All class names will begin with Flow, to eliminate
naming conflicts with the stock networking library. One of the many
reasons you want it (truly, madly, deeply) is that it is a prerequisite
for Squeak images exchanging messages with Spoon images. I don't know
when the new package will be available, but I will send status updates
here (the Flow and IO mailing lists) after I make more progress.
Current status is that I have Craig's latest Squeak bits. I found all
the classes that will go into the Flow 3a release, and put them in
appropriate categories. They are mostly renamed to their new names. I
will send a class hierarchy diagram with the new names shortly after I
finish renaming. In addition, I am combining parts of my URI
implementation (which will be included in Flow 3a in lieu of the
*Locator classes) with Craig's SocketAddress class. These things are
the only refactoring I am planning to do before release -- the intention
is to release as quickly as possible.
After the steps in the above paragraph are done, Craig & I will both do
some testing to confirm I didn't break anything. It is possible that
the easiest way to do this will be to write a test suite, but I'm not
making any commitments on this point yet. Plenty to do left after that..
Brenda
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEtJrrLgS0DKtN84oRAmf2AJ9FS+zcOHzXoxIVtxkgY3VIrEV0eACgnOZ6
DO5F1txdTD9x+VHhehcDqp0=
=Vb48
-----END PGP SIGNATURE-----