[Columba-devel] =?iso-8859-1?Q?[Columba-devel]_Re:_wizard_code_in_thincolumba?=

[<fre...@we...>]

> Hi, 
>  
> > I was a bit surprised finding a new dependency in ThinColumba, its needs 
> > jwizz to compile. I fixed the build.xml file shipped with the plugin 
> > to make this work, but this is just a hack until this is solved correctly.
> 
>  
> This is a misunderstanding: ThinColumba doesn't depend on jwizz, it is just
> one single 
> class I added some time ago that extends the ThinColumba L&F while
> specifying jwizz' 
> behaviour. ThinWizardContentPaneUI does not depend on ThinColumba and
> shouldn't be 
> shipped with ThinColumba so you can safely remove that class from the plugin
> thereby 
> making it independent of jwizz. 

I just meant you need jwizz in order to compile ThinColumba. This makes
it a dependency. 


>  
> I cannot agree to the latter fact - jwizz was designed to be highly flexible
> and customizable 
> and therefore should seamlessly integrate with different L&Fs. jwizz does
> not need to have 
> ThinWizardContentPaneUI, this class was intended to keep a consistent L&F
> for the wizard 
> component throughout different L&Fs (specifically button layout and step
> description 
> component). Thus by changing of L&Fs the wizard should not be affected. I
> thought you 
> would like to keep it consistent. Actually there is no need for UI delegate
> overrides if you 
> do not expecitely force jwizz to look the same with different UIs. Proposed
> solution: 
> remove ThinWizardContentPaneUI and remove the class name from the defaults
> table in 
> ThinColumbaLookAndFeel. If you still want jwizz to be consistent you can
> easily achieve 
> this by signaling UIManager which WizardContentPaneUI implementation to use.
> 

What are those inconsistencies? A Look and Feel shouldn't change the button
layout or step description. 

Sure, I want a consistent looking Columba ;-)

Cheers,
Frederik