While writing my first RIFE application, I found myself writing too much configuration. I know all the arguments in favor of the verbose site structure declaration, but sometimes I feel I'm entering too much redundant information. Why not apply some defaults:
1) If an element has a declared <exit>, try to automatically link it to an element with the same name: Element declaration: <element implementation="test.Input"> <exit name="output"/> </element> Site declaration: <element id="input" file="input.xml"> <flowlink srcexit="output" destid="output"/> <!-- this seems sooo redundant to me --> </element> 2) The same goes for datalinks: if there's a flowlink between two elements (declared explicitly or as suggested above, why not automatically link the source element outputs with destination element inputs with the same name? Element declarations: <element implementation="test.Source"> <output name="id"/> <output name="name"/> <exit name="destination"/> </element> <element implementation="test.Destination"> <input name="id"/> <input name="name"/> </element> Site declaration: <element file="source.xml"> <flowlink srcexit="destination" destid="destination"/> <!-- duh --> <datalink srcoutput="id" destid="destination" destinput="id"/> <!-- say again? --> <datalink srcoutput="name" destid="destination" destinput="name"/> <!-- I kenna hear ya! --> </element> Just think how much cleaner these declarations above would be if flowlinks and datalinks were "autowired" based on naming conventions. Please notice that we're not losing track of the site structure: the inputs, outputs and exits are still declared -- it's just their links that would be automatically wired. -- Marcus Brito _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
