|
Yes, I considered that
means of markup, but it didn't produce the result I was looking for in
the front-ends I was targeting, which is why I went for the level="4"
attribute. This is one of the tensions with XML--function is favored
over form, leaving the form up to the engine's filters or front-end
filters rather than the module developer. This is probably opening a low-priority can of worms, but what if some controls on the form a module is displayed in were encoded in the conf file? I mean, you could define how certain attributes should be displayed to give module developers more control over how their modules display. Otherwise the filters have to come up with a standard implementation that may or may not match the publisher's intention. Just a thought. I realize that may be creating more work than it's worth, but it might solve the tension that currently exists between form and function. Ideally "selah" should be tagged as the standard suggests, but if that means sacrificing form as a module developer I am reluctant to do that. If I can achieve form without sacrificing the essential function, I'll do it. If the module developer didn't have to make that sacrifice and could produce good OSIS markup, that would be my ideal. Daniel Chris Little wrote:
|
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
