wtp-dev

Re: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!

cristal_reaver@xxxxxxx (stanimir petrov) — Fri, 03 Jul 2009 08:31:08 GMT

Ok, and when i want to test my changes to ui for example, how to start new instance of eclipse with loaded my changed plug in. And if i have changes in the other plug in projects for example in the core or debug, how can i run them in one place, without building jars for every plugin and overriding them in another eclipse folder. I am sorry for the question, this is my first plug in project and i did not find anywhere how to do this.

-------- ÐÑÐÐÐÐÐÐÐÐ ÐÐÑÐÐ --------
ÐÑ: Nitin Dahyabhai
ÐÑÐÐÑÐÐ: Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
ÐÐ: "General discussion of project-wide or architectural issues."

ÐÐÐÑÐÑÐÐÐ ÐÐ: ÐÐÑÐÑÑÑÑÐ, 2009, ÐÐÐ 2 19:27:50 EEST

Actually, all of the folders under sourceediting/pluginsare meant to be individual projects in your workspace. Try checkingthem out as different projects to start with.

Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational

stanimir petrov
Sent by: wtp-dev-bounces@xxxxxxxxxxx

07/02/2009 04:09 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wideor architectural issues."
cc
Subject	Re: Re: [wtp-dev] Run WDT/sourceediting,questions - help!

Thank you very much

I thought so, but i checkout the wtp/sourceediting and i set up it as plugin project. I must select the needed plugins in the new instance from hereWindows > Preferences... > Plug-in Development > Target Platform
But i cannot get it how can i add the not build in jars plugins to thetarget platform. How can i add a set of plugins to the running new instance?

>-------- ÐÑÐÐÐÐÐÐÐÐ ÐÐÑÐÐ --------
>ÐÑ: Nitin Dahyabhai
>ÐÑÐÐÑÐÐ: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
>ÐÐ: wtp-dev@xxxxxxxxxxx
>ÐÐÐÑÐÑÐÐÐ ÐÐ: ÐÑÑÐÐ, 2009, ÐÐÐ 1 23:52:14 EEST

>Dimitar,
>You'll have to keep them as separate plug-ins, otherwise you'll haveto
>change the source code in numerous places to support their extension
>points being declared in a different plug-in than they are currently.I'm
>not sure which overview tab you mean, but it's possible to launch withany
>set of plug-ins you choose.
>
>As for the different _javascript_ plug-ins, org.eclipse.wst._javascript_.*
>were the plug-ins used in WTP 2.0 and earlier, and are no longer
>maintained. WTP 3.0 and later include the org.eclipse.wst.jsdt.*
>plug-ins, which provides more full-featured _javascript_ support andis
>under active development. To illustrate the difference at its mostbasic
>level, org.eclipse.wst._javascript_.* contained no validation of _javascript_
>at all.
>
>Regards,
>---
>Nitin Dahyabhai
>Eclipse WTP Source Editing
>IBM Rational
>
>
>
>
>stanimir petrov
>Sent by: wtp-dev-bounces@xxxxxxxxxxx
>07/01/2009 05:38 AM
>Please respond to
>"General discussion of project-wide or architectural issues."
>
>
>
>To
>wtp-dev@xxxxxxxxxxx
>cc
>
>Subject
>[wtp-dev] Run WDT/sourceediting, questions - help!
>
>
>
>
>
>
> Hi guys
>
>My team is intending to use the WDT/sourceediting module of your pojector
>eventualy extend it. We need to build an studio for _javascript_, html,css,
>xml and so on. It will have custom things consernt to the product,which
>we are developing.
>But before contact the eclipse board to ask for the license agreementor
>making our studio open source, we want to make some tests and builds.
>
>So i search the net and your mail list, but i didn't find anything
>intresting for how to build the project.
>I have checkout the module WDT/sourceediting from your cvs. There aremany
>source folders and packages.
>I found that the implementation of the plugins are actualy in plugins
>folder, devided in many plugins.
>My questions are:
>1)How can i run/bulid all the wanting plugins as one i.e. there are
>org.eclipse.wst.jsdt.ui, org.eclipse.wst.jsdt.core,
>org.eclipse.wst.jsdt.debug and so on. How to run all
>org.eclipse.wst.jsdt.* in new instance of eclipse to test. I can runmay
>be one plugin from the overview tab from "Launch an Eclpise application"
>button, but this may be loads only the selected plugin.
>2)There are org.eclipse.wst.jsdt.* and org.eclipse.wst._javascript_.*
>packages. What is the difference and which i can use for _javascript_.
>
>tnx in adnanced
>Dimitar
>
> _______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>_______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
> _______________________________________________ wtp-dev mailing list wtp-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Content assist behaving oddly for JSPs

nitind@xxxxxxx (Nitin Dahyabhai) — Thu, 02 Jul 2009 16:29:32 GMT

This is usually a last resort kind of option, but try shutting down Eclipse and removing the entire .metadata/.plugins/org.eclipse.jst.jsp.core directory from under your workspace. Any cached JSP information would be in there and will automatically be rebuilt when needed.

Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational

JustJoc
Sent by: wtp-dev-bounces@xxxxxxxxxxx

07/02/2009 04:27 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	wtp-dev@xxxxxxxxxxx
cc
Subject	Re: [wtp-dev] Content assist behaving oddly for JSPs

> I can say that the embedded Java content assist won't work unless > you have the Servlet API on the Java Build Path somehow, and it can > be quirky in cases where no Java Source Folder is set on the project I do have the servlet api on the classpath (from JBoss4.0.3 which we are still stuck on), and content assist does work on new JSP files, just not in existing ones BUT if you open an existing JSP that isn't working with content assist, and re-save it using "save as", content assist works from that point onwards. (save doesn't work, it has to be "save as" and overwrite the original file). This is a good enough work around for now, but does this mean there is some metadata or cache that is being updated by "save as" that isn't changed by save? << JOC >> -- View this message in context:http://www.nabble.com/Content-assist-behaving-oddly-for-JSPs-tp24252444p24303076.htmlSent from the Eclipse WTP - general mailing list archive at Nabble.com. _______________________________________________ wtp-dev mailing list wtp-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!

nitind@xxxxxxx (Nitin Dahyabhai) — Thu, 02 Jul 2009 16:27:52 GMT

Actually, all of the folders under sourceediting/plugins are meant to be individual projects in your workspace. Try checking them out as different projects to start with.

Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational

stanimir petrov
Sent by: wtp-dev-bounces@xxxxxxxxxxx

07/02/2009 04:09 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues."
cc
Subject	Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!

Thank you very much

I thought so, but i checkout the wtp/sourceediting and i set up it as plug in project. I must select the needed plugins in the new instance from here Windows > Preferences... > Plug-in Development > Target Platform
But i cannot get it how can i add the not build in jars plugins to the target platform. How can i add a set of plugins to the running new instance?

>-------- Оригинално писмо --------
>От: Nitin Dahyabhai
>Относно: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
>До: wtp-dev@xxxxxxxxxxx
>Изпратено на: Сряда, 2009, Юли 1 23:52:14 EEST

>Dimitar,
>You'll have to keep them as separate plug-ins, otherwise you'll have to
>change the source code in numerous places to support their extension
>points being declared in a different plug-in than they are currently. I'm
>not sure which overview tab you mean, but it's possible to launch with any
>set of plug-ins you choose.
>
>As for the different _javascript_ plug-ins, org.eclipse.wst._javascript_.*
>were the plug-ins used in WTP 2.0 and earlier, and are no longer
>maintained. WTP 3.0 and later include the org.eclipse.wst.jsdt.*
>plug-ins, which provides more full-featured _javascript_ support and is
>under active development. To illustrate the difference at its most basic
>level, org.eclipse.wst._javascript_.* contained no validation of _javascript_
>at all.
>
>Regards,
>---
>Nitin Dahyabhai
>Eclipse WTP Source Editing
>IBM Rational
>
>
>
>
>stanimir petrov
>Sent by: wtp-dev-bounces@xxxxxxxxxxx
>07/01/2009 05:38 AM
>Please respond to
>"General discussion of project-wide or architectural issues."
>
>
>
>To
>wtp-dev@xxxxxxxxxxx
>cc
>
>Subject
>[wtp-dev] Run WDT/sourceediting, questions - help!
>
>
>
>
>
>
> Hi guys
>
>My team is intending to use the WDT/sourceediting module of your poject or
>eventualy extend it. We need to build an studio for _javascript_, html, css,
>xml and so on. It will have custom things consernt to the product, which
>we are developing.
>But before contact the eclipse board to ask for the license agreement or
>making our studio open source, we want to make some tests and builds.
>
>So i search the net and your mail list, but i didn't find anything
>intresting for how to build the project.
>I have checkout the module WDT/sourceediting from your cvs. There are many
>source folders and packages.
>I found that the implementation of the plugins are actualy in plugins
>folder, devided in many plugins.
>My questions are:
>1)How can i run/bulid all the wanting plugins as one i.e. there are
>org.eclipse.wst.jsdt.ui, org.eclipse.wst.jsdt.core,
>org.eclipse.wst.jsdt.debug and so on. How to run all
>org.eclipse.wst.jsdt.* in new instance of eclipse to test. I can run may
>be one plugin from the overview tab from "Launch an Eclpise application"
>button, but this may be loads only the selected plugin.
>2)There are org.eclipse.wst.jsdt.* and org.eclipse.wst._javascript_.*
>packages. What is the difference and which i can use for _javascript_.
>
>tnx in adnanced
>Dimitar
>
> _______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>_______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
> _______________________________________________ wtp-dev mailing list wtp-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Content assist behaving oddly for JSPs

joconnor@xxxxxxx (JustJoc) — Thu, 02 Jul 2009 08:27:56 GMT

> I can say that the embedded Java content assist won't work unless 
> you have the Servlet API on the Java Build Path somehow, and it can 
> be quirky in cases where no Java Source Folder is set on the project 

I do have the servlet api on the classpath (from JBoss4.0.3 which we are
still stuck on), and content assist does work on new JSP files, just not in
existing ones
BUT
if you open an existing JSP that isn't working with content assist, and
re-save it using "save as", content assist works from that point onwards.
(save doesn't work, it has to be "save as" and overwrite the original file).
This is a good enough work around for now, but does this mean there is some
metadata or cache that is being updated by "save as" that isn't changed by
save?

<< JOC >>
-- 
View this message in context: http://www.nabble.com/Content-assist-behaving-oddly-for-JSPs-tp24252444p24303076.html
Sent from the Eclipse WTP - general mailing list archive at Nabble.com.

Re: Re: [wtp-dev] Run WDT/sourceediting, questions - help!

cristal_reaver@xxxxxxx (stanimir petrov) — Thu, 02 Jul 2009 08:09:21 GMT

Thank you very much

I thought so, but i checkout the wtp/sourceediting and i set up it as plug in project. I must select the needed plugins in the new instance from here Windows > Preferences... > Plug-in Development > Target Platform
But i cannot get it how can i add the not build in jars plugins to the target platform. How can i add a set of plugins to the running new instance?

>-------- ÐÑÐÐÐÐÐÐÐÐ ÐÐÑÐÐ --------
>ÐÑ: Nitin Dahyabhai
>ÐÑÐÐÑÐÐ: Re: [wtp-dev] Run WDT/sourceediting, questions - help!
>ÐÐ: wtp-dev@xxxxxxxxxxx
>ÐÐÐÑÐÑÐÐÐ ÐÐ: ÐÑÑÐÐ, 2009, ÐÐÐ 1 23:52:14 EEST

>Dimitar,
>You'll have to keep them as separate plug-ins, otherwise you'll have to
>change the source code in numerous places to support their extension
>points being declared in a different plug-in than they are currently. I'm
>not sure which overview tab you mean, but it's possible to launch with any
>set of plug-ins you choose.
>
>As for the different _javascript_ plug-ins, org.eclipse.wst._javascript_.*
>were the plug-ins used in WTP 2.0 and earlier, and are no longer
>maintained. WTP 3.0 and later include the org.eclipse.wst.jsdt.*
>plug-ins, which provides more full-featured _javascript_ support and is
>under active development. To illustrate the difference at its most basic
>level, org.eclipse.wst._javascript_.* contained no validation of _javascript_
>at all.
>
>Regards,
>---
>Nitin Dahyabhai
>Eclipse WTP Source Editing
>IBM Rational
>
>
>
>
>stanimir petrov
>Sent by: wtp-dev-bounces@xxxxxxxxxxx
>07/01/2009 05:38 AM
>Please respond to
>"General discussion of project-wide or architectural issues."
>
>
>
>To
>wtp-dev@xxxxxxxxxxx
>cc
>
>Subject
>[wtp-dev] Run WDT/sourceediting, questions - help!
>
>
>
>
>
>
> Hi guys
>
>My team is intending to use the WDT/sourceediting module of your poject or
>eventualy extend it. We need to build an studio for _javascript_, html, css,
>xml and so on. It will have custom things consernt to the product, which
>we are developing.
>But before contact the eclipse board to ask for the license agreement or
>making our studio open source, we want to make some tests and builds.
>
>So i search the net and your mail list, but i didn't find anything
>intresting for how to build the project.
>I have checkout the module WDT/sourceediting from your cvs. There are many
>source folders and packages.
>I found that the implementation of the plugins are actualy in plugins
>folder, devided in many plugins.
>My questions are:
>1)How can i run/bulid all the wanting plugins as one i.e. there are
>org.eclipse.wst.jsdt.ui, org.eclipse.wst.jsdt.core,
>org.eclipse.wst.jsdt.debug and so on. How to run all
>org.eclipse.wst.jsdt.* in new instance of eclipse to test. I can run may
>be one plugin from the overview tab from "Launch an Eclpise application"
>button, but this may be loads only the selected plugin.
>2)There are org.eclipse.wst.jsdt.* and org.eclipse.wst._javascript_.*
>packages. What is the difference and which i can use for _javascript_.
>
>tnx in adnanced
>Dimitar
>
> _______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>_______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
>

Re: [wtp-dev] Content assist behaving oddly for JSPs

nitind@xxxxxxx (Nitin Dahyabhai) — Wed, 01 Jul 2009 21:21:05 GMT

JustJoc wrote:

Is there anywhere else in particular I should look for logs relevant to this
area of eclipse?

No, that's the right place. Without knowing more about the specifics, I couldn't tell you why JSP content assist isn't working. I can say that the embedded Java content assist won't work unless you have the Servlet API on the Java Build Path somehow, and it can be quirky in cases where no Java Source Folder is set on the project (there's a bug reported for that already). For finding and using tag libraries, the editor expects they either be in Jar files visible on the project's Java Build Path, or that the WEB-INF folder's parent folder is a parent folder of the JSP file and the tag library, or that you've formally defined the deployment layout using the .settings/org.eclipse.wst.common.component file and have the ModuleCoreNature on the project.

--
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational

Re: [wtp-dev] JSDT InferEngine issues

cmjaun@xxxxxxx (Christopher Jaun) — Wed, 01 Jul 2009 21:04:35 GMT

HI Anselm,

You are correct in stating that we do not have a good way to infer the type of parameter 'x' in a statement such as...

serach.find(a, function(x) {x....});

I did find that if I do something like this....

serach.find(a, /** @param {Date} x */ function(x) {x....})

.... it does correctly infer that x is a type Date. Though we would not expect an end user to be writing code with JSdoc nested in it like in the above example, so its not really a solution for your scenario.

This does sound like a case where we would want metadata in a library to specify that a function takes a function as a parameter(which we can do now) and also specify the parameter values of that function, which I don't believe is possible right now.

Unless I'm missing something this does not sound like a case where you'd need to create a custom extension to the inference engine. My understanding is that your library is just plain _javascript_. Is that correct? If additional work is needed to infer the parameters types of a parameter function that sounds like an enhancement for the default _javascript_ inference engine.

We would welcome any contributions you may be able to provide in this area. Sounds like your already have a good understanding of the inference engine. :-)

Thanks,
Chris

">Anselm R Garbe

Anselm R Garbe

Sent by: wtp-dev-bounces@xxxxxxxxxxx

07/01/2009 11:11 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues."
cc
Subject	Re: [wtp-dev] JSDT InferEngine issues

Hi, as a follow up to the earlier discussion I have some other questions, which also provide more detail about what I'm trying to achieve with the InferEngine and the APIs I'm going to expose. Imagine the following API specified in WebIDL: module search { interface SearchResult { attribute long size; DOMString elementAt(in long i); }; [Callback] interface SearchSuccessCallback { void onSuccess(in ResultArray result); }; [Callback] interface SearchErrorCallback { void onError(in Error error); }; [NoInterfaceObject] interface SearchEngine { void find(in DOMString pattern, in SearchSuccessCallback sc, in SearchErrorCallback ec); }; }; When editing some _javascript_ code with an imagined JSDoc'ed JS library out of this WebIDL, there'll be a global member with the name "search" that itself will expose a method "find". So when typing search.findCtrl+Space the editor will correctly expand to something like search.find(x, y, z) however what I intend to achieve is the following: search.find("foo", function(x) { x.Ctrl+Space and here I'd like to see that x actually exposes the attribute "size" and the method "elementAt". If the [Callback] attribute on the WebIDL interface wouldn't be there, similiarly I want to achieve that search.find("foo", { onSuccess: function(x) {x.Ctrl+Space exposes "size" and "elementAt" as well. The problem I'm facing is, that as far as I understand the AST model and JSDoc syntax processing supported so far, there is no abstraction for a function type argument yet that itself refers to a specific InferredType that provides the glue to the SearchResult interface in the given example. This lack in the JSDoc parsing made me think perhaps I can achieve that with sub-classing the InferEngine natively. Though, when looking at how InferredType is designed atm, I think it won't be possible, because first of all InferEngine.FunctionType is fixed (I can't manipulate InferredType.superClass member on a case by case basis and secondly that won't be sufficient at all, because I'd need to have a InferredType.parent member that references to the exemplified SearchResult InferredType instead. Or am I missing something? So assumed I'd have extended the InferEngine mechanism to provide such extended inference as I'm looking for (of course I'll contribute that portions of code back to you), the main question for me that would remain is, what's your preference on the library input side? I can see two options: a) Keep the JSDoc parsing as is and only provide the extended inference support for implementations that use the inferrenceSupport extension point and feed the extended inference info natively into the AST b) Extend the JSDoc parsing with more metadata (not sure about the details yet), in order to provide the extended inference support just on top of the existing mechanism I think you'd prefer b) pretty much. For me this is an important decision, because it'll effect how such extended inference support is implemented. If you agrre that b) would be the right way to go, there might be no reason for me at all to implement my sub-classed InferEngine at all, but just to contribute the extended changes to the existing implementation back to you, in the hope you will accept that ;) Or my ideal case would be, someone else is already working on this ;) What's your view on this? Kind regards, Anselm _______________________________________________ wtp-dev mailing list wtp-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Run WDT/sourceediting, questions - help!

nitind@xxxxxxx (Nitin Dahyabhai) — Wed, 01 Jul 2009 20:52:17 GMT

Dimitar,
You'll have to keep them as separate plug-ins, otherwise you'll have to 
change the source code in numerous places to support their extension 
points being declared in a different plug-in than they are currently.  I'm 
not sure which overview tab you mean, but it's possible to launch with any 
set of plug-ins you choose.

As for the different JavaScript plug-ins, org.eclipse.wst.javascript.* 
were the plug-ins used in WTP 2.0 and earlier, and are no longer 
maintained.  WTP 3.0 and later include the org.eclipse.wst.jsdt.* 
plug-ins, which provides more full-featured JavaScript support and is 
under active development.  To illustrate the difference at its most basic 
level, org.eclipse.wst.javascript.* contained no validation of JavaScript 
at all.

Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational




stanimir petrov  
Sent by: wtp-dev-bounces@xxxxxxxxxxx
07/01/2009 05:38 AM
Please respond to
"General discussion of project-wide or architectural issues." 



To
wtp-dev@xxxxxxxxxxx
cc

Subject
[wtp-dev] Run WDT/sourceediting, questions - help!






  Hi guys

My team is intending to use the WDT/sourceediting module of your poject or 
eventualy extend it. We need to build an studio for javascript, html, css, 
xml and so on. It will have custom things consernt to the product, which 
we are developing.
But before contact the eclipse board to ask for the license agreement or 
making our studio open source, we want to make some tests and builds.

So i search the net and your mail list, but i didn't find anything 
intresting for how to build the project.
I have checkout the module WDT/sourceediting from your cvs. There are many 
source folders and packages.
I found that the  implementation of the plugins are actualy in plugins 
folder, devided in many plugins. 
My questions are:
1)How can i run/bulid all the wanting plugins as one i.e. there are 
org.eclipse.wst.jsdt.ui, org.eclipse.wst.jsdt.core, 
org.eclipse.wst.jsdt.debug and so on. How to run all 
org.eclipse.wst.jsdt.* in new instance of eclipse to test. I can run may 
be one plugin from the overview tab from "Launch an Eclpise application" 
button, but this may be loads only the selected plugin.
2)There are org.eclipse.wst.jsdt.* and org.eclipse.wst.javascript.* 
packages. What is the difference and which i can use for javascript.

tnx in adnanced
Dimitar

 _______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JSDT InferEngine issues

garbeam@xxxxxxx (Anselm R Garbe) — Wed, 01 Jul 2009 15:11:04 GMT

Hi,


as a follow up to the earlier discussion I have some other questions,
which also provide more detail about what I'm trying to achieve with
the InferEngine and the APIs I'm going to expose.

Imagine the following API specified in WebIDL:

module search {

  interface SearchResult {
    attribute long size;
    DOMString elementAt(in long i);
  };

  [Callback] interface SearchSuccessCallback {
     void onSuccess(in ResultArray result);
  };

  [Callback] interface SearchErrorCallback {
    void onError(in Error error);
  };

  [NoInterfaceObject] interface SearchEngine {
    void find(in DOMString pattern, in SearchSuccessCallback sc, in
SearchErrorCallback ec);
  };

};


When editing some JavaScript code with an imagined JSDoc'ed JS library
out of this WebIDL, there'll be a global member with the name "search"
that itself will expose a method "find". So when typing

  search.findCtrl+Space the editor will correctly expand to something like

  search.find(x, y, z)

however what I intend to achieve is the following:

  search.find("foo", function(x) {
           x.Ctrl+Space

and here I'd like to see that x actually exposes the attribute "size"
and the method "elementAt". If the [Callback] attribute on the WebIDL
interface wouldn't be there, similiarly I want to achieve that

  search.find("foo", { onSuccess: function(x) {x.Ctrl+Space

exposes "size" and "elementAt" as well.


The problem I'm facing is, that as far as I understand the AST model
and JSDoc syntax processing supported so far, there is no abstraction
for a function type argument yet that itself refers to a specific
InferredType that provides the glue to the SearchResult interface in
the given example.

This lack in the JSDoc parsing made me think perhaps I can achieve
that with sub-classing the InferEngine natively. Though, when looking
at how InferredType is designed atm, I think it won't be possible,
because first of all InferEngine.FunctionType is fixed (I can't
manipulate InferredType.superClass member on a case by case basis and
secondly that won't be sufficient at all, because I'd need to have a
InferredType.parent member that references to the exemplified
SearchResult InferredType instead. Or am I missing something?

So assumed I'd have extended the InferEngine mechanism to provide such
extended inference as I'm looking for (of course I'll contribute that
portions of code back to you), the main question for me that would
remain is, what's your preference on the library input side?

I can see two options:

a) Keep the JSDoc parsing as is and only provide the extended
inference support for implementations that use the inferrenceSupport
extension point and feed the extended inference info natively into the
AST

b) Extend the JSDoc parsing with more metadata (not sure about the
details yet), in order to provide the extended inference support just
on top of the existing mechanism

I think you'd prefer b) pretty much. For me this is an important
decision, because it'll effect how such extended inference support is
implemented. If you agrre that b) would be the right way to go, there
might be no reason for me at all to implement my sub-classed
InferEngine at all, but just to contribute the extended changes to the
existing implementation back to you, in the hope you will accept that
;)

Or my ideal case would be, someone else is already working on this ;)

What's your view on this?

Kind regards,
Anselm

[wtp-dev] Run WDT/sourceediting, questions - help!

cristal_reaver@xxxxxxx (stanimir petrov) — Wed, 01 Jul 2009 09:38:07 GMT

Hi guys

My team is intending to use the WDT/sourceediting module of your poject or eventualy extend it. We need to build an studio for _javascript_, html, css, xml and so on. It will have custom things consernt to the product, which we are developing.
But before contact the eclipse board to ask for the license agreement or making our studio open source, we want to make some tests and builds.

So i search the net and your mail list, but i didn't find anything intresting for how to build the project.
I have checkout the module WDT/sourceediting from your cvs. There are many source folders and packages.
I found that the implementation of the plugins are actualy in plugins folder, devided in many plugins.
My questions are:
1)How can i run/bulid all the wanting plugins as one i.e. there are org.eclipse.wst.jsdt.ui, org.eclipse.wst.jsdt.core, org.eclipse.wst.jsdt.debug and so on. How to run all org.eclipse.wst.jsdt.* in new instance of eclipse to test. I can run may be one plugin from the overview tab from "Launch an Eclpise application" button, but this may be loads only the selected plugin.
2)There are org.eclipse.wst.jsdt.* and org.eclipse.wst._javascript_.* packages. What is the difference and which i can use for _javascript_.

tnx in adnanced
Dimitar