[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [e4-dev] Variables Icon Paths
|
Hi,
Well I didn't mean to have variables in CSS-URLs but variables and CSS
are 2 competeing ways to implement icon replacement.
What we need for CSS tool/menu-item pseudo-states at a minimum,
attribute selectors would be great as well but not strictly needed.
Tom
On 24.01.14 08:15, Daniel Rolka wrote:
> The tricky part will be also listening to the context variable changes
> and proper refreshing after the change in context
>
> thanks,
> Daniel
>
>
> From: Brian de Alwis <briandealwis@xxxxxxxxx>
> To: E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,
> Date: 01/24/2014 03:19 AM
> Subject: Re: [e4-dev] Variables Icon Paths
> Sent by: e4-dev-bounces@xxxxxxxxxxx
>
>
> ------------------------------------------------------------------------
>
>
>
> I’m not sure how the CSS engine would obtain the context. I guess we
> could change the ResourceLocator API to provide the CSS Node/Element,
> and have a special ResourceLocator that would do the
> widget.getData(“modelElement” / OWNING_ME) and try to obtain the context
> that way?
>
> Brian.
>
> On 23-Jan-2014, at 6:11 AM, Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx> wrote:
>
>> Right that's what I'm most worried about because the vast amount of Menu
>> & Toolitems we have!
>>
>> Tom
>>
>> On 23.01.14 12:09, Daniel Rolka wrote:
>>> Hi Tom,
>>>
>>> For me it is also +1. However we have to keep in mind the performance of
>>> the CSS engine working on it
>>>
>>> thanks,
>>> Daniel
>>>
>>>
>>>
>>>
>>> From: Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>
>>> To: e4-dev@xxxxxxxxxxx,
>>> Date: 01/23/2014 10:03 AM
>>> Subject: Re: [e4-dev] Variables Icon Paths
>>> Sent by: e4-dev-bounces@xxxxxxxxxxx
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> Hi Daniel,
>>>
>>> In javafx CSS i'd write if the ToolItem has the ID 'save':
>>>
>>> #save:enabled {
>>> -fx-graphic: url("platform:/bla/my/enabled/image.css");
>>> }
>>>
>>> #save:disabled {
>>> -fx-graphic: url("platform:/bla/my/disabled/image.css");
>>> }
>>>
>>> Tom
>>>
>>> On 23.01.14 09:57, Daniel Rolka wrote:
>>>> Hi,
>>>>
>>>> Do you have any CSS snippet with the use case fot it?
>>>>
>>>> thanks,
>>>> Daniel
>>>>
>>>> IBM SWG Lab, Cracow, Poland
>>>>
>>>> IBM Polska Sp. z o.o. oddział w Krakowie
>>>> ul. Armii Krajowej 18
>>>> 30 -150 Kraków
>>>> tel. +48 12 628 9993
>>>>
>>>> NIP: 526-030-07-24
>>>> Sąd Rejonowy dla m.st. Warszawy, XIII Wydział Gospodarczy KRS
>>>> KRS 0000012941, Kapitał zakładowy: 34.650.000 PLN
>>>>
>>>>
>>>> From: Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>
>>>> To: E4 Project developer mailing list
>>> <e4-dev@xxxxxxxxxxx>,
>>>> Date: 01/23/2014 09:27 AM
>>>> Subject: [e4-dev] Variables Icon Paths
>>>> Sent by: e4-dev-bounces@xxxxxxxxxxx
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> While reading an article from Marc Teufel on an Eclipse 4 application it
>>>> reminded me of something I wanted to purpose since some time already (I
>>>> also saw a bug flying by to allow one to control the icons via CSS!).
>>>>
>>>> Anyways here we go. The idea is fairly simple and already known from 3.x
>>>> where one can use a fixed set of variables in the image paths.
>>>>
>>>> I'd like to extend this to use all variables of the IEclipseContext so
>>>> one can write an image URL like this:
>>>>
>>>> platform:/plugin/icons/${themeId}/${enabled}/img.png
>>>>
>>>> What do you think, does this make sense?
>>>>
>>>> Tom
>>>> _______________________________________________
>>>> e4-dev mailing list
>>>> e4-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> e4-dev mailing list
>>>> e4-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>>>>
>>>
>>> _______________________________________________
>>> e4-dev mailing list
>>> e4-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> e4-dev mailing list
>>> e4-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>>>
>>
>> _______________________________________________
>> e4-dev mailing list
>> e4-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>
>
>
>
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>
