On Monday 21 April 2008, Bogdan-Andrei Iancu wrote: > Hi Dan, > > So far it was about displaying information regarding dialogs and > additional context - no other kind of ops. > > I think the main issue is about the "generic" & "low level" support > offered by dialog module and if the dialog module shold be aware and do > some something for the modules on top of it.
While I agree with that the low level module should not depend on the high level module (that being the primary reason I raised the issue in the beginning), I do not see a big issue if the top modules only provide some information formatted in a standard way for display purposes. > I find it non-logical to have dialog module displaying info it does not > keep and it does not understand, data form this upper modules ( the > dialog context). I do not think it has any issue understanding it, since it doesn't have to know anything about the upper module and its context. It only receives a name and an associated value which is a MI node list tree, which it understands very well as long as it only has to display it under the given name. Anyway, the issue as I see it is wether to query for and display all the dialog related information together in single request, or by querying for each piece separately from a different module with a different command. I would personally prefer to have all dialog related info (including the one from the upper modules) displayed in a single place with a single command, rather than having to make N queries in N modules. -- Dan _______________________________________________ Devel mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/devel
