Hi Marcus,

Marcus Roth wrote:
>> 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.

I would be ok with these things that are mainly a few additions to 
fcdEdit, as those can be auto-generated for 90% of the code (you'd have 
to add them manually for the few base types like FC, Node and NodeCore).

I just want to avoid spending a lot of dev time on back-porting things 
from 2 to 1. I'd rather have people spend time on porting stuff form 1 
to 2. ;)

Feel free to add them, I won't have the time anytime soon.

Yours

        Dirk



-------------------------------------------------------------------------
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