JavaFX for the Enterprise - Working Group

Tom Schindl tom.schindl at bestsolution.at
Wed Oct 17 15:00:23 PDT 2012


The problem is that we only get a control which is able to render rich text but unfortunately no editor! To get an editor with features you see in todays IDEs is a very long way from what we get with jfx8.

Tom

Von meinem iPad gesendet

Am 17.10.2012 um 18:01 schrieb Peter Pilgrim <peter.pilgrim at gmail.com>:

> Richard Bair gave a presentation on rich text components vis-a-vis
> TextPane and TextFlow at JavaOne
> 
> Supporting styles, bidirectional flow, Arabic /Hebrew maybe Chinese?,
> proper text wrapping and flowing around a defined area.
> 
> So in affect we should be all able to write IDE in JavaFX
> 
> If Kim is lurking about still on this list, he will definite
> understand the verbosity  of the old Swing style text document Apis ,
> I expect better with the new FX text Apis in Fx8
> 
> Sent from my iPhone 4S
> 
> On 17 Oct 2012, at 16:34, Mark Claassen <markclaassenx at gmail.com> wrote:
> 
>> I am not as concerned in the "bridge" as I am in the framework.  Although I
>> agree a bridge is necessary, and would like it to work well.
>> 
>> My comment is more about being on a track to where someone could
>> (eventually) build Netbeans from scratch using only JavaFX.  The customized
>> window behavior, the Drag and Drop, the little tooltip-like popup windows
>> used in the tree renderers to show the text that is not visible because of
>> the visible bounds of the tree, ... all of it.
>> 
>> What about the document model?  The Swing javax.swing.text.Document
>> interface is pretty powerful.  The way it seems implemented in JavaFX does
>> not seem nearly as powerful, or as pluggable.
>> 
>> Mark
>> 
>> On Wed, Oct 17, 2012 at 11:21 AM, Mario Torre <
>> neugens.limasoftware at gmail.com> wrote:
>> 
>>> """
>>> This thread is interesting. I've seen at J1 some tools using JavaFX
>>> with the SWT bridge. The Swing one will also work equally well. We
>>> also have (we need to put some love to make it work on 2.2
>>> """
>>> 
>>> Somehow this got cut, I meant:
>>> 
>>> This thread is interesting. I've seen at J1 some tools using JavaFX
>>> with the SWT bridge. The Swing one will also work equally well. We
>>> also have (we need to put some love to make it work on 2.2) that
>>> can be used to embed Swing on top of JavaFX (the other way around).
>>> 
>>> Cheers,
>>> Mario
>>> 
>>> 2012/10/17 Mario Torre <neugens.limasoftware at gmail.com>:
>>>> 2012/10/17 Mark Claassen <markclaassenx at gmail.com>:
>>>>> I joined this list a few days ago because I wanted to start contributing
>>>>> So far, I am not sure it is quite where I should be.  I would like to
>>>>> discuss more about the components (table, list boxes, ...).  I am not
>>>>> exactly sure where to do that.
>>>> 
>>>> You just unfortunately ended up subscribing to this list in the middle
>>>> of a storm :)
>>>> 
>>>> But this list has been used in the past to discuss components and
>>>> details of the implementation, so this is definitely the right place
>>>> to start discussing those things.
>>>> 
>>>> @Richard: Perhaps it would be more fun to simply have a list dedicated
>>>> to flaming Oracle for supporting HTML 5 rather than JavaFX :)
>>>> 
>>>>> However, I will add here that I started (a very short-lived) thread on
>>> the
>>>>> netbeans user list along these lines.  Basically what I was saying was
>>> that
>>>>> Netbeans is a wonderful UI built on Swing.  Could this same project be
>>> done
>>>>> in JavaFX?  Maybe not yet, but could it be in the future?  It seems like
>>>>> the JavaFX team could get a lot of advice and requirements from the
>>>>> netbeans team.
>>>>> 
>>>>> http://forums.netbeans.org/topic51717.html
>>>> 
>>>> This thread is interesting. I've seen at J1 some tools using JavaFX
>>>> with the SWT bridge. The Swing one will also work equally well. We
>>>> also have (we need to put some love to make it work on 2.2
>>>> 
>>>> The big trouble is #2, this will only work if:
>>>> 
>>>> 1. Netbeans can ship JavaFX
>>>> 2. JavaFX is included in any major OpenJDK/JDK releases (that means,
>>>> including distribution related IcedTea builds).
>>>> 
>>>> For both options, JavaFX needs to be fully Open Sourced, or even
>>>> NetBeans will fall back into non free bits, so I agree with them.
>>>> 
>>>>> Some of the main data structures, like the ObservableList, make me
>>> cringe.
>>>>> I created a similar structure 10 years ago and have since learned the
>>> error
>>>>> of my ways.  Granted, the JavaFX team has a lot more resources and
>>>>> experience than I did all those years ago, but from my point of view,
>>> there
>>>>> are dangerous waters ahead.
>>>> 
>>>> I'm sure this is the kind of discussion mostly welcomed on this list,
>>>> after all, this is what makes it a community project.
>>>> 
>>>> Cheers,
>>>> Mario
>>>> --
>>>> pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
>>>> Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF
>>>> 
>>>> IcedRobot: www.icedrobot.org
>>>> Proud GNU Classpath developer: http://www.classpath.org/
>>>> Read About us at: http://planet.classpath.org
>>>> OpenJDK: http://openjdk.java.net/projects/caciocavallo/
>>>> 
>>>> Please, support open standards:
>>>> http://endsoftpatents.org/
>>> 
>>> 
>>> 
>>> --
>>> pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
>>> Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF
>>> 
>>> IcedRobot: www.icedrobot.org
>>> Proud GNU Classpath developer: http://www.classpath.org/
>>> Read About us at: http://planet.classpath.org
>>> OpenJDK: http://openjdk.java.net/projects/caciocavallo/
>>> 
>>> Please, support open standards:
>>> http://endsoftpatents.org/
>>> 


More information about the openjfx-dev mailing list