This is a Q&A regarding Kirikiri Z.
Click here for Q&A regarding development.
Click here for Q&A that users might find confusing.
- Q. Why is the name "Kirikiri Z" so confusing?
- A. Since it is no longer fully compatible with Kirikiri 2 and changes were made to the core components, the name was changed.
It was named by Mr. W.Dee.
【Tentative Call】 Name for the Kirikiri 2 VC fork version
— jin (@jin1016) April 9, 2013
No, shouldn't that be the trunk? Rather. RT @jin1016: 【Tentative Call】 Name for the Kirikiri 2 VC fork version
— wdko (@wdko) April 9, 2013
So, it feels like it will change significantly around Kirikiri 2 2.33, right? lol RT @wdko: No, shouldn't that be the trunk? Rather. RT @jin1016: 【Tentative Call】 Name for the Kirikiri 2 VC fork version
— jin (@jin1016) April 9, 2013
I thought a stable version of Kirikiri 2 finally came out, only to find it's become a VC build and changed drastically.
— jin (@jin1016) April 9, 2013
@jin1016 Kirikiri Z
— wdko (@wdko) April 9, 2013
"Kirikiri Z" is a confusing name, but I think it's a good name with a sense of playfulness.
- Q. Why did it change to the "Modified BSD License"?
- A. This is because the "Modified BSD License" is a license that makes it easier to make changes.
Kirikiri Z constitutes a modification under the Kirikiri 2 license, and the Kirikiri 2 license states the following:
"You may modify and distribute this software, but in this case, it must be distributed only under the same license as this software's license, or a license specifically approved by the author of this software."
In other words, it is possible to change to a license for which Mr. W.Dee's permission has been obtained. At Mr. W.Dee's request, Kirikiri Z became licensed under the "Modified BSD License".
While we're making it Kirikiri Z, why don't we change the license to Modified BSD?
— wdko (@wdko) April 10, 2013
- Q. Why did it move to GitHub?
- A. Mr. W.Dee requested that the current repository be kept only for Kirikiri 2 maintenance, as he wants to work on Kirikiri 3 on GitHub. He asked me to start Kirikiri Z by moving the Kirikiri 2 repository, so it was moved to GitHub.
@jin1016 jin-san, sorry, but could you start Kirikiri Z by moving the current repository to GitHub or somewhere? I'll keep the current repository for Kirikiri 2 maintenance only. I want to do Kirikiri 3 on GitHub.
— wdko (@wdko) April 9, 2013
We planned to migrate to GitHub using the logs from the Kirikiri 2 repository, but during the conversion from SVN to Git, it proved difficult to properly migrate only Kirikiri 2 due to the influence of past folder moves and other factors. Since it became clear that this task would require a significant amount of labor, we abandoned moving all the logs.
- Q. Why did you create Kirikiri Z? It feels like things just got more confusing.
- A. If you are a programmer, I think you would agree with the goal of being able to build with VC instead of C++Builder 5, but it is difficult to explain the benefits to others.
In short, it's because VC is easier to develop with in the case of Kirikiri.
However, it might not be the case that end-users will immediately feel the benefits of Kirikiri Z.
Kirikiri Z is something where the effects will be felt gradually over one or two years.
Currently, only the programmers developing it feel that it has become much more convenient with Kirikiri Z.
It all started when I made it possible to build only TJS2 with VC while adding bytecode support to Kirikiri 2.
After that, the background is easier to understand if you read this summary: Kirikiri 2 VC Build Support.