Page 1 of 1

Better import/export method

Posted: Mon May 18, 2009 6:50 pm
by Vadi
I posted these back in December, but they were never used - while a need for a better solution than "export profile, cut out what you need, repeat when you make a change" is needed.

This places all of the left item views into a row where you can check off all the items you'd like to export, and same for importing.

It also assumes that Mudlet will remember previously-made packages so if you're re-exporting again, you can just select a previous selection.

Screenshot of import
User selects a package to import via the Browse button
- Mudlet reads all settings inside, and adds them to the treeviews. Also, select all scripts by default
- User presses Import

Screenshot of export
- when dialog is shown, it should load all items from the treeviews in the script editor
- user selects items by clicking on the checkboxes beside each script (selecting a parent selects all children)
- press Export button to export to a file

Re: Better import/export method

Posted: Wed May 20, 2009 2:32 pm
by Vadi
Ok, updated dialogs. ... N742j4.png
Export - add a field to add images and etc into the package. ... UELkE3.png
Import - removed option to selectively import - didn't make sense, the user would want to import the whole thing most of the time.

Sent patches to Heiko.