#968: create a GUI resource editor ----------------------------+--------------------------- Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Applications | Version: R1/pre-alpha1 Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ----------------------------+--------------------------- Comment (by TriEdgeAI): '''[TODO]''' - Copy/Paste functionality of ResourceRows. - Tab view with three tabs about Resources, Types and Enums. - Support for editing custom types. These can pretty much use ResourceRow*, too. - Support for editing enums. - Finish parsing support for .rdef files (arrays, type-recognition, types, enums, etc..) - Finish output support for .rdef files. - Provide more settings. This is done by adding views in the settings dir and mapping them in the SettingsWindow class. Actual setting data is stored in SettingsFile class. - Add support for child resource rows (arrays, messages, custom types, etc). The code is already prepared for such an addition I believe. - Provide more edits for editing different types of resource data. This is done by adding self-attaching views to the edits dir. Good edits would be ColorEdit, NumericEdit<>, StringEdit, NoEdit, etc. Edits are registered to specific resource types in DefaultTypes.h. Resource types like images or icons should be handled by external programs like Icon-O-Matic or WonderBrush instead of having ResourceEdit provide it's own means. - Add validation to editing resources. Resource info validity should be checked in EditWindow class, resource data validity should be checked in the respective -Edit class. - Merge from functionality (Just like normal load, except you don't clean the list beforehand). - Help documents and menu. - Drag and drop functionality to add files to the .rdef with option to choose hexdump or import mode. - Separate ResourceRow's actual data from preview data. For example if the data is "true" for a boolean resource, one could display "✔ TRUE" instead. Colors can be displayed with background color and inverted color for the text and so on. - Allow for thumbnails to be displayed for image resources. - Exporting/importing to .rsrc (could either be done through rc, which would be an easier but unsafer way, and through BResources from the Haiku API). - Allow resource IDs to use enums. All I can think of right now. Probably a lot more. I've left TODO comments throughout the code here and there which should assist further by guiding people where to implement things. -- Ticket URL: <http://dev.haiku-os.org/ticket/968#comment:9> Haiku <http://dev.haiku-os.org> Haiku - the operating system.