Autocompletition (Total Nub) [message #494060] |
Thu, 29 October 2009 02:20 |
|
Hello,
I am a newcomer to both modeling and Epsilon. My prior, and short, experience is with oaw. I was trying to do a small ETL example to initiate my work in Epsilon.
The issue is that in oaw once I defined a variable of a metamodel "type", I could use the '.' (dot) to navigate throught the properties of that varaible. I tried doing the same on ETL but the editor is not giving me any options when either using the '!' or the '.'.
Any pointers?
Horacio Hoyos
Horacio Hoyos Rodriguez
Kinori Tech
Need professional support for Epsilon, EMF?
Go to: https://kinori.tech
|
|
|
|
Re: Autocompletition (Total Nub) [message #494178 is a reply to message #494149] |
Thu, 29 October 2009 13:34 |
|
Thanks for the clarification.
For me no typos, "faster" writing and Epsilon functions/methods hints are definitively among the benefits. Any chance this will happen in the future? In the time being is there any "dirty" (hopefully easy) way to git this functionality?
Horacio Hoyos
Horacio Hoyos Rodriguez
Kinori Tech
Need professional support for Epsilon, EMF?
Go to: https://kinori.tech
|
|
|
Re: Autocompletition (Total Nub) [message #494328 is a reply to message #494178] |
Fri, 30 October 2009 10:05 |
Dimitrios Kolovos Messages: 1776 Registered: July 2009 |
Senior Member |
|
|
Hi Horacio,
The main reason why we haven't added static type-checking is so that we
can keep the infrastructure lightweight and agile. This has enabled us
to add novel features such as extended properties, integration with
Java, support for models without metamodels etc. with little effort and
side-effects.
I understand and appreciate the benefits of code completion and semantic
error highlighting but we really don't want to lose this flexibility, so
we'll have to think of a good way to harvest the best of both worlds.
Unfortunately, there doesn't seem to be easy/dirty way to do this (but
please let us know if you can think of any), so this will most probably
require significant changes to Epsilon. We don't have any plans for this
for the near future but it's definitely something worth considering in
the long run.
Cheers,
Dimitris
P.S. For further reading on the pros/cons of static vs. dynamic
languages please Google "static vs. dynamic languages"
P.S.2 The EPackage registry view
( http://www.eclipse.org/gmt/epsilon/doc/articles/epackage-reg istry-view/)
might be able to compensate to an extent for the lack of static typing.
Cheers,
Dimitris
Horacio wrote:
> Thanks for the clarification.
>
> For me no typos, "faster" writing and Epsilon functions/methods hints
> are definitively among the benefits. Any chance this will happen in the
> future? In the time being is there any "dirty" (hopefully easy) way to
> git this functionality?
>
>
> Horacio Hoyos
--
Spread the word: http://www.eclipse.org/gmt/epsilon/spreadtheword
Follow Epsilon on Twitter: http://twitter.com/epsilonews
|
|
|
Re: Autocompletition (Total Nub) [message #582403 is a reply to message #494149] |
Thu, 29 October 2009 13:34 |
|
Thanks for the clarification.
For me no typos, "faster" writing and Epsilon functions/methods hints are definitively among the benefits. Any chance this will happen in the future? In the time being is there any "dirty" (hopefully easy) way to git this functionality?
Horacio Hoyos
Horacio Hoyos Rodriguez
Kinori Tech
Need professional support for Epsilon, EMF?
Go to: https://kinori.tech
|
|
|
Re: Autocompletition (Total Nub) [message #582419 is a reply to message #494178] |
Fri, 30 October 2009 10:05 |
Dimitrios Kolovos Messages: 1776 Registered: July 2009 |
Senior Member |
|
|
Hi Horacio,
The main reason why we haven't added static type-checking is so that we
can keep the infrastructure lightweight and agile. This has enabled us
to add novel features such as extended properties, integration with
Java, support for models without metamodels etc. with little effort and
side-effects.
I understand and appreciate the benefits of code completion and semantic
error highlighting but we really don't want to lose this flexibility, so
we'll have to think of a good way to harvest the best of both worlds.
Unfortunately, there doesn't seem to be easy/dirty way to do this (but
please let us know if you can think of any), so this will most probably
require significant changes to Epsilon. We don't have any plans for this
for the near future but it's definitely something worth considering in
the long run.
Cheers,
Dimitris
P.S. For further reading on the pros/cons of static vs. dynamic
languages please Google "static vs. dynamic languages"
P.S.2 The EPackage registry view
( http://www.eclipse.org/gmt/epsilon/doc/articles/epackage-reg istry-view/)
might be able to compensate to an extent for the lack of static typing.
Cheers,
Dimitris
Horacio wrote:
> Thanks for the clarification.
>
> For me no typos, "faster" writing and Epsilon functions/methods hints
> are definitively among the benefits. Any chance this will happen in the
> future? In the time being is there any "dirty" (hopefully easy) way to
> git this functionality?
>
>
> Horacio Hoyos
--
Spread the word: http://www.eclipse.org/gmt/epsilon/spreadtheword
Follow Epsilon on Twitter: http://twitter.com/epsilonews
|
|
|
Powered by
FUDForum. Page generated in 0.43255 seconds