Re: [Gitclipse-devel] Wizards vs Dialogs

[Michelle S O. <ms...@ny...>]

There's nothing requiring you to create a 'page'. You can put all of your code into the dialog class if you like. I think I did this first, and I did it because I was copying an example from the Clearcase plugin. It seemed nice to separate most of the widget-related code from the actions taken when OK or Cancel are pressed, but it's in no way mandatory.

----- Original Message -----
From: Patrick Winters <pat...@ny...>
Date: Thursday, July 17, 2008 5:14 pm
Subject: [Gitclipse-devel] Wizards vs Dialogs
To: Gitclipse Devel <git...@li...>


> Hey All,
>   I thought a bit about why we should be using Wizards instead of Dialogs.
> Firstly, the claim was made that Dialogs are easier because we don't have
> multiple pages to begin with.  Looking at every dialog committed into 
> the
> repository so far, each one has an associated page.  Each page or part 
> is
> not using any interface or base class and is being implemented in its 
> own
> way everytime.
>   If we need to implement pages and parts to build a dialog, then we should
> just use the Wizard interface and benefit from the Page base classes.  
> There
> is no difference in code amount, and it simplifies things.
> --
> Patrick
> 
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great 
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the 
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Gitclipse-devel mailing list
> Git...@li...
> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel