See & edit code for whole class?

[Massimo_Valle]

@14380:@Joe Ranieri

There used to be some documentation on the XML format, but I don’t know if it’s still available. It’s worth noting, however, that the XML format is not The Future. The text format is going to become the one true format.

I’d really like to adopt the text format, but I had to switch to XML for external items support.
Is it planned to add external items support to the text format before deprecating the XML format?

[Paul_Lefebvre]

@50506:@John Jones

How does the feedback:// url work? Must this be clicked via the Xojo program?

With the Feedback app installed, the feedback:// URLs load in the app. You can download it from here:

http://www.xojo.com/download/extras.php

[Paul_Lefebvre]

[quote=50531:@Massimo Valle]I’d really like to adopt the text format, but I had to switch to XML for external items support.
Is it planned to add external items support to the text format before deprecating the XML format?[/quote]
You can add external XML (or binary) items to Text projects.

[Massimo_Valle]

@50534:@Paul Lefebvre

You can add external XML (or binary) items to Text projects.

Yes, I see, but it’s pretty useless if I can’t save as text the external items.
How is it supposed to compared/diff them in VCP environment?

Again, I’d be very happy to have all saved as text, but at this time it’s an half-baked solution.

[Chay_Wesley]

I’ve assumed (quite possibly incorrectly) the resistance to the idea of having the full class / module code visible is an attempt to raise the difficulty level for people who might attempt to manually circumvent the concerns Geoff posted about here:

[quote=930:@Geoff Perlman]Without such a restriction, a team of five developers could purchase a single set of build licenses and have one person do all the building. That was never the intention of the new model. By requiring a build license to use XML and VCP (especially the later), any developers needing to use version control will also need a build license. That means each member of that five member team will purchase a build license.

You could, in theory, use the binary format and make all items external but that would be pretty useless with version control.[/quote]

[Paul_Lefebvre]

@50538:@Massimo Valle

How is it supposed to compared/diff them in VCP environment?

You mentioned you were using the XML Project for external file support. I’m just pointing out that you can use the Text Project and still have external file support using XML project items. Surely it is better to be mostly in Text Project format and only have the items you are sharing in XML format (making only the shared items tricky to diff). This won’t make much sense if you are sharing everything, but surely that’s not the case.

Of course, I agree the Text Format should be able to share text format items, but it can’t yet.

[Norman_P]

[quote=50531:@Massimo Valle]I’d really like to adopt the text format, but I had to switch to XML for external items support.
Is it planned to add external items support to the text format before deprecating the XML format?[/quote]
We’d probably not be able to deprecate binary or XML for a long time

But there are a number of things we intend to address in order to make a text format be “the one true format” and external item support would have to be there

[John_Jones1 (John Jones)]

Oh no! With all this discussion of a binary file format, I just wondered how can a version control system be used with Xojo?

[Paul_Lefebvre]

@50611:@John Jones

Oh no! With all this discussion of a binary file format, I just wondered how can a version control system be used with Xojo?

Just use the “Xojo Project” file format, which saves each project item as a text file for easy use with version control systems. There is more information about this format (and the other formats) in both User Guide Book 1: Fundamentals and Book 4: Development (Code Management chapter).