It may be possible to change the LOOK with CSS, but not the FEEL, which is
where Java apps have traditionally failed big time.
Some things that I don’t think can be changed with CSS:
1) texts
2) order of buttons
3) escape characters for shortcuts
4) menus
5) system-level stuff (double-clicking o
On 9 Dec 2013, at 03:18, Felix Bembrick wrote:
> @Stephen, you are absolutely right about this. But such an approach (and
> pretty much *any* approach) to "emulated" native look and feels is fraught
> with difficulties and complexities.
>
> Firstly, it will *never* be possible to completely e
dgets I have no
> idea...
>
> On 9 Dec 2013, at 22:49, Stephen Winnall wrote:
>
>> On 9 Dec 2013, at 03:18, Felix Bembrick wrote:
>>
>>> @Stephen, you are absolutely right about this. But such an approach (and
>>> pretty much *any* ap
> I am with you on the "design pattern" approach you refer to which is
> basically a higher level of abstraction than say one which actually specifies
> which widget types to use.
>
> But who is this "someone who loves the target platform" and how and when do
> they get to hook-in the actual wi
I am trying to make JavaFX 8 work with OSGi Declarative Services. My preferred
solution would be to instantiate javafx.application.Application as an OSGi
service.
As I understand it, there are two ways of activating JavaFX:
1) sub-class javafx.application.Application or
2) call javafx.applicati
tatic { Platform.RunLater} calls spread
> out in different classes, so don't try to load those classes before your
> javafx application was started... OUCH!
>
> Didn't I say it was hairy and messy? JavaFX and OSGi is quite a bad match
> unfortunately.
>
>
n/Platform.html#startup-java.lang.Runnable
>>
>> <http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable>-
>>
>>
>> On 18 February 2016 at 20:08, Stephen Winnall
>> <mailto:st...@winnall.ch> wrote:
>>
>>
>>> As I understand it, there are two ways of activating JavaFX:
>>>
>>> 1) sub-class javafx.application.Application or
>>> 2) call javafx.application.Application.launch()
>>>
>>>
>>
>>
>>
>>
blic void stop(BundleContext context) throws Exception {
> Platform.exit();
>}
>
>public BundleContext getBundleContext() {
>return context;
>}
> }
>
> Op 20-02-16 om 01:28 schreef Stephen Winnall:
>> Anirvan, Kevin
>>
>> Thanks for this.
>
m.cuhka.home.application.Application.class,
> this, properties);
> }
>
> Maurice.
> Op 20-02-16 om 15:08 schreef Stephen Winnall:
>> Hi Maurice
>>
>> I have done something similar, but it has the following drawback in my view:
>> the class launched (Udoo15App
eateDictionary();
> BundleContext bundleContext =
> UdooActivator.bundleActivator().getBundleContext();
> bundleContext.registerService(com.cuhka.home.application.Application.class,
> this, properties);
> }
>
> Maurice.
> Op 20-02-16 om 15:08 schreef Stephen Winnall:
>
10 matches
Mail list logo