Assigning to Nathan, because the script is similar to rf.fi, he agreed to look at it next week or so

[canned response]

Hi, can you prepare a wiki page with a bit of a manual about how to
use this? It surely would help the review process :)

See
http://wiki.blender.org/index.php/Dev:2.5/Py/Scripts/Guidelines/Addons

Thanks!

Hello,
Because we have a new stable release of blender 2.5 we are starting with a new plugin to support rendering in RenderFlow.

I will upload a new RenderFlow plugin version. As you can see, I have structured the source code in several packages and files.

By now, the plugin does the work, but still not active on our renderfarm so you can not launch scenes to RenderFlow. I hope you can test it on a couple of weeks.

The plugin

Thanks, I've put it on my todo list for this week!

Now this version is supported in RenderFlow, We are starting with the tests...
You need to decompress it into 2.57/scripts/addons

Fixed the path name

Some remarks:

1) tooltips for input fields should be added, just their RNA-level name is not very obvious what one should input there. If there are system limits (on the render farm or for the uploader) on those input fields, make sure the user can find info about that (preferably in tool tip)

2) The wiki page is empty, a good overview of what it does and what the dependencies are (java web start)

3) remove unnecessary prints from the system, perhaps also remove the old cmdline for instance (OperatorRender.py).

4) a backup file exists in the zip

5) what does the uploader.jnlp really do? From this addon code it looks like it would take the config and from that whatever is found, but it's rather opaque, so hard to say. If this plugin gets included with this upload mechanism, I think it's good to have a warning icon shown, because this is a part that we can't verify: a software that is downloaded to the user machine, and that then uploads some files.

Please take the above points into consideration. To Luca, since the plugin downloads external software upon operation, I think that 1) the warning icon is important for addon browser and 2) this plugin fits into the contrib section.

Forgot to add the note that I didn't try an upload with the system, because I don't know what the uploader will do, and without seeing the code it's hard to say if this is a robust piece. Next to that it's hard to trust if one doesn't know what it really will do.

Updated remarks 1) 3) and 4)

I will have a wiki page tomorrow, I hope. It will include explanation about use and how it works.

Now you can review the wiki page.

Please, could you tell us how can we improve our addon to be included into the release section?

Added the warning icon

Hi, any advance about this?

Hi,
Just a Reminder for people to Join the Mail List.
If you have not already, please visit this page:
http://lists.blender.org/mailman/listinfo/bf-extensions-cvs
& join the list.

Hi,
Due to changes to the api including the merging of bmesh, several addons are outdated.
Please, if you are the author of an addon check your script with blender revision 44256 or newer.
That is builds made After blender 2.62 official release.
I would ask that updates be made to your addon before the Blender 2.63 release.
6-8 weeks away.
This allows time for the api to become more exposed & bmesh to stablize furthur.
If you need help, drop into irc freenode #blenderpython or #blendercoders & feel welcome to ask questions.
At the time of 2.63 release, scripts that are not repaired or in active developement will have their tracker page marked "Closed"
this will not affect your links to the tracker, similar to closing scripts in 2.49b, the page will be still availible & can be re-opened.

Thanks for your understanding & patience during these Exciting Times.
Brendon.

hi, any status updates for this?

Hi,

About blender rev 44256, we are still making some tests and soon we can confirm that our addon is compatible with it. But our main interest is to know what possibilities we have that our plugin will be included in the next blender release.

Since we asked for the integration we have worked on several topics in order to increase the performance and create new features for Blender so that it can be used in large, professional projects.

We are developing the following features (still in beta phase):

1. Support for the use of linked libraries in the scene.
2. Reuse of textures to minimise the file size for the upload.
3. Support for Cycles with CPU , to avoid GPU memory limitations.
4. Cycles with GPU support in our new nodes that dispose of 3 Cuda per node.
5. The creation of particles´ cache at the farm to avoid that the client has to process and upload it. (still under development).

Our wikipage is outdated but the main/basic concepts are still valid.
http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Render/renderflow

We have released the python code as GPL, (we can provide a scm or use one from blender.org) but at this time we cannot do the same with the uploader. We will have news about the uploader in the future but we need feedback from the community first to take decisions about that.