Reply to Re: New *WORKING* cross-platform editor
If you don't have an account, just leave the password field blank.
September 28th 2011, 04:18 AM
shevek
Do you need to
No, you don't. The editor creates an image like this:
- It creates an image with the screen and current hardness
- It then starts whatever editor you want to use for editing the image. What I showed is just how I like to edit images. You can use any other program (paint, photoshop, whatever you like). The only thing that matters is what pixels are in the image in the end.
- When you're done, it will read the image and set hardness according to what you made of it.
yeoldetoast: I considered two things:
- adding game play support to the editor (which would avoid the significant delay when testing the dmod). This would mean the editor turns into an alternative for freedink (and dink.exe). Bonus would be that I could ignore all the crazyness of dink instead of copying it. Downside is that games using the features would require my "editor", and would not be playable with original dink or freedink.
- Using python-style input for my preprocessor, instead of C-style. This would be pretty easy and has no downsides I can think of. I didn't do it so far because I assumed that most people would be more comfortable with writing C, given that dinkC does slightly resemble that.
No, you don't. The editor creates an image like this:
- It creates an image with the screen and current hardness
- It then starts whatever editor you want to use for editing the image. What I showed is just how I like to edit images. You can use any other program (paint, photoshop, whatever you like). The only thing that matters is what pixels are in the image in the end.
- When you're done, it will read the image and set hardness according to what you made of it.
yeoldetoast: I considered two things:
- adding game play support to the editor (which would avoid the significant delay when testing the dmod). This would mean the editor turns into an alternative for freedink (and dink.exe). Bonus would be that I could ignore all the crazyness of dink instead of copying it. Downside is that games using the features would require my "editor", and would not be playable with original dink or freedink.
- Using python-style input for my preprocessor, instead of C-style. This would be pretty easy and has no downsides I can think of. I didn't do it so far because I assumed that most people would be more comfortable with writing C, given that dinkC does slightly resemble that.
