>>16370
>I look forward to what you have in mind for Pandora.
You're the team leader for the project AllieDev. I'll try to help out as I may. So, if you're asking for my advice then I would say basically that:
A) We need to stay as nearly compatible with the
MaidCom project as is feasible with
Pandora's design allows.
B) We need to keep
everything (designs, mechanical engineering, electrical engineering, sensors & computer hardware, software goals, etc., etc.) as
small & simple & cheap as possible during this first prototyping attempt. After all, it's important to make something that
just werks first, then we can blue-sky later as we go along, right Anon?
That's pretty much it from my current perspective. If we can just follow these two basic goals, then we are very likely to succeed with Pandora right out of the gate. I pray we do so! :^)
===
As far as specifics relating to our software goals go, we're already working towards general-purpose solutions under the umbrella of the
RW Foundations framework, as you're aware. Now the
RW Pandora sub-project 'inherits' the vast bulk of her abilities from the
RW Arigato's main project. This is the same for
all robowaifus that choose to adopt the Foundations in their system's designs.
Sumomo &
Kotoko for example, also indirectly inherit all their abilities from RW Arigato.
Longer term, Arigato has many different capability goals on tap. Here's the current listing of member classes:
>arigato.hpp snippet
inline auto animeyes() const -> Animeyes& { return animeyes_; }
inline auto atashi() const -> Atashi& { return atashi_; }
inline auto bones() const -> Bones& { return bones_; }
Message too long. Click
here
to view full text.