Topic: SaLiVA - new format

[BlinkenLights]

SaLiVA is Standard Laser Vector Art
or Super Awesome Laser Vector Art

The idea is to have a file type that that is truly flexible and usable from both an artistic and technical standpoint.

all good projects start with a great name (i know thats not true)

[Fanny Pack]

Hmmm, maybe we can work on the name later...

[BlinkenLights]

ok how about it.. im thinking we store info as splines and primitives.. and then the software reads the vector data and creates output.. so a circle will only have 1 point (its origin)

[Agent C]

Take a look at the POVRay file format.

[BlinkenLights]

no YOU take a look at it.. im just the idea guy ya see.. i dont do the hard work..
I just pop off at the mouth constantly and eventually something smart comes out...

[Fanny Pack]

  I think we are all pretty much that way.  I guess that's why nothing ever happens.

[James]

I'm trying, but nobody listens to me!

In the mean time, I'll just keep putting good ideas to work in LaserBoy, even if no one else ever finds them or uses them!

James. 

[BlinkenLights]

well something needs to effing happen.. all this brain power in here, there is no excuse.. we just need to put our heads together and figure this shit out..

Here is a list of things i believe a new file structure should have.

Framed data and linear data layouts
(one is for animation of complex shapes the other is more like an abstract over time where the frames dont matter)

True vector storage of shapes, no extra points required

[James]

There is a lot of room for new ideas and improvements in laser display; not just in the file storage catagory.

Although.... if you want to start there, how about a uniform way to store color vector laser data in plain ASCII?

That way people could make frames in a text editor.

James.

[Fanny Pack]

Does anyone not think XML is a good starting point?  I'm not saying that it is the best solution in the long run but if we are going to start designing something i think it is the best choice since we can all look at it and read it without having to twiddle bits.  It's also very object oriented so it lends itself to being able to describe anything from vectors all the way up to frames.

But, I'm jumping ahead.  First thing would be to make a wish-list of every feature that we would want to go into the file.  So add yours and everything is fair game.  And please don't start arguing about what other people put on their lists.  We can debate the pros/cons of everything later and decide on what goes and stays later.

With me?

[BlinkenLights]

ABSOLUTELY ! !

a XML data structure is something that makes tons of sense..

its simple ascii and on top of that it compresses well.

it could be used as either the descriptor file for the vectors (aka vector id 1 fades from #333333 to #000000)

it could be used as actual shape storage

Code: [Select]

<shape>
    <curve>
        angle= blah
        size = blah.....
        etc.....


thats where we need to be exploring..

[James]

Whatever it is should be something that is also implemented in open source code.

Generic C++ would be the best language to use.

All of the code necessary to write, read and interpret the ASCII should be part of the distribution.

James. 

[Fanny Pack]

Whatever it is should be something that is also implemented in open source code.

Generic C++ would be the best language to use.

All of the code necessary to write, read and interpret the ASCII should be part of the distribution.

James. 

Why?  Standards are never implementation specific.  It's fine to give examples in your language of choice but ultimately it's up to the developer to decide how they want to implement it. 

[James]

That's absolutely true!

However, if it is implemented in code that proves that it's a bit more than just a good idea!

James. 

[BlinkenLights]

yes at some point it has to actually work...