Why would it not if booted inside a sig patched fw?With .elf, yes, through appropiate Makefile! But, as I say, there is a high probability that HBL in .cia format doesn't work ever!
Why would it not if booted inside a sig patched fw?With .elf, yes, through appropiate Makefile! But, as I say, there is a high probability that HBL in .cia format doesn't work ever!
Because a HBL in .cia format couldn't load .3dsx homebrew files, as currently HBL (boot.3dsx) does!Why would it not if booted inside a sig patched fw?
I see where you're coming from but has anyone actually tried a .cia version of the HBL? If no ones tried it how can we be certain that it will/wont work? (Haven't read much so if someone has attempted a .cia build don't kill me)Because a HBL in .cia format couldn't load .3dsx homebrew files, as currently HBL (boot.3dsx) does!
Well, I'm not completely sure about that, but there are some tecnical reasons to infer that. For this, I say "high probability it doesn't work"... However, would be good if someone try to make a .cia from this HBL, load from CFW and see if really works or not!I see where you're coming from but has anyone actually tried a .cia version of the HBL? If no ones tried it how can we be certain that it will/wont work? (Haven't read much so if someone has attempted a .cia build don't kill me)
Well that's just amazing...I decided to whip up a concept of how I think it should look
Will be great if someday custom HBL looks like that!I know it's currently in an early build, but I'm just a little bit concern on how it would turn out in the end. Based on past experience, concepts sometimes don't translate very well into products (not all programmers are necessarily graphic designers).
So I decided to whip up a concept of how I think it should look.
I tried to keep the concept as realistic as possible based on how the homebrew launcher currently handle things. I thought the waves from the official homebrew launcher looked great, so I've added them here. I've also changed the font to Robot since Segoe UI is the property of Microsoft. Lastly, I've changed some things to blue as I think accent colors are important for providing characteristics to the launcher.
If only OP put it on GitHub ._.Will be great if someday custom HBL looks like that!
I already told him; he hasn't answered since then.Teach him how to?
I know it's currently in an early build, but I'm just a little bit concern on how it would turn out in the end. Based on past experience, concepts sometimes don't translate very well into products (not all programmers are necessarily graphic designers).
So I decided to whip up a concept of how I think it should look.
I tried to keep the concept as realistic as possible based on how the homebrew launcher currently handle things. I thought the waves from the official homebrew launcher looked great, so I've added them here. I've also changed the font to Robot since Segoe UI is the property of Microsoft. Lastly, I've changed some things to blue as I think accent colors are important for providing characteristics to the launcher.
Looks nice. But it is 90 % the same as TS. I would prefer a bigger icon on the upper screen!
What about selectable themes?I would too, but right now .smdh files don't have bigger icons. If you made the icon bigger, it would just look blurry. I made the concept so that it is actually possible to create based on how the Homebrew Launcher currently works.
We might be able to get bigger icons if the launcher used .bin files from CIA homebrew apps, but I don't think that'll happen.
Yeah, making the icon bigger is not the solution. That shadow, the big text, and the wave make it look way better than a bigger icon IMO.I would too, but right now .smdh files don't have bigger icons. If you made the icon bigger, it would just look blurry. I made the concept so that it is actually possible to create based on how the Homebrew Launcher currently works.
We might be able to get bigger icons if the launcher used .bin files from CIA homebrew apps, but I don't think that'll happen.
This response is neither helpful nor encouraging. I have already been made aware that it doesn't work, have already said I will try to sort it, and have already added it to the todo list. Posting to say "it's still not working" is pointless and will only make me feel resentful about working on it at all.Target title selector still not working...
This isn't supposed to come off as rude and I apologize if you're offended. But at this point it's also stressful if it's done by a lone person. Sure everyone will have their input and opinion but as someone said, putting it on github isn't so someone can steal credit or so. Rather we can help with the input while still remaining as your work, the commits posted or added by people who are script kitties can be cherry picked by you. Not releasing the source code only makes it difficult for people to help but also closes the window where no help can be provided and you might as well deem this and lock it up until you feel like you're ready to try again. Not trying to provoke you or anything but the whole point of a beta phase is to accumulate feedback.This response is neither helpful nor encouraging. I have already been made aware that it doesn't work, have already said I will try to sort it, and have already added it to the todo list. Posting to say "it's still not working" is pointless and will only make me feel resentful about working on it at all.
Suggestions about the UI are helpful and I do agree that the large icon is not the best solution. I already intend to change the font and will do so when I am back home at my main computer and can compile the font library.
Releasing the source will not happen while this is still in beta. I'm having issues where adding new code to the project causes it to hang when launching an app. I will therefore not release the source until I have either sorted that or added all of the features I originally intended for this project and managed to keep it stable.
I don't mean to sound harsh about any of this, but I'm getting several posts here and also private conversations started which are all asking about the same things, so I just want to be clear.
Thanks for this post Misledz - no offence taken at all. I do understand your points about sharing on GitHub and will be looking in to how to do this next week. I would still prefer the source to be at least stable when adding new code before releasing as otherwise it's hard for others to contribute.This isn't supposed to come off as rude and I apologize if you're offended. But at this point it's also stressful if it's done by a lone person. Sure everyone will have their input and opinion but as someone said, putting it on github isn't so someone can steal credit or so. Rather we can help with the input while still remaining as your work, the commits posted or added by people who are script kitties can be cherry picked by you. Not releasing the source code only makes it difficult for people to help but also closes the window where no help can be provided and you might as well deem this and lock it up until you feel like you're ready to try again. Not trying to provoke you or anything but the whole point of a beta phase is to accumulate feedback.
Just my two cents.
Thanks for understanding if you need help with github I'm sure there are more experienced users than I am, who are willing to assist you in setting it up in any way we can be it simple or complex, for this project of yours to be a long term one. Not sure if someone has mentioned it but github desktop is fairly easy to use and set up, even better as the commits done are easily checked for errors so makes it easier to compile. Looking forward to it mate.Thanks for this post Misledz - no offence taken at all. I do understand your points about sharing on GitHub and will be looking in to how to do this next week. I would still prefer the source to be at least stable when adding new code before releasing as otherwise it's hard for others to contribute.