On Feb 13, James Howe wrote:
[snip]
> Perhaps they have their own special 'grid-like' control instead of using
> the standard grid?
Yup. For LaszloMail, we had to replace the grid component with something
custom for performance reasons. Also, the grid component uses some pretty
wierd tricks to make it easier to use, and if I remember correctly, the
mail team had trouble getting a handle on the point at which replication
was done ;)
I've found that in my applications, it's advantagous to create a custom
grid rather than to use the grid component -- especially when I need to do
stuff like add/remove rows at runtime. Also, the performance of a custom
grid can usually be optimized well past what is possible with the
component.
As for getting a handle on grid's LzLazyReplicationManager, check out this
method on basegrid:
<method name="makeCellsAndColumns">
This is where the replicated row gets made ("rowclass" is a property of
basegrid that contains a cons'd up row made from the column definitions)
var r = new _rowclass ( content.rowparent , initArgs, cells , true );
If you look above this, you'll see that the initArgs name property is set
to "replicator" so after replication happens, the grid's
content.rowparent.replicator will be the replication manager.
You could override makeCellsAndColumns in your grid, but remember that
content.rowparent.replicator will not be a replication manager until the
grid's contentdatapath matches multiple nodes.
Good luck.
-A
_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user
