[Coco] VCC Update

Fri Apr 14 16:00:06 EDT 2017

True, but no problem, we will talk and correct it as we can, we have to learn

________________________________
De: Coco <coco-bounces at maltedmedia.com> en nombre de James Ross <jrosslist at outlook.com>
Enviado: viernes, 14 de abril de 2017 03:45 p.m.
Para: CoCoList for Color Computer Enthusiasts
Asunto: Re: [Coco] VCC Update

Oh, wow ... that is disappointing.  I am mistaken about the comment showing up on both forks commits. – Since it is the exact same commit (#7d83e2ed7112920d4bfab62728c7f20e9c3d4187), it would only make sense to me that it should.  But right now, it appears to be only showing up on my fork of that commit.

Daing ... that means to catch all the messages you would have to check each fork w/ that same commit.  Boy that’s not right.

I guess the trick then is comment on the Fork of who is the author of that particular commit

Oh, well ...  Live and learn.

James

________________________________________

Just a suggestion --> Discussions at this level should probably be taken off the list and put in the GitHub messaging system on the commits where they are being modified... (We need to learn how to use GitHub for this kind of communication back-and-forth OR we will bore the others on this list to death!)

Comment left ...

https://github.com/jross9/VCC/commit/7d83e2ed7112920d4bfab62728c7f20e9c3d4187

or (same commit from Luis fork)

https://github.com/Luis46coco/VCC/commit/7d83e2ed7112920d4bfab62728c7f20e9c3d4187

Anyone can chime in and the list of commits has a little flag showing which ones have comments.

James

________________________________________
From: Coco <coco-bounces at maltedmedia.com> on behalf of Luis Fernández <luis46coco at hotmail.com>
Sent: Friday, April 14, 2017 7:18 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] VCC Update

Ok for me, but keep this in mind
Start playing cartridges, every time you open one, you have to make a change in the selection of hardware to cartridge, and in the end, the hardware is used little, once loaded and not touching loads

Also if the directory is full of * .ccc, * .pak or * .rom, the interesting thing is to see the ccc at first glance, I propose something like bill,

Also the roms and the ccc are loaded in $C000, whether they are rom basic or rom cartridges and ccc also, just have to make a touch to accept .pac

Program pak (*.rom, *.ccc, *.pak)
Virtual Hardware (*.dll)
All (*.*)

By the way is written in English Program pak or Program pack?

---------------------------------------------------------------------------------

________________________________
De: Coco <coco-bounces at maltedmedia.com> en nombre de James Ross <jrosslist at outlook.com>
Enviado: viernes, 14 de abril de 2017 03:03 p.m.
Para: CoCoList for Color Computer Enthusiasts
Asunto: Re: [Coco] VCC Update

Bill and Luis, how about this as a compromise:

Virtual Hardware (*.dll)
Program Packs (*.ccc, *.pak, *.rom)
All Files (*.*)

So that away, there is a clear distinction between a ROM file, regardless the extension or a piece of hardware attached. That might clear up the difference between the two kinds?

Luis, the thing about using "Cartridges" by itself is that some carts (sound, etc...) would actually fall into the  Virtual Hardware category.

That was actually confusing to me at first, a while back, that you could load DLL's  -- so for some time, I couldn't understand what happened to my MPI and then I would go directly to the *.INI file and fix it there.

I still need to check if VCC already knows what do w/ the other extensions ... and the any file option would have to equate to being a ROM file as well.

________________________________________
From: Coco <coco-bounces at maltedmedia.com> on behalf of Luis Fernández <luis46coco at hotmail.com>

I would like to propose:
The virtual hardware should be called: instead of Program Paks, would it be, virtual hardware, would you agree?
Not integrated, I propose

Virtual Hardware (*.rom, *.dll)

Cartridges (*.ccc, *.pak)

All Files (*.*)
________________________________
De: Coco <coco-bounces at maltedmedia.com> en nombre de Bill Pierce via Coco <coco at maltedmedia.com>

This looks cool James, It's something I've complained about since I first ran VCC back when Joseph was developing it.

BTW, Luis's patch could very well just include both sets in one line. There's not need to differentiate the types as they're all the same (except dll). It would get confusing to some. I.E. "Program Packs(*.ROM,*.DLL,*.ccc,*.pak)

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco
CoCoList for Color Computer Enthusiasts - pairlist5.pair.net<https://pairlist5.pair.net/mailman/listinfo/coco>
pairlist5.pair.net
This is a list for enthusiasts of the Color Computer in all its forms, its clones, and its software. To see the collection of prior postings to the list ...

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco