[Gambas-devel] Copying forms

[Robert Rowe]

I would agree the copying is generally bad. Visual inheritance is the 
way to go. Visual inheritance can be rather tricky to implement though 
so as long as someone doesn't go overkill then some limited copying 
shouldn't be harmful as long as core functionality is in a class that 
both forms utilize.

This reminds me of something. FTextEditor has the same editor splitting 
capabilities as FEditor does so I'll need to make the same fixes to it 
that you made to FEditor. You said that you wanted to make some more 
changes to the code though so I'll wait until you have FEditor in it's 
final form.

I guess I'll table the copy idea for now as there is another way to 
accomplish it. I was just trying to keep the interface consistent. I'll 
move on to my next item.

Robert Rowe

Benoit Minisini wrote:
> On dimanche 23 mars 2008, Robert Rowe wrote:
>   
>> The intent of this feature was not to have the same form in a project
>> twice. Rather it is to assist the creation of new forms that are similar
>> to an existing form. A perfect example of where this comes in handy
>> would be the FTextEditor and the FEditor forms. FEditor has everything
>> from FTextEditor plus more so FTextEditor could have been written then
>> copied to FEditor for further modification. I know now that this can be
>> accomplished via the "new form" dialog. I'll pass this information on to
>> Richard (he's the one who requested the feature). I still think that
>> implementing this via the popup menu is more intuitive but it's okay if
>> you feel differently.
>>
>> Robert Rowe
>>
>>     
>
> Actually copying is a bad thing, and the example you took just show that 
> FTextEditor and FEditor were badly designed, as they have many common code 
> that is not factorized. :-)
>
> But if you really want, you can implement this feature. Just tell me, because 
> there are a few modifications to do in the Project class first - The methods 
> already exist, they just need to take that new way of creating forms (and 
> modules, and classes...) into account.
>
> Regards,
>
>