CEED wishlist - Revision history

Kulik at 11:18, 29 June 2011

2011-06-29T11:18:50Z

Kulik at 16:48, 21 May 2011

2011-05-21T16:48:57Z

Kulik: /* Auto-saving and restoring in case of crashes (medium) */

2011-05-21T15:37:02Z

‎Auto-saving and restoring in case of crashes (medium)

Kulik at 15:36, 21 May 2011

2011-05-21T15:36:10Z

Kulik at 15:24, 21 May 2011

2011-05-21T15:24:02Z

Kulik at 15:23, 21 May 2011

2011-05-21T15:23:51Z

Kulik at 23:00, 17 May 2011

2011-05-17T23:00:13Z

Kulik at 13:31, 14 May 2011

2011-05-14T13:31:45Z

Kulik: Created page with "A wishlist of smaller CEED features that I want implemented but can't get around to do that. Catch me on IRC if you would like to implement any of these. == Recent files (easy) ..."

2011-05-12T20:29:35Z

Created page with "A wishlist of smaller CEED features that I want implemented but can't get around to do that. Catch me on IRC if you would like to implement any of these. == Recent files (easy) ..."

New page

A wishlist of smaller CEED features that I want implemented but can't get around to do that. Catch me on IRC if you would like to implement any of these.

== Recent files (easy) ==
We already have recent projects (even though it's slightly broken), recent files also makes sense. Probably only for files not opened from the project manager screen.

== Compatibility layers (easy) ==
Since the editor has API for compatibility layers, adding support for new formats is relatively cheap (the editor is there and works the same no matter the format) as long as you somehow map the "foreign" format to CEGUI's format. The candidates that come to mind are MyGUI imagesets, Gorilla spriteset support (it's already there but needs finishing and polishing) and other imageset formats.

Future candidates include Ogre overlay mapping to CEGUI layout format. My idea is to create a fake looknfeel mimicking Ogre's overlays and map that to Ogre's overlay elements.

note: compatibility layers allow a two-way support (and that's strongly preferred over one-way support to just open the file), that means that you can migrate freely between formats and even edit foreign imageset formats semi-natively.

== MetaImageset editor (hard) ==
GUI to manage meta imageset files, I will implement command line tool for compiling them in the comming days but it would be neat to have a tool to manage meta imagesets in a comfortable way.

== Auto-save project file when files are changed (easy) ==
Basically mimicking the behaviour of Eclipse and MSVC (which I think is what people are used to and expect). Right now saving the project has to be done explicitly.

== Better image creating in the imageset editor (medium) ==
Right now it always creates 50x50 image centred around the cursor. It would be nice to have some sort of click and drag image creation for the tool to be more productive and intuitive.

@@ Line 19: / Line 19: @@
 == Save project file when files are changed (easy) ==
 Basically mimicking the behaviour of Eclipse and MSVC (which I think is what people are used to and expect). Right now saving the project has to be done explicitly.
 == Finish the bitmap previewer / external editor launcher tool (very easy) ==

← Older revision		Revision as of 16:48, 21 May 2011
Line 25:		Line 25:
	== Finish the bitmap previewer / external editor launcher tool (very easy) ==		== Finish the bitmap previewer / external editor launcher tool (very easy) ==
	At the moment, it just displays the image as it is and offers a "Launch external editor" button that doesn't do anything.		At the moment, it just displays the image as it is and offers a "Launch external editor" button that doesn't do anything.
		+
		+	== Better XML editing (easy) ==
		+	Right now I am using plain text QTextEdit to edit code in both imageset and layout editor. The best would be to include XML highlighting that allows you to see mistakes and distinguish tags and property name typos, etc... The module I am talking about is called xmledit and it's in the root CEED directory. It's not used at this point. Perhaps the best would be to include QScintilla but that's another dependency and I would have to really think about that, CEED already has a lot of dependencies IMO.

@@ Line 5: / Line 5: @@
 == Auto-saving and restoring in case of crashes (medium) ==
-Currently when things go mighty wrong (SIGSEGV, SIGABRT or such), the editor crashes and all changes are lost. Saving most of the CEGUI files is quite easy and maybe we could create some sort of restore folder inside the project folder and store changes to opened files there (maybe also including the project file). WHen you save a file or choose to discard changes, this tmp file would get deleted. When you open a new file it looks into the tmp to check whether there is a recovery file there, if there is, user is asked if she wants to recover.
+Currently when things go mighty wrong (SIGSEGV, SIGABRT or such), the editor crashes and all changes are lost. Saving most of the CEGUI files is quite quick and cheap, maybe we could create some sort of restore folder inside the project folder and store changes to opened files there (maybe also including the project file). When you save a file or choose to discard changes, this tmp file would get deleted. When you open a new file it looks into the tmp to check whether there is a recovery file there, if there is, user is asked if she wants to recover.
 == Compatibility layers (easy) ==

@@ Line 17: / Line 17: @@
 GUI to manage meta imageset files, command line tool for compiling them is already done (mic.py) but some sort of easy to use, artist-friendly editor of the meta imageset sources would be very helpful and super easy to do (I labeled this as hard because it's harder than the rest but this is probably the easiest editor in the whole CEED to make).
-== Auto-save project file when files are changed (easy) ==
+== Save project file when files are changed (easy) ==
 Basically mimicking the behaviour of Eclipse and MSVC (which I think is what people are used to and expect). Right now saving the project has to be done explicitly.

@@ Line 4: / Line 4: @@
 We already have recent projects (even though it's slightly broken), recent files also makes sense. Probably only for files not opened from the project manager screen.
-== Auto-saving and restoring in case of crashes (medium)
+== Auto-saving and restoring in case of crashes (medium) ==
 Currently when things go mighty wrong (SIGSEGV, SIGABRT or such), the editor crashes and all changes are lost. Saving most of the CEGUI files is quite easy and maybe we could create some sort of restore folder inside the project folder and store changes to opened files there (maybe also including the project file). WHen you save a file or choose to discard changes, this tmp file would get deleted. When you open a new file it looks into the tmp to check whether there is a recovery file there, if there is, user is asked if she wants to recover.

@@ Line 12: / Line 12: @@
 == MetaImageset editor (hard) ==
-GUI to manage meta imageset files, I will implement command line tool for compiling them in the comming days but it would be neat to have a tool to manage meta imagesets in a comfortable way.
+GUI to manage meta imageset files, command line tool for compiling them is already done (mic.py) but some sort of easy to use, artist-friendly editor of the meta imageset sources would be very helpful and super easy to do (I labeled this as hard because it's harder than the rest but this is probably the easiest editor in the whole CEED to make).
 == Auto-save project file when files are changed (easy) ==
@@ Line 20: / Line 20: @@
 Right now it always creates 50x50 image centred around the cursor. It would be nice to have some sort of click and drag image creation for the tool to be more productive and intuitive.
-== Finish the bitmap previewer / external editor launcher tool (very easy ==
+== Finish the bitmap previewer / external editor launcher tool (very easy) ==
 At the moment, it just displays the image as it is and offers a "Launch external editor" button that doesn't do anything.

← Older revision		Revision as of 13:31, 14 May 2011
Line 19:		Line 19:
	== Better image creating in the imageset editor (medium) ==		== Better image creating in the imageset editor (medium) ==
	Right now it always creates 50x50 image centred around the cursor. It would be nice to have some sort of click and drag image creation for the tool to be more productive and intuitive.		Right now it always creates 50x50 image centred around the cursor. It would be nice to have some sort of click and drag image creation for the tool to be more productive and intuitive.
		+
		+	== Finish the bitmap previewer / external editor launcher tool (very easy ==
		+	At the moment, it just displays the image as it is and offers a "Launch external editor" button that doesn't do anything.