Christopher James Huff scribis news:chrishuff-
AD4### [at] netplexaussieorg:

> 
> Here it is, first alpha release. If anyone wants to do a Windows/Linux 
> port, just say so

I would be intrested in working on a BeOS port (only OS I have a good IDE 
for).
But the files are "not avaliable" at the links you gave.

-- 
Gis poste, Arto.

Post a reply to this message

In article <87w### [at] bachcomposers>,
 Ole Laursen <ola### [at] hardworkingdk> wrote:

>   3. Demand that all use of foobar-0.1 comply with the new license.
> 
> As long as you're only doing 1 & 2 there's no problem (well, depending
> on your point of view there might be some moral problems, and people
> are likely to complain...), but you can't legally do 3.

If I understand things properly, #3 is legal if the old license 
specifically stated that the license could be changed, so anyone using 
the software has warning.


> Else, I would suggest GNU GPL because choosing that makes it possible to
> share code with the rest of the GNU world and avoid license wars with
> various parties (that's the pragmatic reason, anyway). And then you
> don't have to worry that someone will steal your code and abuse it in
> some future commercial product.

But I worry about people *not* using it because it is GPL...some people 
apparently don't like GPL, which is why I'm looking on information about 
licensing.
The artistic license seems interesting...it looks like it would let 
people use it in a program and only have to release the CSDL part of the 
source code. The only other thing is that I want to be sure people know 
they're using CSDL, what it is, and where it came from. I basically 
don't want someone to take the code, maybe make it slightly incompatible 
and release it as something else or use it as the main feature of their 
program and make it look like their work.
If someone is willing to invest the time/money to make a product that 
uses CSDL, I would have nothing against them charging for their product 
or withholding the source code for their work, as long as they make any 
changes/enhancements to CSDL available. People will only buy it if it is 
better than the free stuff, and if the developer makes something better, 
I'll thank them.

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Arthur Flint scribis
news:Xns### [at] 204213191226: 

> Christopher James Huff scribis news:chrishuff-
> AD4### [at] netplexaussieorg:
> I would be intrested in working on a BeOS port (only OS I have a good
> IDE for).

Found the correct links, thanks.
And congrats! The source compiled first time, no errors.
(a few warnings, but no errors)
So, when you have another release to let us try, let me know.


-- 
Gis poste, Arto.

Post a reply to this message

It compiles fine in Cygwin - now to figure out how to use it :-)

--
duncan gold [TurboPower]
TurboPower: http://www.turbopower.com
Personal: http://www.autowitch.org

"Christopher James Huff" <chr### [at] maccom> wrote in message
news:chr### [at] netplexaussieorg...
> Here it is, first alpha release. If anyone wants to do a Windows/Linux
> port, just say so.
>
> Supports:
> while loops, if-else conditionals
> objects
> functions with parameters
> 1D arrays
> file output
> mathematical expressions. No boolean operators, just +-*/. Parentheses
> should work, but are untested. Vectors and scalars work.
>
> To-do for next release:
> boolean operators
> global variables
> general code cleanup, especially the parser
> function return values
> better documentation/sample files
>
>
> I just realized I forgot to document the syntax of the CSDL
> interpreter...though it is pretty obvious, "csdl INPUT_FILE". Make sure
> the executable is alongside the "library" directory or all the files are
> in the same directory, or CSDL won't be able to find the library files.
> BTW, if you attempt to run the library files, they will print
> information about the file.
>
> Source code (20KB):
> homepage.mac.com/chrishuff/csdl_source.tgz
>
> Documentation, example files, library files (12KB):
> homepage.mac.com/chrishuff/csdl_dist.tgz
>
> Mac OS X compile (208KB):
> homepage.mac.com/chrishuff/csdl_macosx.tgz
>
> --
>  --
> Christopher James Huff <chr### [at] maccom>

Post a reply to this message

In article <3c4cb4df$1@news.povray.org>,
 "autowitch" <aut### [at] autoSPAMwitchorg> wrote:

> It compiles fine in Cygwin - now to figure out how to use it :-)

Well, at least nobody's having trouble compiling it...
Alpha 1 only takes one parameter, the CSDL file to run. Make sure the 
CSDL executable is in the same directory as the demo files and library 
folder. And if you need any help on the language itself, ask...the 
documentation is pretty bad, but the language should be fairly easy for 
anyone who can handle POV-Script or C.

BTW, I just got OpenGL display (using GLUT) working...and I almost have 
function return values working.

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Christopher James Huff scribis news:chrishuff-
9F0### [at] netplexaussieorg:

> In article <3c4cb4df$1@news.povray.org>,
>  "autowitch" <aut### [at] autoSPAMwitchorg> wrote:
> 
>> It compiles fine in Cygwin - now to figure out how to use it :-)
> 
> Make sure the CSDL executable is in the same directory as the 
> Demo files and library folder. 

Can it be stored in a directory in the system path and run that way?
Or does it store all output files in the same dir that the binary is
stored in? Do you plan to use an *.ini file that lets it know where 
to find needed files?

> 
> BTW, I just got OpenGL display (using GLUT) working...and I almost have 
> function return values working.
> 

Please let us know when you have another release.


-- 
Gis poste, Arto.

Post a reply to this message

In article <Xns### [at] 204213191226>,
 Arthur Flint <mra### [at] chesapeakenet> wrote:

> Can it be stored in a directory in the system path and run that way?
> Or does it store all output files in the same dir that the binary is
> stored in? Do you plan to use an *.ini file that lets it know where 
> to find needed files?

I've already added a command-line option to specify an alternate place 
to look, that library path was just a quick fix to give me some way of 
keeping my files organized. An *.ini file method is certainly a 
possibility, as I add more options.


> Please let us know when you have another release.

I plan to do Alpha 2 this Saturday, it will be a lot more useable and 
useful, with things like a graph object and rewritten documentation.

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Christopher James Huff wrote:
> 
> Here it is, first alpha release. If anyone wants to do a Windows/Linux
> port, just say so.
> 

Ok, i have finally found some time to have a look, as autowitch mentioned
it compiles with cygwin, even with -mno-cygwin/MinGW (in case you want to
use a non open source license) For future versions a makefile would of
course be useful.

The samples all worked, starting Povray of course not, but that's just a
small change in the 'povray.csdl' file.  The indention of the Povray
output could be improved, but you probably already noticed that.

The syntax is pretty self explanatory although learning everything will
probably take some time.  But it seems that writing malicious programs is
quite easy so you should consider some security mechanism like Povray's
IO-restrictions.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

In article <3C4EDD1C.848E9D11@gmx.de>,
 Christoph Hormann <chr### [at] gmxde> wrote:

> Ok, i have finally found some time to have a look, as autowitch mentioned
> it compiles with cygwin, even with -mno-cygwin/MinGW (in case you want to
> use a non open source license) For future versions a makefile would of
> course be useful.

Especially since it now uses GLUT...I'll get to work on one, but I have 
very little experience in such things, beyond modifying them to compile.


> The samples all worked, starting Povray of course not, but that's just a
> small change in the 'povray.csdl' file. 

Hmm? What changes were necessary? Is POV-Ray not named "povray" on your 
system?
I'll eventually have the engine name be a variable, it was mainly 
hard-coded because there are no string manipulation functions yet. The 
same goes for the source file name.


> The indention of the Povray output could be improved, but you 
> probably already noticed that.

In the current POV library, I've removed all indentation...it won't be 
too hard to implement though, I just haven't done it because I haven't 
decided on the best way to store the data.


> The syntax is pretty self explanatory although learning everything will
> probably take some time.  But it seems that writing malicious programs is
> quite easy so you should consider some security mechanism like Povray's
> IO-restrictions.

More dangerous is the system() function...I'll eventually add security 
features to limit file I/O and turn that function off, though they will 
probably be platform-specific extensions to the core code. I'm focusing 
on getting the thing fully operational first...

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Christopher James Huff wrote:
> 
> Hmm? What changes were necessary? Is POV-Ray not named "povray" on your
> system?
> I'll eventually have the engine name be a variable, it was mainly
> hard-coded because there are no string manipulation functions yet. The
> same goes for the source file name.

It's 'pvengine.exe' but it's usually not in search path and the windows
version is not very suited for automatic starting anyway so most people
will either not use the render function or have a command line version.

> 
> More dangerous is the system() function...I'll eventually add security
> features to limit file I/O and turn that function off, though they will
> probably be platform-specific extensions to the core code. I'm focusing
> on getting the thing fully operational first...

I mostly meant 'system()', i think it would be good if you could have a
confirmation before executing a program.

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message