TheBounty Renderer (rewrite for wxWidgets)

[povmaniac]

Forget you 'thebounty_0.1.6_rc4_win64.7z', is an old version. Use only the file mark on the image above. This file include last binaries and wings3d exporter.

[micheus]

Use only the file mark on the image above. This file include last binaries and wings3d exporter.

No, it doesn't! The is only wpc_thebounty.beam inside that zip you linked.
That is why I download the "old" file too.

[oort]

Micheus is right.

Here is a link to the download link for the newer version of The Bounty. I copied it from one of the earlier posts.

Download latest version of The Bounty

oort

[micheus]

Thanks oort.

[povmaniac]

Ohh! Sorry, my fault ( Going to fix!!)

[povmaniac]

Hi.. new User interface first step: load xml scene file and launch render to console.



Back to code!!

[povmaniac]

A question for Micheus / dgud
I am preparing my repository to create a pull request to the 'master' and wonder if I can maintain my current design of the code. To move wpc_thebounty.erl to the folder 'import_export' and the rest of the code in 'import_export/thebounty' due to the number of files (15), and like that to keep the folder clean 'import_export'. What seems to them? Is it a good idea? Or does it alter very much the current design of the code?
But please, do not ask me to place the whole code in only one file .erl.

Greetings..

[micheus]

A question for Micheus / dgud

It's for Dan, for sure.

[dgud]

Is that erlang code?

I really don't want any other code (or rather anymore dependencies) to wings, in that case it is better as a standalone download.

[povmaniac]

Oh not. The code of the image of above, it is for TheBounty standalone, substituting the current Qt, for the same motive of not adding dependencies on my project.
My question refers to the Erlang code of TheBounty exporter. ( See the github repo..)