On 09.01.02 18:54 Paul Hammant <[EMAIL PROTECTED]> wrote: > > Peter, > > I think BlockListener needs : > > void blockStarted( BlockEvent event ); > void blockStopped( BlockEvent event ); > void blockInitialized( BlockEvent event ); > > Thoughts? > > - Paul > Hi,
good idea. I am also using the BlockListener and it really has reduced features if you compare it with a block. The BlockEvent is great (especially the blockAdded method) but I had problems to get a Logger and the ComponentManager. I don't know if you have already fixed that, haven't checked out the cvs for a while. At the moment I am using a dummy block to get a Logger and a BlockContext. Because (in my version) the BlockListener isn't compose-able, so that I wait for a block coming up I need and then just keep the block-object. Then I just have to invoke the requested methods, that's it. Very simpel and it works perfectly. How are the thoughts going on to improve the features of BlockListener? Why not using a normal Block as BlockListener? If that Block is defined as a BlockListener (within assembly.xml), the block is able to get access to the blockAdded, etc. methods? Bye, Holger > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
