Thanks! On Jan 6, 2014, at 8:33 AM, Eric Le Ponner <eric.le.pon...@oracle.com> wrote:
> I would say it's deeply embedded. > > SB2 currently defines a fixed list of "property classes" that can be edited > in the Inspector panel. > Extending this list with a new type means: > - adding some specific metadata that help Scene Builder to edit/create FXML > text > - adding some specific UI logic that enables the Inspector panel to present > and let the user edit the value > Doing this requires a pretty deep understanding of SB2 architecture. > > Eric > > > > Le 6 janv. 2014 à 17:20, Richard Bair <richard.b...@oracle.com> a écrit : > >> If somebody else wanted to contribute, where should they go looking for >> those limitations and how to remove them? Or is it very deeply embedded in >> the code? >> >> On Jan 3, 2014, at 2:15 AM, Eric Le Ponner <eric.le.pon...@oracle.com> wrote: >> >>> Yes, SB currently makes a filtering : for custom components, it displays: >>> - properties that are inherited from JavaFX core classes >>> - properties with basic java types (integer, double, string, boolean). >>> >>> We'll try to remove some of those limitations over the time. >>> >>> Eric >>> >>> >>> Le 3 janv. 2014 à 11:01, Tom Eugelink <t...@tbee.org> a écrit : >>> >>>> >>>> Adding the controls in JFXtras to SceneBuilder worked without a problem, >>>> but scene builder does not show all their properties. For example >>>> CalendarTextField has 5 properties like Locale, Calendar, DateFormat, but >>>> only "promptText" is shown by SceneBuilder. >>>> >>>> >>>> >>>> >>> >> >
