What percentage of world-wide browser users actually perform add-on coding?

[Pallid Planetoid]

^ That's OK -- and totally understandable. You're time is certainly very valuable! (at least I'll maybe get the last word this way -- that's just a bit of humor on my part, so please do not be offended )

[coffeebreak]

Almost as though MDN and the XUL Tutorial don't exist.

But Mozilla will remove that stuff by the end of the year.

mdn-removal-notice.png

I gather that the MDN documentation is disorganized and incomplete.
But nevertheless, it's what there is.

So are there plans to mirror that material?

[Moonchild]

If someone can make a functional mirror of it, I'll happily host it.

[New Tobin Paradigm]

There is no such thing as a functional mirror. Even with the MDN dump I have which they don't offer dumps any anymore.. It can't just be put up on the web and function. I believe that the 2016 dump of mdn I have is sufficient for all our needs.. The issue is extracting and translating it because it is marked up with syntax that only a functioning mdn software of the time would understand.. etc.

So in any event, it would not ALL be lost and since most of the xul and api shit is perpetually out of date anyway.. Doesn't really matter it is a few months before ESR52 happened. Especially the XUL parts.

I would argue MDN info TODAY is less useful cause of losses, rewrites, and infections. And yeah, I will get to it.. Soon.

[moonbat]

And yeah, I will get to it.. Soon.

Bless you, Tobin

Any SDK needs up to date and decent documentation if it is to survive, yet despite that there were 20k extensions over the years due to the enthusiasm of extension developers despite their permanently incomplete docs (even the tutorials they have were contributed by 3rd parties such as XULPlanet). A cursory look at their WebExtensions documentation when I accidentally found a page relevant for that shows that even today there's stuff marked 'to do'. Amazing how with all their revenue they can't be bothered to hire a few decent technical writers and include documentation updates as part of the release cycle. Then again if you're churning out releases every couple of weeks like an Energizer bunny amped up on meth, that doesn't make for stable software that anyone else can code against.

[coffeebreak]

If someone can make a functional mirror of it, I'll happily host it.

I believe that the 2016 dump of mdn I have is sufficient for all our needs.. The issue is extracting and translating it because it is marked up with syntax that only a functioning mdn software of the time would understand.. etc.
[...]
And yeah, I will get to it.. Soon.

That's great. Thank you.

[New Tobin Paradigm]

The subset for XUL widgets and development is the top priority.. Really most other things can be gleamed by-example.

[Moonchild]

I do have somewhat complete docsets for XUL, XSLT, and pre-madness CSS and HTML.

[New Tobin Paradigm]

Feel free to send them to me at some point that isn't directly after you read this post.

[Moonchild]

Feel free to send them to me at some point that isn't directly after you read this post.

For everyone's benefit. These are Zeal compatible.
http://archive.palemoon.org/contrib/docsets/

[coffeebreak]

These are Zeal compatible.

I'm guessing that "Zeal" is this: https://zealdocs.org/ ?

Are these docs intended in addition to the hopefully forthcoming mirror?
Or in lieu of?

[New Tobin Paradigm]

I am not creating a mirror. Though for some aspects it may appear as one initally.. I intend on creating a functioning and relevant resource for all of UXP-kind. It will take a while and I will need your help in doing it. Good news is, I already have the software for it worked out as well as simple method of contributing and quality control.

I will let you know in the near future. THERE IS ONLY XUL!

[moonbat]

I intend on creating a functioning and relevant resource for all of UXP-kind. It will take a while and I will need your help in doing it.

I volunteer. Do let me know how I can help, or better, when would be a good time to reach out to you on IRC.

[coffeebreak]

I am not creating a mirror. Though for some aspects it may appear as one initally.. I intend on creating a functioning and relevant resource for all of UXP-kind.

What kind of resource?
Meant to do what?

Will this "resource" provide the documentation to support individuals learning, such that they can fully understand the code in some given extension they wish to fork?

[New Tobin Paradigm]

What do you think?

[coffeebreak]

What do you think?

I'm sorry that you don't wish to answer the question.
Certainly I can't force you to answer, but I had hoped you would choose to.

I have doubts - or else I wouldn't have asked what I did.

> I am not creating a mirror. Though for some aspects it may appear as one initally.
What does this mean?
Are you preserving what remains of the MDN classic extension documentation and making it available to all?
Or not?
Because It's not at all clear to me from your earlier post that you are doing that.

[New Tobin Paradigm]

Guess neither a mirror or what I plan to do would serve you very well by the looks of it. What a disappointment.

[Moonchild]

Or, y'know, relax and wait to see what is created.

[coffeebreak]

Guess neither a mirror or what I plan to do would serve you very well by the looks of it.

Me personally...?
A mirror would suit me just fine. If I chose to use it.
You clearly have the resources to make one available. I'm sorry that you are not willing to do it.

As for what you have planned, you have not shared what that is.
So long as it's a secret, it's pretty hard to know what to think of it or say about it.

I wish that you would explain specifically what you have in mind to do.

(Edit: Sorry Moonchild, missed your post.)

[AgentOrange]

Or, y'know, relax and wait to see what is created.

I will subsidize this course of action by snatching the big archive to limit the worst-case scenario

I assume that the most helpful CoA from there (assuming my plea to Mozilla's web guys goes entirely unheard) will be to begin looking into to how to clean up the files, and isolate just the relevant ones?