I added an extra asconfig.json file at the project folder level. That seemed to
sort-of work until I added too many projects to that.
> On Jan 30, 2017, at 6:58 PM, Josh Tynjala wrote:
>
> Okay, I understand. The NextGenAS extension supports only a single project
> per window right now, and the
Try adding “projects” to VS Code as a project.
> On Jan 30, 2017, at 6:14 PM, Josh Tynjala 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 wrote:
>
>> I just added a bunch of asconfig files to the p
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, Harb
What specifically do you mean when you say "adding all full project folder"?
- Josh
On Mon, Jan 30, 2017 at 5:15 AM, Harbs 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 a
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 wrote:
Huh. Now the errors went away…
Weird.
> On Jan 30, 2017, at 12:15 PM, Harbs 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 caus
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 wrote:
>
> I had tried that and i
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
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" 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
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
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
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 sh
12 matches
Mail list logo
