Ok Richard. Right now I have to do more than copy paste. I have to use reflection to call private package and private fields/methods. Copy pasting would be fine, I think that having to use reflection to circumvent the fields/methods protection level is a no go.
I'm hacking up a XYBarChart, when I'm finished I'll look at the code and see what I think is needed or nice to have. Thanks, best regards, On Thu, Sep 26, 2013 at 9:42 PM, Richard Bair <[email protected]>wrote: > I think it would be good to file some feature requests for specific API / > functionality that you'd like to see added. There are a lot of things here > that we just weren't ready to commit to forever, and since the code is open > source you at least can copy/paste a big chunk of it if needed and that > still leaves us with some flexibility to change our implementation in the > future without breaking you. So while copy/paste is not the nicest, it is a > lot nicer than us committing to API prematurely. However if you have > specific use cases that need to be supported, we can start doing the > planning to see how we can accommodate that. > > Thanks > Richard > > On Sep 6, 2013, at 1:15 PM, Pedro Duque Vieira < > [email protected]> wrote: > > > Hi, > > > > I'm trying to create a custom chart: a XYBarChart. That is a chart that > > won't have the same limitation as the BarChart which only allows you to > > specify a ValueAxis/CategoryAxis pair. > > In doing this I was looking at the code for BarChart and copying as much > as > > I can from its implementation. The problem is that it uses a lot of > package > > private methods and fields from XYChart. > > I think the framework chart implementations should be less reliant on > > package private methods because if that happens then programmers trying > to > > create their own charts will probably need to rely on those same methods > > which of course they won't be able to call. > > > > Best regards, > > > > > > > > -- > > Pedro Duque Vieira > > -- Pedro Duque Vieira
