The colorForth Movies: Ray's Glad to Accomodate
Ray St. Marie
Group:
On Wed, Nov 4, 2009 at 10:47 PM, peekay <pksharmakolk...@gmail.com>
wrote:
> ---------- Forwarded message ----------
> From: peekay <pksharmakolk...@gmail.com>
> Date: Nov 5, 10:45 am
> Subject: movies about color forth
> To: comp.lang.forth
> On Nov 5, 12:58 am, John Passaniti <john.passan...@gmail.com> wrote:
Hi John Passaniti.
>> What is that movie supposed to be showing us? Replacing the sound
>> track with someone speaking and explaining what is on the screen (and
>> why it is important) would potentially be useful to get people
>> interested. But most of what the video shows is cursor flying around.
The name of the movie explains its purpose. It is but a test of some
of
tools I am now contending with to bring such a production to
fruition.
>> What I think would be ideal is a start-to-end video where a simple but
>> non-trivial problem is solved in ColorForth and narrated. From
And so do I. And as you can see from the TestMovie.* that I now
have the ability to do demos of what you say here:
>> booting the system to writing/testing the code to finally committing
>> the code back to some media, seeing ColorForth actually being used, in
>> real-time, by someone who is comfortable with the environment would be
>> useful. Such as "watching over the shoulder" video would give people
>> an immediate taste of what ColorForth is about.
One of the major obstacles was showing colorForth programs running at
full speed. I'm close to the answer to that little gem. Another is
lighting.
still again, maintaining focus and clarity.
Other tools that I am using include books on technical writing, and
on
production level constructions of this nature. It may be a bit more
work
then that test lets on.
Hi Pk
> "Such as "watching over the shoulder" video would give people
> an immediate taste of what ColorForth is about."
> as also the many aspects that people want to know about ..
> from booting to code-locations, asm codes which make it
> tick, adding words/macros/comments, saving, reloading the
> saved work, loading on and from hard-disk,
> i'm sure ray is on this list and will be happy to get this
> and more suggestions
I am very glad to read and act on productive suggestions.
I intend to show pretty much everything I can think of, given time.
> (in any case, i'll forward this to the Color-Forth group on google)
> --
Thanks for Forwarding this to Group, PK, as I don't tend to
read C.L.F. but maybe twice a year.
> You received this message because you are subscribed to the Google Groups "ColorForth" group.
> To post to this group, send email to color...@googlegroups.com.
> To unsubscribe from this group, send email to color-forth...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/color-forth?hl=en.
So to re-cap.
1. Movie of tests is just a TestMovie as the name states
2. Much detail to follow.
On that note, I got permission ( and got Howard to re instate )
to use the excellent information at karig.net as part of the
documentation of the code.
3. I'm glad to receive e-mail of this nature stating what the
interested are interested in.
4. I vary rarely read C.L.F
I liken it to the News on TV. When something real happens, it gets
out of
the list much like this did.
Best Wishes
Ray
--
Raymond St. Marie ii,
public E-mail Ray.stma...@gmail.com
a quickstart guide http://colorforthray.info
Community Blog http://colorForth.net
Community Wiki http://ForthWorks.com/c4th
John Passaniti
> One of the major obstacles was showing colorForth programs running at
> full speed.
That's only an obstacle if the program is doing something graphical
that is updating the screen quickly. When I suggested that you pick
some simple but non-trivial problem to solve, I wasn't necessarily
thinking it had to be graphical.
> Another is lighting.
In the finest tradition of solving problems by avoiding them, you
might see if ColorForth will run as a virtual machine under
VirtualBox. If so, I believe VirtualBox offers abstracting the video
framebuffer over VNC. If so, there are VNC recorders.
A second option would be to write some code spew out the network card
the current video framebuffer. You could avoid a real networking
stack and spew out UDP packets. Another computer on the network can
then grab the packets and dump out the video memory as bitmap files
which you can then combine to create movie files using freely-
available tools. We're not talking about a lot of code to pull that
off.
Ray St. Marie
> On Nov 5, 11:32 am, "Ray St. Marie" <ray.stma...@gmail.com> wrote:
>
> > One of the major obstacles was showing colorForth programs running at
> > full speed.
>
> That's only an obstacle if the program is doing something graphical
> that is updating the screen quickly. When I suggested that you pick
> some simple but non-trivial problem to solve, I wasn't necessarily
> thinking it had to be graphical.
I agree. In the works and currently on tape is a more informal
introduction with some programming examples not necessarily graphical
in nature. If you(general readership) are interested, please stay
tuned.
Eventually, the series will cover all of the blocks that come with
many of the systems in the class, and many of the code snippets found
by other authors and myself. Long term project comes to mind.
>
> > Another is lighting.
>
> In the finest tradition of solving problems by avoiding them, you
> might see if ColorForth will run as a virtual machine under
> VirtualBox. If so, I believe VirtualBox offers abstracting the video
> framebuffer over VNC. If so, there are VNC recorders.
This is an interesting idea, but it may not be necessary to go so far
as that. I'll expound here after:
>
> A second option would be to write some code spew out the network card
> the current video framebuffer. You could avoid a real networking
> stack and spew out UDP packets. Another computer on the network can
> then grab the packets and dump out the video memory as bitmap files
> which you can then combine to create movie files using freely-
> available tools. We're not talking about a lot of code to pull that
> off.
Very neat idea. Like to try that.
colorForth has had screen capture since first delivery. The PNG block,
in conjunction with the Lz77, crc, and file blocks have been used to
take frame buffer snaps and convert to PNG format, and then store that
in a save-to-file-buffer and then send that buffer to a prepared file
in Windows. I have done this at least once sucessfully, many years ago
and am trying to remember the details.
If I remember correctly, I used Roman's colorForth for Windows, which
came with a way to prepare files and map them so that
WindowsColorForth could comunicate with the Windows file system.
Included are a couple of zeroed out files, one 16k and another 4k and
these can be extened to proper size of the output files by hex editor
or even ammended to. One picks a 4 letter name for the file so that
the name fits in a colorForth 32bit byte, and then using fmap--Roman
provided, and put--from files block, write the buffer to the file.
Chuck prepars many kinds of output that must be transfered off disk in
several formats and those code examples exist in the deliverd public
system.
I am certain a similar aproach can be taken with colorForth2. Speed of
capture doesn't matter because each and every screen change can be
captured as the next operation just after screen completion. This
would mean storing a large buffer, could even be a dedicated HDD
drive.
This would make a cool presentation itself. Added to the list.
Your idea above makes me wonder about a streaming in real time
solution that could include the constantly captured output of a system
running, and an inset of the programmer on camera showing examples of
system usage. Two machines, colorForth machine screaming to a server
on the second machine, that combines the presentation.
Much to think about,
Take care,
Ray
Ray St. Marie
those of you that watched the first few
batches of colorForth specific movies at
http://youTube.com/Raystm2 playlist C.MooreMath
over the last month or two.
A Happy New Year and Best Wishes
for You and Yours! and Thank You again!
Ray