Thanks for your reply. I'm able to wire up the event easily enough:
protected void lbutton1_Command(object sender, CommandEventArgs e)
string s = e.CommandArgument.ToString();
But that doesn't really get me where I was hoping. When I make a user control for the front-end, obviously Sitefinity is taking care of all the background work and I just need to add the appropriate attributes to my property to specify which WebEditor to use. In the case of a back-end module, though, it's easy enough to know that a user wants to see a specific dialogue (for example CmsUrlWebEditor) via the CommandArgument, but I still don't really see a straight-forward way to make that window 'popup' once the initial postback (that determines which action to take) is finished, and then collect the response when the user is done with the dialogue (presumably after another postback)? How do I bring the WebEditor up in server-side code?
If you could point me to an example of existing code within Sitefinity, perhaps if I can see an example of how you did this yourself and it would make more sense to me. The alternative is I can make a custom view, redirect to that, and then come back to the source view ... but that's reinventing the wheel when you've already done a great job yourself with your existing editors.