Community
Participate
Working Groups
After writing yet another simple command handler to simply indirect to a method on a part, which requires (1) creating a handler class to get and check the active part, (2) hooking the handler in the .e4xmi, and (3) possibly importing the command if in a fragment.e4xmi, I'm convinced that the DI should be able to do better. Taking inspiration from sitebricks, which provides a simplified approach for mapping methods to REST-style actions [1], I propose that DI should automatically wire up handlers to methods with a @Command("commandId") annotation. I haven't a scooby how to implement this yet, but that's merely a matter of time. But I'd appreciate any pointers. [1] http://code.google.com/p/google-sitebricks/wiki/GettingStarted#My_First_Web_Page
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. --
