Chart2/Open Technical Issue in Chart2
There still some architectural issues left that have to be solved. This section serves for showing those problems and showing the progress in finding solutions.
- 1 Application-Framework-Related Problems
- 2 Calc- and Writer-Related Problems
- 3 Chart Problems
Identify the XDataProvider reliably
If the chart is embedded in a container document that provides the data for this chart, the chart contains range-strings at several places in its conten.xml stream that are understood by the container, so that the data can be located there. In Calc such a string would look like this: "Sheet1.A2:A7". Such range-strings can appear in the chart:plot-area element of a chart or at a chart:series, chart:categories or chart:domain element.
If a chart has its own data, this data is stored in a local table in the XML-file. The mentioned range-strings are then of a similar form, with the fixed table-name "local_table". But, the local table is also stored, as a kind of cache, if the data comes from outside. Therefore the existence of the local table does not imply that a chart has own data.
So, neither the existence of local data, nor the existence of range-addresses (and even the content, considering that it is allowed that a sheet may also have the name local_table) determines whether or not a chart uses own data or data from the container document.
In the old chart implementation, the chart always reads the internal data and uses it. If the data comes from the container, the container has an additional attribute that contains the complete data-range as one string. It then sets this string at the chart, which gives the chart the knowledge that data comes from outside (actually, in the old implementation, there is always local data. If data in Calc changes, the Calc prepares an SchMemChart object that contains the new local data and sets this object at the chart).
In the new implementation, we must to get rid of the badly-designed approach, as we no longer have one complete address-range for the entire chart.
Solution: We have to introduce a new XML-attribute at the chart that identifies the data provider. This may be a flag denoting "own data" or "external data", or even a URL, or the like, that uniquely identifies the data provider document.
Problem: Currently, it is necessary that when loading a chart, the container document is set as XParent before the chart itself is loaded. Otherwise there is no data provider, and the ranges are not valid for the internal data provider, and therefore are forgotten. A later setting of the data provider does not re-establish the correct range-strings.
Note: When copying a chart into the clipboard it is saved into a temporary storage. While saving it is not known where the chart will later be pasted into. So, it would be good if, for this case, the attributes in the chart stream would uniquely identify the data source, such that on paste you can decide whether you still have the pointed-to data in your document or not.
Update of the Chart on changed Data
When a chart gets its data from the container document, and the data changes, the changes are notified via a listener mechanism. That is, when the chart queries for data at the XDataProvider, it gets XLabeledDataSequences. At those XLabeledDataSequences it starts listening for changes. If a change event is fired, the chart sets itself as modified, which forces the view to repaint, as it listens to model changes exactly via this mechanism.
However, if a Calc document containing Charts is loaded, the charts are either not loaded immediately because they are not visible, or because the contain a replacement image that shows the last rendered view.
In both cases, changes in the spreadsheet, like a change in data (which should be visible via a newly rendered view) or moving around ranges (which must change the ranges that are stored in the model), are not propagated to the chart, as it is not loaded and therefore is not listening.
In the old implementation, again, the fact that the Calc knew the data-range for each chart, solved this problem. Because the Calc could load all unloaded charts affected by the change, and then notify it. However, this requires internal knowledge of the chart to be exposed to the container document.
Solution: When an OLE-object is loaded, it only shows the replacement image. This state is called the "LOADED" state. This means only a small "stub" is loaded, not the entire object. The XModel of an object (including the entirely applied content of the XML-streams) is loaded in the "RUNNING" state. So when all charts would initially be set into the RUNNING state, this would ensure the existence of all XModels, which would allow the listening to work.
See also: Chart2 Single-Click Concept. There, the issue of loading models at the right time is also handled.
Problem:: It has to be evaluated, if loading the XModel objects of all charts in a document might take too long in loading a document, or if it consumes too much memory.
Calc- and Writer-Related Problems
The com.sun.star.table.XTableCharts object is based on the old chart
When you want to insert a new chart into Calc or Writer, this can be done via the com.sun.star.table.XTableChartSupplier interface that returns an XTableCharts container. At this container there is a method:
void addNewByName( [in] string aName, [in] ::com::sun::star::awt::Rectangle aRect, [in] sequence< CellRangeAddress > aRanges, [in] boolean bColumnHeaders, [in] boolean bRowHeaders );
You need a sequence of CellRangeAddresses to give a range and the parameters whether to use the first column or row for labels. In comparison to the XDataProvider method:
XDataSource createDataSource( [in] sequence< ::com::sun::star::beans::PropertyValue > aArguments );
the parameters in aArguments differ in the following way: instead of sequence< CellRangeAddress >, we only have one string. This is no problem, as there exists a conversion. But the parameter "DataRowSource" is missing. So you can only say if the first column or row is used for labels, but not if the data comes from rows or columns. Without this information, the other information is also useless. This renders the entire interface useless.
As a work-around, you can create the chart with some dummy data, and then attach new data using the data provider interface. However, a new interface, probably one that only gets the name and the rectangle would be more appropriate than the work-around.
Drag & Drop in Calc: Identify Drag-Source
If you want to drag some selected cells in a spreadsheet and drop them on a chart, so that the chart uses this new data, the chart will get an XTransferable. The format that is contained in the XTransferable is currently the DDE format. The chart has to make sure that the dropped content comes from the same document or the same XDataProvider in particular. To do that, there must be a possibility to find out if an XTransferable belongs to the XParent of the current chart, or the XDataProvider which is attached.
One idea was to compare the "Topic" part of the DDE message with the title of the Calc document's window. Currently this is the same. At least during Drag & Drop this should not change either. So, we would need a way to query the title of the parent XModel in exactly the format that is contained in the DDE topic (for an unsaved document the name is Untitled1, Untitled2, ...).
Maybe there is a better approach. Something like
XDataProvider::isValidTransferable( [in] XTransferable xObject )
This way, the data provider can implement what fits best to find out if the XTransferable comes from the same document.
Drag & Drop works only in ACTIVE mode
Drag & Drop only works when the chart is always ACTIVE. So, unless charts will be always ACTIVE, drag & drop does not work, as the drop target is not the chart but the surrounding embedded object. Alternatively, we need a mechanism that forwards the drop-request to the underlying OLE-object, which would require activation at least in this moment. This could be flag-driven, to avoid loading all OLE objects when hovering over them with drop content.
Autoscaling of Text relative to Diagram Size
In the old chart implementation, when auto-scaling was on, a resize of a chart OLE object or the resize of the Window of a standalone chart resulted in a resize of the actual font sizes in the model, i.e. the model was changed. In the case of an OLE object this is ok, as this also changes the visual area, which is also a model property. However, resizing a document window should not modify the model.
To overcome this bad design, in the new chart we decided to add a reference size to font sizes in the model. So when auto-scaling should be on for an object, the size of the page (the whole chart, which equals the visual area size) is set as ReferencePageSize along with the font. So if the chart is resized, the view can calculate a new font size by comparing the new size of the page with this reference size and adapt the stored font size. So the font becomes bigger without having to change the model (apart from the fact that a resize of the OLE object modifies the model, because the visual area size is changed). If a font should not be scaled, the reference size is simply set to void. So far this concept is very good. It also solves the problem of getting the exact same font size after resizing the chart to an extreme (e.g. very small) and back to the original size again, which was a mess in the old chart.
However, there are objects where the fonts are supposed to scale with the diagram size rather than the page size, e.g. the axes. The problem here is that the diagram size may be void, which means the view has to calculate it by itself. The actual size of the diagram is therefore not known unless a view is created that does the auto-calculation. So, if you want to enable auto-scaling for an axis in a chart, you would have to set the actual diagram size as reference size at the model axis object. However, you don't know it when the diagram has an auto-size.
In the file-format we should also have the currently visible font size plus a boolean flag saying whether an object should auto-scale or not. So, here we have a similar problem. We would need to have a view that calculates the size of the diagram (if it has auto-size), after a chart was loaded, in order to translate the boolean flag into a fitting diagram reference size. And also for saving, we would need the current diagram size for calculating the currently visible font size.
So, for case that the diagram is auto-sized, to avoid having a view for switching auto-scale on for diagram-dependent font sizes, as well as saving and loading of files we need a solution here.
- In case the diagram is auto-sized, set the page size as reference size. Unless the diagram is resized, the mechanism would then work for resizes of the whole chart like before. The font size written to the file would be the real font size in the model, which is ok. The view would have to use the page size for comparison when it finds out that the diagram's model has no size.
- What happens if a user resizes the diagram? In this scenario we would need a mechanism that sets the currently calculated auto-size of the diagram (before the resize) as a fixed size to all model objects that use a diagram reference size and have the page size set as reference. Then it has to set the new diagram size at the diagram. This is error prone, as you might forget objects. Also, comparing the current reference size with the page size is also not very elegant.
- Drop the feature of diagram-related font sizes. Use only the page as reference size. This would simplify things but would break the feature of getting smaller fonts when you resize the diagram inside a chart document. I currently prefer this solution for different reasons.
- First, we only have one concept: a reference page size, not reference sizes that refer to different objects.
- Second, we always know the page size, as it is equal to the visual area size of the model. Apart from that an auto-page size wouldn't make much sense. So, we solve this problem.
- Third, the down-side of doing this is, that resizing the diagram would not scale the fonts at axes, (axis titles?) and data points. But on the other hand, a chart document should layout the chart in a nice way, so that a user should not have the need to resize the diagram. If a user still wants to change the diagram size, he can change the font sizes manually. I think this is a valid compromise, as I think this does not happen too often. Also, for small diagram size changes a non-scaling font doesn't matter too much.
- It simply does not make sense to set a reference size that is not found at the correspodning object (the diagram) in the model, but can only be obtained by a view. If you replaced your view implementation or you changed the auto-calculation of the view, you will get different results, so it is not reliable.
- On resize change the model.
- Setting re-scaled fonts is a bad idea as the old chart showed. You get rounding errors with sometimes drastic results.
- It would be ok for OLE objects, as they are modified anyway (the visual area size)
- If we would introduce a stand-alone chart some day, we would have to change the behaviour similar to draw or writer: The chart has a fixed page size and resizes of the window only change the visual area of the document. However, this conflicts with the use of the visual area as page size in the OLE scenario, where we definitely want to have the page size equal to the visual area size.
- Therefore, this is seems like a bad idea.
- Do not allow an empty diagram size if there are objects with DiagramReferenceSizes.
- This is also no good idea, as the diagram would need knowledge about all objects with diagram reference sizes, to behave accordingly on setting the size.
- When we want auto-resize as default, this would also mean the default would be to have a concrete diagram size, which is not reasonable.
So, summarizing, dropping the feature of fonts scaling with the diagram seems the most appropriate thing to do. Of course we will lose a feature and have to decide if it is ok for users to no longer have this. As I said, I think resizing the diagram to something very much smaller than the one you get with auto-calculation is not a very common or typical scenario.
(article by Bm@openoffice.org)