Changes between Initial Version and Version 1 of Ticket #13605, comment 22


Ignore:
Timestamp:
01/30/13 05:18:26 (8 years ago)
Author:
andrew.mathas
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13605, comment 22

    initial v1  
    2020 This has the advantage that you could check generically to see whether an option was a valid option by checking hasattr(self,'_latex_'+self.options['latex']) when the option is changed.
    2121
    22 The reason that I care about this is that I have a class which wants to use particular TeX and display options for partitions -- namely, a class for displaying matrices which which have rows and columns indexed by particular partitions. As it is currently written, the only way that ,y class will able to access the latex methods it wants is by playing silly games with partition_options. As partitions and tableaux are widely used as indices I would think that there will be other examples eventually.
     22The reason that I care about this is that I have a class which wants to use particular TeX and display options for partitions -- namely, a class for displaying matrices which which have rows and columns indexed by particular partitions. As it is currently written, the only way that my class will able to access the latex methods it wants is by playing silly games with partition_options. As partitions and tableaux are widely used as indices I would think that there will be other examples eventually.
    2323
    2424A second point, as above, I think that none of the "option clients" should ever access partition_options and tableau_options directly. Rather, they should call self.options() or self.parent().options() to do this.