[udig-devel] Where to process additional menu contributions into uDig?

[Adrian Custer]

Hey Jody,

I don't want to start really reading this thread because I can't focus
exclusively on it right now. Can I assume you are going to write up a
new wiki page that will deprecate the rest once you have decided on a
course of action?

Also, in your assessment please keep in mind that I would really like a
left most menu that is *not* the 'file' menu but, like on the mac, the
'app' menu, ideally with the preferences and update links moved from
their regular eclipse hangouts. Ideally, I would dump the meaningless
'file' and have a menu structure that starts:

  myDig  Catalog Project 

or some such.

--adrian, 
        who now goes off to delete jody's recent spew thankfully
        imagining that this aspect will get properly resolved.

Oh, and I am willing anytime to be your documentation guinea pig since
this is something I hope gets resolved correctly for everyone.



On Mon, 2007-10-29 at 23:09 -0700, Jody Garnett wrote:
> My problem is with the functionality not quite pulling off its goals. 
> Both of these extension points require specific hooks into an 
> applications WorkbenchWindowAdvisor.
> 
> Jesse Eichar wrote:
> > That's not totally accurate.  At one of the extension, if not both, 
> > follow the Keyboard configuration pattern which chooses the extension 
> > defined in the preferences.  The default can be set in a ini file 
> > indicated by the product.  This was not a mistake.
> So we can specify the override in an product ini file; suppose we best 
> hunt down an example.
> 
> For an example of this kind of thing done "right" consider, this can be 
> reused in any RCP application:
> > UDIGDragDropUtilities.registerUDigDND(configurer);
> I can see this approach making sense for the WorkbenchConfigurations (as 
> long as it is documented as specificly for UDIGWorkbenchWindowAdvisor). 
> For the UDIGMenuBuilder this approach does not make sense; and the a 
> normal RCP application will not be able to play with this just based on 
> an extention point (it will need to make use a code snippet in its 
> WorkBenchWindowAdvisor).
> 
> Jody
> >
> > Jesse
> >
> > On Oct 29, 2007, at 8:28 PM, Jody Garnett wrote:
> >
> >> I have found several attempts at implementing the following story 
> >> "use the UDIGApplication but let me change some stuff" ...
> >> - 
> >> http://udig.refractions.net/confluence/display/DEV/Using+UDIGMenuBuilder
> >> - 
> >> http://udig.refractions.net/confluence/display/DEV/Using+WorkbenchConfigurations 
> >>
> >>
> >> Both of these attempts try to override the default behavior of 
> >> UDIGWorkbenchAdvisor (ie the main reason you would implement your own 
> >> RCP Application). UDIGMenuBuilder has the added goal of letting an 
> >> RCP developer "mix in" UDIG menu contributions to there existing 
> >> application.
> >>
> >> In reviewing this code I found that:
> >> - both extentions only engage when a contribution is found; a single 
> >> contribution at that
> >> - if no contribution was found they would use an internal default
> >> - both extentions had a single contribution provided as part of the 
> >> udig.ui plugin set to the internal default
> >>
> >> So I can only conclude that these ideas were broken; plugin order 
> >> would cause the internal default to be picked up semi randomly.
> >>
> >> My guess is both of these hacks are quick fixes, documenting how to 
> >> make your own RCP Application would of been less pain, less code, and 
> >> less crazy. But at least for now there are some docs.
> >>
> >> Cheers,
> >> Jody
> >> _______________________________________________
> >> User-friendly Desktop Internet GIS (uDig)
> >> http://udig.refractions.net
> >> http://lists.refractions.net/mailman/listinfo/udig-devel
> >
> > _______________________________________________
> > User-friendly Desktop Internet GIS (uDig)
> > http://udig.refractions.net
> > http://lists.refractions.net/mailman/listinfo/udig-devel
> 
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel