Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [mdt-papyrus.dev] sash windows

Very thanks,
Patrick 


---------------------------------------------------------
Patrick Tessier
Research Engineer
DRT LIST/DTSI/SOL/LISE CEA-Saclay
91191 Gif sur Yvette Cedex
Tel: 01 69 08 48 63
www.papyrusuml.org
---------------------------------------------------------

-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Francisco Javier Cano
Envoyé : jeudi 13 novembre 2008 10:38
À : Papyrus Project list
Objet : RE: [mdt-papyrus.dev] sash windows

Contents of 'es.cv.gvcase.mdt.common' have been moved to 'org.eclipse.papyrus.diagram.common'.
Because of this, the activity ans sequence diagram have, as expected, changed too.

What is strange is that the use case diagram also used some functionality from 'es.cv.gvcase.mdt.common'.
I performed the necessary changes the use case diagram.

The 'es.cv.gvcase.mdt.common' and its remaining contents can be removed from the repository.
The 'es.cv.gvcase.mdt.common' plugin should be removed from the feature.xml.

Let me know if this has moving/renaming has broken any of your plugins and we'll try to solve it.

Regards,
Javi

----
Francisco Javier Cano Muñoz
Programador senior
Prodevelop
www.prodevelop.es



-----Original Message-----
From: mdt-papyrus.dev-bounces@xxxxxxxxxxx on behalf of Francisco Javier Cano
Sent: Thu 13/11/2008 8:51
To: Papyrus Project list
Subject: RE: [mdt-papyrus.dev] sash windows
 

 'es.cv.gvcase.mdt.common' is being renamed/moved to the appropiate namespaces.
 It will be committed before the day ends.

 Regards,
 Javi

----
Francisco Javier Cano Muñoz
Programador senior
Prodevelop
www.prodevelop.es



-----Original Message-----
From: mdt-papyrus.dev-bounces@xxxxxxxxxxx on behalf of Cedric Dumoulin
Sent: Thu 13/11/2008 0:37
To: Papyrus Project list
Subject: [mdt-papyrus.dev] sash windows
 

  Hi all,

  I have reconnected the sash windows, and do the merge with the new di refactoring.
 It work for me. I have do a fully clean install, and nearly everything compile ok without any additional tasks to perform.
Some small problems remain, but you can still use PII:

    * some errors still in def or codegen
    * oep.outline is missing some library. Maybe the patch proposed by
      Jacques could save that
    * oep.outline contains subfolders trunk, release, ... I think we
      should better have not such dirs per project, but per workspace.
    * oep.diagram.emftree has one extra dir level. It should be removed
    * es.cv.gvcase.mdt.common should be renamed asap.
    * All bin directories should be excluded from CVS :-)

I have also detect some bugs:

    * The properties are not showned when we select the background of a
      diagram. This forbid to rename a diagram.
    * The CPU usage raise to 100% when  you  have a visible class in a
      classdiagram.  It fails as soon as  the class is hidden, for
      example when you move the scrollbars to hide the class.
    * Some actions on sash are not implemented or fails. I will correct
      that.

  Cedric


BEGIN:VCARD
VERSION:2.1
N:TESSIER;Patrick
FN:TESSIER Patrick 202707 (Patrick.TESSIER@xxxxxx)
ORG:;SOL/LLSP
TITLE:Ingénieur Chercheur
TEL;WORK;VOICE:(01) 69 08 48 63
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;B=E2t. 451 Pce 9;CEA SACLAY=0D=0ADRT/DTSI;GIF/YVETTE CEDEX;;91191;FRANCE
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:B=E2t. 451 Pce 9=0D=0ACEA SACLAY=0D=0ADRT/DTSI=0D=0AGIF/YVETTE CEDEX 91191=
=0D=0AFRANCE
EMAIL;PREF;INTERNET:Patrick.TESSIER@xxxxxx
REV:20071011T094630Z
END:VCARD

Back to the top