Just wanted to inform everybody that since AODL project is not active. I am thinking of a fork.
The goals will be to: * make all tests pass (currently not all tests are green) * reduce memory consumption * speed-up large-document generation (this is very related to reduce memory usage)
.Net 1.1 support will be dropped if there will be a need to do that.
Whad do you think about it?
Post edited by: darius.damalakas, at: 2008/02/18 16:57
The administrator has disabled public write access.
Re:Fork of AODL
Date: 2008/02/17 07:17
By: Phil Jollans
Status: User
Karma: 0
Junior Boarder
Posts: 5
Hi Darius,
I have only started using AODL today, to write a spreadsheet file. Lars has obviously put a lot of work into this project, and for the most part, it seems fantastic. On the other hand, I have already downloaded the source code and made some minor changes, in order to create a spreadsheet at all.
I am dismayed to read that the project is "not active". What does this mean? Is this your assumption, or do you know that Lars has ceased working on it?
Phil
The administrator has disabled public write access.
Re:Fork of AODL
Date: 2008/02/18 17:07
By: Darius Damalakas
Status: User
Karma: 0
Senior Boarder
Posts: 19
That is my personal opinion.
However, last time Lars posted something on this forum in or in mailing list was at least lats year summer.
My intention with this post was to attract attention of what is happening, and see if people react at all.
Phill, what modifications did you need to make in order to make spreadsheets? AFAIK, everything's already there.
The administrator has disabled public write access.
Re:Fork of AODL
Date: 2008/02/26 06:27
By: Phil Jollans
Status: User
Karma: 0
Junior Boarder
Posts: 5
Hi Darius,
sorry that I didn't reply more quickly.
I have more or less rewritten the functions - Table.InsertCellAt - Row.InsertCellAt because I found that these functions basically didn't work. In fact, I found that the sample at http://wiki.services.openoffice.org/wiki/AODL_example_1 did not work.
I have made an insignificant change to Table.Row_OnRowChanged() concerning the name of the style which is generated.
I have added a new constructor to FormatedText to create an instance with an existing TextStyle object. This is basically new functionality.
I have put in an break statement in ChartImporter.CreateContent(). I think I only did this because an error message when I compiled the library using Visual Studio 2005. I don't need this change.
My main problems were with creating cells and setting styles.
I think there needs to be more clarity about when cell objects are created or replaced. Cell objects are created by Row.InsertCellAt(), but also by the event handler Table.Row_OnRowChanged(), which makes sure that all rows have the same number of cells. It is not at all clear to me, whether this functionality is necessary.
I find the handling of syles generally confusing. I had to dig into the OpenDocument specification and poke around in the XML files until I figured it out at all. For my spreadsheet, I use only 3 CellStyles and 3 TextStyles which I create as objects and then assign to cells as I generate them.
AODL usually creates unique CellStyle, RowStyle, ColumnStyle and TextStyle objects for each Cell, Row, Column of FormatedText object. This ends up as a question of philosophy. For example, I would be happy to define a default RowStyle to be applied to all new rows, but other users might not want that at all.
If this sounds like I an discontent with the quality of the library, I must stress that Lars has done a fantastic job. These are really minor issues.
Phil
The administrator has disabled public write access.
Re:Fork of AODL
Date: 2008/02/26 06:27
By: Phil Jollans
Status: User
Karma: 0
Junior Boarder
Posts: 5
Hi Darius,
sorry that I didn't reply more quickly.
I have more or less rewritten the functions - Table.InsertCellAt - Row.InsertCellAt because I found that these functions basically didn't work. In fact, I found that the sample at http://wiki.services.openoffice.org/wiki/AODL_example_1 did not work.
I have made an insignificant change to Table.Row_OnRowChanged() concerning the name of the style which is generated.
I have added a new constructor to FormatedText to create an instance with an existing TextStyle object. This is basically new functionality.
I have put in an break statement in ChartImporter.CreateContent(). I think I only did this because an error message when I compiled the library using Visual Studio 2005. I don't need this change.
My main problems were with creating cells and setting styles.
I think there needs to be more clarity about when cell objects are created or replaced. Cell objects are created by Row.InsertCellAt(), but also by the event handler Table.Row_OnRowChanged(), which makes sure that all rows have the same number of cells. It is not at all clear to me, whether this functionality is necessary.
I find the handling of syles generally confusing. I had to dig into the OpenDocument specification and poke around in the XML files until I figured it out at all. For my spreadsheet, I use only 3 CellStyles and 3 TextStyles which I create as objects and then assign to cells as I generate them.
AODL usually creates unique CellStyle, RowStyle, ColumnStyle and TextStyle objects for each Cell, Row, Column of FormatedText object. This ends up as a question of philosophy. For example, I would be happy to define a default RowStyle to be applied to all new rows, but other users might not want that at all.
If this sounds like I an discontent with the quality of the library, I must stress that Lars has done a fantastic job. These are really minor issues.
Phil
The administrator has disabled public write access.
Re:Fork of AODL
Date: 2008/02/26 17:11
By: Darius Damalakas
Status: User
Karma: 0
Senior Boarder
Posts: 19
Phil, i am registering a project AODL2 at sourceforge.
Would you like to share your code and/or contribute?
The administrator has disabled public write access.
Forum 
