On Sun, 05 Jun 2011 17:18:06 -0500 Jeff Hoogland <[email protected]> said:
> What would people think of having an option in the profiles GUI that would > allow for easy one click import/export of profile settings? Think this could > be useful for users that want to share their setups. > > Figured I would throw the idea out of having it added to the main code branch > before I went ahead and had it written as a seperate module for Bodhi. well there is a problem here. there are some things inside the config that are highly personal and specific to that machine or users files that when transferred need either to be set to some defaults or be modified into some "generic non full-path form" and/or have the dependent data (the wallpape3r, theme referenced) packaged along with the profile. this is why i never did it as the profile was pretty personal. e.g. wallpaper(s), theme, path appends for data, images, fonts, themes, etc. now modules also is another matter - profile may have set of modules enabled that other user doesn't have, but its not really possible to just package these up like edje data files with wallpaper/theme. some config is "internal and pointless to export" like wallpaper import last dev/path some other config is also just dependent on system setup like path to system apps menu to use, icon theme, maybe custom env vars, desklock custom command, exebuf term cmd, input method (tho exebuf now is replaced by evry), acpi, key, mouse and other bindings... and more. and speaking of evry - every module will have its own config that may or may not have such system specific entries. hell some may even store sensitive personal information. evry will hold history of executed commands and typed in stuff and much more... so to do this kind of feature you need a way to handle the above. i think it falls into the following categories: 0. the config is safe to just transfer over 1. a way of finding dependent data (a theme, wallpaper, whatever) and putting it in the packaged up profile, unpacking it to a sane location and modifying the config filed that referred to that data so it works at the other end. 2. a way of setting some fields back to empty/0/defaults/whatever if they contain useless or entirely personal information 3. a way of realizing that there is some system dependency (a specific application menu file on the system, a specific icon theme) and a way to detect that dependency and tell the person who is trying to use the exported profile of the lack of a dependency 4. all config be it in the main e blob or in evry or other modules needs to be known to b e in one of the above groups and then dealt with appropriately at both the time of packing it up into a tarball or eet file or whatever and at the time of installation. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
