[Bf-committers] ActiveX code rewrite (or request for creating a branch)

[Ton Roosendaal]

Hi,

> (by Roger Wickes)
> If the Blender Foundation has an active certificate, they could sign  
> the plug-in when it is released, which would solve the IE Security  
> requirement.

I'm extremely reluctant to go into this. I'd still rather see a third  
party picking it up, and turn into a business model with support,  
security, signed/locked/trusted content, and also accepting the  
responsibility. A public web player is really a big step... not  
realistic to handle for a volunteer-based organization, and not  
something I have time or energy for to manage here (via Foundation or  
Institute).

-Ton-

------------------------------------------------------------------------
Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute BV  Entrepotdok 57A  1018AD Amsterdam The Netherlands

On 25 Nov, 2008, at 16:39, Roger Wickes wrote:

>  
> ----------------
> Sent by Roger Wickes for intended recipient. If you are not the  
> intended recipient, please delete this message and contact Mr. Wickes  
> immediately.
>
> Atlantica Investments, Inc.
> PO Box 680310, Marietta, GA 30068 USA
>
>
> From: Marcelo Coraça de Freitas <mfreitas at ydeasolutions.com.br>
> To:  bf-committers at blender.org
> Sent: Tuesday, November 25, 2008 9:08:21 AM
> Subject: [Bf-committers] ActiveX code rewrite (or request for creating  
> a branch)
>
>  Hello there,
>
>      I've just received dev rights in subversion (WOOT! And thanks for  
> the trust! Honestly! <unknown.png>). Time to start using it.  
> <unknown.png>
>
>      I've rewritten the ActiveX code from scratch for the web plugin.  
> There are some limitations so far and it's not quite ready for use  
> (mainly because it requires you to turn your security settings in  
> internet explorer off to use the plugin in web pages <unknown.png>)  
> but I'd like to put it in the subversion somewhere so the blender  
> family can keep track on the changes.
>
>      So far I'm using our own (Ydea's) subversion as it's a completely  
> independent code, but it depends on some changes in other areas of  
> blender code (GPG_ghost, GPG_Application, GHOST_SystemWin32 and  
> GHOST_WindowWin32 and some python packages).
>
>      The plugin works fine thought (  
> http://www.youtube.com/watch?v=-A_3bVONgSY ).
>
>      I'm in doubt in where to put this code. Wouldn't a branch be more  
> appropriated?
>
>      Putting it in trunk would require not only those patches to be  
> reviewed as some more patches as well (I know I'll have to change  
> GPG_ghost again so I can remove that security issue). We will also  
> require some major changes to allow scripting (both in Linux and  
> Windows plugins). We'll require IPC for that and we've even though  
> about using dbus (yes, in both platforms).
>
>      There is no code for OS X yet, but I believe those will also  
> require some changes in other blender modules.
>
>      A branch would give us more flexibility to change things across  
> the blender source in order to implement everything needed for the  
> plugin to work (it's a quite big project). Other benefit of the branch  
> is that, as it's insecure code for now, we wouldn't infect blender's  
> trunk with insecure code.
>
>      Btw: in #blendercoders most devs seems to agree that the branch  
> is the best option. And I tend to agree.
>
>      If the branch gets approved, may I create it? <unknown.png>
>
>      Suggested branch name: webplugin.
>
>
>  Regards,
>
> <unknown.jpg>
>
> Marcelo Coraça de Freitas
> Gerente de TI
>
> Ydea Desenvolvimento de Software LTDA.
> Av. Adolfo Pinheiro, 2338 - Alto da Boa Vista
> CEP.:04734-004 - São Paulo - SP
> Tel.: 55-11-5523-0333
> Tel.: 55-11-8685-1429
>
> <stock_smiley-1.png><stock_smiley-3.png><stock_smiley 
> -6.png><ydea.jpg>_______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers