[Coco] Phoenix progress

[Roger Taylor]

At 11:33 AM 10/16/2010, you wrote:
>Roger, can you talk about the text editor for the IDE?
>
>Ie, what languages, if any, does it know about.  As in, will it do indenting
>if I'm using C, or how about, DECB or Basic09.  Does it know the keywords of
>the Coco and OS9 languages?

Disk BASIC, OS9 assembler, RMA, and OS9 C  syntax coloring hasn't yet 
been defined, but CCASM, OS9, RMA assemblers have been defined as far 
as usage goes, just no syntax coloring yet.

However, all popular languages and probably 40 more you rarely hear 
about are already defined in the lex schemes provided by the editor, 
but I have yet to implement a way to let the user choose the scheme 
yet because I've been focused on all the other features.  For now, 
the syntax for my CCASM assembler is chosen by default until I add 
the syntax property to the base class that's inherited by all the 
various editor controls used by the IDE.   In short, Yes... but I'm 
working to implement this so the user can choose the language from a 
drop-down list in the file properties, and optionally (eventually) as 
a bells-and-whistles feature, have the IDE detect the language 
automatically if desired.

I'll have a syntax editor in the IDE as well.  Schemes are saved in 
.xml files and I can include 3rd party schemes in future releases 
fairly easily.







> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com
> > [mailto:coco-bounces at maltedmedia.com] On Behalf Of Roger Taylor
> > Sent: Sunday, October 10, 2010 1:22 PM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: [Coco] Phoenix progress
> >
> > Today I decided to try going seamlessly from CoCo ML source
> > code to a tape file audio stream and noticed that my
> > cocotape.exe program won't output the audio when being called
> > from the Phoenix IDE.  Although CoCoTape is still incomplete,
> > I have plans to rewrite it but not in the current HLA
> > language.  Instead of getting side-tracked on that project
> > right now I chose to just use the -o=output.wav syntax of
> > CoCoTape and then tell the IDE to use another tool to play
> > the generated wave file.  It worked great.
> >
> > At this time, Phoenix can have up to 6 chained builders/tools
> > operating on a source file and it's subsequent object files.
> > Whatever object is output from the previous file can be fed
> > into another builder.
> >
> > I just opened my main.asm program, set the object file to be
> > main.bin, set the 2nd project file as main.bin and the
> > builder as cocotape.exe, and the 3rd project file to be
> > main.wav with the builder wv_player.exe.  Bing.  Source code
> > to a CLOADM'able file in less than a second.  On the CoCo
> > you'd just type CLOADM or CLOAD depending on the type of
> > program being written.
> >
> > This was just a first trial run of that idea.  Why support
> > such an unpopular loading method?  Because sometimes it's the
> > only way.  It would give yet another quick way of getting
> > software onto a CoCo that only has cassette cable.
> >
> > You could also just do this with existing binary or BASIC programs:
> >
> > 1st project file [mygame.bin]
> > build process: cocotape.exe mygame.bin -o=mygame.wav
> >
> > 2nd project file [mygame.wav]
> > build process: wv_player.exe mygame.wav
> >
> > Type CLOADM on your CoCo and click GO from the IDE and it's
> > done.  This is a perfect audio stream that none of my CoCos
> > have complained about yet.
> >
> > --
> > ~ Roger Taylor
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco

-- 
~ Roger Taylor