11:59:34 <teruna> Hello! I just encountered this encoding error when applying the latest patch queue: "abort: decoding near 'm in rustc�s regress': 'utf-8' codec can't decode byte 0x92 in position 267: invalid start byte!". It seems to stem from mozilla-release/patches/servo-18854-58a1.patch.
12:02:27 <frg_Away> teruna. I fix it in a minute. Just change rust´s to rust's or rusts
12:03:19 <teruna> frg_Away: Perfect, thank you!
12:05:04 <frg_Away> should be ok now: https://gitlab.com/frg/seamonkey-253-patches/-/commit/ba4038f399365f16c45418049a731f0e0b8966bd
12:29:09 <teruna> Thanks, all patches applied successfully. Compiling now.
12:31:36 <frg_Away> teruna probably another bunch in later. Shoudl need to do some bugzilla cleanup but slurping coffee and appyling stuff is easier :)
12:55:12 <teruna> Posting from the new build (Arch Linux, clang 14.0.6, rust 1.64.0). :-)
19:07:10 <CaptainTobin> frg_Away: rustcquestionmarkdiamond.s is disgusting.
19:08:06 <CaptainTobin> frg_Away: your platform has some corrosion
19:51:47 <tomman> waiting for a programming language named after composite materials
20:16:15 <frg_Away> Well I recently needed to fill out a skill matrix at work. Because I have some limited knowledge wrt rust I listed it. Together with the disclaimer that I will quit if I need to actually do something using it. Thank god unlikely. Cobol is as far as I go currently but there are limits :)
20:34:30 <tomman> let's rewrite the Linux kernel in COBOL!
20:35:31 <tomman> MOVE REGISTER-B TO GPU-REGISTER-XZ
20:37:53 <tomman> while I have terrible memories from COBOL at college (in 2006!), I'll take it over those newfangled hipster languages and platforms
20:38:22 <tomman> just do not force me use any compiler made by Fujitsu or I'll commit arson :D
20:44:20 <frg_Away> I started with Cobol in 1984 and swore I would not end with it. The money is good so call me sellout :)
20:46:01 <frg_Away> 88 RUST-BAD VALUE 'URGKKK'.
20:47:52 <frg_Away> tomman is the idiotic js underscore number representation widespread? Can probably make it happen in SeaMonkey then.
20:48:28 <tomman> frg_Away: it's not exactly new, but Discourse is the first consumer I've seen of it
20:48:55 <tomman> dunno why in the hell developers would want number separators on constants, but sadly that now got baked in into the standards
20:49:42 <frg_Away> Number representation with an underscore is probably th dumbest thing I have seen in a long time.
20:54:37 <tomman> oh man, Discourse now has a Loading Screen™
20:55:24 <frg_Away> I am bored. Can I have some spam message in my browser please: https://hg.mozilla.org/mozilla-central/rev/efccbd3e12f8
20:56:25 <CaptainTobin> frg_Away: if you were using Borealis you wouldn't be using a browser.. u'd have to get some spam for the navigator instead
20:58:18 <frg_Away> CaptainTobin. I would first need to switch to something modern so that I have a new tab experience telling me what recent spam I missed.
20:59:03 <tomman> https://meta.discourse.org/t/discourse-not-working-on-an-old-phone-with-an-unsupported-browser/138293 oh, so the sabotage IS intentional
20:59:19 <tomman> you're supposed to disable JS to please Discourse, instead of getting, y'know, served BASIC HTML!
20:59:31 <tomman> oh no, that doesn't follow The Vision™
20:59:32 <CaptainTobin> while I do want to make the blank page/newtab shit work like Phoenix my first attempt was a failure.. I don't want to do that shit tho BUT a new tab page mechnism being there can be extended by extensions
20:59:59 <CaptainTobin> I'd basically make it like Pale Moon's logopage just with a few buttons and a search bar
21:00:20 <CaptainTobin> New Tab New Window New Private Window searchbar.. brand.. done
21:00:26 <CaptainTobin> that's reasonable
21:00:27 <CaptainTobin> eh?
21:00:49 <CaptainTobin> well no new tab that is redundant
21:00:52 <tomman> apparenly I now need to define a GoogleBot UA override for EVERY SINGLE Dickhouse board, how nice of you, Atwood and friends
21:01:01 <CaptainTobin> and if new window or private window it will close the tab
21:01:02 <tomman> otherwise I get punished with JS lockdown
21:01:21 <CaptainTobin> so basically an extensiablity point and two-click change your mind :P
21:01:23 <tomman> "If I were in your position I’m sure I’d be annoyed too. But this is one of the reasons I use an iPhone instead of an Android phone. With iPhone, you get updates for years after buying your phone, while Android is very hit or miss and company-dependent. This means that I can continue benefiting from improved web features used by Discourse while, unfortunately, you lose support."
21:01:26 <frg_Away> You miss search suggestions and the mosteverawesomebar
21:01:29 <tomman> phoneshaming, of course
21:02:01 <frg_Away> tomman Set 91a1 in the current 2.53.15b1 pre. If IanN lets me I will keep it in the release.
21:02:43 <CaptainTobin> the only difference is Apple WILL software sabotage your device a few updates before the final.. Google MAY do the same but more likely the manufacturer or carrier abandons all updates and software ages out of compat range
21:02:51 <CaptainTobin> that is the Truth.
21:02:55 <CaptainTobin> frg_Away tomman
21:02:59 <CaptainTobin> Prove me wrong.
21:03:31 <tomman> and yet, that's the development model chosen by Discourse: "if you're not using the latest shiny bought yesterday, you do not deserve to even read the information you're looking for"
21:03:40 <frg_Away> I own this one: https://www.gsmarena.com/siemens_me45-263.php
21:04:06 <frg_Away> Still works but my eyes could now use a better screen.
21:04:17 <tomman> this piece of garbage board software was released circa 2013, and that has been their position since then: shaming users who deviate from The Vision™
21:04:21 <CaptainTobin> same result, same amount of evil.. less obvious means.. Google for whatever reason is still half-trying to maintain a pretense of not being what they are.. i dunno why they bother but waste resources on that instead of the other activities i guess
21:05:03 <tomman> what really pisses me off is the intentional lockout on Discourse if it ever detects you're using a "not iPhone/modern computer" - it's entirely artificial!
21:05:26 <tomman> remove that, and the forum is actually USEABLE, even if for read only (which it's my use case for 100% of those boards)
21:05:39 <frg_Away> Well we can't change the world. Apple at least supports its hardware for about 8 to 10 years.
21:05:44 <tomman> in the meanwhile, phpBB boards Just Work™ even on lowly IE3 :D
21:06:15 <CaptainTobin> I respond to threats to MY vision only when they have no vision of any kind.. IF someone has a good pure competing vision then may the superior win but those with no vision no understanding .. interfearing with MY shit.. nah dood
21:07:21 <CaptainTobin> tomman: Believe it or not my special component default template layout actually renders decently on IE
21:07:31 <CaptainTobin> not perfect but not bad either
21:07:46 <CaptainTobin> well anything that supports div and some css will do OKAY
21:08:23 <tomman> At my former job I kept compatibility for IE8, even if only because I Could™ (we didn't had any users on IE8, and only one or two on IE11, which were more like happy accidents instead of intentional users)
21:08:47 <tomman> and now that I remember, the IE8 compat stuff was rather minimal
21:08:53 <CaptainTobin> I kept compat with gecko/1.9.2 up until 2018 or so
21:09:10 <CaptainTobin> slightly degraded but perfectly servicable
21:09:34 <CaptainTobin> most stuff i used at the time had prefixes back then
21:09:51 <tomman> I still maintain that product but now as a external contractor, and while I've dropped the IE8 bits, my baseline is still FF52 and whatever was the final Chrome version that ran on XP
21:09:52 <CaptainTobin> like box-shadow
21:09:58 <CaptainTobin> i love me some drop shadows
21:10:12 <CaptainTobin> as anyone here who has looked at more than one thing I have designed can tell
21:10:14 <tomman> it helps that my UI design is "boring, but It Works!"
21:10:52 <tomman> also helps that the kind of software I've worked on is not meant for Joe Bloggs and Jane Tiktoks, but for corporations
21:11:04 <tomman> AKA "you have to use this program or you don't get paid"
21:11:54 <CaptainTobin> I want to get my default/special template to be a windows window obviously.. BUT i also want it to have different apperances depending on what i want to set it to.. from 3.1 through Chicago, Watercolor, Luna, Aero and 8-10 favoring 10's re-adding of things like window borders
21:11:56 <tomman> fortunately I'm not an UX criminal either - if an user complains that some UI bit is hard and it is not a problem of the actual procedure itself (hard to deal when your workflow is regulated by law), then yeah, I can help~
21:13:10 <CaptainTobin> I should actually also configure the template to just get rid of the window frame and fill and use js to update the status text .. anything other than Borealis gets the window as-is cause screw them
21:13:35 <CaptainTobin> or just make it a thing the thing can do
21:13:42 <CaptainTobin> that always works
21:13:44 <CaptainTobin> eh?
21:15:30 <tomman> what we need is to implement all the ES2024++++ additions into our products, pronto :D
21:15:36 <tomman> "but ES2024 is not a thing yet!"
21:15:42 <tomman> just use the next week Chrome release
21:15:56 <tomman> otherwise you're a grandpa
21:16:11 <CaptainTobin> what we need is to collaboratively work together to uplift our respective JS engines as far as we can go reasonably
21:16:54 <CaptainTobin> build system wise the stuff would be nearly identical.. most of the adapation elsewhere would also also be applicable but not str8 apply
21:18:32 <CaptainTobin> frg_Away: of course there may be a more attainable and beneficial goal for both of us as a stepping stone..
21:19:46 <CaptainTobin> We can sync our js engines.. we add everything UXP/GRE/ARE added to yours THEN we backport yours to mine THEN we can take a gander at what should be done next
21:19:49 <CaptainTobin> IanN_Away:
21:21:14 <CaptainTobin> between fork/52 and sm/56 there is no reason on this earth we can't be running the same spidermonkey
21:21:38 <CaptainTobin> fuck i can even conditionalize any self-contained build logic differences
21:22:27 <CaptainTobin> but the thing IS that in order for this to happen for me.. i have to make sure your js engine is at minimum functionally eq to mine
21:22:34 <frg_Away> Currently I/we are still able to backport stuff halfway clean. I would like to keep it that way for some time still. Too much currently missing which would need extensive work if done standalone not using spidermonkey as the base. Not that I like it but I see it as the path of least resistance for now.
21:23:18 <CaptainTobin> frg_Away: So you'd reject patches that add newer es features?
21:23:45 <CaptainTobin> that can be adapted fairly easily
21:24:20 <frg_Away> Engine is at 57 and well into 58 with some later backports. Some parts are at 60 already and some well later. Not rejecting patches but I and ianN try to take the full "path" to them in so that they apply halfway clean.
21:24:51 <CaptainTobin> don't forget that if i identify the differences between UXP/ARE spidermonkey and YOURS and then refit it into my codebase any uxp patches THEY make become a fuck ton easier to port
21:27:14 <CaptainTobin> frg_Away: you also realize that if I accomplish THIS MUCH it is highly likely someone at mcp will take it and then you'd have THREE GROUPS ALL ON THE SAME ENGINE
21:28:07 <CaptainTobin> BUT
21:29:39 <CaptainTobin> let's say frg_Away that it only went as far as you guys either adapting UXP patches or doing it the mozilla way then those remaining features will only improve things for your users and nothing else would have changed but if it were to happen even remotely like I envision.. drama community bullshit etc is irrelevant everyone will benefit everyone even despite their abject hate
21:30:20 <CaptainTobin> and in this day and age it would be a hell of an accomplishment
21:33:36 <frg_Away> Overall the software is not there where I feel confident that we can deviate too much from the mozilla source. Also not enough contribution and that is where I see the most problems. If one of us all buys the field or wanders off  it is over.
21:34:07 <CaptainTobin> frg_Away: you're falling into a trap
21:34:58 <CaptainTobin> the stuff isn't good enough so we can't change it cause not enough people to do the work.. but there aren't enough people to do the work because you aren't changing enough of it SO it will be good enough
21:35:14 <CaptainTobin> never be*
21:35:39 <CaptainTobin> i dunno man.. it just seems like sometimes when it comes to the more pressing and serious decisions that the tone around here just kinda goes into this sort of "Well we are gonna just do what we have always done if for no other reason than I get bored occasionally.. I have tried really hard to shake that sense but it persists.. Is there a vision and end goal that drives this project and if so what exactly is it?
21:39:02 <CaptainTobin> i mean it just seems like that adding a handful of features which you already have some backported beyond your general feature level and getting one or potentally two additional groups all working on the same code and maybe as lost and defeated as most seem to be can get a sense that what they are doing actually does matter in a much larger context and there CAN be actual sharing of code even if projects are at best apathetic or at worst hostile ..
21:39:53 <CaptainTobin> you want the support.. so do a few bits that you're gonna do anyway evntually now and incrase that support potental by a good deal
21:40:24 <CaptainTobin> it is basically risk free for you
21:40:29 <CaptainTobin> at that juncture
21:40:39 <frg_Away> CaptainTobin. It is just that I take tha path of least reisitance. I don't have a vision and spending too much time on it already.  I try to enhance the product within the limits of the codebase and over time get some web compatibility in. I don't think there is enough outside support for doing it standalone or in collaboration with another project.  I think the suite codebase is in the best...
21:40:40 <frg_Away> ...shape since ever. It could always be better but the plan is to move forward one step at a time.
21:40:59 <CaptainTobin> There are no limits.
21:41:55 <CaptainTobin> You know this is exactly why I wasn't able to do much for this project 12 years ago
21:42:00 <CaptainTobin> this EXACT thing
21:42:21 <CaptainTobin> and this is why this project is so starved for contributors
21:43:13 <CaptainTobin> who wants to even bother commiting to something that can barely be bothered to exist unless it is handed to them on a silver platter.. FUCK even WHEN it is on a silver platter.
21:43:19 <CaptainTobin> the fuck man
21:43:48 <CaptainTobin> you HAVE to change this status quo dude
21:43:53 <CaptainTobin> even if you do nothing else
21:43:56 <CaptainTobin> THIS has to go
21:44:21 <frg_Away> The sad truth is that all our projects together don't make a dent and all are starved for contributors. It is work and no one wants to do this without being paid. Open source is in a coma. Just look at outside contributions to TB or Mozilla. More or less non existing now.
21:45:42 <CaptainTobin> Then why are you here at all?
21:45:51 <CaptainTobin> why should we do anything at all
21:46:03 <CaptainTobin> it means nothing and has no impact on anything or anyone
21:47:06 <CaptainTobin> There is a phrase I came across and used heavily in the past.. "We are the agents of our own salvation."
21:47:41 <frg_Away> CaptianTobin Because I am like you, SeaMonkey is my browser of choice and I am stubborn like a mule. And looking at latest 2.53.15 it works mostly great for me :)
21:48:16 <frg_Away> And in the long run nothing matters yes but at least I tried.
21:49:42 <CaptainTobin> I think even if the effect is marginal or even insignificant it is ALWAYS mesurable. So that means everything we do has meaning.
21:50:25 <frg_Away> And I am also waiting for mozilla to fold to see what comes next then. Would like us to be still standing then.
21:53:26 <CaptainTobin> frg_Away: let me lay this on you.. While it is true that SeaMonkey as an Internet Suite is extremely niche and mozilla tech is the same and open source globally is kinda fucked BUT if you will make it a priority just below "CRITICAL WEBCOMPAT" to match the UXP features so that I can attempt an engine refit it might allow me to gain some additional appeal and if that happens then I can start repairing the spotty evolution and eventually if we work
21:53:26 <CaptainTobin> really hard we could effectively end up VERY CLOSE in all the core bits and bobs of course i'd never go rust but u'd never not cause you can't
21:54:05 <CaptainTobin> you want to try and last out to see if mozilla collapses?
21:54:07 <CaptainTobin> ME TOO
21:54:26 <CaptainTobin> Let's do it as together as reasonably possible, k? Then we can hang out and watch it burn!
21:54:34 <CaptainTobin> Mozilla that is.
21:56:12 <CaptainTobin> frg_Away: final tl;dr speed up a couple of tidbits so I CAN catch up so we can help each other help our selves to survive to watch Mozilla burn in a glorious spectical!
21:56:23 <CaptainTobin> THAT is a CORE MISSION STATEMENT if I ever heard one
21:56:48 <CaptainTobin> with one addendum "Oh and make some neat software too."
21:58:35 <frg_Away> Well to backtrack a bit I am not sure I want to see them burn. Still lots of good people and we still use some services. I just think they will :) I would like to see what comes then and maybe salvage some pieces.
21:59:47 <CaptainTobin> Well i hope any remaining legit people survive. But I want that red dragon to burn.. I always prefered Green Mozilla anyway.. Green Mozilla is TRUE Mozilla!
22:00:35 <tomman> And if everything fails, we can just send boxes full of live cobras to each webdev in California :D
22:00:55 <CaptainTobin> fuck i am surprised with all the eco-dictatorship bullshit Mozilla hasn't brought back a bastardized version of the orginal Mozilla to shill for eco-masocysim
22:02:59 <frg_Away> Well currently he is digging a grave :) http://home.snafu.de/tilman/mozilla/Mozilla_Digging.gif
22:03:21 <CaptainTobin> Well Netscape was always ahead of the curve eh?
22:03:36 <tomman> until Microsoft joined the party
22:03:45 <tomman> I do not want to see Mozilla burn
22:03:53 <tomman> the one I want to see burning and rotting is GOOGLE
22:03:55 <CaptainTobin> IE would still be spyglass mosaic if not for Netscape
22:04:14 <tomman> Mozilla just need to sack the SJWs and her overpaid CEO
22:04:23 <tomman> oh, and the UXtarded art school dropouts
22:04:34 <frg_Away> tomman Lets just say the current mozilla management is not my cup of tea.
22:04:35 <CaptainTobin> tomman: put me in charge of UX design?
22:04:52 <CaptainTobin> come on tomman you like my UX style preferences don't you?
22:04:53 <tomman> CaptainTobin: depends: do you hate menubars, toolbars, and statusbars?
22:05:02 <CaptainTobin> do you?
22:05:34 <tomman> Let me be clear: the reason I'm using SeaMonkey (or in general, not-Firefox/not-Chrome) is because of the UI
22:05:47 <CaptainTobin> http://personal.mattatobin.com/image/capture/76c1c13f-9716-4b1c-831d-ea258e319610.jpg
22:05:53 <CaptainTobin> what do YOU think the answer is?
22:06:21 <CaptainTobin> tomman: I am gonna put statuspanels with icons for ALL the managers
22:06:29 <tomman> When FF4 came with that ridiculous redesign, we could just rearrange the pieces and have our FF3.6 back
22:06:32 <CaptainTobin> it will work like the menus in the tools menu
22:06:37 <tomman> then... they ruined that with Australis
22:06:47 <tomman> that day, I ran away, fast, fast as I could
22:07:06 <tomman> but didn't figured that Chrome was eating the world not only with its horrible minimalist UI
22:07:10 <CaptainTobin> tomman: at some point emulating fx2 or navigator with Phoenix be it Firefox or Pale Moon just wasn't good enough anymore
22:07:20 <tomman> but also by pretty much forcing webdevs to rely on shiny new APIs introduced every next week
22:07:21 <CaptainTobin> I wanted the real thing and more i wanted it to also have my mark on it
22:07:45 <tomman> cellphones and lazy webdevs using frameworks only made things worse
22:07:51 <CaptainTobin> i have been speaking out about it since 2011
22:08:10 <CaptainTobin> i told everyone i could everywhere i could i did so for years
22:08:12 <tomman> of course, if you tell webdevs that what they're doing is destroying the world, you get answers like the Discourse morons
22:08:21 <tomman> "progress is good for The Vision™"
22:08:23 <CaptainTobin> I am a web developer.
22:08:37 <CaptainTobin> But I am NOT an OpenWeb Developer.
22:08:48 <CaptainTobin> aka framework scriptkiddy
22:08:55 <CaptainTobin> aka communist
22:09:00 <tomman> I mean modern wedevs like your average SIlly Valley framework vomit, or those idiots that came up with the idea of using COMPILERS to build webapps
22:09:07 <tomman> not dinosaurs like us that like sane and sensible
22:09:30 <tomman> but hey, "sane and sensible" doesn't attract the megamillion$$$ of the VC lottery
22:09:51 <CaptainTobin> tomman: something like gogs is a good example of how to do something as a "compiled webapp"
22:10:14 <tomman> It's funny: MS tried with this crapola (webapps on the desktop) circa 1998, and failed miserably
22:10:15 <CaptainTobin> but i assume you mean bytecode and str8 up runtime binaries via js packaged in a format you can't inspect
22:10:20 <tomman> Mozilla tried too, and burned badly
22:10:32 <tomman> why Google had to be the one that actually had success with such a bad idea?!
22:10:52 <CaptainTobin> The issue with ActiveDesktop wasn't what it did.. it was that it wasn't a choice and can BARELY be disabled without more drastic shit
22:11:47 <CaptainTobin> if they had kept the window frame for 95 explorer and turned off webview and made THAT the option vs browser file manager people would have accepted it as the quite remarkable technology and impl it was for the time
22:11:51 <tomman> heh, ActiveDesktop was the thing us noobs used to have JPEGs as desktop wallpapers until we learned to find something else to convert them to BMP and not have our wallpapers dissapear with the ActiveDesktop safe mode white screen of death
22:12:53 <tomman> I spent way too much time looking at those "ActiveDesktop has failed, click this button to restore" fallback desktops
22:13:11 <CaptainTobin> Mozilla should have used their XPFE technology to extend the suite into a full shell on windows and DE (sans wm) on linux..
22:13:24 <CaptainTobin> THAT would have kept Netscape up vs Winders
22:14:01 <tomman> And people would have hated it too because web browser engines are overkill for driving a desktop, much more with the terrible machines of back then
22:14:04 <CaptainTobin> BUT xpfe was very componitized so you could just have the navigator or navigator and composer or just mailnews and the shell
22:14:10 <CaptainTobin> or just the file manager and not the shell
22:14:28 <tomman> IIRC early KDE1 actually used some HTML engine for rendering the file browser windows
22:14:44 <tomman> and it was kinda heavy, and crashed a lot (but I still miss KDE1 :D)
22:14:58 <CaptainTobin> IE's only real impact 95% of the time on the shell (assuming not a js script running a much) is that it used ram
22:16:00 <CaptainTobin> because aside from some js and html .. shell folders used an activex control which was basically the same folder control used before
22:16:38 <CaptainTobin> KDE3 still had konquorer as an IE-like web and file client
22:16:40 <CaptainTobin> and desktop
22:17:47 <CaptainTobin> I bet I could make an extremely simple PoC of a "desktop" xul window
22:17:59 <CaptainTobin> I just love the idea of a XUL-enabled shell
22:18:10 <CaptainTobin> I will build a file manager one day tho
22:19:41 <tomman> reminds me when I used StarOffice back in 2001 in Linux
22:19:58 <tomman> the thing was SO heavy that under Linux I would quickly run out of RAM on my Deceleron shoebox
22:20:15 <tomman> and magazines of the era tip for that would be "run StarOffice as your destko"
22:20:18 <tomman> --desktop
22:20:37 <tomman> surprisingly StarOffice had a desktop-esque mode, complete with file browser and Start menu!
22:20:45 <tomman> no WM, tho
22:22:24 <CaptainTobin> lol.. my shell would likely just end up being more Program Manager like than Chicago-like
22:23:51 <CaptainTobin> heh.. I could ADD an explorer widget then just control it with the UI but where is the fun in that
22:24:25 <CaptainTobin> i wanna see if i can abuse the directory index component to provide more
22:24:59 <CaptainTobin> in fact the suite-only xul version of the ui could be a good starting point
22:27:58 <CaptainTobin> tomman: use the sidebar for a directory tree
22:28:02 <CaptainTobin> or a places bar
22:28:28 <CaptainTobin> SPEAKING OF
22:31:08 <CaptainTobin> frg_Away: you do realize that navigator.xul's basic construction lends its self to becoming a suite.xul with the content area and tabstrip being able to be interchanged with something else
22:31:35 <CaptainTobin> well it would be a good structure to replicate in my example app
22:31:39 <CaptainTobin> when i revamp it
22:39:01 <CaptainTobin> anyway keep getting distracted
22:39:03 <CaptainTobin> sorry guys
22:39:22 <frg_Away> cleaning up the overlay hell without preprocessing would also be a good start for this. A bit more hierarchical.
22:40:16 <CaptainTobin> Well I believe preprocessing is superior to AppConstants
22:40:53 <CaptainTobin> WELL obviously the superior choice is code that doesn't NEED to be preprocessed but when it is needed it is better than runtime choices
22:41:06 <CaptainTobin> especially for an increasingly overburdoned js engine
22:41:24 <CaptainTobin> same with dynamic chrome registration overlays and subscript loaders
22:42:16 <CaptainTobin> and I know THAT is what Mozilla is doing as long as it still has any vague resemblance to what it was and if I were to do that and then throw a modern website at it .. the js engine would stall even worse than it normally does
22:42:40 <CaptainTobin> frg_Away: what exactly do you mean by overlay hell tho
22:44:01 <CaptainTobin> I plan in my platform code to create a new basic window overlay which will provde the named elements like menubar toolbox main-toolbar statusbar and some basic menuitems
22:44:19 <CaptainTobin> that will take over for what CommunicatorOverlay does in the suite
22:44:25 <CaptainTobin> but even more than that
22:44:38 <frg_Away> Lots of stuff in xul overlays and included a bit too randomly for my taste. overlay loads overlay loads overlay. I bet some of them could be deleted or reorganized.
22:44:41 <CaptainTobin> but yeah elements but not the structure so non-applicable bits don't apply
22:44:57 <CaptainTobin> that is true
22:45:37 <CaptainTobin> well maybe you will draw some inspiration from my reworked toolkit
22:46:12 <CaptainTobin> good thing is among my work is distributing locales and skin resources to their components so they are along side their content
22:46:45 <CaptainTobin> so if you ever DO wanna steal one of my revampped component UIs you can just take the whole component.. at least that is the end goal
22:47:20 <CaptainTobin> frg_Away: I question why there is a navigator.xul and a navigatorOverlay.xul
22:47:57 <CaptainTobin> http://xr.binaryoutcast.com/seamonkey-2.53/search?string=navigatorOverlay.xul&find=
22:48:36 <CaptainTobin> JUST the debug extension?
22:48:58 <CaptainTobin> well even then.. that doesn't need to be on that
22:53:24 <frg_Away> yes stuff like this.
22:54:59 <frg_Away> and now some sleep