On Jan 25, 2014, at 5:54 AM, John Hendrikx wrote:
> On 24/01/2014 22:28, David Grieve wrote:
>> On Jan 24, 2014, at 4:02 PM, John Hendrikx wrote:
>>
>>> I've got an update on this.
>>>
>>> I've rewritten the code now to make use of multiple skins, and doing some
>>> trickery with Factories t
On 24/01/2014 22:28, David Grieve wrote:
On Jan 24, 2014, at 4:02 PM, John Hendrikx wrote:
I've got an update on this.
I've rewritten the code now to make use of multiple skins, and doing some
trickery with Factories to make them easily switchable.
The main reason I've rewritten them is bec
On Jan 24, 2014, at 4:02 PM, John Hendrikx wrote:
> I've got an update on this.
>
> I've rewritten the code now to make use of multiple skins, and doing some
> trickery with Factories to make them easily switchable.
>
> The main reason I've rewritten them is because I think I will not be able
I've got an update on this.
I've rewritten the code now to make use of multiple skins, and doing
some trickery with Factories to make them easily switchable.
The main reason I've rewritten them is because I think I will not be
able to provide CSS properties that are accessible if they are not
On Wed, Jan 8, 2014 at 10:56 PM, John Hendrikx wrote:
> On 7/01/2014 18:11, Tomas Mikula wrote:
>
> With a non-reusable skin, dispose is pretty much just removing the
> listeners. With a reusable instance, I suspect there is more work to reset
> the state of the instance (e.g. removing childre
I've written the Agenda control (Google Calendar alike) in JFXtras, which of
course also can have multiple skins although right now it only has one. So this
is an interesting discussion.
On 2014-1-8 22:31, John Hendrikx wrote:
That's basically how I've solved it so far (although I call the r
On 7/01/2014 18:11, Tomas Mikula wrote:
With a non-reusable skin, dispose is pretty much just removing the
listeners. With a reusable instance, I suspect there is more work to
reset the state of the instance (e.g. removing children, or, if you
were concerned about performance, returning them to
That's basically how I've solved it so far (although I call the reusable
skins "Layouts" for lack of a more imaginitive name).
However, I'd like to support CSS properties as well for the delegates,
and I'm not sure how the CSS engine deals with Skins that can change
their properties when som
On Tue, Jan 7, 2014 at 4:26 PM, John Hendrikx wrote:
> On 7/01/2014 14:50, Tomas Mikula wrote:
>
>> Interesting ideas. I'm wondering, do you switch skins often enough that
>> you are worried about performance (and thus care about reusability of
>> skins)? Because I don't see how reusability of sk
Could you write a single skin that delegates to one or more reusable skins?
On Jan 7, 2014, at 7:26 AM, John Hendrikx wrote:
> On 7/01/2014 14:50, Tomas Mikula wrote:
>> Interesting ideas. I'm wondering, do you switch skins often enough that you
>> are worried about performance (and thus care a
On 7/01/2014 14:50, Tomas Mikula wrote:
Interesting ideas. I'm wondering, do you switch skins often enough
that you are worried about performance (and thus care about
reusability of skins)? Because I don't see how reusability of skins
saves you lines of code - whether the code is in the constru
Interesting ideas. I'm wondering, do you switch skins often enough that you
are worried about performance (and thus care about reusability of skins)?
Because I don't see how reusability of skins saves you lines of code -
whether the code is in the constructor or in the initialize() method, it is
th
12 matches
Mail list logo
