DM's Toolkit Program--NOW AVAILABLE!

[Eldritch_Lord]

Unless you're planning to sell it, why so paranoid?

Because I'm naturally paranoid. In some of my computer science classes in school I've had classmates try to decompile my code and use it themselves, so I've become somewhat paranoid about letting my code get out even if it's something trivial.

Also Icons and splash screens aren't necessary, and installers just mean things can get tucked in odd places.

Installers are also what a lot of not-quite-so-tech-savvy computer users are used to, and the splash screen and icons are in there because my co-developer is the artistic one and he insists that they're a good idea.

 

[Kzach]

I have to say, as a Mac user, this is very irritating.

To be prevented from utilising something merely because the developer encases the file in a proprietary format is very uncool.

But then it's free so I guess I have no real avenue of complaint.

 

[Hodag]

I have to say, as a Mac user, this is very irritating.

To be prevented from utilising something merely because the developer encases the file in a proprietary format is very uncool.

But then it's free so I guess I have no real avenue of complaint.

I use Macs, PCs, and Linux boxes and also dislike proprietary code, but as you said it is free. However, without open sourcing, this code could have not been developed, which is just a touch hypocritical...

 

[Kzach]

Interestingly enough, I'm now in Windows and I'm getting an error trying to open the file.

"Invalid or corrupt jar file..."

 

[Hodag]

Interestingly enough, I'm now in Windows and I'm getting an error trying to open the file.

"Invalid or corrupt jar file..."

I had that too and had to re-download it

 

[Eldritch_Lord]

Regarding the "corrupt file" thing, we were re-uploading the files to ensure the right version was up; the version we had before had a buggy Monster Creator available when it was supposed to display a "Creator not implemented" message instead. If you downloaded it then, it wasn't completely there, and re-downloading it will fix the problem.

Regarding the Mac issue:

I have to say, as a Mac user, this is very irritating.

To be prevented from utilising something merely because the developer encases the file in a proprietary format is very uncool.

But then it's free so I guess I have no real avenue of complaint.

I use Macs, PCs, and Linux boxes and also dislike proprietary code, but as you said it is free. However, without open sourcing, this code could have not been developed, which is just a touch hypocritical...

Hypocritical it may be, but there is a big difference between open-source code and code which is decompiled and reverse-engineered. If and when I release it as open-source, I will be perfectly willing to let everyone use and modify it to their heart's content--but that will be when and where I choose.

Until the Toolkit is in a more complete form (i.e., until all of the Creators are in at least a somewhat-functional form), I want to retain control over it. I'm working on finding an executable creator for Macs; I have a few friends with Macs in my dorm, so I will probably be able to find something for that soon and then you'll have a Mac version.

If you really want to discuss my reasoning, we can do that, possibly over PM, but I would hope that you can respect my decision for now.

 

[Kzach]

On the download issue, it was actually a problem on my end. A download manager fixed it.

And just out of curiosity, if someone really wanted to steal your code, would an executable .jar file really stop them? I mean, we'd be talking people with the know-how to steal code in the first place so wouldn't they also have the resources to crack whatever protections you have in place?

If that's the case, then who are you really affecting by limiting access?

 

[Eldritch_Lord]

And just out of curiosity, if someone really wanted to steal your code, would an executable .jar file really stop them? I mean, we'd be talking people with the know-how to steal code in the first place so wouldn't they also have the resources to crack whatever protections you have in place?

If that's the case, then who are you really affecting by limiting access?

It's not an executable .jar file, it's an executable. As in, .exe in Windows and .bin in Linux. Decompiling an executable gives you assembly code, and trying to mess with graphics in assembly code is a pain in the ass.

 

[Crashy75]

Glad to see this moving along. I'd suggest editing the link into the OP.

 

[Eldritch_Lord]

Glad to see this moving along. I'd suggest editing the link into the OP.

Uh...right. *facepalm* Doing that now.