Where to report issue's with the IDE?
Hi @Chris, great work on the IDE!!
Well build and lots of Computer to choose from.
Question: Your message says;
"Note: This is a beta version of the IDE. Please report any issues you find."
What is the right place to report these? Is that in this General Chat of the community or is there another place for that?
Issue of the day is the all Commodore variants are down ' Platform not found C128'.
Yesterday it was all working fine!
(There are some others I am happy to share but first want to make sure what is the right place).
Keep up the good work!! (-8
This is as good a place as any for bug reports, though if it is a OMG IT IS BROKEN kinda deal then perhaps a message on bluesky is quicker.
Platform is down was because I deployed new code and Cloudflare seems determined to hold on to some of the JS and deliver other as fresh and I can't for the life of me figure out why that happens. That mismatch causes the error. I'm using cache-busting everywhere, still happens. Right now even for me I have to open incognito for some platforms, down right annoying!
BUT C128 should be back now.
Should ...😩
WOW Seriously Impressed Chris Garrett with the very quick turn around in adding the features much appreciated!!
Well you know what they say you give them one finger and they will want more... (-'
So if I am overstepping just let me know...
But when possible would the following be possible as well perhaps;
- For the C128 using the CA65 assembler. As working with the CC65 it is useful to be able to test assembler files separately as well.
- It would be really helpful if next to the provides .lst file also the 'map' file can be provided in the right banner using the -vm option. As this provides vital debug information for development.
- Due to a known issue with CC65 the 'Wrap Function' will break when using the optimize option (-O). Would it be possible to have the '-O' option selectable CC65 perhaps? So to choose to compile with or without that option. (But at least the default would be without the -O option as you have it right now).
To conclude a question: When creating a new file how do I make clear what I want to use?
C, BASIC, asm (ACME) or asm (Kickassembler) etc.? Especially, for asm when there are multiple options. How does the backend knows what compiler/assembler to use?
Again wonderful IDE you created!
ZXCommodore all good suggestions not overstepping at all. I am going to add "templates" in the 'new' option, but in most cases the assembler has a specific file extension with the default .asm being the first assembler I add, same with basic will usually be the manufacturer bundled basic as .bas then .xcb for xc-basic, and so on, but it is very not obvious so I need to make that better :)
How would you suggest the CLI switches be selected? we could have # directives in the code?
Chris Garrett Thanks for the encouragement I will keep them coming in that case.
Looking forward to the templates and guidance on which extensions to use to select which assemble/compiler.
As for the CLI it could indeed be via # directives but is perhaps how the 'godbolt.org' site does it also an option?
Being just a field in top bar where you can add the appropriate options which then will be checked and parsed by your backed?
ZXCommodore ooh, yeah that is a good ide. The mobile experience is pretty cramped but I doubt anyone would miss using that on their phone so should work fine