Re: CvsAlert changes adjustment

Karl,

>Sometime ago you told me to give it a try and I did it. I think I will
>add a branch for further merges and put it into HEAD later. I think
>there should be higher kind of framework based on our rf framework.

Or we need to find third-party framework ;)

We might give something like wxWindows a try later on, but at this stage I
don't want to mess with the frameworks. I want the stable release out ASAP
;)

One problem with putting a lot of conditional compilations is that
ClassWizard gets confused and it makes work quite impossible. The code that
is close to the GUI level can't be merged too well at the moment which is
why I tend to move the "business logic" to separate classes rather than
trying to merge the GUI dialog classes. If the whole classes are separated
it's not a problem but if the definitions are intersected it is unable to
resolve the conditions and I loose a lot of IDE support.

Moreover, the Alert dialog uses some tricks to make the dialog size properly
and look nice as opposed to command dialogs where we only add functionality
to control commands parameters. For the commands we have the funtions to
interface but for the sake of simplicity of use the Alert is using CvsAlert
class and CvsAlert::ShowAlert method instead. It's an exception and it will
not merge nicely.

Best Regards,
Jerzy


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/