Can't edit omni.ja

[Moonchild]

A dev essentials account is free. I guess I flagged my account as a dev account in the past by signing up for it. Doesn't make much difference, just gives you access to developer tools.

https://visualstudio.microsoft.com/dev-essentials/

[New Tobin Paradigm]

He can still do what he wants to do via an extension.. So I dunno why he is trying to grab visual studio to recomple with.

You realize he is gonna ask every single question ever and not understand what you tell him right?

It will go on for literal days.

[Isengrim]

I'm all for trying to build it yourself, but yeah, it's a lot of work for what I think they want to do. *Shrug*

[John connor]

I looked over the Wiki page on compiling PM and it looks straight forward and fairly easy to do. I'm not particularly dumb when it comes to computers or even my own websites. I can follow instructions quite well. It's just that double account crap that has be tripped up. In typical M$ fashion not only do I need a M$ account, but another damn account just to download a FREE, let me repeat that and bold the most pertinent. FREE download of Visual Studio Community Edition.

The only thing that's gonna be a PITA is that from what I read at the Wiki page here is that it sounds like it takes forever to compile. Yes, my gaming desktop more than meets the requirements.

Now I realize this is all dumb beyond dumb just to change the about:palemoon and the logo that displays in blank tabs. But as I said before, I did these simple edits via editing the omni.ja file and successfully repacked the omni.ja file and my browser worked without any issues once so ever. I even made a backup of the original omni.ja file just in case. Never the less, I have always wanted to learn how to compile this thing called Pale Moon and perhaps learn something in the process. I never realized how complex a browser really was.

Question: what is the code at Github that is used for the source prior to compiling? Is it all mostly HTML, CSS and JS or what? Perhaps one day I'll learn those. As of right now I'm code stupid, but I can understand a few things. After all, I edited the omni.ja file and learned how to do it on my own.

Edit- And just an FYI. I already found the necessary code in the Github source to make my edits and I have edited those files and placed in my new about.png image ready for compiling. I used a great free, but also paid offering called Fileseek to find the right files.

PS. Try reading my profile biography.

[Isengrim]

Most of the "chrome" (front-end) is XUL, JS, and CSS with a smattering of HTML. A lot of the application code beneath that is C++. There's also quite a bit of scripting for the build system including Python and Bash. The Windows installer uses NSIS. It's a real hodgepodge of technology.

[New Tobin Paradigm]

Somebody better pick up that phone BECAUSE I FUCKING CALLED IT.

Look all you need to do is put your little logo in an xpi file with an install.rdf and a chrome.manifest with a chrome override directive for the actual chrome url that about:logo resolves to and it will work forever on any normal UXP application not just Pale Moon.

Give me your image and I will do it for fuck sakes.

Btw, we.. don't offer support for building the software nor custom builds. Use an extension as I described or you are cut off and on your own.

[Moonchild]

Use an extension as I described or you are cut off and on your own.

Now, now, we're not against helping people who want to try and build from source now, are we? They did say it was something to do "as a learning thing".

I'd be happy to help with that as well but if you already have a problem with just signing up for a dev account to get a PROPRIETARY and commercial development suite at no cost, then I think your priorities are wrong. Remember Visual Studio is a huge development environment and is not cheap -- Microsoft is well in their rights to ask that you specifically indicate that you are interested in developing software (it will all be under one account and once login, as I already explained it just flags your account as dev, and might send you a dev newsletter by default that you can unsubscribe from) before allowing you to download a copy of what they have released for free to the community (this is not "free software"!). So don't be a putz and click the link, say yes, and proceed on your merry way to download.
Then do your best to follow the clear instructions -- yes it will take a while to build; it's over 20 million lines of source code. Expect about an hour for a full build from scratch. Builds after that will be much shorter if you've edited files unless the build system triggers a rebuild.

P.S.: I won't be able to guide anyone through the process -- it's supposed to be a learning experience so try to figure out as much as you can yourself.
I do agree with Tobin that aside from the learning thing, you should be using an extension for what you want to change. Rebuilding from source just for that is dumb and you will forfeit any support on your use of the private build in the process because we cannot be sure if it was built correctly.

[rickmv]

download-visual-studio-community-edition-2015 ISO direct from M$

https://stackoverflow.com/questions/442 ... 5-not-2017

[John connor]

and you will forfeit any support on your use of the private build in the process because we cannot be sure if it was built correctly.

Fair enough.

download-visual-studio-community-edition-2015 ISO direct from M$

https://stackoverflow.com/questions/442 ... 5-not-2017

Thanks.

[Goodydino]

To change an image in part of the interface, you could use userChrome.css and a new image in the content directory. Why not do it that way?

[New Tobin Paradigm]

He could also build a simple extension with an override chrome directive. He is just being an idiot. Ignore it.

[Moonchild]

Why are we still discussing this, again?