[Coco] VCC Update

[Luis Fernández]

> Issue #67, right?

yes

Very interesting

Another thing that is needed is to pass a PC text to the keyboard buffer so that the coconut writes it as if typed

I would also like to put several languages, this I have already done, for example, it was I who did the Spanish translation of Nestopia, the emulator of Nes, and I was fine

I can do these things initially and after studying the code I could do deeper things



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


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

Luis Fernández wrote:
> I would like to know if the improvements to the VCC are dealt
> with here or by the page
> https://github.com/VCCE/VCC/issues
[https://avatars3.githubusercontent.com/u/14001679?v=3&s=400]<https://github.com/VCCE/VCC/issues>

Issues · VCCE/VCC · GitHub<https://github.com/VCCE/VCC/issues>
github.com
VCC - Virtual Color Computer Emulator ... Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the ...




Yes, it looks like you posted it to the right place. Issue #67, right?

As far as I know, there has been no one working on improving the current Windows only version of VCC.  At least for quite some time.

Just the other day (this Monday actually), I finally decided to take a whack at it. Let’s see how far I get. :) :)

My “fork” of is https://github.com/jross9/VCC  you can read my plans on the main page there.
[https://avatars1.githubusercontent.com/u/16421413?v=3&s=400]<https://github.com/jross9/VCC>

jross9/VCC<https://github.com/jross9/VCC>
github.com
VCC - Virtual Color Computer Emulator




Don’t know what will be the ultimate outcome yet – if Bill (the upstream) maintainer of VCCE/VCC agrees w/ what I am doing or not and if he wants to eventually incorporate what I will have done back into the “official” release(s) he/we can do that -- and I can send “Pull Requests” etc (I am still learning Git/GitHub) … otherwise I’ll probably create a new branch VCC-Classic.

I want to incorporate as many improvements as I can.  But as only being able to work on it in my free time (which is not that much) then progress might be slow.

I will keep my progress public by making commits often. If you don’t see any commits for more than a day or two, that probably means I haven’t worked on it during that time.

Your issue Issue #67 looks simple enough – I will add that on my to-do and update it to include when I might do an “informal” binary release.  I have few fixes I want in there on that first release.

James

--
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 ...