Jump to content
  • Advertisement
  • entries
  • comments
  • views

More Editor Work

Sign in to follow this  


Well, I finally got fed up with manually creating/editing files, so I've picked back up on working on the editor. I got quite a bit done today, but most of it is backend stuff. I hate to have my code tied directly into the UI, so originally I started off working on a separation of the Editor and the UI...and I failed lol.

I was working back through things today and had to rewrite quite a bit, but I'm caught back up and have moved forward a little bit: I can create, save, and load project files as well as importing/removing textures. As I use a base class for all of the assets, most of the work for the other types should just be in saving/loading.

I do have to admit that the code is kind of bulky and hard to follow at times; mainly because the UI makes calls to the Editor class which in turns calls callbacks...to the UI. This is an example:
User clicks 'View Texture' in the UI, which calls EditAsset (passing in the texture), which calls the OpenAssetRequested callback and loops back to the UI to actually view the file.
While bulky, this will allow me to keep the two separate and if I need to I can completely gut the UI without affecting any of the actual editor stuff. As an added bonus, I could easily expand with plugins if needed.

Here's a screenshot of the test project I've been using. I've got the settings page open in the background, but I'm currently viewing an old concept texture:


Hopefully my prediction is right and I can fly through the majority of this. The item editor, object editor, and character editor are already "done"; I created them as panels and have been using them for most of the demo (I just threw the panels in some forms.) The major hurdles will be the scene editor, integrating with MSBuild, and then bringing it all together with the script editor (though the latter is working pretty well so far.)

Time for bed for me!


Script files are in now. I'm thinking there needs to be a little more refactoring; adding a new asset type shouldn't amount to the code changes that need to be made. Now, I'm really going to bed.


Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!