RW Foundations Caturday Drop : v211204 edition
It's Caturday again Anons. Woot!
Well we've kind of shifted gears for this go-round, Sumomo
's on hold for now, and we are focusing on getting the new Bumpmaster
project up and running successfully within the overarching library framework. As mentioned elsewhere;
>"So, when we reach a level where a functioning robowaifu needs to use Bumpmaster or Waifusearch, she'll be able to do so with very little extra effort on the part of the men developing her." (>>14353)
We believe this style of software adoption is a good general approach for us, for a number of reasons:
- Ensures the libraries all each work together successfully
- Enables our robowaifus to have additional programs to safely use as well
- Better proves-out our general stability, safety, security, & control concepts
Hopefully, we can help move towards achieving all of these goals by prototyping, then fully integrating both Bumpmaster
into our Foundations library. Not only will it be a nice thing to have these new (somewhat more capable) programs ourselves
, but eventually giving our robowaifus the facility to directly run them will also be helpful too.
Even if it turns out we need to remove them both in the end, this effort will certainly be a good learning experience for everyone involved. And since we are writing the (vastly more simple) software ourselves
--with full access & visibility for every line of code--it's very likely to be much safer than just giving a robowaifu unrestricted access to the data outputs from some potentially malware-infested pages through a web browser's file-save facility, etc.
Read-only access (as in: literally
reading directly from an external computer's monitor) using either approach is probably OK for her in most contexts, roughly-speaking. About the same as it might be for a human child for instance. But, when it comes to any more-direct
data accesses (involving storing either files, data or information locally for offline-retrieval, for example) then we consider our approach to be a much safer one for our robowaifus.
On that note; we've removed the main library RW Wired
from the Foundations library itself, and begun moving to implementing that functionality within the RW Dollhouse
library. Dollhouse was always meant to be a 'General Outboard Systems' (that is, outboard of the robowaifu herself) library, in addition to it's other features. Therefore, it seems the most appropriate place to consolidate all external network accesses through it's interfaces.
It's both easier to control, and to account for any external networking usage through this approach. It's also far easier for a regular robowaifu owner to control things using the dollhouse hardware itself. He can flip the networking hardware switch itself off, or even just literally 'pull the plug'. BTW, we're adopting an "only-briefly-connected, 'Dolldrop'
" approach & philosophy for all our external networking code within the Foundations (which has proven to be a pretty fun thing to begin thinking through, actually).
In other news;
we've begun some initial basic efforts to provide both callgraph-recording/tracing & function-level access-control within RW Foundations. Both of these facilities should be particularly helpful once the code grows larger. Actually understanding
what's going on within a highly-complex systems is the first
order of business for software architects and engineers building
those systems. We hope our approaches will greatly enhance that ability for every Anon involved. Indeed for anyone.
So, the plan is probably to just continue using this same thread for any new "RW Foundations" drops (even if they seem at first glance to be off-topic ITT). Over time all of these interrelated software & hardware technologies and concerns will blend together into a single, large
, system in the end. We'll try to keep it all sorted out properly along the way.
Be patient Anon, Good Lord is willing we'll all eventually get there! :^)
-add global and local 'do_stamps' flags to control callstamping
-begin 'stamps_.emplace()' calls into class' func defs
-begin 'Stampstack stamps_' private member fields (callgraph analysis)
-bumpmaster gets member; board
-begin Board in rw::curator::bumpmaster
-bumpmaster gets member; site
-begin Site in rw::curator::bumpmaster
-begin class' Master-only func protos; catalog, thread
-begin enum class rw::Type + integrate across system
-begin bind_master(), slave objects intended for a Bumpmaster 's use only;
catalog, page, post, thread
-in rw::curator::bumpmaster; rm aliasing of catalog, page, post, thread
-begin prototyping the binding of all member slave objs to their master class
-dollhouse gets member; shell (shell & power care)
-shell gets member; dollhouse (shell & power care)
-shell gets member; gears
-rw::wired main library removed from RW Foundations
-arigato, bumpmaster, curator gets member; dollhouse (dolldrop comms)
-arigato, bumpmaster removes member; wired
-begin protected/private classes Dolldrop, Wired within rw::dollhouse::Dollhouse_b
-begin architectural rework; mv all RW Foundations network comms through dollhouse
-ren Tip>Hip, consolidate RW field' accessor as 't()'; integrate everywhere
-begin bumpmaster demo project; shifting dev focus over to bumpmaster for now
-ren 'Sumomo' project to 'Sumomo's World!' project
-ren sumomo_version.log>version.log; mv to RW Foundations lib's domain;
-sumomo gets members; confetti, dustpan, whisk
-begin Confetti, Dustpan, Whisk in rw::chibitsu::props
-moveit gets member; bones