Allow to move a set of classes, modules(a library) in a single copy/paste

slo1958

The idea is that one would create a library made of, for example, a set of classes, modules, .. . Once the library matches requirements, it can then be copy/pasted in one consistent operation to another project. A few ideas in attached document.

moving-items-forming-a-library.pdf

674kB

Garry

Thanks for taking the time to put such a detailed PDF together. The screenshots and logging-library example make the problem very clear, and I appreciate the effort you went to.

I’ve logged Copy folders and transfer modules with all nested items to address the immediate problems. My intention is that ordinary Copy/Paste should include the complete selected folder or module hierarchy, including nested items. Moving a module should also bring its children with it. The operation should preserve the associated source information, report conflicts clearly, and be undoable in one step. I agree that you shouldn’t have to transfer each class individually.

For broader library support, I’m thinking along similar lines to your proposal. I’m already working on the C# plugin SDK and managed Plugin Library, and the longer-term direction is to build support for libraries written in Objo on that same package infrastructure. A library would have an identity and version, and a project would record which version it uses. Updates would be deliberate, so installing a newer library wouldn’t unexpectedly change existing projects. Online discovery and information about available updates could follow later.

Copy/Paste would remain useful alongside that: it gives you an independent copy to edit freely. A managed library reference would let Studio track the dependency and its version.

I want to get the copying and module transfers working properly first, without making them wait for the larger library-management feature. The filesystem-layout suggestions are useful input too, but those need separate consideration. There’s no need to change the solution format to deliver the immediate improvements.

slo1958

Thank for the reply.

Indeed, a solution to easily move nested items via copy/paste is a good solution and the requirement will not disappear if/when a library management is added. And library metadata (like name, version, author, ...) could be discovered even with copy/paste.

When I was 'talking' about libraries, I was thinking about source code libraries. So, it is mainly something for the IDE, with user experience like PyCharm (PyPi), Arduino IDE, ... I have the feeling, but could be wrong, that source code libraries help the growth of a community.

Object code libraries bring their own issues.

It could make sense to have information (name, version, ...) about included libraries, extracted from library metadata, available at run time, so a developer may add something like (when needed):

for each lib as xxx in app.libraries
print (lib.name + ":" + lib.version)

Garry

Yes, libraries written and distributed as Objo source are part of what I had in mind too. The connection to the C# SDK work is the package identity, version tracking and library-management infrastructure. An Objo source library could use those foundations while remaining readable source that is compiled with the application.

I agree that making source libraries easy to share and discover would be valuable for the community.

Making library metadata available at runtime is a useful suggestion too, particularly for About windows and diagnostic reports. Your app.libraries example captures that well, although the exact API would need designing.

For copy/paste, retaining that metadata could also be useful. One detail to consider is how to distinguish the original library version from a copied version that the developer has subsequently modified.

Garry

This has been fixed in the next release.

slo1958

And working as expected. Thanks !!

slo1958

Garry Well, as long a a user copy/paste a library, he/she is responsible to retain the relevant version, which is not always the latest one. This is a lot easier if, as you suggested, the copy/paste also retains the metadata.

The two examples I have in mind (PyCharm and the Arduino IDE) both help you retain the right version if you uses the built in library manager. If the you copy/paste code in your project, great job, but you're on your own.