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

Example usage #9

Open
avivace opened this issue Jul 11, 2024 · 8 comments
Open

Example usage #9

avivace opened this issue Jul 11, 2024 · 8 comments
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@avivace
Copy link
Member

avivace commented Jul 11, 2024

To better promote/show off the tool, it would be cool to add some example usage/output

@Rangi42 Rangi42 added this to the v0.3.1 milestone Aug 3, 2024
@Rangi42 Rangi42 added the documentation Improvements or additions to documentation label Aug 3, 2024
@Rangi42
Copy link
Contributor

Rangi42 commented Aug 8, 2024

@ISSOtm Want to handle this one? I'm not sure if you'd want it in the README, man page, --help output, or what.

@ISSOtm
Copy link
Member

ISSOtm commented Aug 8, 2024

I'm thinking the README and/or website would be appropriate. We would surely want to keep it simple, so I'm thinking of a video of assembling the following ROM and running it in an emulator?

SECTION "Header", ROM0[$100]

EntryPoint:
    jp Main

    ds $150 - @, 0 ; Reserve some space for RGBFIX to fill in the header.

SECTION "Main", ROM0

Main:
    ; Wait for VBlank.
.waitVBlank
    ldh a, [rLY]
    cp 144
    jr nz, .waitVBlank

    ; Move the Nintendo logo left a little.
    ldh a, [rSCX]
    inc a
    ldh [rSCX], a

    ; And keep going!
    jr Main

@avivace
Copy link
Member Author

avivace commented Aug 8, 2024

Cool @ISSOtm . Should we create a section / a page on the rgbds-www?

@ISSOtm
Copy link
Member

ISSOtm commented Aug 8, 2024

If it's meant to show off a little, shouldn't we put it on the front page?

@avivace
Copy link
Member Author

avivace commented Aug 8, 2024

If it's meant to show off a little, shouldn't we put it on the front page?

but then front page of a separate website? Is it worth to build a separate website when rgbds-www?

@ISSOtm
Copy link
Member

ISSOtm commented Aug 8, 2024

Oh, this is rgbobj, not rgbds itself. My apologies, I got confused.

Scratch what I said above about a video, an ASCIIcast would probably be a good idea. Not sure where to put it, though.

Something @Rangi42 and I have been considering for rgbds-www, is creating a page showing peripheral tooling support (e.g. editor/IDE syntax highlighting, etc.), maybe seeded with some of the current content of awesome-gbdev. rgbobj would have a good place there!

@avivace
Copy link
Member Author

avivace commented Aug 8, 2024

Oh, this is rgbobj, not rgbds itself. My apologies, I got confused.

Scratch what I said above about a video, an ASCIIcast would probably be a good idea. Not sure where to put it, though.

Something @Rangi42 and I have been considering for rgbds-www, is creating a page showing peripheral tooling support (e.g. editor/IDE syntax highlighting, etc.), maybe seeded with some of the current content of awesome-gbdev. rgbobj would have a good place there!

Yes, exactly. What about a Tools -> rgbobj page ? (with tools in the navbar?). See also #2

Anyway, @ISSOtm the snippet you previously posted for rgbds itself could also be a nice addition to the home page, no? (maybe let's move this discussion to an issue on rgbds-www ?)

@ISSOtm
Copy link
Member

ISSOtm commented Aug 8, 2024

“Tools” sounds a little less broad than what we're aiming for, since it includes things like syntax highlighting. “Integrations”? (“Support” sounds like we're offering some kind of on-call service :P)

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

No branches or pull requests

3 participants