First let me say that XMI2PHP is a wonderful tool. I find it incredibly useful.
I recently evaluated Visual Paradigm for UML. XMI exported from that program encodes interfaces differently than, for example, ArgoUML which I have also used. The code that XMI2PHP generates from that XMI file has the interface coded correctly, but the class that should be implementing the interface does not.
I've read the topic and see what the problem is. I believe the support for the syntax
'<UML:Abstraction client="[XMI_ID_1]" supplier="[XMI_ID_2]" xmi.id="[XMI_ID]"/>' can be quite easily implemented. Will be added in the next release.
BTW: if you have any suggestions how the XMI2PHP could be improved, they'll be appreciated.
Thank you,
Pawel
P.S. Sorry about the late answer. I didn't receive notification about your message and my SF.net visits are not too frequent these days ;).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'll be on the lookout for the new version. If I notice anything that could be better, I'll certainly let you know. It's actually the smoothest part of my UML workflow right now, so don't expect too many comments.
Thanks again,
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First let me say that XMI2PHP is a wonderful tool. I find it incredibly useful.
I recently evaluated Visual Paradigm for UML. XMI exported from that program encodes interfaces differently than, for example, ArgoUML which I have also used. The code that XMI2PHP generates from that XMI file has the interface coded correctly, but the class that should be implementing the interface does not.
I have a topic on Visual Paradigm's forums about it here:
http://forums.visual-paradigm.com/posts/list/2029.html
I'll be happy to provide example xmi if you think that XMI2PHP might be able to handle the XMI they are creating.
Many thanks,
Scott
Hi Scott,
Thank you :).
I've read the topic and see what the problem is. I believe the support for the syntax
'<UML:Abstraction client="[XMI_ID_1]" supplier="[XMI_ID_2]" xmi.id="[XMI_ID]"/>' can be quite easily implemented. Will be added in the next release.
BTW: if you have any suggestions how the XMI2PHP could be improved, they'll be appreciated.
Thank you,
Pawel
P.S. Sorry about the late answer. I didn't receive notification about your message and my SF.net visits are not too frequent these days ;).
Wonderful!
I'll be on the lookout for the new version. If I notice anything that could be better, I'll certainly let you know. It's actually the smoothest part of my UML workflow right now, so don't expect too many comments.
Thanks again,
Scott