Video dan Biodata Vici Dior Artis TikTok dan Instagram

#Terviral - Salah satu nama yang belakangan ini sering muncul di berbagai #platform adalah #Vici #Dior atau dikenal juga dengan nama #Vicidior. #Konten-konten yang ia bagikan di #Instagram maupun #TikTok sering kali #viral dan mendapatkan #sorotan #publik. Tidak heran jika banyak orang penasaran dengan siapa sebenarnya sosok di balik akun tersebut. Baca: Video dan Biodata Kienzy Mylien Seleb DJ TikTok Terviral…

https://terviral.id/video-dan-biodata-vici-dior-artis-tiktok-dan-instagram/

VICI - Building a Multiproject System

VICI is a C++ project built with Autotools.

Autotools has support for building systems from multiple subprojects. However there is one glaring issue: If one project depends on a different one the first one cannot be built until the second is installed.

The work-around for this is to do an install for each project into a staging area when its being built. The alternative would require the build step to be done as an admin (root) user which is generally considered a bad idea.

With VICI I ended up with 12 (!) modules. That is probably too many for a project of that size, but it did demonstrate that a full build of the system is possible.

VICI has thus demonstrated that it is practical to build and test subprojects in isolation, and then be able to build (and test) the entire suite when its ready to distribute.

3/3

#VICI #programming

VICI - Interfaces

The important thing that is necessary to have well separated subprojects is that their interfaces have to be very well defined. Actual working code is the best option.

While VICI only required function calls and shared data files, other projects could use interprocess connections ranging from shared memory to web based calls over HTTP.

When the architect subdivides the project into modules she will need to provide very detailed specifications for the interfaces between the modules.

These interface specs should then be handed to a development team to create an implementation. This will consist of a test harness that simulates each end of the interface, plus any code for the interface itself. The simulation will typically have two parts, one that receives calls and one that makes them, the latter driven by a test system.

Each project can then be worked on without reference to the others and be confident that if they meet the interface test harnesses there won't be too many issues when they come to work together.

For VICI this worked quite well.

2/n

#VICI #programming

VICI - An Experiment with Subprojects

My #softwarearchitecture hypothesis is that for large projects it is better to subdivide them into a collection of small projects, each of which can be developed without reference to the others.

A caveat is that this really only applies for each level of the software. The low level infrastructure does need to exist prior to the levels that use it. I am not going to build a GUI program without an existing GUI library!

I discovered that there are two areas that need to be addressed for this to work: How to simulate the interfaces between sibling projects, when some of them don't even exist yet; and how to build the entire system when it comes time to deliver it.

1/n

#VICI #programming

VICI - An Introduction

VICI is intended for users of Linux that primarily use the GUI desktop and are a bit shy of the terminal and command lines.

The intention is to enable such users to create simple scripts which they can then execute via their usual system menus.

Rather than a text editor to create the scripts a graphical interface is used to compose the script in the form of a flow chart. Each node is a command. The edges are either control flow or data flow (pipelines). For the advanced user it also supports simultaneous threads and parallel processing of data streams.

On the assumption that the user is not very familiar with command line programs the editor has a tab for searching for commands and for classifying them with tags for future reference.

Another tab assists with setting the options for commands. It provides a man page reference and a syntax diagram.

There are tabs that allow a script to be run from within the editor, for progress and values to be monitored. The script can be run slowly or stepped.

Another tab allows the script to be installed into the user's menus or scheduled for automatic running. It is business oriented scheduling with things like "the second last work-day of the month".

The VICI system comes with some support programs in addition to the editor and the run-time program. There is an admin program for preparing commands for use in VICI, a stand-alone version of the search tab, a command line interface version so VICI scripts can be run from bash, and a cron like program for running scheduled scripts.

It also comes with a user guide.

#VICI #programming

VICI has now been updated and uploaded to SourceForge. You can get a copy to build from https://sourceforge.net/projects/ocratato-vici/files/

Background
VICI was built for two reasons. First it seemed odd that Linux has a large collection of quite useful command line programs that are almost invisible for a user that uses the GUI desktop. VICI provides a means to access these programs using GUI interfaces.

The second reason was to investigate an idea for building systems using independently developed modules. The premise being that large systems should be developed from separate small components, thus replacing one large project with several small ones.

#VICI #programming #softwarearchitecture