Re: [pdt-dev] Introduce own internal model

[Dawid Pakuła <zulus@xxxxxxxxx>]

No, see https://github.com/pisv/gethandly/wiki and http://mirror.dkm.cz/eclipse/handly/docs/handly-overview.pdf

In DLTK/JDT/CDT IModel is mostly container for all language projects , IModelElement is concrete item (IProject, IFolder, IFile, IVariable etc…).

Handly brings basic infrastructure for building language models. In opposite to DLTK we will be able to build all fields and strukctures required by PHP to day and in future. We will get more control.  

On 13 June 2020 at 13:34:46, Marc Veary (marc.veary@xxxxxxxxx) wrote:

Hi Dawid,

I am assuming IModel means IModelElement?

Best regards

On Sun, Jun 7, 2020 at 12:10 PM Dawid Pakuła <zulus@xxxxxxxxx> wrote:

Hi,

Maybe in future. 

For now we have to untick form DLTK IModel/IType/IField/ISourceModule. It's too limited:

1. Problems with class alias

2. Not available traits in hierarchy

3. Problems with imports

4. Not possible to keep reference to PHPDoc/Interface infos in member

5. No annotation support (PHP 8)

On 7 June 2020 at 08:39:41, Marc Veary (marc.veary@xxxxxxxxx) wrote:

Hi,

I was looking over GItHub and wondered if the project to abandon the DLTK model means: completely remove the use of DLTK from PDT?

Regards

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev