00:00:03 I dunno what I like better.. babbling all day or just popping in and out.. 00:01:11 may try popping in and out more.. 00:01:46 lazyload nsITobin?! 00:01:49 i dunno 00:02:45 it's up to njsg 00:06:07 awe we need more tonymec 00:07:37 I'll hold out for Ximo++ 00:12:13 :P 01:33:23 https://cci-dev.thereisonlyxul.org/special/test/?case=markdown 01:34:19 standard html formatting IS slightly fighting my special component formatting 01:34:39 but again.. good.. enough 01:34:44 and I am done for the day 01:35:49 the ironic thing is I could likely translate phoebusCode to either wikitext or markdown now and it would actually work properly 09:46:20 https://www.vintagecomputing.com/index.php/archives/3292/the-pc-is-dead-its-time-to-make-computing-personal-again 13:16:31 case 'markdown': 13:16:31 $this->helper = $this->LoadHelper('markdown'); 13:16:31 if (!$this->helper) { return $aContent; } 13:16:31 $this->helper = new Parsedown(); 13:16:31 $this->helper->setSafeMode(true); 13:16:32 $aContent = $this->helper->text($aContent); 13:16:34 break; 13:16:36 simplest yet 13:38:26 html entities are more fun than unicode emoticons 13:38:43 xml entities too 13:42:01 frg_Away: it may be a good idea to reiterate the vauge lifecycle of SeaMonkey on NT 6.1 for users somewhere cause that guy last night isn't the only windows 7 user getting twitchy about future support.. The question has sprung up recently in lunar orbit as well. 13:44:38 my feeling is there is gonna be another rash of depercations for older windows because now no one unless specifically targeting LTSC has no reason to target older than windows 11 let alone a host of legacy code paths.. Not to mention when Mozilla doesn't instantly kill windows support it echos through all the mozilla-based projects. 13:44:52 (or server) 14:09:09 Why can't the program just use the APIs and syscalls from an older version of Windows kernel? 14:09:35 Not like I support using Windows anyway, just asking 14:11:30 Sompi: these day OS version support is generally enforced by the compilers, and if you're under Windows this means you're most likely using Visual C++ 14:11:50 and every newer VC++ release enforces whatever Windows OS baseline that Microsoft wants 14:12:22 now, that won't stop developers than just using "Windows 10+" APIs for whatever reason they see fit 14:12:37 but many times it's just the compiler saying "Windows 10+, sorry" 14:13:03 https://repo.palemoon.org/MoonchildProductions/UXP/issues/2505 14:13:41 Sometimes new APIs actually are nice to have, or solve an actual problem... but then that means either you get to maintain two codepaths (icky!), or do an Executive Order saying "sorry but this is too good to let it pass" 14:14:08 But these days newer APIs are used because "oooh, shiny" instead of "oh, this is actually good" 14:14:54 nsITobin: oh, that means UXP won't be fit for Government Use™! 14:14:59 MUH FIPS CERTIFICATIONS! 14:16:20 is firefox fips certified 14:16:46 they don't even use an nss that builds or has? i haven't checked.. shlibsign 15:16:39 anyway m-c has no signing either 15:16:45 mozilla-central 15:34:26 nsITobin unlike xp I intend to support it as long as possible. Same for 8.1. With the hacky updates good till 2026 at least. There is not much/anything in 10 land which is needed for SeaMonkey right now. I am still running it for tests and my mail in a vm. 15:35:25 f*cking rust is already a problem so we will see how this goes. 15:36:07 frg_Away: well i am gonna have to learn to compile rust deps at some point how else can I attempt to enter nomans land to explore the xbl divide and conquor it? 15:37:15 it is frankly ridiuclous I can compile xpfe seamonkey, uxp, seamonkey 253, some shadow of seamonkey on 102-cental but can't do spit on 60ish through 91ish 15:37:58 also for sure 24-52 as well 15:38:49 xp was seriously lacking support for later apis but 7 only a few like better dpi support. The store stuff can go to the way to the dodo right now if you ask me. Same for later .net all all the stupi stuff ms introduced to make it look more modern aka bad. 15:40:45 fedor knows the secret to compiling rust for xp and esr68 15:40:55 but .. 15:41:07 i was all Tobin at him.. so not gonna get that .. 15:43:01 I use xp for some very special chip burner hardware but if you don't have these needs it is braindead to run it. Only use it on 2 dedicated laptops too. One with 98se too for some other program. 15:43:22 rust is still a hard thing for me to accept.. on one hand i hate it with every fiber of my being.. on the other hand its already here and not being as useful as it could be and removing it and doing without just isn't feasable at this stage .. maybe 2019 but not today.. I say use it but no one has to like it. 15:43:50 best i can do for now on acceptance 15:44:07 same here. Would love to kick it out in a minute but a one man army is defeated fast. 15:45:09 frg_Away: like with actual iron rust.. sometimes its a fact and just needs to be managed and kept under supervision ;) 15:47:07 lets just say anyone wanted to put a rust component in suite and not needed as a critical backport from TB or Fx will get r- from me in 10 seconds. Not sure how IanN would do it but I am not :) 15:47:13 * frg_Away start to rant 15:51:48 well I am guessing stylo related rusticals aren't gonna dramatically bust xul functions.. other rust stuff certainly would.. issue is the dep hell 15:52:38 but i get your point frg_Away don't want someone rewriting the sidebar as a rust component 15:53:18 stylo s*cks but this is onevthing still needed. 16:15:40 sure seems to be the case 16:15:50 unless an nsLayout style expert shows up 16:52:33 gone for the evening. Have fun 16:57:22 Hope frg has a good evening.. relaxing.. going out.. somethin fun. 16:58:16 for me it's not even noon yet but I am gonna try to reduce the idle babbling as an active task. 16:59:23 If I am babbling.. I ain't codin. 16:59:27 ;) 18:41:39 github Assets works with the latest palefill, https://github.com/martok/palefill/releases 18:43:24 or maybe not? 18:45:25 I need to speak to martok at some point or at least identify him as not JustOff .. the only thing that makes me think it isn't JustOff is all the cpp work.. Good c++ work.. JustOff mainly botched javascript and glorywhored other people's extensions. 18:48:01 ok, i'm now confused. 18:48:05 ti is also strange his github history save the odd pull request or ownrepo activity drops off around the same time JustOff became a thing and suddenly picks up when JustOff vanished after russia invaded 18:48:23 no, it is actually Greasemonkey that gets it working 18:48:40 someone needs to fork greasemonkey 18:49:02 therube: how do you have a FUNCTIONAL greasemonkey for seamonkey .. mine was only PARTLY functional on 2.49 18:49:07 https://www.greasespot.net/ 18:49:44 actually what we need is first-party userscript support in seamonkey 18:49:54 i don't know if it is functional. not really familiar with it. but with it github Assets works. 18:50:00 and not need greasemonkey cause gpl 18:50:35 but as far as new UI features for seamonkey goes.. site specific UAO manager ui is needed more 18:50:52 it is on mah list 18:51:55 i've got a script in there (& i'm not at all familiar with this stuff), github.com_include_fragments@void::gmscripts 18:52:06 not sure where i came across it or why 18:52:30 after I get this ftp panel done I will start my general porpoise CMS with non-public wiki features 18:53:06 I had a script on greasyfork to disable github ajax 18:53:15 no idea how that works now with customelemenets gitshrub 18:53:16 therube: 18:53:37 https://greasyfork.org/eo/users/6698-matt-a-tobin 18:54:22 https://greasyfork.org/en/scripts/407745-bypass-github-ajax 19:14:24 looks like the greasemonkey actually came from here, https://sourceforge.net/projects/gmport/files/ 19:14:54 & then i did something to it to get it to work in SeaMonkey 19:16:18 or no that was an older version where i had to mod it. 3.10.0.1rc5 i'm thinking should be good as is 19:26:09 hi IanN