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 - Sam_Mancarella

Pages: [1]
1
Suggestions and Requests / Re: PHP Pre-reqs
« on: March 15, 2004, 05:48:26 pm »
Thank you for your interest in EA's support for the PHP language.

We will definately add by-reference parameter support for function parameters during the next two builds. We will also consider supporting the PhpDocumentor documentation syntax for a future release of EA.

Best Regards

Sam Mancarella

2
Hello to all PHP@EA fans,

We're very pleased with the positive feedback on adding PHP to the list of supported code languages in EA, and its increasing uptake in use in PHP Projects.

We will be adding a number of much-requested improvements to our PHP support over the next few builds, including the PHP Code gen options page (As seen in tools->options for every other supported language).

Once again we appreciate your feedback, stay tuned for these improvements over the coming month, and keep them PHP improvements coming along!

Best Regards
Sam Mancarella

3
General Board / Re: Linux version
« on: April 25, 2004, 08:56:40 pm »
Quote
....the only problem - it does print diagrams with text up-side-down

We have made this correction to build 726 which should be due out later this week - our apologies for that one!  ;D

Sam Mancarella - Sparx Systems

4
General Board / Re: Linux version
« on: April 14, 2004, 10:37:26 pm »
We have released an edition of EA 4.00 that is designed to run using CrossoverOffice on Linux.

Please refer to http://www.sparxsystems.com.au/EAOnLinux.htm for additional info.

Best Regards
Sam Mancarella - Sparx Systems

5
General Board / Re: 3.6/4.0 Side-by-Side Installation
« on: March 22, 2004, 06:37:32 pm »
Hi to all.

Just a quick post to announce that the compatibility edition of EA 3.60 for EA4.00 users is available in the registered users download page.

To Reiterate from my previous post, this edition of EA3.60 will:
- Install itself in a different directory (eg: "%programfiles%\Sparx Systems\EA360")
- Install itself with a different product ID (so that there are no install/uninstall/upgrade conflicts with current and future EA builds and releases)
- Not register itself as an automation server
- Not register itself as the default application for .eap file types

Remember also that the "legacy" version will only open and modify EA 3.60 repositories and not EA 4.00-upgraded versions, nor will EA 4.00 open an EA 3.60 model without upgrading it - this also applies if the repository is accessed via automation.

Note also that EA4.00 upgrades an EA3.60 model via the model upgrade wizard, which runs when an EA3.60 model is opened in EA 4.00.

Best Regards,
Sam Mancarella
- Sparx Systems

6
General Board / Re: 3.6/4.0 Side-by-Side Installation
« on: March 17, 2004, 09:24:34 pm »
Quote
However, the "auto" update feature that converts 3.6 automagically to 4.0, is a concern.
 
I take it that 4.0 does this without notification?

This is not the case - EA actually performs the upgrade via the Upgrade Project Wizard which should show when you open a pre 4.0 model.

NB: It will also backup your model (if it's an eap file) before the upgrade is performed.

Sam Mancarella
Sparx Systems

7
General Board / Re: 3.6/4.0 Side-by-Side Installation
« on: March 16, 2004, 03:45:47 pm »
Hello to all.

Firstly many thanks to all of you for bringing the EA3.60 / EA4.00 issue to light. We intend to address this issue by making a "legacy" version of EA3.60 for registered EA4.00 users, now that EA4.00 has been released.

What we would like from all of you is a "show of hands" to know whether what we propose is suitable, namely to create a build of EA3.60 that will:
- Install itself in a different directory (eg: "%programfiles%\Sparx Systems\EA360")
- Install itself with a different product ID (so that there are no install/uninstall/upgrade conflicts with current and future EA builds and releases)
- Not register itself as an automation server
- Not register itself as the default application for .eap file types

The only drawback to this solution as it currently stands would be that the "legacy" version will only open and modify EA 3.60 repositories and not EA 4.00-upgraded versions, nor will EA 4.00 open an EA 3.60 model without upgrading it - this also applies if the repository is accessed via automation.

All going well, this version should be available for registered users in the next couple days.

In the meantime, we'd be pleased to hear everyone's thoughts on the proposed solution.

Sam Mancarella
- Sparx Systems

8
General Board / Re: Code Generation MustOverride
« on: December 21, 2003, 07:56:57 pm »
Yes this is correct.

The modified Operation Body template should appear as follows at the end of this post. We shall make this template available in the default templates in the next immediate build (657)

Seasons Greetings & many thanks for your support
Sam Mancarella

--== Begin ==--
%PI=""%
%if opTag:"delegate" == "true"%
%endTemplate%

%if opTag:"MustOverride" == "true"%
%endTemplate%

%if opAbstract == "T"%
%endTemplate%

..... remainder of template....

9
General Board / Re: Quotation mark in template output (EA 3.6)
« on: September 01, 2003, 04:51:20 pm »
EA3.60 (635) currently does not allow escaping of the percent symbol (%), dollars symbol ($) or double-quote symbols ("). Presently, to escape a % or a $, it would have to be assigned to a variable as a string literal, viz:

$dollar_sign = "$"
$percent_sign = "%"

$something = $dollar_sign + "foobar" + $dollar_sign

This behaviour is described under "Planned Extensions" in the "Code Template Framework" section of EA's help.

To escape a double-quote in templates is somewhat different. You would have to output the double-quote as literal text.

For example - the Operation Body template in VBNet and Visual Basic has the following statement:
 %opName% = ""

Which assigns a return value of "" if the operation is a function and it is of String type.

To achieve a similar result for setting default parameter values (for example), you could use the following "Parameter" template in VB  and VBNet:

%PI=" "%
%paramDefault ? "Optional"%
%paramKind == "in" ? "ByVal" : ""%
%paramKind == "inout" ? "ByRef" : ""%
%paramKind == "out" ? "ByRef" : ""%
%paramName%
As
%PI=""%
%paramType%
%if paramType == "string" and paramDefault != ""%
="%paramDefault%"
%else%
%paramDefault ? "=" value%
%endIf%

NB: To use this template, you would have to ensure that your default string parameter value is saved without quotes.

Hope this helps.

Sam Mancarella
Sparx Systems


10
Automation Interface, Add-Ins and Tools / Re: Diagram Automation
« on: April 14, 2004, 11:12:24 pm »
As promised, we have made the necessary changes fo the AI to make use of the LayoutStyle parameter in the Project.LayoutDiagram() method.
Using this parameter, one can pass in all relevant layout options as would be found in the Diagram Properties->Set Layout Style dialog box using the constants defined in ConstLayoutStyles.

An example use of these parameters is shown below as a VB Function:
Code: [Select]
Private Function LayoutDiagram _
 (ByRef oProj As EA.Project, _
  ByVal sDiagramGUID As String) As Boolean

 Dim lLayoutStyle As Long
 If sDiagramGUID = "" Then
   LayoutDiagram = False
   Exit Function
 End If

 ' Set some styles using ConstLayoutStyles values
 ' Depth First Search Cycle Removal, Optimal Link Length Layering
 ' Naive Initialize, Default Spacing, Up Layout Direction
 ' Aggressive crossing reduction (8 iterations)
 lLayoutStyle = ConstLayoutStyles.lsCycleRemoveDFS Or _
   ConstLayoutStyles.lsLayeringOptimalLinkLength Or _
   ConstLayoutStyles.lsInitializeNaive Or _
   ConstLayoutStyles.lsCrossReduceAggressive Or _
   ConstLayoutStyles.lsLayoutDirectionDown Or _
   ConstLayoutStyles.lsCrossReduceIteration Or _
   CByte(8)

 LayoutDiagram = oProj.LayoutDiagram(sDiagramGUID, lLayoutStyle)

End Function


A couple of points to be aware of:
  • Using ConstLayoutStyles.lsDiagramDefault will layout the given diagram using the layout styles defined for it
  • ConstLayoutStyles.lsProgramDefault will layout the given diagram using EA's layout defaults
  • The three layout options requiring numerical values to be set are not mutually exclusive - ie: you can only set one numerical value to the parameter to define Layer Spacing, Column Spacing or the Cross Reduce Iterations values - this will be rectified in a later release of EA.


Hope this change proves useful for you in the meantime!
Best Regards
Sam Mancarella - Sparx Systems

[/list]

11
Automation Interface, Add-Ins and Tools / Re: Diagram Automation
« on: March 31, 2004, 06:39:28 pm »
Hi all,

Quote
Looks like you're right.
 
Just tried all values 0 - 128 and all powers of 2.
 
All diagrams laid out according to settings I set by hand in the GUI.
 
Me thinks the feature doesn't work...!  


This is because the LayoutStyle parameter in the Project.LayoutDiagram() method is not actually used anywhere in the automated layout process, so yes, it doesn't work.  :o

Thanks for pointing out the design omission we'll be implementing a set of LayoutStyle options for this parameter for use in diagram layout. We endeavour to provide this within the next build or two of EA (during the next fortnight).

I will post an announcement here in this thread once we have made this layout customisation available.

Watch this space,  ;)

Sam Mancarella
- Sparx Systems

Pages: [1]