Am Donnerstag, 17. August 2006 13:21 schrieb Philipp Bracher:
> > And finally how did you get your bit of javascript code loaded up  
> > as you
> > access your custom tree view?  My tree is brought up by a menu item  
> > I set up
>
> The cool thing in magnolia 3.0 is that all js files in the resources  
> under js-classes are loaded by default.
>

I did just track this down in:
info.magnolia.module.admininterface.pages.JavascriptIncludePage

Then I added my js file to my module under mgnl-resources/js-classes 
directory, and it is loaded up with the rest of the contents 
of  /magnolia/.magnolia/pages/javascript.js.  So I am halfway there.

> You can see this in the adminInterface module or in the DMS if you like.
>
> > with a call to MgnlAdminCentral.showTree('luxoom-jcr');  Looking at  
> > that code
> > I didn't see how to get my tree related javascript loaded up as  
> > well.  I can
>
> See the answer above. If you need to load other things you will be  
> able to do it by subclassing the tree handler.

I think the other method will work well enough to get the javascript in place.  
But  now that I look further at the AdminTreeMVCHandler, I wonder if I should 
be extending the command handling for my subclass of the AdminTreeMVCHandler?

>
> > certainly toss it in somewhere, but wonder if there is an intended  
> > point of
> > integration I should be using?
>
> Hope will help

Okay, I have just upgraded to Hope 2.0, but I wonder if that is compatible 
with the current release candidate...hmmm.  Probably doesn't matter, I have 
also had much success relying on the Luck 4.x, and Imagination 2.x debug 
tool-set integrations as well.

Cheers,
Chris

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to