Dirk Reiners wrote:
>     Hi Johannes,
>
> Johannes Behr wrote:
>   
>> Well, some "old" programs are quite big and cannot ported easily
>> to 2.0, especially since 2.0 is still a moving target. We cannot
>> force the developer to use 2.0 right now. Some would like
>> to use 2.0 as basis to try new things and some
>> would like to stay with a stable version.
>>   
>>     
...
> Hm, I don't know if that's a sensible goal. My idea was that people 
> should stay on 1.X until 2.x has acceptable stability and then port, and 
> making that port quick and as painless as possible. Being able to use 
> both will make the program complicated.
>   
Systems are getting stable, if they are used seriously. So it would be 
great, if we could compile Avalon with 1.8 and 2.0
with as less IFDEFs as possible. Additionlly we are forced to port 
avalon to 2.0 because we need to compile it on WindowsCE.

I think there are some interface changes that can be portet to 1.6 very 
easy. For example the FieldContainer access methods.

For example the set methods for MFFieldContainer fields have changed a lot.

1.6
viewport->getForgrounds().clear();
viewport->getForgrounds().push_back(myForeground);
2.0
viewport->clearForegrounds();
viewport->addForeground(myForeground xx);

The following methods can easily be generated with the fcdEdit in 1.8

    void addForeground           (ForegroundPtrConstArg value   );
    void insertIntoForegrounds      (UInt32                uiIndex,
                                    ForegroundPtrConstArg value   );
    void replaceInForegrounds  (UInt32                uiIndex,
                                    ForegroundPtrConstArg value   );
    void replaceInForegrounds (ForegroundPtrConstArg pOldElem,
                                    ForegroundPtrConstArg pNewElem);
    void removeFromForegrounds (UInt32                uiIndex );
    void removeFromForegrounds(ForegroundPtrConstArg value   );
    void clearForegrounds            (void                          );

by the way, it would be nice to have a copy method to do
viewport1->getForegrounds() = viewport2->getForegrounds()
something like
viewport->setForegrounds(MFForegrounds &fg);


I dont't think that 1.8 sould be fully compatible with 2.0 but if it 
causes not a lot of work, we should
reduce the cases where an IFDEF if needed.

Marcus








-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core

Reply via email to