|
|
|
Forum Member
      
Group: Forum Members
Last Login: 2 days ago @ 10:06:20
Posts: 36,
Visits: 94
|
|
Hi,
A few questions regarding ECO and what IDE/language to use...
1. I understand ECO will not support Delphi Prism (DP) until version V. So, when do you expect version V to be released?
2. I read that you will try to make the C# and DP (and VB too) experience as sinilar as possible, but what differences WILL exist?
3. What major new features will appear in version V?
4. Will ECO V with DP have solved the old old problem with having to put all generated code into a single unit (possibly split using include files) to be able to use type-safe object lists for associations?
In other words: With ECO and Delphi Prism, will I be able to put classes in separate units AND have typed and type-safe object lists for associations?
Thanks,
Kjell
|
|
|
|
|
Supreme Being
      
Group: Administrators
Last Login: 2010-11-30 12:17:13
Posts: 1 230,
Visits: 1 382
|
|
krilbe (2009-01-13) A few questions regarding ECO and what IDE/language to use...
1. I understand ECO will not support Delphi Prism (DP) until version V. So, when do you expect version V to be released?
I had hoped to prepare the first public beta early this week, but I came down with a fever :-( It should be up in a few days. I have already posted the changelog for all the things we have done since we started with beta-builds to our fieldtesters:
http://www.capableobjects.com/apps/InstantKB13/KnowledgebaseArticle50020.aspx
Unless anything unexpected happens after that the official release shouldn't take too long.
2. I read that you will try to make the C# and DP (and VB too) experience as similar as possible, but what differences WILL exist?
So far, the RemObjects team have been very helpful to iron out the compiler issues we have had with some of the more odd constructs in our new code-generator (custom attributes referring to nested classes in nested classes and stuff like that). The only thing I can remember off the top of my head is that DP doesn't currently support WebApplication projects, only WebSite projects (or is it the other way around, I can never remember which is which, DP doesn't support the kind of web-projects that have a project file). From what I have heard, this will be fixed in their next release,
DP doesn't support the Rename-refactoring (afaik), and our codegen uses this feature from the IDE when you rename a class or attribute in order to get all the references updated. This is not critical, and in DP it will simply result in a compiler error for the references that are not renamed and you will have to update the reference manually. If RemObjects implement this functionality in a future version, it should work automatically with ECO.
3. What major new features will appear in version V?
* New designer, integrated into VisualStudio
* Reverseengineering of existing databases (this has been available in the RadStudio version, but now the feature is completely rewritten and integrated into the new UML designer)
* new codegenerator that uses partial classes.
* Support for tuples in OCL
* All code translated to C# (fewer eco assemblies, no more borland.delphi.dll)
* as always, lots of small and large bugfixes and optimizations
4. Will ECO V with DP have solved the old old problem with having to put all generated code into a single unit (possibly split using include files) to be able to use type-safe object lists for associations?
In other words: With ECO and Delphi Prism, will I be able to put classes in separate units AND have typed and type-safe object lists for associations?
Yes! DP doesn't have the same limitation as the old delphi.net compiler (dccil). It is works perfectly to have two DP-files with classes that reference each other, just like you can in C# and VB. The DP codegen is using the same mechanisms as the C# and VB codegen. The code for each class is generated as two separate files, MyClass.pas and MyClass.eco.pas, where the .eco.pas-file contains all of the autogenerated code and the .pas-file contains the userwritten methods. This gives a very clean code imho. We have further made sure that the auto-generated code is always generated in the same order to make it as easy as possible to diff changes in your version control system.
/Jonas Hogstrom [CapableObjects]
|
|
|
|
|
Forum Member
      
Group: Forum Members
Last Login: 2 days ago @ 10:06:20
Posts: 36,
Visits: 94
|
|
| Many thanks for this very elaborate and complete reply!
|
|
|
|
|
Supreme Being
      
Group: Forum Members
Last Login: 2010-08-11 16:02:44
Posts: 338,
Visits: 890
|
|
[b]Jonas Hogstrom
3. What major new features will appear in version V?
* New designer, integrated into VisualStudio
* Reverseengineering of existing databases (this has been available in the RadStudio version, but now the feature is completely rewritten and integrated into the new UML designer)
* new codegenerator that uses partial classes.
* Support for tuples in OCL
* All code translated to C# (fewer eco assemblies, no more borland.delphi.dll)
* as always, lots of small and large bugfixes and optimizations
Nothing about Linq2Eco support? Disappointing 
Cheers.
My Blog: http://dnagir.blogspot.com
|
|
|
|
|
Supreme Being
      
Group: Forum Members
Last Login: 2009-12-21 19:09:25
Posts: 111,
Visits: 839
|
|
The lack of Linq2Eco is very disappointing indeed. I would also like to see a disconnected API out-of-the-box.
Do you have something planned for releases beyond ECO V?
--
Pedro Brown
pedro@tectrilha.com.br
Tectrilha Software - Borland Learning Partner
|
|
|
|
|
Supreme Being
      
Group: Administrators
Last Login: 2010-11-30 12:17:13
Posts: 1 230,
Visits: 1 382
|
|
Yes, we are looking into Linq2eco now.
We feel that we have made lots of progress with the product and while we completely understand your desire for LINQ-support, we would really like to get the new designer out the door.
/Jonas Hogstrom [CapableObjects]
|
|
|
|
|
Forum Guru
      
Group: Forum Members
Last Login: 2011-07-06 03:19:22
Posts: 65,
Visits: 156
|
|
Linq => compile time check syntax
Ocl => run time check syntax
Could ECO5's Ocl be more convenient in *.cs coding window?
|
|
|
|
|
Supreme Being
      
Group: Administrators
Last Login: 2010-11-30 12:17:13
Posts: 1 230,
Visits: 1 382
|
|
gattaca (2009-01-15) Linq => compile time check syntax
Ocl => run time check syntax
Could ECO5's Ocl be more convenient in *.cs coding window?
I dont understand exactly what you mean? We can't get compiletime check of OCL as long as it is stored as a string in the code, and I doubt it is possible to get OCL added to the C# specification. Could you elaborate on what you had in mind?
/Jonas Hogstrom [CapableObjects]
|
|
|
|
|
Supreme Being
      
Group: Forum Members
Last Login: 2010-08-11 16:02:44
Posts: 338,
Visits: 890
|
|
Hi Jonas,
So what are the plans for:
* Linq2Eco
* Disconnected API (as Pedro Brown asked, +1 vote from me)
* Stored Procedures support
Cheers,
Dmitriy.
My Blog: http://dnagir.blogspot.com
|
|
|
|
|
Forum Guru
      
Group: Forum Members
Last Login: 2011-07-06 03:19:22
Posts: 65,
Visits: 156
|
|
I mean it may be like code templete.
#/OCL_strOCL# ClassW.allInstances->select(strFinish <> '1') #OCL_strOCL/#
IOclService ocls = EcoServiceHelper.GetOclService(EcoSpace);
IElement oclRe = ocls.Evaluate( #/OCL_strOCL/# );
1. Let compiler check the OCL syntax surround with #/OCL_ # ..... #OCL_ /#
2. If OCL syntax passed, replace templetes to C# code.
#/OCL_strOCL# => string strOCL ="
#OCL_strOCL/# => ";
#/OCL_strOCL/# => strOCL
|
|
|
|