Blocking serial support

Craig Latta craig.latta at netjam.org
Wed Jun 12 04:05:22 UTC 2002


> > What do you think of the framework put forth by Flow
> > (http://netjam.org/flow)? I think the things you want would fit
> > nicely there.
> 
> They probably would. I'd use it if it were available for 3.2.
> 
> Do both the full- and half- duplex modes of operation work simply?
> i.e. having one process reading/writing or have two processes, one
> reading and one writing?

	I think so. Can you give an example? (Also, I'm not sure I was able to
parse your last sentence correctly. :)  What test scenario do you
recommend I use?

> When do you expect to have a version that'll work with 3.2 Squeak
> (i.e. stock Exceptions) with serial port support?

	Well, for the last few months I've thought that it'd be better to spend
my time banging on the module system, so that I'd could release Flow as
a module which could be simply loaded and unloaded. It seemed like until
that was done, Flow wouldn't get used much (currently unloading it is
difficult). Given that, all the tedious effort involved in integrating
Flow with the ever-changing current image via changesets didn't seem
worthwhile. The problem is that I can't make a good estimate of when the
module work I'm doing will be far enough along.

	I've already changed Flow to use the official exceptions (quite some
time ago now). I guess I'll switch to making "one last release" the old
way, with serial support. I think the modularity prerequisite is
important, but not worth any more release delay.

	So, I'll get back onto my normal schedule of first-friday releases, and
say Friday 5 July.


	thanks,

-C

--
Craig Latta
improvisational musical informaticist
craig at netjam.org
www.netjam.org
Smalltalkers do: [:it | All with: Class, (And love: it)]



More information about the Squeak-dev mailing list