Pat, On 9/30/07, Pat Cappelaere <[EMAIL PROTECTED]> wrote: > > It could be done in a custom participant but it could not be done by an end > user at the graphical interface level. This is where I am going with this. > I need more generic participants that can be generically wired or have the > capability to transform/aggregate their outputs.
As already said, CsvParticipants are available for that. The interface is google docs, publishing as CSV and here we go. There is thus a transformation description format (CSV) and a designing interface (a spreadsheet). That said, if you want to have something more point-and-clicky, isn't it in the scope of your Matelot project ? I find CSV adapted as a support for transformation descriptions, of course nothing beats ruby custom participants (although CsvParticipant understands embedded ruby snippets). What format / description type would you propose ? Such transformation participants testing can easily be automated. Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-dev?hl=en -~----------~----~----~----~------~----~------~--~---
