.dll CC's Yes or No

i voted.
now, my 2 cents.

i like the idea of the cc devs being able to share their code or not to share it.
ie. giving them the choice to dll or not to dll.

having dll ccs is a great way for those that would like to learn coding to get
ideas and inspiration from.

i also can understand that those who have worked hard crafting an amazing cc
may not want others effing with it.

if it could be both ways, i think it would be good.

 

I dont agree with the "one dodgy dll and its all over for us", because it is much easier to grab say, BigSister that gets your acc info, and send it to a remote server. It even works standalone, so, nothing HB2 can do about it.

It comes down to what you trust and not trust...

 

I dont trust you, your Big er than me

 

Enough said
Yay for DLLs

 

Well 67% is a fair number in favour of this, it doesn't surprise me.

Not trying to flog a dead horse (as the saying goes) but if this product was to grow and evolve like any other product - by users feedback and input - then DLL support should be included. But thats just my logical point of view.

 

Sorry Tony, I was rounding.

 

You ARE round.

 

And it's 66.92% by now

 

Imo there should be possibility for developers to cover their hard work.

However as HB user i would appreciate requirement for combat part of code to be fully customizable for everyone (thinking about rotations/priorities parts of code).

 

The One CC has customizeable spell rotations and spell prioritization, even in DLL form.

 

look, in the end, dlls make things easyer, to get ecliptor running, you need 3+ files now, more files = more things end users can mess up, and cause problems for you. not only that but i implemented a nice gui config because it gives users a nicer experience not having to edit values manualy, and it makes it look more professional, i guess in the end, i couldnt care less. and i fail to understand why the "average user" even cares. when in theory this is only a CC Dev, and HB/GB dev issue.

 

The One CC is 6 files

 

Abstraction...

DLL compilation permits a form to configure the custom class, which precludes the possibility (mostly) of people messing with the code itself. Rather, they are permitted to get and set variables as needed to configure. Moreover, if security is a concern, why not have the cc developers give an MD5 of the dll to the HB devs so that each release can be verified. Or the signing key would work as well.

 

Works for me

 

make it so number 1.

 

booyakasha

 

The Fat32 File System can only contain a Maximum of 65,534 Files


</pre>