From yomgui1 at gmail.com Wed Nov 16 15:11:48 2005 From: yomgui1 at gmail.com (Yomgui) Date: Wed Nov 16 14:49:56 2005 Subject: [tuhopuu-devel] New platform to support, new layer to append to blender Message-ID: <73ed309e0511160611y59c66cd4gc5b0ec337b9e5a88@mail.gmail.com> Hello everyone, I've made a port of blender 2.37a for platform MorphOS (check the wikipedia for MorphOS). But to bring it into the official tree on CVS I need to modify in deep blender to append a new layer: an OSAL (OS Abstraction Layer). This layer will be in charge to bring all functions that communicate directly with the OS, like open/close, memory handling, task, etc... I've seen in the current release of blender that differences between platforms, especially for Windows paths handling, are handled in too many sections of code. The issue of that is many identical and redundant code every where. On my platform (MorphOS), I've an identical issue with paths construction. So to resolve any issues in future, I want to bring my acknowledges about such layer into blender. To do that, my idea is to test the layer into the tuhopuu project first, so what is the process ? Should I need to have an account as developer for tuhuppo-CVS? or just send to you (who exactly ??) a diff file? Regards, Guillaume R. From cwant at ualberta.ca Wed Nov 16 17:38:29 2005 From: cwant at ualberta.ca (Chris Want) Date: Wed Nov 16 17:16:37 2005 Subject: [tuhopuu-devel] New platform to support, new layer to append to blender In-Reply-To: <73ed309e0511160611y59c66cd4gc5b0ec337b9e5a88@mail.gmail.com> References: <73ed309e0511160611y59c66cd4gc5b0ec337b9e5a88@mail.gmail.com> Message-ID: <437B6085.1010003@ualberta.ca> Hi Guillaume, The tuhopuu project is dead, and I think your efforts would be better spend preparing and submitting a patch for the official tree. You should probably submit the patch a couple of weeks after the official release of 2.40, so that you aren't caught in a period of feature freeze. Regards, Chris Yomgui wrote: > Hello everyone, > > I've made a port of blender 2.37a for platform MorphOS (check the > wikipedia for MorphOS). > But to bring it into the official tree on CVS I need to modify in deep > blender to append a new layer: an OSAL (OS Abstraction Layer). > > This layer will be in charge to bring all functions that communicate > directly with the OS, like open/close, memory handling, task, etc... > > I've seen in the current release of blender that differences between > platforms, especially for Windows paths handling, are handled in too > many sections of code. The issue of that is many identical and > redundant code every where. > > On my platform (MorphOS), I've an identical issue with paths > construction. So to resolve any issues in future, I want to bring my > acknowledges about such layer into blender. > > To do that, my idea is to test the layer into the tuhopuu project > first, so what is the process ? > Should I need to have an account as developer for tuhuppo-CVS? or just > send to you (who exactly ??) a diff file? > > Regards, > Guillaume R. > _______________________________________________ > tuhopuu-devel mailing list > tuhopuu-devel@projects.blender.org > http://projects.blender.org/mailman/listinfo/tuhopuu-devel > From yomgui1 at gmail.com Wed Nov 16 17:47:37 2005 From: yomgui1 at gmail.com (Yomgui) Date: Wed Nov 16 17:25:43 2005 Subject: [tuhopuu-devel] New platform to support, new layer to append to blender In-Reply-To: <437B6085.1010003@ualberta.ca> References: <73ed309e0511160611y59c66cd4gc5b0ec337b9e5a88@mail.gmail.com> <437B6085.1010003@ualberta.ca> Message-ID: <73ed309e0511160847uf1ea6e9m1e397b1cd9b7064b@mail.gmail.com> tuhopuu project is dead !? oh... blender web site needs to be updated so ! ;-) ok, I'll do that. I've not started the layer, so I can wait :-) Thanks Chris! On 11/16/05, Chris Want wrote: > > Hi Guillaume, > > The tuhopuu project is dead, and I think your efforts would be > better spend preparing and submitting a patch for the official > tree. You should probably submit the patch a couple of weeks > after the official release of 2.40, so that you aren't caught > in a period of feature freeze. > > Regards, > Chris > > Yomgui wrote: > > Hello everyone, > > > > I've made a port of blender 2.37a for platform MorphOS (check the > > wikipedia for MorphOS). > > But to bring it into the official tree on CVS I need to modify in deep > > blender to append a new layer: an OSAL (OS Abstraction Layer). > > > > This layer will be in charge to bring all functions that communicate > > directly with the OS, like open/close, memory handling, task, etc... > > > > I've seen in the current release of blender that differences between > > platforms, especially for Windows paths handling, are handled in too > > many sections of code. The issue of that is many identical and > > redundant code every where. > > > > On my platform (MorphOS), I've an identical issue with paths > > construction. So to resolve any issues in future, I want to bring my > > acknowledges about such layer into blender. > > > > To do that, my idea is to test the layer into the tuhopuu project > > first, so what is the process ? > > Should I need to have an account as developer for tuhuppo-CVS? or just > > send to you (who exactly ??) a diff file? > > > > Regards, > > Guillaume R. > > _______________________________________________ > > tuhopuu-devel mailing list > > tuhopuu-devel@projects.blender.org > > http://projects.blender.org/mailman/listinfo/tuhopuu-devel > > > _______________________________________________ > tuhopuu-devel mailing list > tuhopuu-devel@projects.blender.org > http://projects.blender.org/mailman/listinfo/tuhopuu-devel > From mal at candomultimedia.com Wed Nov 16 17:55:12 2005 From: mal at candomultimedia.com (Mal) Date: Wed Nov 16 17:33:18 2005 Subject: [tuhopuu-devel] New platform to support, new layer to append to blender In-Reply-To: <73ed309e0511160847uf1ea6e9m1e397b1cd9b7064b@mail.gmail.com> References: <73ed309e0511160611y59c66cd4gc5b0ec337b9e5a88@mail.gmail.com> <437B6085.1010003@ualberta.ca> <73ed309e0511160847uf1ea6e9m1e397b1cd9b7064b@mail.gmail.com> Message-ID: <437B6470.9050600@candomultimedia.com> Is there not going to be a new Tuhopuu project, when 2.40 has been released? It has been an excellent way of allowing new coders to sandbox ideas, and have users try them out. Regards... Mal >tuhopuu project is dead !? oh... blender web site needs to be updated so ! ;-) > >ok, I'll do that. I've not started the layer, so I can wait :-) > >Thanks Chris! > >On 11/16/05, Chris Want wrote: > > >>Hi Guillaume, >> >>The tuhopuu project is dead, and I think your efforts would be >>better spend preparing and submitting a patch for the official >>tree. You should probably submit the patch a couple of weeks >>after the official release of 2.40, so that you aren't caught >>in a period of feature freeze. >> >>Regards, >>Chris >> >>Yomgui wrote: >> >> >>>Hello everyone, >>> >>>I've made a port of blender 2.37a for platform MorphOS (check the >>>wikipedia for MorphOS). >>>But to bring it into the official tree on CVS I need to modify in deep >>>blender to append a new layer: an OSAL (OS Abstraction Layer). >>> >>>This layer will be in charge to bring all functions that communicate >>>directly with the OS, like open/close, memory handling, task, etc... >>> >>>I've seen in the current release of blender that differences between >>>platforms, especially for Windows paths handling, are handled in too >>>many sections of code. The issue of that is many identical and >>>redundant code every where. >>> >>>On my platform (MorphOS), I've an identical issue with paths >>>construction. So to resolve any issues in future, I want to bring my >>>acknowledges about such layer into blender. >>> >>>To do that, my idea is to test the layer into the tuhopuu project >>>first, so what is the process ? >>>Should I need to have an account as developer for tuhuppo-CVS? or just >>>send to you (who exactly ??) a diff file? >>> >>>Regards, >>>Guillaume R. >>>_______________________________________________ >>>tuhopuu-devel mailing list >>>tuhopuu-devel@projects.blender.org >>>http://projects.blender.org/mailman/listinfo/tuhopuu-devel >>> >>> >>> >>_______________________________________________ >>tuhopuu-devel mailing list >>tuhopuu-devel@projects.blender.org >>http://projects.blender.org/mailman/listinfo/tuhopuu-devel >> >> >> >_______________________________________________ >tuhopuu-devel mailing list >tuhopuu-devel@projects.blender.org >http://projects.blender.org/mailman/listinfo/tuhopuu-devel > > > From cwant at ualberta.ca Wed Nov 16 18:21:15 2005 From: cwant at ualberta.ca (Chris Want) Date: Wed Nov 16 17:59:22 2005 Subject: [tuhopuu-devel] New platform to support, new layer to append to blender In-Reply-To: <437B6470.9050600@candomultimedia.com> References: <73ed309e0511160611y59c66cd4gc5b0ec337b9e5a88@mail.gmail.com> <437B6085.1010003@ualberta.ca> <73ed309e0511160847uf1ea6e9m1e397b1cd9b7064b@mail.gmail.com> <437B6470.9050600@candomultimedia.com> Message-ID: <437B6A8B.9050803@ualberta.ca> Hi Mal, There are a few problems: 1) I retired from the project and stopped doing merges at the beginning of October; 2) The current tree is so far out of sync that merging it at this point would be a very painful task; 3) Somebody (other than me) is more that welcome to re-fork at 2.40, but to be effective they need to commit to merging the tree regularly (at least once a week), and that process can sometimes take hours if there has been a lot of recent work in either tree. There is some hope for new coders to experiment with their projects: the blender sys admin team are currently looking at switching the blender source repositories from CVS to Subversion (the main nagging issue here is that gforge needs a hefty upgrade for this to work). With subversion there is better control over forking and merging, so new projects can start on branches off of the official bf-blender tree, and these branches can have commit permissions for that dev without granting commit to the main tree -- very nice! Regards, Chris Mal wrote: > Is there not going to be a new Tuhopuu project, when 2.40 has been > released? > > It has been an excellent way of allowing new coders to sandbox ideas, > and have users try them out. > > Regards... > Mal