Add title attributes to the screenshot links
Modernise the AppStream file
Replace YouTube video with links to the auto-generated channel and search
I inherited the project from the original author @amuzen, unfortunately they didn't document the format apart from the source code in packfile.h and they didn't release the source level files. I have been meaning to decompile levels.dat back to some sort of source level files and then delete the levels.dat file from git, but I never got around to it. Looking at the code, I see there might already be some form of level editor that is enabled when you define an EDIT macro, and I got it to compile and...
*.users.sourceforge.net: full file listing?
Have the DevOps team found the cause yet?
SDL2: Destroy the old window when changing the window size
wip
WIP: no longer stretched, still ugly
WIP: working now, but ugly
fix ftbfs
use right config header
use right config header
fix ftbfs
fix build
fix building
WIP
WIP: Enable window resizing and keep the correct aspect ratio.
Add a recording of the frogs in the pond at La Escuela de la Mariposa
WIP: gluPerspective replacement
WIP
WIP joystick fixes
wip
wip
WIP
WIP
wip
wip
SDL2: Destroy the old window when changing the window size
wip
SDL2: Fix window event handling
On Tue, 2022-09-20 at 00:43 +0000, Stephan Sokolow wrote: It's a bit incomplete. Aside from me being a completionist and a perfectionist, I'm not sure it'll pass validation, Is there a command-line validator tool for the format I should use? You'll probably see me offering up a patch to expand your Appstream XML out to something like [this] Great, thanks. Speaking of which, would you like me to add a [bugtracker] element to the Appstream XML for Tomatoes when I add the x-checker-data definitions...
On Mon, 2022-09-19 at 06:58 +0000, Stephan Sokolow wrote: No problem. As long as you're OK with it, I'd be willing to put together a build manifest and Appstream XML for it. Please do. There is an Appstream XML file in the upstream git repo already, hopefully it is suitable for Flathub too. Would you prefer I put something up on my personal GitHub account for you to review before I do the "fork new-pr on flathub, put your submission in it, open a PR, and let them review it" dance and involve a submission...
Thanks for the suggestion and sorry for the delay in responding. I agree that it would be useful for Hex-a-Hop to be available on Flathub for folks who use immutable systems like Fedora Silverblue or SteamOS. Since Flatpak is a packaging system I think that the packaging files should be maintained separately to the upstream project. The appropriate location would be where separate Flatpak packaging is often stored. For Flathub that seems to be in a git repository in the @flathub organisation on GitHub....
config.guess is not in the git repository, only the release tarballs. Please re-run the autogen script during your build process to update the config.guess file. Your distribution should be doing this for every package already, otherwise you can't be sure that you will be able to rebuild the configure/Makefile files. The next release tarball will of course update config.guess. -- bye, pabs https://bonedaddy.net/pabs3/
icns2png.c:70: possible missing "," ?
Thanks for the report, I have fixed this in the git repository with this commit: https://sourceforge.net/p/icns/code/ci/921f972c461c505e5ac981aaddbdfdde97e8bb2b/ BTW, if you have any further changes, I suggest you use the SourceForge merge requests feature. First you make a fork of the git repository, then you push to your fork, then you request we merge your fork into the main git repository. https://sourceforge.net/p/icns/code/fork https://sourceforge.net/p/icns/code/merge-requests/
Add missing comma to the list of image size strings
Is the copy of the LZMA SDK in NSIS identical to the upstream one or has it been modified for NSIS?
SourceForge supports forking and merge requests too: https://sourceforge.net/p/sox/code/fork/ https://sourceforge.net/p/sox/code/forks/ https://sourceforge.net/p/sox/code/merge-requests/
Are you planning on packaging cdesktopenv for Debian? If so, these pages might be helpful: https://bugs.debian.org/689098 https://mentors.debian.net/intro-maintainers
When saving PNG use original data instead of re-encoding
Version bump
wip
wip
Merge Debian changes from the last two uploads
Reflect the VCS change in debian/changelog
wip
wip
wip
FIXME: size elements should be unsigned!
GNU poke
wip
wip
wip
Point taken re GIF, although I'm fairly sure modern video codecs compress more than GIF can, and modern HTML features allow using videos in a similar way to how old browsers treated GIF. The code is in C++ and OpenGL, with an in-progress port to OpenGL ES. -- bye, pabs https://bonedaddy.net/pabs3/
Sounds like you are talking about a new menu item that brings up a new screen listing the powerups. Unfortunately there isn't enough room on the menu for any new menu items. Another approach might be to extend the in-game tips (we already have one for super shields), so that when a powerup appears for the first time, a tip appears telling you what it does. The screenshots unfortunately aren't easy to recreate or modify since they are just captures during games created by user input. I'd like to make...
WIP
wip
Add a recording of the frogs in the pond at La Escuela de la Mariposa
WIP
WIP: Enable window resizing and keep the correct aspect ratio.
WIP: gluPerspective replacement
WIP
fix build
fix ftbfs
WIP
fix building
use right config header
WIP joystick fixes
Initial attempt at an SDL_ttf text rendering backend
foo
use right config header
fix ftbfs
WIP: working now, but ugly
WIP: no longer stretched, still ugly
wip
That is weird, it is the first link on the website so Google should be finding it easily. Maybe because the website is not on https, Google is penalising it. I have switched it over to https in the admin, it should get the redirect to https added soon. If I search for "Chromium BSU powerups" it tells me to do a search for "Chromium BSU power ups" instead and if I search for that then the info page is the second result in the links, so maybe I just need to add the word without a space to the page...
The powerups are actually already documented on the website: http://chromium-bsu.sourceforge.net/info.html This file is also in the source code: https://sourceforge.net/p/chromium-bsu/code/ci/master/tree/data/doc/info.html I see the powerups are not documented in the manual page, it would be good if you could send a patch for that, otherwise I can do it later. -- bye, pabs https://bonedaddy.net/pabs3/
There are three different coloured skull powerups: The red/orange skull gives you double fire rate for the starting weapon. The green skull gives you a centrally fired slow moving blue-green column that does lots more damage than the starting weapon. The blue skull gives you a pair of blue balls alternately fired at a fast rate from either side of the ship outside your starting weapons, these do the most damage of all three weapons. There are three different coloured penguin powerups: The blue one...
Assorted cleanups in preparation for SDL2 port
Merged the new branch, thanks!
Lets defer the cmake removal for now.
Looks good, a couple of thoughts/questions: Is the SDL_endian.h change compatible with SDL 1.2? The FATAL merge should probably have some whitespace before the #endif. I would move the FATAL commits before the SDL_Init commit so that the commit checking the SDL_Init return can be eliminated in favour of the one making it use FATAL. I'm not sure about the cmake removal, since cmake is a lot easier to use on non-Linux platforms than autotools.
I have proposed to the SDL folks to accept SDL_Pango within their new GitHub org.
I have written the attached cvs2git script to convert the CVS repo to git.
On second thought I think the best option would be to move sdlpango to the new libsdl-org GitHub organisation, where it can be maintained by the libSDL community. https://github.com/libsdl-org
SourceForge has a procedure to take over projects, I suggest doing that instead of forking this project.
Thanks for the information. Could you also share the modifications that you used to confirm the information on WikiPedia? The output of git format-patch would be the best option. -- bye, pabs https://bonedaddy.net/pabs3/
Thanks for the information. Could you also share the modifications that you used to confirm the information on WikiPedia? A link to your git repo containing the modifications would be the best option, otherwise the output of git format-patch would work too.
icnsutil: add missing icon names
Add support for 64px ARGB (icp6) icons
Split some long and repetitive if statements into multiple lines
Add support for 128px ARGB (ic07) icons
Remove unnecessary parentheses
add call to set interlace handling required by libpng 1.6.x or later