[Fwd: 3D Logo program]

[Doug Loss <dloss@csrlink.net>]

I got this from Miguel Sepulveda this morning; if you're interested in
participating in his project send him email at Miguels@mdli.com.

Miguel Sepulveda wrote:
> 
> Hi Doug,
> 
> I am considering starting a mailing list on the project 3DLogo but I 
> am not sure if it is worth the effort right now.  Do you know how many 
> people in your mailing list would be interested on participating in 
> the 3DLogo project?  As I told you in a previous email I am studying 
> about CORBA because writing the program as CORBA components will make 
> it easier for future enhancements and porting to other OSes.  It is 
> also a matter of having an easier interface for a Network 3Dlogo 
> version so that several people can communicate structures on the
> net.
> 
> What I would like to release first, within a 1 1/2 weeks is the data
> definition for the geometrical objects.  Each lego-like block will be 
> defined externally in a Data File.  After thinking it over, I came to 
> the conclusion that having blocks defined externally in data files is 
> the best solution, as opposed to defining blocks hardwire into the 
> program.  This way people can define their own blocks and 3D objects 
> and create libraries of interesting structures.  One thing I would
> like to discuss in the list is the protocol for specifying the blocks. 
> I have some ideas but I would like to open the floor for debate.  If 
> you think about it, it is not so easy.  The definition of a 3D 
> structure is trivial, just make a connection table.  However a 
> definition that supports and easy implementation of building and 
> joining structures of block withiout imposing some kind of condition
> on the block structure is more challenging.  The way I see it, LEGO 
> has already solved the problem for as.  Every piece of lego has a well 
> defined interface (the anchor points) that implement the joining of 
> blocks.  So there is always a limited number of ways to join to 
> blocks.  I think this is the best solution.  Another issue is that in 
> our data file definition of the blocks we have to allow for future 
> enhancements like textures, material, illumination, decals etc...
> 
> Miguel Angel

-- 
Doug Loss                 A life spent making mistakes is not only
Data Network Coordinator  more honorable, but more useful than a
Bloomsburg University     life spent doing nothing.
dloss@bloomu.edu                G. B. Shaw