[ http://jira.andromda.org/browse/AAAA-25?page=comments#action_13900 ]
Thorsten Pohl commented on AAAA-25: ----------------------------------- My Ideas: I think long running operations would typically be created and run within a workflow, so that this workflow could be a good candidate for a progress context. In this way we would have at least two levels of progress: + One would be the workflow that triggers other plugins to perfom a given number of steps + and the other the plugins actually perfoming these steps. I am not sure, if it is useful for the plug-ins to structure their own tasks in a hierachy themselves in a way that the progresses can be split into subprogresses. Do you have any thoughts about this? > Think about communication infrastructure between plug-ins and runners > --------------------------------------------------------------------- > > Key: AAAA-25 > URL: http://jira.andromda.org/browse/AAAA-25 > Project: AndroMDA 4 > Type: Task > Components: Technical utilities > Reporter: Peter Friese > Assignee: Matthias Bohlen > > In order to be able to provide meaningful feedback to users during long > running operations, we should think about a communication channel for sending > progress information. > For A3, Chad and I once discussed using some special kind of Log4J appender > to grab the log messages being issued by the various parts of AndroMDA. > However, I'd like to have a dedicated communication channel in A4 that's > designed by purpose. > Here are my ideas: > a) provide an interface IProgress with methods beginTask(String message, int > overalAmount) and worked(int amount). Plug-ins that implement this interface > can easily call these methods to send their progress info to the AndroMDA > engine. The AndroMDA engine should then provide an extension point > "progressProvider" that can be implemented by some other plug-ins. These > plug-ins can then grab those progress messages and display them appropriately > for the respective frontend technology (Eclipse / Maven / cmdline). > b) Provide an API that plug-ins can use to create a progress context in which > they can send progress message just like in option (a). The distribution of > the progress information would then be handled in the way described above. > Any other thoughts? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.andromda.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
