Home → Suggestions →

ModuleSignalContext

Toby Street

06 Oct, 2010 04:41 PM via web

Admin Functions

• Edit
• Remove

Guys, I'm still getting to grips with the Robotlegs framework, Signals and a heap of other stuff so please excuse my naivety/confusion.

I've looked at two independent sets of sub-classes for Context, Command, CommandMap, etc. One was the Modular Utility and the other was Signal (which gave me ModuleContext and SignalContext etc). Is there an easy way of combining the two or would that require an additional set of sub-classes? Or is the Modular Utility eventually going to make use of Signals instead of Events anyway?

Just thought it may be useful to combine them. What do you think?

Thanks

1. 2 Posted by Stray on 06 Oct, 2010 05:08 PM

   

   Here's what I do:

       public class ModuleContext extends SignalContext implements IModuleContext

   So compile from source and just hack that in.

   We've talked about finding a way to make 'special contexts' like decorators, or to do it all through bootstrapping. No answers yet.

   For now just hack away - you don't sound naive at all, it's a very valid combination and just not something we've found a neater solution to yet.

   Stray

   Admin Functions

   • Edit
   • Split
   • Remove

2. Support Staff 3 Posted by Joel Hooks on 07 Oct, 2010 07:02 AM

   

   Or is the Modular Utility eventually going to make use of Signals instead of Events anyway?

   Not likely. Stray's approach is what I would do as well.

   Admin Functions

   • Edit
   • Remove

3. Stray closed this discussion on 16 Feb, 2011 09:28 PM.

Comments are currently closed for this discussion. You can start a new one.