19:14:37 hiya nsITobin 19:22:22 IanN_Away: Hi 19:22:26 what can I do for you? 19:24:10 nsITobin: any idea where Nvu repo is? 19:24:53 GUID {136c295a-4a5a-41cf-bf24-5cee526720d5} 19:25:54 how does it have a guid.. it was xpfe 19:29:10 not entirely sure 19:29:16 i am searching 19:29:31 mandrake did serve it but i'd need to find old mandrake rpms 19:29:39 checking vcs 19:31:01 just looking to see what fixes were added to it 19:32:24 compared to SM composer 19:33:44 best i can find ftp://ftp.icm.edu.pl/vol/rzm1/linux-mandriva/official/2007.1/SRPMS/main/release/nvu-1.0-7mdv2007.1.src.rpm 19:33:56 tarball inside the src rpm 19:34:08 yeah it is xpfe 19:34:13 gcc 4.1 19:34:34 however if it is following xpfe codepaths it should be buildable by modern gcc 19:34:49 i built seamonkey 1.1 on modern gcc with a few edits 19:35:01 the firefox toolkit codepath ttho was constant error spew 19:35:11 IanN_Away: it might be possible to build this 19:35:16 not the rpm 19:35:19 but the source 19:38:17 1.7.5 19:38:21 ok maybe not.. 19:38:48 IanN_Away: i dunno unless you can USE nvu how useful the xpfe versions of the files will be 19:39:07 cause you won't be able to just reuse code 19:42:27 didn't NVU evolve into one of the other two standalone editor projects? 19:44:10 i am pretty sure kompozer was the continuation or fork for nvu 19:44:35 yeah, just reading that on wikipedia. And BlueGriffon was at least meant to be a new editor from scratch 19:45:09 bluegriffon is still just composer ui 19:45:17 just been heavily skinned 19:46:54 I apparently don't have that well organized in my notes, bah. Need to check that out, because that's probably a good place to at least look and compare what's done 19:47:34 gluegriffin aside from a more modern looking interface isn't much more featureful vs kompozer or seamonkey composer 19:48:01 so that'd be https://sourceforge.net/p/kompozer/code/ci/default/tree/, now does that include Nvu history? 19:48:09 kompozer was an issue because much of its added benefit thanks to nvu was xpfe style code extensions 19:48:25 checking 19:48:55 no i dunno how they are doing this 19:49:19 the hell.. last composer tree i saw was an xpfe 1.8 tree and it was complete 19:51:10 njsg: this is release engineering code for their setup routine 19:51:12 yeah, when I looked at Kompozer, it just seemed to import the source at a certain point from Nvu 19:51:16 has zero mozilla code in it njsg 19:52:16 njsg: https://sourceforge.net/p/kompozer/svn/HEAD/tree/ is probably what you are looking for 19:52:48 and https://sourceforge.net/p/kompozer/svn/commit_browser 19:53:45 yjere we hp 19:56:27 attempting conversion 19:56:33 to something useble 20:11:23 i'm sure svn is one of the worst vcs 20:18:07 IanN_Away: does hg have a good way to import svn directly? 20:22:32 nsITobin: there's hg convert but might be easier using TortoiseHG 20:23:45 i can turn a git into hg 20:24:07 but IanN_Away i will upload the git version to gitlab for you of kompozer 20:24:22 when git-svn gets done 20:33:49 thanks 21:38:33 nsITobin: ... that's on sourceforge, I clicked the "code" tab 21:38:58 I mean that's sourceforge's doing, dunno why that was the default repo shown 21:39:21 I guess I should have gone with the svn tab :-D 21:44:45 IanN_Away: no it doesn't have the nvu source 21:45:16 i don't even think this has kompozer's history either 21:45:20 before 2007 21:45:36 Author: paul-h 21:45:37 Date: Mon Jul 30 04:47:27 2007 +0000 21:45:37 from 0.7.9.20070726 src upload 21:45:37 21:45:37 git-svn-id: https://svn.code.sf.net/p/kompozer/svn/trunk@2 55ead531-2e2b-0410-b405-93e52e755431 21:46:08 IanN_Away: do you still want the repo? 22:44:58 IanN_Away: https://gitlab.com/thereisonlyxul/kompozer# 22:45:03 for whatever use it is 22:46:14 https://gitlab.com/thereisonlyxul/kompozer/-/tree/trunk-svn/mozilla/extensions/editor/cascades?ref_type=heads 22:48:58 i do have a very important question 22:49:13 WHY THE HELL WASN'T THIS DONE BACK THEN?! 22:49:22 .. aside from that.. lol 22:49:48 i mean really .. sourcing then-contemporaries 15-20 years later.. 22:50:28 kompozer really is a seamonkey failure