This is an idea that's been talked about for a long time, though the talks have been more serious lately.  There are a number of use cases in browser and on mobile that would be solved by this type of functionality.

The download/archive option that exists today is for the entire library itself.  There is no capability to get a text version of what's in a library for documentation purposes.  Soon the API will provide a capability to list the contents of a build (would come as JSON) which could be used for this p...

Due to the openness of Launch and these configuration screens being controlled by Extension Developers, we actually don't have the ability to do this system wide.  There is a feature request logged to do it for the Core Extension, but that is the only one controlled by the Launch team.

This is related an issue that has already been reported Failed Build Message :: List out the missing items using their friendly name .  I'm consolidating the feedback from this idea and that issue into one in the development system.--DTM-10352

Can you explain a little bit more exactly what you mean?  Every time you save custom code in a code editor, you'd want there to be a version history for that specific code block?  Maybe the ability to look at previously saved versions and revert to one?  Just trying to understand how you'd envision ...

Migrated from Alpha--It is really hard to tell through the publishing interface what code or items (data elements, rules, extensions, etc.) are currently deployed to each environment.It would be nice to have a UI that says what items are deployed on which environments.For example, in the screen shot...

Migrated from Alpha--UX Flow of this page needs a little tweeking so the user knows where they are at all times and what they’ve completed.  Leave rule components where they are when creating conditions (events, actions, etc) so the user knows where they are at all times. Just expand and close the w...

Migrated from Alpha--Hi, I have a suggestion. I’d really appreciate having a Create Data Element button when choosing from the existing ones. It would be a very welcomed shortcut.

Migrated from Alpha--After making edits to a Rule, Data Element, or Extension, I wish i could initiate a publish to a dev library from the Rules and Data Element screen, instead of having to switch to the Publishing screen and doing it from there. Maybe something like you check the Rules you want an...

Migrated from Alpha--I find myself logging in and searching for the same properties over and over.  It would be nice if we could bookmark or favorite them to make them quicker to access.