Show Idle (>14 d.) Chans

← 2020-04-06 | 2020-04-08 →
ossabot: Logged on 2020-04-04 18:09:23 jfw: billymg: come to think of it I should just blog all my patches; though some are oudated or underinformed there's still some more good stuff. Will do by Monday night but likely sooner.
BingoBoingo can confirm flights are still moving cargo.
feedbot: << Young Hands Club -- RMD weeks 22 and 23 review and plan, Mar 28th-Apr 6th, 2020
billymg: jfw: comment in your mod queue
diana_coman: - billymg, the question is exactly what's the reason for having plugins as separate things to start with; (I get the original idea plug various things here and all that but meanwhile practice looks very different from that hallucination of a plan)
ossabot: Logged on 2020-04-06 17:54:56 billymg: diana_coman: the server side selection code works globally when added to the MP-WP-Content-Processing plugin
diana_coman: I am not necessarily (or not yet, lol) against wp-plugins altogether but I don't yet know exactly in what way is that different
diana_coman: jfw: did you find all those archives for gnat?
jfw: diana_coman: not quite; do you have gprbuild-gpl-2017-src.tar.gz and xmlada-gpl-2017-src.tar.gz available?
diana_coman: probably; I'll have a look.
diana_coman: jfw: yeah, it seems I have them
diana_coman: I had this summary and info quite clearly saying I even had them, lolz; not that anyone ever read it I suppose; will possibly add the whole set there at some point.
billymg: << i agree that "plugins" (as a framework for handling random drive-by additions from people outside of the wot) doesn't make sense in mp-wp, something i understood even more clearly after mp explained why the the code embed code should live inside the existing (footnotes) plugin rather than making a new one
ossabot: Logged on 2020-04-07 16:06:13 diana_coman: - billymg, the question is exactly what's the reason for having plugins as separate things to start with; (I get the original idea plug various things here and all that but meanwhile practice looks very different from that hallucination of a plan)
billymg: so currently i'm using "mp-wp-content-processing" plugin as a centralized place for content processing within the mp-wp codebase, not as a dumping ground for future "plugins
jfw: diana_coman: seems I wasn't explicit enough with my actual question which was, would you mind making the tarballs available to me? Though it's still useful to know that at least somebody has them, yes.
billymg: longer term this can also go away, and what is now in the "plugins
diana_coman: billymg: do you have any sort of rough map of the mp-wp codebase otherwise?
billymg: lifecylce can be moved into a more fixed(?) part of the code
diana_coman: billymg: aha, I rather suspect it will; but I admit that I'm only vaguely aware of the whole mpwp codebase, can't be of much help there
diana_coman: or at least not atm
billymg: i.e. put it in plugins now because that makes more sense than the individual theme level, but eventually that one plugin becomes woven into the rest of the codebase
diana_coman: billymg: since you are the one most familiar with the whole mp-wp codebase, my question is simply if you consider that the best place for it rather than simply a convenient place, that's pretty much it so far.
billymg: diana_coman: no, i do not currently have a design diagram / map of any kind, though this would be useful imo and i suspect i will get there eventually
diana_coman: aha, ok.
diana_coman: jfw: do you have a full list of all archives ? because if I spend the time to add them there, it makes exactly 0 sense to put only those 2 that happened to be difficult to find atm.
billymg: diana_coman: ah, gotcha. i can't say for sure if i'm most familiar with the codebase, my changes/contributions so far have been targeted and the codebase is rather large, however...
ossabot: (trilema) 2020-03-01 billymg: << i have a strong feeling the reason it's *not* this, and the reason the mp-wp genesis is 7x the size of trb genesis by LOC, is because it was designed by the "no one user matters more than another" crowd
jfw: diana_coman: I can readily make such a list, with caveat that I haven't yet tested the recipe (perhaps this idea that I could get the deps assembled while the getting was good then schedule the build experimenting for later doesn't actually work)
billymg: i do think that in the current state, where content is processed to extract and markup footnotes and code embeds, that file makes the most sense for adding code to process content to add markup for selections
billymg: and the benefit of keeping this content processing/markup code in one place will make it easier later when we rip out the plugins framework in favor of adding these features in a more fixed way
diana_coman: jfw: well, shitgnomes since March last year in there at least so dunno about the getting was good but whatevers; I guess I'll just upload then whatever I conveniently find and that will be that.
billymg: s/place will/place is that it will/
diana_coman: billymg: makes sense; perhaps trinque might want to weigh in on this too; from my point of view atm I don't have anything specifically against it.
billymg: diana_coman: ok, sounds good
jfw: diana_coman: is what I assembled so far with keccak sums which should be everything but the mentioned gprbuild and xmlada. And yeah, should have done this in 2018.
whaack: I didn't renew my domain name and so got routed to a placeholder page; the issue is now addressed.`` can be added to the hosts file for while the DNS update propagates.
jfw: diana_coman: I got the missing tarballs from asciilifeform btw. (thread)
ossabot: (trinque) 2020-04-06 asciilifeform: jfw: i posted my copy of his dep tarballs
← 2020-04-06 | 2020-04-08 →