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 - Paolo F Cantoni

Pages: 1 ... 542 543 [544] 545 546
8146
Automation Interface, Add-Ins and Tools / Model Package has no Element
« on: August 20, 2005, 07:39:45 am »
The Help system says (in part):
Package  A Package object corresponds to a package element in the EA Project Browser. It is accessed either through the Repository Models collection (a Model is a special form of Package) or through the Package Packages collection. Note that a Package has an Element object as an attribute - this corresponds to an EA Package element in the t_object table and is used to associate additional information (such as scenarios and constraints) with the logical package. To set additional information for a package, reference the Element object directly.

Now by Model, I think the Help system is meaning the Project Root node on the Browser.  Does that sound right?

The Model package doesn't appear to have a .Element attribute.

Can anyone else confirm that?

This would seem to be consistent with the fact that you can't open the Package Properties dialog for a Project Root, but you can for a View.

I have several repositories with multiple project roots,  I think I should be able to add standard Element properties for my project roots.  What do others think?

Cheerz,
Paolo



8147
Quote
These attributes are not available in the reporting context either (the new report writer).  I've reported this a couple weeks ago.  Perhaps they are the unloved stepchildren :>
Yes,

I think so, they aren't even available on the Attribute UI.

Paolo

8148
The Help file defines:
Length  Read/Write. Attribute length where applicable.  
Precision  Read/Write. Precision value.  
Scale  Read/Write. Scale value.

They appear on the AI, but don't appear to be emitted.  How can I set them and/or get them emitted.  Or are they also vapourware?

Cheerz,
Paolo

 



8149
Quote
Tried any sanity check for your model?
If you mean Tools|Data Management!Data Integrity?  That's the first thing I did... :)  No problems - according to EA...

I have a few classes with Max(.Pos) in the twenties, and one with 39, but then there's "daylight" between it and the 25 I mentioned in the original post.

Paolo


8150
Automation Interface, Add-Ins and Tools / Attribute Position - way OFF?
« on: August 17, 2005, 08:31:22 pm »
Attribute.Pos Read/Write. Position of Attribute in class attribute list.
Looks OK...

In my test project (embedded in a single larger Model file) I have half a dozen classes.  One of them has 3 attributes.  The .Pos values are 0, 1 and 1000!   ???

Further research shows that of the approximately 1000 attributes in the model, 25 have the value 1000!

Anybody know what's going on?

Cheerz,
Paolo

8151
Quote
If the property aligns with the attribute according to the rules about how properties are created, it does link it back to the property.  (At least it just did in my test case)

Was that C#?
You make a good point though Gunga-Din.  My code was:
Code: [Select]

private int currentLevel;
public int Level
{
 get
 {
   return currentLevel;
 }
 set
 {
   currentLevel = value;
 }
}

Which DOES not conform to the suggested format.  Since you can change the name...

Quote
I don't think the dialog is likely to be exposed in the near future.  I would recommend just creating the methods yourself.

Simon
I have developed an alternative technology for simulating missing EA functionality for my emitter.  It's just a pain to have to do it...

Paolo

8152
Quote
Is the property you are exposing read-only, write-only or read/write?

What this looks like is dependant on the language.

I don't think that functionality is available through the automation interface, but it just creates one or two methods that link back to the attribute.

Simon
Thanx Simon,
So these checkboxes determine (in theory - since I can get at them yet...) whether the setter or getter are actually created.

If you reverse engineer (at least in C#) it doesn't link back to the attribute...  It just creates some operations.  There's no linkage to the attribute...

Will this dialog be exposed in the next release?

Paolo

8153
Automation Interface, Add-Ins and Tools / Access to Property metadata
« on: August 17, 2005, 12:13:39 am »
When you wish to expose the class attribute as a property, you tick the property box and this enables the Property information dialog.

There doesn't seem to be any way to access this via the Automation Interface.  Does anybody know how to do it?

In any event, what do the Read and Write checkboxes mean on the Property information dialog?

Inquisitively,
Paolo

8154
Quote
Paolo,
that's right - more or less. .
[size=13][SNIP][/size]
Thanks Thomas,

I'm not particularly worried about Perl, per se, although I might talk to you off-line about RTF.  It was really a question about the practicality of formatting down-stream, using model context.  I'm glad to see it worked well for you.  I'll probably do something similar but using my model emitter XML/XSD interface as the context generating mechanism.

Regardz,
Paolo

8155
Quote
I use the Tags for things like "Date Due", "Responsible" a.s.o.

For reports I take a quite unusual way. Once I played around with a Perl package for RTF generation and I pimped it up for my use. Now I'm very flexible in generating any RTF docu I like.  Working with RTF tags is really awkward so I hardly can change anything in layout...
Thomas,

Do I understand  you correctly to say that you embed no formatting information within the model itself, but use contextual information at time of generation to format the output document?  For example, using Perl (which I'm not overly familiar with), you get access to the COM model for EA, you then say (something like) all classes with stereotype "Fred" will be rendered in "Fred" styles and structure, while classes with stereotype "Bill" get Bill styles and structure.

I'm thinking of doing the same kind of thing with my Model Emitter and would be interested in your experiences.

Cheerz,
Paolo

8156
Automation Interface, Add-Ins and Tools / Re: CustomProperties?
« on: August 16, 2005, 09:57:44 pm »
Thanx Simon,

I tried an Activity and I did indeed get them...

Paolo


8157
Automation Interface, Add-Ins and Tools / CustomProperties?
« on: August 15, 2005, 12:19:23 am »
In their traversals of the Automation Interface, has anybody come across any custom properties?  The Help system doesn't enumerate what they are.  I've placed some tracers in the code to emit them if I come across any, but so far the small testing model hasn't found any.

How can I set some through the UI so they are emitted?

Cheerz,
Paolo

8158
Automation Interface, Add-Ins and Tools / Re: IsNew?
« on: August 15, 2005, 10:42:39 am »
Further investigation seems to suggest that IsNew is permanently set to True.

Paolo

8159
Automation Interface, Add-Ins and Tools / IsNew?
« on: August 14, 2005, 11:17:32 pm »
Exactly what does the EA.Element IsNew attribute mean?

The Help file says: Read/Write. Boolean value indicating element is new or not. 1 = true, 0 = false  
which is tautological. ::)

What are the semantics of IsNew?

Cheerz,
Paolo

8160
Well, I've done a bit of testing on my own.  I can't get either Element.Stereotype or Element.StereotypeEx to set the stereotype programmatically. ???

Has anybody done it?  (I'm using C#)

Help!

Paolo

Pages: 1 ... 542 543 [544] 545 546