Great! There’s some branches off of the develop branch where I’ve done some work on some of the issues. Would it be useful if I go through and mark some issues as ‘Good first issue’ and perhaps create a GitHub Project for the coding print with Paladin issues that are short work items?
Here’s the Kanban style summary for all the good first issue issues for the coding sprint! If there’s any guidance/notes that need to be added there to assist, let me know!
Would any of the seasoned developers wants any specific hardware or hardware combinations available to test during this period? Either as in someone else testing certain setups, or shipping something out to them?
Quick question: Is the recommended way to develop Paladin on Haiku? i.e by bootstrapping it?
I boot Haiku on a VM, and am on a Windows 10 machine, my workflow being clang/MSCV, CMake and VSCode. So it generally works well for cross platform C++ projects. I read the CONTRIBUTING.md and had this question.
Yes, it’s easiest to do it inside Haiku since you will need to run the generated binaries there anyway.
Cross compilation is possible; but not easy to set up because we do not ship a ready to use cross compiler (there are some scripts to create one but they are not well documented and possibly not well maintained).
If you still need a icon for Kottan this a quick (2D) draft of a weird detective with trench coat, moustaches and a fedora hat, somehow between Clouseau, Poirot and Columbo; Kottan never aired in Italy so I don’t have a reference, in the 80’s we only had Derrick and Matula ^^;
This is a pretty good start for an icon! All it needs is to be rendered at an isometric angle just like most Haiku-style icons. Colours are quite on-point already.