I guess it needs to be said, but feel free to help out with development!
Grab git and/or sourcetree, check out the source code, check the issues and make edits, and create a pull request. It's not terribly difficult to get set up for that, and anyone without any knowledge can tackle some of the "good first issues" marked on our issue tracker, like Issue #1140 (UXP)
Feel free to help out!
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Feel free to help out!
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Feel free to help out!
Is there a high-level description of how the UXP source code is structured?
Like, where to find components dealing with certain features or something like that. Doesn't have to document everything in details.
I looked around the core when I was developing an extension (I was looking for a certain API and ended up exploring the xref), and it's hardly obvious where to go to find something when starting out.
This is actually a problem most programs have, so it'd be awesome if UXP could have something like that.
Like, where to find components dealing with certain features or something like that. Doesn't have to document everything in details.
I looked around the core when I was developing an extension (I was looking for a certain API and ended up exploring the xref), and it's hardly obvious where to go to find something when starting out.
This is actually a problem most programs have, so it'd be awesome if UXP could have something like that.
-
Fedor2
Re: Feel free to help out!
vannilla
Look schemes there https://wiki.mozilla.org/Gecko:Overview.
Regarding the issue, Do you want Pale Moon cease registers its self...?
Look schemes there https://wiki.mozilla.org/Gecko:Overview.
Regarding the issue, Do you want Pale Moon cease registers its self...?
Re: Feel free to help out!
Thanks, I bookmarked it.Fedor2 wrote: ↑2019-06-26, 15:10vannilla
Look schemes there https://wiki.mozilla.org/Gecko:Overview.
I'll check it out when I can.