End of September 2017 Update
👉It has been a while since we wrote something about the process we are going through in the development of this web site. No excuse. I guess it is just more fun to actually spend time developing for Civilcp than it is writing about the code work and such. In any event, I will try to give a bit of insight into what we have been doing as of late.
👉Basically, we have been working on Conversations stuff (conversations that follow the originating topic). This is much more complicated than working with the topic stuff. Topic stuff is the basis for all that follows and is handled pretty routinely with normal processes. Replies, on the other hand, are much more complicated.
👉Anything written as follow-up to a topics within Civilcp is all being housed in a single database table. There is no obvious way to understand how the code written within Civilcp handles gathering the conversations to be listed below the topics, and conversations that follow other conversations. So, there is some very complicated code that lines things up appropriately. Let's say we hypothetically have a conversation that is twenty-levels deep underneath a topic. In other words, we have nineteen conversations written between the one we are looking at and the originating topic. In order to know which conversation belong in this chain of conversations back to the topic requires a bit of code work. This code, thankfully, has been developed but seems to need a little twitting.
👉We have written a routine to do this and this allows us to list only the videos, links germane to where the reader might be within the conversation. Remember, if a reader were to go sideways and up another conversation thread, the videos & links and their status could be different. All of this is probably why no one else seems to allow this kind of flexibility in their collaborative social media pages. It is highly complex.
👉The first is to make sure that the necessary security is on each membership page and that there are no avenues for non-members to reach these pages. This process will take a few weeks. Not too bad as all of the security code has been written, and implemented sporadically. Just need to finish this up.
👉The second is a renaming and refoldering all of the content. Why would we do such a thing? Well, simply because the development process is rather messy and a lot of junk is laying around no longer in use. The best way to find out what is no longer necessary is to rebuild everything from scratch using that we have created, changing names when appropriate. This process will probably take a few weeks.So, let's just say that if we do get Civilcp finished during the winter months, it won't be early.