Reply to thread

Message

<blockquote data-quote="ge2301" data-source="post: 1199265" data-attributes="member: 145639">[USER=48495]@morpheus_xx[/USER] in the previous posts (though already some time ago) users are confused, that TE is a theme of BV and I'm sure that many standard users even don't find this theme.The reason is clear between us, TE refers to the BV menu model. Currently I'm heavily working on the MIA-rework implementation and overworks into the BV themes. There will be a new look and feel.However I want to have TE as it's own skin, it has besides menumodel nothing in common with BV.It's besides confusion, that people shifting from MP1 would like to see something familar and this is the popular TItanium design.1) I just create it as own skin and we have the same MenuModel 2 times2) There is any possibility to make a skin dependent on another skin!?3) It was once discussed: To make the MenuModel not skin related, but addit to skinbase and everything can refer to it.Which variant is most preferable? I guess you don't line (1) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />, (2) is easiest, (3) means work for you, but most elegant I guess.</blockquote>

[QUOTE="ge2301, post: 1199265, member: 145639"] [USER=48495]@morpheus_xx[/USER] in the previous posts (though already some time ago) users are confused, that TE is a theme of BV and I'm sure that many standard users even don't find this theme. The reason is clear between us, TE refers to the BV menu model. Currently I'm heavily working on the MIA-rework implementation and overworks into the BV themes. There will be a new look and feel. However I want to have TE as it's own skin, it has besides menumodel nothing in common with BV. It's besides confusion, that people shifting from MP1 would like to see something familar and this is the popular TItanium design. 1) I just create it as own skin and we have the same MenuModel 2 times 2) There is any possibility to make a skin dependent on another skin!? 3) It was once discussed: To make the MenuModel not skin related, but addit to skinbase and everything can refer to it. Which variant is most preferable? I guess you don't line (1) :), (2) is easiest, (3) means work for you, but most elegant I guess. [/QUOTE]

Verification