Would it be acceptable for the launcher to be written from scatch and still by made offical?
thanks
New: DesktopSnowOK (Jan 6, 2025), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec/Jan!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Not a developer here, remember that.
I would think so long as it was Open Source, bug free, and followed the same "rules" as the other launchers that it should be fine. In fact if you could write a better launcher I'm sure John would want to use it. I myself did not even realize that there was a question. I figured that most launchers were based on pre-existing ones to make it easy. I didn't think they had to be.
JMO, but remember I'm not a developer, so I might be completely wrong here. I defer to John,
Things have got to get better, they can't get worse, or can they?
its gonna be ALOT simpler.....
Na na na, come on!
if you can ... that's the first Question?
Will it be better? That's the Second Question
,
Things have got to get better, they can't get worse, or can they?
Na na na, come on!
IMHO, it's best to stick with the official launcher. All the language strings are the same, ini for splash disabling, etc. All the variables are the same, and overall, it's really not that hard once you get used to it.
Is the PortableApps Suite Base, not the simplest thing to use already? You just extract it to the root of your device, click the icon there and your ready to start adding apps! No configuring any settings, (unless you actually want to) or anything to update. Unlike geek.menu, (which I like too) that has options to configure upon
the initial set-up.
It's kind of hard to keep up/keep track of multiple launchers and such. I say stick with the official one.
The official launcher needs to be better templatized. You know, with BEGIN/END sections like the installer source has. Right now it's really confusing to try and edit. The custom path handling doesn't make it any easier, either...
I'm finding it pretty straightforward, and I'm just starting to develop apps.
Yeah, but the BEGIN/END section comments couldn't hurt.
They're great in the installer because they say right away "modify this" but also additionally, "don't touch anything else!" Rather than having to read through the code to figure out from context what's safe to change and what's not...