General Category > Porting and API

Corona for Rhinoceros :)?

<< < (9/11) > >>

vespista88:
There are lots of people who would love to get it, including myself!!

Buzzz:

--- Quote from: vespista88 on 2018-12-18, 16:27:38 ---There are lots of people who would love to get it, including myself!!

--- End quote ---

Yes!

Any posibility to have Corona for Rhinoceros this year?

FrostKiwi:

--- Quote from: Ondra on 2017-08-10, 11:02:42 ---sorry, no plans to start at the moment...

--- End quote ---

--- Quote from: Ondra on 2017-08-10, 11:02:42 ---start at the moment...

--- End quote ---

--- Quote from: Ondra on 2017-08-10, 11:02:42 ---moment...

--- End quote ---
If there are no plans, then put out a statement that there actually is no intention to look into it.
Logic being: If there is indeed enough interest in the rhino community someone might develop a script to export to corona standalone. If it's left half communicated, it crushes the chance that someone might actually try this daunting task, because maybe the actual devs will do it.

You made the great post explaining why there won't be a blender integration, same for rhino would bring clarity.

TomG:
The thing is there is never "no intention" - there's only "no intention at the moment". We don't have a crystal ball to know how things will go in the future (user interest, finding good developers who want to do this as a project). So we can't say "never an intention". If we say "no intention at the moment" then that would mean it would be at least 2 or 3 months before work could start (assuming the perfect situation of a developer contacts us, wants to join, passes the interview, wants to work on this as a project, joins the company, gets up to speed), and then another 2 or 3 months before something was usable even in early form.

So if a third party developer wants to create an exporter, they know they have quite a large window in which to work if we've said "no intention at the moment". However we just can't say "never" because then if things change and we do decide to work on it, people would complain - and since we really don't mean "never" but just "not at the moment for sure" then we have to be honest and say that :)

Buzzz:

--- Quote from: TomG on 2019-02-25, 14:16:23 ---The thing is there is never "no intention" - there's only "no intention at the moment". We don't have a crystal ball to know how things will go in the future (user interest, finding good developers who want to do this as a project). So we can't say "never an intention". If we say "no intention at the moment" then that would mean it would be at least 2 or 3 months before work could start (assuming the perfect situation of a developer contacts us, wants to join, passes the interview, wants to work on this as a project, joins the company, gets up to speed), and then another 2 or 3 months before something was usable even in early form.

So if a third party developer wants to create an exporter, they know they have quite a large window in which to work if we've said "no intention at the moment". However we just can't say "never" because then if things change and we do decide to work on it, people would complain - and since we really don't mean "never" but just "not at the moment for sure" then we have to be honest and say that :)

--- End quote ---

Ok, Thank you!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version