Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - TerryC

Pages: [1]
1
General Board / Re: COllaborative working
« on: October 03, 2002, 04:39:55 am »

Hi Jason

I've just tried out the controlled packages feature and it makes import/export easier. Here's some info I've found:

1. You can use a relative path name for the package's XML file i.e. type something like .\packagename.xml in the 'XML filename' field in the Package Control/configure menu. Relative paths are better as they don't force you to checkout your CVS module to the same directory.

2. It would be nice if you could put $id: $ in the version ID field so that CVS could do the version tracking. Unfortunately when I tried this I got problems loading the package - the CVS had put the correct value into the XML but EA fell over because the string was too long - it's also caused the project to lose all of its package control information - this stuff should be transactional (if the Access DBMS can handle that).

3. Another problem is that loading and then saving a package - without making any changes - results in lots of changes to the XML file (mostly dates and GUIDs). Ideally there would be no changes and so the XML files would appear unmodified to the CVS.

If this could be done then ideally there would be an 'auto load/save' checkbox on the package-control/configure menu that would make EA automatically import/export that package's XML file when a project was loaded/saved.

Cheers

2
General Board / Re: COllaborative working
« on: October 02, 2002, 08:20:12 am »

Hi

I'm evaluating EA for use by a team over a WAN. We currently put all of our code into a CVS repository and it would be nice if we could do this with EA. Unfortunately the fact that EA stores its data in a binary file means that CVS can't store differences and so every CVS update would mean sending a potentially large file across the network and completely replacing the current CVS entry - which is impractical over a WAN.

I've noticed that EA can save its diagrams as tagged values in XMI files - so I could save the XMI files in the CVS instead, but there doesn't seem to be a way to save ALL the EA model in the XMI file e.g. the issues list gets lost.

An ideal solution for me would be to have a way of exporting/importing a complete project as XML. That way it would work with any source code control system.

Cheers






Pages: [1]