Hi,
How to set font for a tabview page's title label and a table's header
labels?
I tried this in Appearance.js:
>
> "tabview-page/title" : {
> style : function(states) {
> return {
> font : qx.bom.Font.fromString("14px verdana bold"),
> marginTop: 5,
>
Ok, last post for today: here is the summary of my suggestions, wrapped up in
one page:
http://qooxdoo.org/documentation/rpc
I'd be very much interested in feedback. I wonder how we should proceed -
creating individual bugs and voting on them?
Best,
Christian
--
View this message in context
Derrell Lipman wrote:
>
> Jean-Baptiste, the reason that a hasCapabilities() method is required is
> that a backend can be used by/for multiple applications. The backend need
> not be updated on the same schedule as the applications (except for adding
> the requisite backend methods, of course).
Replying to a number of comments without proper attribution...
Christian, I have no problem with getCapabilities() as opposed to
hasFeature().
Vincent, 0.7 is old enough that anyone beginning a project requiring a
backend _now_ will need one that is 0.8+ compatible. The java backend needs
to be u
One other option is to roll the backends INTO the Qooxdoo framework
distribution so that they are always supplied with the appropriate
Qooxdoo version - why do they need to be kept as contributions? From
time to time, contributions are combined into the Qooxdoo mainstream
distribution, aren't they
Hello Jean-Baptiste,
Jean-Baptiste BRIAUD -- Novlog wrote:
>
>
> Could one explain to me why this kind of method is needed ?
> How this method will be used ?
>
>
It is a useful method once you move away from creating backends solely for
the purpose of servicing a single application, and tow
On Nov 28, 2009, at 12:44 , panyasan wrote:
>
> Hi Derrell,
>
>
> Derrell Lipman wrote:
>>
>> Agreed. A qxServer.hasFeature(String featureName) method or something of
>> that sort would be appropriate I suppose. We might end up with other
>> qxServer.* methods, such as the introspection. (I'm
Hi Derrell,
Derrell Lipman wrote:
>
> Agreed. A qxServer.hasFeature(String featureName) method or something of
> that sort would be appropriate I suppose. We might end up with other
> qxServer.* methods, such as the introspection. (I'm not at all wed to that
> name nor even to containing them i
Hi all,
not being a java person, it seems nontheless imperative to me that an
updated and unified Java backend, together with some decent and up-to-date
docs should accompany the qooxdoo 1.0 release. Everything else - at least
that would be my impression - would be unfortunate and unneccessarily
