Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are some ways we can improve SBTCVM for the v2.0.3 release? #4

Open
ThomasTheSpaceFox opened this issue Sep 2, 2017 · 3 comments
Labels
Milestone

Comments

@ThomasTheSpaceFox
Copy link

areas to think about:

  • ease of use of graphical utilities
  • easing the learning curve for new users
  • general polish
  • general improvements

@SBTCVM/core-devs any ideas?

@ThomasTheSpaceFox ThomasTheSpaceFox added this to the v2.0.3 milestone Sep 2, 2017
@eekee
Copy link

eekee commented Jan 23, 2018

The assembler requiring '|' as a separator is awkward to type, a bit awkward to read, and to be blunt, unnecessary. Space would work just as well.

Assembling from the launcher would be nice, perhaps by clicking on .tasm files. Perhaps they could appear in another folder tree. I guess it might be best if the assembler wrote its output to a file in this case, as well as displaying it. That way, the file could be opened in a text editor for copy/paste.

Or, of course, copy/paste in the various text fields would be very nice. (Shell, console, calculator...)

@ThomasTheSpaceFox
Copy link
Author

firstly, the assembler not to long ago got an alternate separator. (semicolon)
secondly, assembling from the launcher is doable in theory, particularly if we make the assembler log its output.
third, the textinput function is still incomplete, and pygame's clipboard support is experimental, and subject to break... so clipboard integration might take some extra dependencies.

@eekee
Copy link

eekee commented Jan 24, 2018

Clipboard still a problem in the 21st century? sigh Perhaps other languages/libraries may have better support. I hope so.

Another idea: Some means of automatically checking assembler documentation against assembler code so they don't get so far out of sync. I might be able to provide a prototype for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants