Okay, I understand. The NextGenAS extension supports only a single project
per window right now, and the asconfig.json must appear in the root
directory. If you need to have multiple projects open at the same time,
you'll need to open multiple windows.
- Josh
On Mon, Jan 30, 2017 at 8:54 AM, Harbs <harbs.li...@gmail.com> wrote:
> Try adding “projects” to VS Code as a project.
>
> > On Jan 30, 2017, at 6:14 PM, Josh Tynjala <joshtynj...@gmail.com> wrote:
> >
> > What specifically do you mean when you say "adding all full project
> folder"?
> >
> > - Josh
> >
> > On Mon, Jan 30, 2017 at 5:15 AM, Harbs <harbs.li...@gmail.com> wrote:
> >
> >> I just added a bunch of asconfig files to the projects.
> >>
> >> The individual projects now get proper intellisense. Adding all full
> >> project folder causes an error and the code is not properly analyzed.
> I’m
> >> not sure if it’s just too heavy for the extension…
> >>
> >>> On Jan 30, 2017, at 1:31 PM, Harbs <harbs.li...@gmail.com> wrote:
> >>>
> >>> Huh. Now the errors went away…
> >>>
> >>> Weird.
> >>>
> >>>> On Jan 30, 2017, at 12:15 PM, Harbs <harbs.li...@gmail.com> wrote:
> >>>>
> >>>> It works in HTMLClasses.as, (in the HTML project) but any other file
> >> gives me a “Can not resolve” error.
> >>>>
> >>>> Actually: I’m only getting errors for blocks, but COMPILE statements
> on
> >> functions don’t cause VS Code to complain.
> >>>>
> >>>>
> >>>>
> >>>>> On Jan 30, 2017, at 12:03 PM, Harbs <harbs.li...@gmail.com> wrote:
> >>>>>
> >>>>> I had tried that and it did not work. I just realized that I put it
> in
> >> the wrong place.
> >>>>>
> >>>>> This works:
> >>>>>
> >>>>> {
> >>>>> "config": "flex",
> >>>>> "type": "lib",
> >>>>> "compilerOptions": {
> >>>>> "debug": true,
> >>>>> "define": [
> >>>>> {
> >>>>> "name": "COMPILE::SWF",
> >>>>> "value": true
> >>>>> },
> >>>>> {
> >>>>> "name": "COMPILE::JS",
> >>>>> "value": true
> >>>>> }
> >>>>> ]
> >>>>> },
> >>>>> "files":
> >>>>> [
> >>>>> "src/main/flex/HTMLClasses.as"
> >>>>> ]
> >>>>> }
> >>>>>
> >>>>>
> >>>>>> On Jan 29, 2017, at 7:36 PM, Josh Tynjala <joshtynj...@gmail.com>
> >> wrote:
> >>>>>>
> >>>>>> You can add the define compilerOption to your asconfig.json for
> >> CONFIG::JS
> >>>>>> and CONFIG::SWF.
> >>>>>>
> >>>>>> - Josh
> >>>>>>
> >>>>>> On Jan 29, 2017 4:09 AM, "Harbs" <harbs.li...@gmail.com> wrote:
> >>>>>>
> >>>>>> I have not had success with Maven outside VS Code, and using the
> Maven
> >>>>>> build inside VS Code prompts me to accept an EULA. I don’t know how
> to
> >>>>>> accept inside the VS Code output.
> >>>>>>
> >>>>>> I’m also having issues with VS Code not recognizing COMPILE::JS and
> >>>>>> COMPLIE::SWF as valid.
> >>>>>>
> >>>>>>
> >>>>>>> On Jan 29, 2017, at 1:33 PM, Carlos Rovira <
> >> carlos.rov...@codeoscopic.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi Harbs,
> >>>>>>>
> >>>>>>> I'm using VSCode with NextGenAs for framework development.
> >>>>>>>
> >>>>>>> You have the wiki as main docs:
> >>>>>>> https://github.com/BowlerHatLLC/vscode-nextgenas/wiki
> >>>>>>>
> >>>>>>> I recommend you to use Maven over ANT since development is a breeze
> >> in
> >>>>>> this
> >>>>>>> way. You can have a VSCode window with one library (i.e:HTML,
> >> MDL,...) ,
> >>>>>>> make changes and build with CTRL+CMD+B using maven
> >>>>>>> You can have other separate window with your project and make
> >> changes and
> >>>>>>> operate the same way and you're ready to test in browser.
> >>>>>>>
> >>>>>>> Some things to take account:
> >>>>>>>
> >>>>>>> 1.- You can create a maven "distribution" to have a fresh SDK with
> >> your
> >>>>>>> latest changes and use it in VSCode:
> >>>>>>>
> >>>>>>> (see
> >>>>>>> https://cwiki.apache.org/confluence/display/FLEX/
> >>>>>> Building+FlexJS+with+Maven)
> >>>>>>>
> >>>>>>> For example I write: mvn -s settings-template.xml
> >>>>>>> -DdistributionTargetFolder=/Users/carlosrovira/Dev/Flex/
> >>>>>> sdks/apache-flexjs-0.8.0
> >>>>>>> -P build-distribution clean install
> >>>>>>>
> >>>>>>> and in VSCode:
> >>>>>>>
> >>>>>>> "nextgenas.sdk.editor":
> >>>>>>> "/Users/carlosrovira/Dev/Flex/sdks/apache-flexjs-0.8.0"
> >>>>>>>
> >>>>>>> (this needs a reload of VSCode, hope Josh read this and could get
> >> some way
> >>>>>>> that VSCode notice the sdk change, or have some reload button...
> >>>>>>>
> >>>>>>>
> >>>>>>> 2.- In your library and project you can use write in
> >> .vscode/tasks.json to
> >>>>>>> get CTRL+CMD+B to build (pass maven) in each project
> >>>>>>>
> >>>>>>> {
> >>>>>>> // See https://go.microsoft.com/fwlink/?LinkId=733558
> >>>>>>> // for the documentation about the tasks.json format
> >>>>>>> "version": "0.1.0",
> >>>>>>> "command": "mvn",
> >>>>>>> "args": ["clean", "install", "-DskipTests"],
> >>>>>>> "isShellCommand": true,
> >>>>>>> "showOutput": "always"
> >>>>>>> }
> >>>>>>>
> >>>>>>>
> >>>>>>> Let me know if you have some issues or need something more
> >>>>>>>
> >>>>>>> Carlos
> >>>>>>>
> >>>>>>>
> >>>>>>> 2017-01-29 10:52 GMT+01:00 Harbs <harbs.li...@gmail.com>:
> >>>>>>>
> >>>>>>>> I assume this question is aimed at Josh, but if anyone else has an
> >>>>>> answer,
> >>>>>>>> please pipe up…
> >>>>>>>>
> >>>>>>>> I’d really like to use VS Code for work on the FlexJS framework. I
> >>>>>> managed
> >>>>>>>> to setup a project for development of an app, but I’m not sure
> what
> >>>>>>>> settings to use for framework development.
> >>>>>>>>
> >>>>>>>> Ideally, there should be a way to have VS Code understand each
> >> project
> >>>>>>>> separately and be able to build everything together.
> >>>>>>>>
> >>>>>>>> It’s not a big deal if we need to use the command line to build
> >>>>>> everything
> >>>>>>>> though. I can deal with separate projects for each one.
> >>>>>>>>
> >>>>>>>> Any pointers?
> >>>>>>>>
> >>>>>>>> Harbs
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>>
> >>>>>>> Carlos Rovira
> >>>>>>> Director General
> >>>>>>> M: +34 607 22 60 05
> >>>>>>> http://www.codeoscopic.com
> >>>>>>> http://www.avant2.es
> >>>>>>>
> >>>>>>> Este mensaje se dirige exclusivamente a su destinatario y puede
> >> contener
> >>>>>>> información privilegiada o confidencial. Si ha recibido este
> mensaje
> >> por
> >>>>>>> error, le rogamos que nos lo comunique inmediatamente por esta
> misma
> >> vía y
> >>>>>>> proceda a su destrucción.
> >>>>>>>
> >>>>>>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> >>>>>> comunicamos
> >>>>>>> que sus datos forman parte de un fichero cuyo responsable es
> >> CODEOSCOPIC
> >>>>>>> S.A. La finalidad de dicho tratamiento es facilitar la prestación
> del
> >>>>>>> servicio o información solicitados, teniendo usted derecho de
> acceso,
> >>>>>>> rectificación, cancelación y oposición de sus datos dirigiéndose a
> >>>>>> nuestras
> >>>>>>> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
> >> documentación
> >>>>>>> necesaria.
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>
