Is ots necessary?
It might be unnecessary.

I think so.
The specification only for the theme installer is . ..meaningless...
It is necessary to standardize it from it previously.

So why is OTS a bad idea?

It makes installing themes easier, with no side effects (other than having to conform a little)

Tell me why you think its so bad?

以下の文面は私に強制的にOTS対応のテーマを造れと執拗に言ってくるxcalに
対して述べているものです。
まあ、参考程度にしてください、思いは通じると思います。

OTSってテーマインストーラ造った連中が推進してるものなんだろ。
利点というかメリットというか今一良いところが理解できないんだよね。

太古の昔から構造かなるものはプログラミングの世界にあったのは確かだけど。
その部類ともかけ離れているように思える。
第一、メンテナンスしにくいし、OTS準拠を謳ってTheme.rcを記述してるつもりでも
最初の謳い文句以外はダラダラとコア以外の定義とかも記述されていたりする。

要するに理解できてるつもりでも、実際はできていないと言うことだ。
ディレクトリ構成を統一して、余計なフォルダを排除して手軽にメンテしやすくするのが
本来の目的なのではないだろうか、現状ではインストーラに合わせる為だけのモノとしか思えない。

実に下らんものだ。

これに固執する奴がいるとは(w

酷い連中なると、最初の謳い文句とNLMの記述だけで、コアrcもConfigに入れている(w
NLM対応にしておけばOTSだと思ってる(w
一番酷いのがpopupの定義なんだが、theme.rcにもconfigにも定義が入ってる奴(w
変数も専用のrcがあるにも関わらずに、scriptの中で沢山定義してる(w

ああ、それとIncludeすりゃOTSなんだよみたいな奴もいるな、
まあ、includeは構造化する上では欠かせない部分ではあるがOTSとは関係ないよな(w

もっと言うと、includeを上手に使って、ディレクトリ構成を十分吟味してキチンと分類してやれば
メンテのしやすいテーマが造れるはずである。
rcを全て把握しなくても肝となるrcを修正すれば済むというようなね。
それが構造化なんだろう？

なんかインストーラの為だけにOTSを普及させようとしても無理があるんだよな。

全く、システムとしてのLitestepを考えた場合は、構造化して弄りやすい造りやすいモノとして
rcの細分化、役割、ディレクトリ編成、それを統一させるためのルールを確立してから、
それに準じて初心者にも導入できるようにとインストーラを造るのが基本的な流れなんだろうけどな。

インストーラありきで話ができてるからな(w

キチンとした開発支援とか仕様とかができてるならOTSのような記述を勧められても
納得できるけど、それができていない以上はOTSのような無意味なインストーラの為だけの
記述を無理やり勧められる必要は無い。

OTSを推進する前に、標準化について今一度考えればいいのではないだろうか。

話はそれからだ。

OTS、OTSって馬鹿の一つ覚えみたいに人に押し付けるんじゃないよ(w

Hahaha... no idea what all that was, but I did see my name in there.

I think we're a few charset's short of a language.

for the mono-linguists among us, here's what babel fish came up with:

Contents below that make the theme of OTS correspondence mandatorily in me, are something which has been expressed vis-a-vis xcal which is said obstinately. Well, please do, as for thinking you think in reference that it leads. The OTS っ て theme installer the ろ which is thing what which the party who was made has propelled. You call advantage, or call the merit, or now one cannot understand the good place, it is, don't you think?. But as for those which structure become from ancient former times as for being in the world of programming certain In order to be widely different also the category, you can think. First, maintenance it is difficult to do and, praising OTS conformity, other than of first praise complaint lazily definition other than the core being described, reaches even with the intention of describing Theme.rc. In a word being able to understand, really it is even with る intention not to do. Standardizing directory constitution, removing the excessive folder, easily メンテ to do it probably means that what it makes easy is original purpose, just in order to adjust to the installer mono with only you cannot think with present condition. They are lower viewing ones truly. The person who is persisted in this is with (w When it becomes the terrible party, with just first praise complaint and the description of NLM, are inserting also core rc in Config, if (it makes wNLM correspondence, thinking, that it is OTS, the る (w the fact that it is most terrible is defined what of popup, but definition entering into theme.rc and into config, the る person (w variable there is private rc without relating, Sawayama it is defined in script, (w Well, that and it is り ゃ OTS what which Include is done, we would like to read the person it is, when well, include structures, is the part which cannot be missed, but OTS there is no relationship, (w Speaking more, using include skillfully, closely examining directory constitution sufficiently, if the chitin classifying, it is the expectation where it can make the メンテ present easy theme. Rc everything is not grasped and don't you think? it seems that rc where if also the て becomes the liver may be corrected. That probably is structuring what? Something it tries to spread OTS just because of the installer the excessiveness it is. Completely, case of Litestep as the system was thought, structuring, it is easy to fumble, it is easy to make, after the subdivision, role and directory formation of rc, establishing the rule in order to make that standardize mono as, in order to be able to introduce into also the beginner according to that, the fact that it makes the installer probably is basic flow what however. There is an installer and starts with story being possible, from the る (w Development support or the specification which is made the chitin being possible, if the る being able to recommend the description like OTS, you can agree upon, however, above that does not do, the excessiveness you do the description just for the meaningless installer like OTS it is not necessary to be recommended. Before propelling OTS, it probably is now one time you should have thought concerning standardization. As for story then is. OTS, the one of the OTS っ て fool you remember and we would like to try push to the person it is it is not (w

beats me

And google:



just a wee bit different.

hatari: The machine translation is no good.
Here is your first sentence:


Google English to Japanese BETA:
機械翻訳はよいよでない。 あなたの最初文はここにある:

ots is unnessesary, but not useless. This topic is both.

どうでもいいんだけど、機械翻訳しかできない連中ばかりなのには気がめいります。
日本語くらい、まともに訳せないのでしょうか、ここの人達は。

笑える、愚民ドモの集まり(w

He just called us ignorant and is laughing at us. He thinks we can't understand him. Of course, coming to a predominantly english-speaking forum that mostly supports a specific standard, then telling them that standard is useless and insulting them in another language, isn't really that far off from ignorant either.

This is just a waste of time as long as we have to rely on machine translations. Doesn't anyone know someone who speaks Japanese? (wasn't there some Japanese guy in the LS community some years ago who also spoke English?)

This is a waste of time regardless of how good our translation is.

can we close this thread now?

Seconded!

Maybe fractal has some closing words... ? :)

Since becoming a news admin he hasn't had very many words. Bye Bye crazy Japanese person's thread that nobody could read.