I think that you could make a static function on the module profile in the main app, this way the code will call it instance of the "sfContext::getInstance()->getController()", probably you have to instanciate the action, since the calls must go from one app to the other. In that case may be required that the action/module live in the plugin, since it looks like theres no way to add a common module to apps in the same project (unless you could generate the output without the action).
On 7/24/07, Ian P. Christian <[EMAIL PROTECTED]> wrote: > Matthias Nothhaft wrote: > > If working with "application independent" stuff I always put it into a > > plugin. This way I can use it within each application. > > > > Whilst it might be application independent, it certainly depends on the > project. Creating a plugin seems like a lot of work to have a bit of > code working from 2 apps in the same project - is that really the > easiest way? > > -- > Ian P. Christian ~ http://pookey.co.uk > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
