Forgot to mention that this errors occured in the source version of
showcase.
And the Error seems to come from the theme select window.
Dietrich Streifert schrieb:
@Fabian: I saw your change in rev. 8628 of trunk where you removed the
dependency from qx.theme.classic.Appearance.
Now I'm get
@Fabian: I saw your change in rev. 8628 of trunk where you removed the
dependency from qx.theme.classic.Appearance.
Now I'm getting errors about missing appearances in the console. The
missing appearances I found:
"table-pane", "table-header", "widget", "image", "atom",
"window-captionbar-ti
Thanks Fabian, in this way smaller qx.js can be build.
When I create a new appearance entry or update an existing one, I will try
to update both themes.
Fabian Jakobs-2 wrote:
>
> Hi David,
>
> the inheritance was mainly used for convenience because we could start
> with only a small subset a
dperez schrieb:
> I have tried to comment the extend key, and seen no effect:
>
> qx.Theme.define("qx.theme.ext.Appearance",
> {
> // extend : qx.theme.classic.Appearance,
>
> title : "Ext",
>
> appearances : ..
>
> }
>
> So, the extend clause adds an unneeded dependency.
> Am I right?
>
>
As a matter of fact, only a few appearance entries are reused.
dperez wrote:
>
> I have tried to comment the extend key, and seen no effect:
>
> qx.Theme.define("qx.theme.ext.Appearance",
> {
> // extend : qx.theme.classic.Appearance,
>
> title : "Ext",
>
> appearances : ..
>
> }
>
I have tried to comment the extend key, and seen no effect:
qx.Theme.define("qx.theme.ext.Appearance",
{
// extend : qx.theme.classic.Appearance,
title : "Ext",
appearances : ..
}
So, the extend clause adds an unneeded dependency.
Am I right?
dperez wrote:
>
> Hi,
>
> Is it inten
Hi,
Is it intended to derive the ext.Appearance class from classic.Appearance?
It seems that the ext class redefines all the appearance entries, so there
is no need to inherit.
In this way, if I like more the ext appearance as a starting point, I could
remove from my build the classic one, which
