[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [Dltk-dev] Error reporting API
|
Well, the main reason I want to look at DLTK 3 is to see if there are improvements in the code assist/autocomplete.
I've patched my native compiler to emit AST information, which I partially translate into DLTK AST and a code model, so I can generate the list of potential completions. The more difficult part is detecting they type of object being completed so I can narrow the list of options.
At the moment I can limit myself to just member method/field completion on known objects, but even that doesn't seem straightforward.
On Jun 22, 2011, at 4:29 AM, Alexey Panchenko wrote:
>> Is there a recommended way of doing this? I feel it's always trial and error picking the right packages.
>>
>> I have eclipse 3.6 right now, with the ruby/python/JS/tcl modules checked out of CVS as projects to use as reference. I'd hate to spend several hours reconfiguring to get a DLTK 3.0 installation, only to find that I can no longer build the DLTK reference projects.
>
>
> You can checkout dltk core plugins from CVS as well without installing
> it into your eclipse installation.
>
> Regards,
> Alex
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev