news.eclipse.technology.dltk

[news.eclipse.technology.dltk] [BUILD] R1.0-I

alex@xxxxxxx (DLTK Builds) — Mon, 08 Sep 2008 12:15:29 GMT

Hi all,

New build is uploading to http://download.eclipse.org/technology/dltk/downloads/drops/R1.0/I-I200809081043-200809081043/ and will be available shortly.

Regards,
The Build System at Xored Labs.

[news.eclipse.technology.dltk] [BUILD] R1.0-I

alex@xxxxxxx (DLTK Builds) — Fri, 05 Sep 2008 14:59:12 GMT

Hi all,

New build is uploading to http://download.eclipse.org/technology/dltk/downloads/drops/R1.0/I-I200809051155-200809051155/ and will be available shortly.

Regards,
The Build System at Xored Labs.

[news.eclipse.technology.dltk] Re: Tcl Task Tag problems

ophelie.mezy@xxxxxxx (Ophélie ) — Fri, 05 Sep 2008 06:40:21 GMT

Hello,

Thank you for your answer.

In fact, perforce server manages differents projects, and makes all projects right protected. I think the problem comes from right protected projects. When we open right protected projects, task tags not recognize "todo" comment as task.

I tried with unright protected projects and task tag runned well, but the problem is we cannot change right of projects every time we need a project, it will be to much heavy.

I am sorry about my English, but I expect you will understand my problem.
Best regards

Ophélie

[news.eclipse.technology.dltk] Re: Tcl Task Tag problems

haiodo@xxxxxxx (Andrei Sobolev) — Fri, 05 Sep 2008 02:42:46 GMT

Hi Ophélie,

I've could not reproduce first problem you specified, could you please provide exact steps you perform and project structure. May be you could simulate situation on not perforce project.

For a second problem I've created bug in eclipse https://bugs.eclipse.org/bugs/show_bug.cgi?id=246311

Best regards,
Andrei Sobolev.

Hello,
We use Eclipse DLTK ganymede to program in Tcl. So, this tool is very usefull and facilitates us the programming in Tcl.

But, we just have a little problem about Task tag. I explain. We have a lot of big projects which are saved and referenced by version on a perforce server. This server permit us to save, modify, download different files of projects, and to class all projects about their number of versions. This server permit to centralize all works of peoples on company.

So, when we want to work with a created project, first of all we have to check out Tcl changed files of project from perforce server, that makes these changed files writable on Eclipse but not all project. In fact entire project is open on Eclipse, but just some files are writable. So, on no-writable files of eclipse, Task Tag not recongnize "Todo" comment as a task.

And the other problem is, when we configure Preferences/Tcl/Task Tag, after a restart of Eclipse this configuration come back per default even if we saved this configuration.
Thank you for your help
Best regards
Ophelie

[news.eclipse.technology.dltk] [BUILD] R0.95-M

alex@xxxxxxx (DLTK Builds) — Thu, 04 Sep 2008 18:53:32 GMT

Hi all,

New build is uploading to http://download.eclipse.org/technology/dltk/downloads/drops/R0.95/M-M200809041502-200809041502/ and will be available shortly.

Regards,
The Build System at Xored Labs.

[news.eclipse.technology.dltk] Tcl Task Tag problems

ophelie.mezy@xxxxxxx (Ophélie ) — Wed, 03 Sep 2008 11:10:47 GMT

Hello,

We use Eclipse DLTK ganymede to program in Tcl. So, this tool is very usefull and facilitates us the programming in Tcl.

But, we just have a little problem about Task tag. I explain. We have a lot of big projects which are saved and referenced by version on a perforce server. This server permit us to save, modify, download different files of projects, and to class all projects about their number of versions. This server permit to centralize all works of peoples on company.

So, when we want to work with a created project, first of all we have to check out Tcl changed files of project from perforce server, that makes these changed files writable on Eclipse but not all project. In fact entire project is open on Eclipse, but just some files are writable. So, on no-writable files of eclipse, Task Tag not recongnize "Todo" comment as a task.

And the other problem is, when we configure Preferences/Tcl/Task Tag, after a restart of Eclipse this configuration come back per default even if we saved this configuration.

Thank you for your help
Best regards

Ophelie

[news.eclipse.technology.dltk] [BUILD] R1.0-I

alex@xxxxxxx (DLTK Builds) — Tue, 02 Sep 2008 05:29:44 GMT

Hi all,

New build is uploading to http://download.eclipse.org/technology/dltk/downloads/drops/R1.0/I-I200809020446-200809020446/ and will be available shortly.

Regards,
The Build System at Xored Labs.

[news.eclipse.technology.dltk] Re: Type Hierarchy features

brunodomedeiros+spam@xxxxxxx (Bruno Medeiros) — Thu, 28 Aug 2008 23:02:38 GMT

Alex Panchenko wrote:

Hi Bruno,
Type hierarchy is supposed to be working, however there could be some bugs or side effects after changing the related parts of the system.

From the user viewpoint is should work the same as in JDT. The super classes are determined by the name - in the interpreter languages there are no other ways to statically identify it, but if you have class with the same name in different files then there is no simple choice.
I am going to review the type hierarchy on the next week.
After that I will post the message with more details, please stay tuned.
Regards,
Alex

Thanks. Also, for the record, I was interested in something indeed like JDT's views, as D has the same inheritance model as Java: single inheritance + multiple interfaces, and a common Object superclass for all classes.

In DLTK some of the differences I found (besides the odd bugs), where: * In the supertype hierarchy, the list of supertypes is ordered alphabetically. I would rather the order of supertypes given by the SourceElementParser was respected, especially because I want to make sure the class supertype always appears before the interface supertypes (like JDT) * In the subtype hierarchy, besides only some of the subtypes appearing, the view also shows the supertype hierarchy (in the direction torwards the root of the treeview, which is weird). In JDT, the subtype hierarchy also shows some of the supertypes, but only the primary supertype (ie, the parent class), so that you can form a single branch upwards in the TreeViewer, instead of multiple upward branchs, which is weird (if I make myself clear).

I'll stay tuned! :)

--
Bruno Medeiros - Software Developer, MSc. in CS/E graduate

[news.eclipse.technology.dltk] [BUILD] R1.0-I

alex@xxxxxxx (DLTK Builds) — Thu, 28 Aug 2008 05:31:15 GMT

Hi all,

New build is uploading to http://download.eclipse.org/technology/dltk/downloads/drops/R1.0/I-I200808271527-200808271527/ and will be available shortly.

Regards,
The Build System at Xored Labs.

[news.eclipse.technology.dltk] Re: Type Hierarchy features

alex@xxxxxxx (Alex Panchenko) — Wed, 27 Aug 2008 01:40:22 GMT

Hi Bruno,

Type hierarchy is supposed to be working, however there could be some bugs or side effects after changing the related parts of the system.

From the user viewpoint is should work the same as in JDT. The super classes are determined by the name - in the interpreter languages there are no other ways to statically identify it, but if you have class with the same name in different files then there is no simple choice.

I am going to review the type hierarchy on the next week.
After that I will post the message with more details, please stay tuned.

Regards,
Alex

Bruno Medeiros wrote:

Hi. I've been doing some more work on the DLTK-based D Eclipse IDE, and I was trying to implement the Type Hierarchy View features, however I couldn't get it to work correctly, and I'm not sure if it's due to an error on my part, or due to some bugs in DLTK.

Has this feature been fully implemented in DLTK, or is it a work-in-progress? I've seen some strange bugs which seem to come from DLTK, like the same type having a certain hierarchy shown the first time the view (or TH popup) is invoked, but having a different hierarchy the second and subsequent times the view is invoked, even though no code has been changed meanwhile!

If it's fully implemented, can you give an overview of how the Type Hierarchy features work (both from a user-viewpoint, and from an IDE plugin view-point)? How does DLTK determine the superclass elements, given only the TypeInfo.superclasses String array in the SourceElementParser? Is the Type Hierarchy feature able to correctly identify all subtypes of the class under analysis?