You should try VSCode! Ever since I heard about VSCode (on this list) a [code editor] dream has come true for me! It’s fast, open source, lots of extensions, and fits like an F16 fits a pilot — you just become one with it.
And with Josh’s NextGenAS extension it will be even better. I’ve used IntelliJ IDEA for years and I’m personally fed up with their lack of support for everything AS3/Flex/FlexJS. They don’t even get basic things like syntax coloring for AS3/Flex working reliably. Josh OTOH is not only listening and responding, but he’s also in the same boat with the rest of us — can’t get any better than that! :) -Christian > On Dec 2, 2016, at 2:29 AM, Hans Nuecke <hnue...@vservu.de> wrote: > > OK, then I'll give it a try with VS Code ;-) > > Perhaps later I'll end up with a mix to get the best out of both worlds? > Future will tell > > Hans > > > Am 01.12.2016 um 23:46 schrieb Josh Tynjala: >> IntelliJ IDEA works great for projects that target the Flash runtimes, but >> its debugger doesn't work with ActionScript transpiled to JavaScript. You >> can only debug the generated JavaScript. Not even source maps help. The >> generated JavaScript isn't all that different from the ActionScript, so >> it's not terrible, but it's not ideal either. In VSCode, source maps are >> fully supported, and you can use VSCode's integrated debugger with the >> original ActionScript when running in Chrome, Firefox, and Node.js (those >> are the ones I've personally tried, but other browsers may work too). >> >> Debugging SWFs in VScode isn't possible yet, but that's the next big thing >> on my TODO list. Once I get that up and running, I'm going to try >> developing my Flash projects in VSCode full time and switch away from >> IntelliJ IDEA. >> >> - Josh >> >> >> On Thu, Dec 1, 2016 at 2:31 PM, Hans Nuecke <hnue...@vservu.de> wrote: >> >>> Hi Josh, >>> >>> compliments to what you've already achieved. Looks promising and I'm >>> considering giving it a try, when I'll start porting an AS3 project to >>> Javascript. >>> >>> The first project will be pure AS3, but I have another project in mind >>> that makes heavy use of Flex and would be a nice candidate to test FlexJS. >>> >>> So far I considered Typescript and most probably React as framework for >>> the first project; perhaps together with Pixi (if I do not continue using a >>> JS library that actually does most of the display list related things). >>> >>> But something like continuing developing in AS3 and then "simply" convert >>> it to JS sounds too nice to be true. >>> >>> But if I understood things about NextGenAS correctly, that could be >>> possible. No sure how to handle dozens of classes, but I'll find out. >>> >>> Before I dive into all that, I have a short question you hopefully can >>> answer: >>> >>> You focus on VS Code as IDE. I'm used to IntelliJ IDEA, and prefer using >>> that. >>> >>> I know you're an IntelliJ user also and iIrc you even plan a video about >>> that topic. >>> >>> So what is your recommended approach for me? >>> >>> Thanks and regards >>> >>> Hans >>> >>> >>> >>> Am 01.12.2016 um 21:47 schrieb Josh Tynjala: >>> >>>> VSCode doesn't really have its own concept of project templates. I think >>>> Microsoft recommends using something like Yeoman. http://yeoman.io/ >>>> >>>> That said, VSCode extensions can add commands to the Ctrl+Shift+P command >>>> palette. For instance, the NextGenAS extension has a custom command to >>>> generate a tasks.json file that runs asconfigc. I think it would be >>>> possible for an extension to add a command that creates and populates a >>>> set >>>> of files as a way to generate a new project. There are a few options for >>>> displaying simple UI (pick from a list of options, choose a file, show an >>>> alert bar with a few buttons), so the wizard could ask a few questions in >>>> the process. >>>> >>>> - Josh >>>> >>>> On Thu, Dec 1, 2016 at 12:29 PM, Harbs <harbs.li...@gmail.com> wrote: >>>> >>>> That would be perfect. Automatically adding imports is something I’m >>>>> really missing in VS Code. >>>>> >>>>> “Organize imports” is another item that would be really nice to have. >>>>> >>>>> “Command 1” is something else I use in Flash Builder regularly. >>>>> Generating getters and setters from variables is a great time saver. >>>>> (Other >>>>> quick fixes too) >>>>> >>>>> I’m really pumped up about your extension. Good tooling for FlexJS is >>>>> really important IMO, and tooling built around a modern editor with >>>>> features like multi-selection, etc. is great. >>>>> >>>>> What would be involved in having templates for different project types? >>>>> Is >>>>> that something that’s do-able in VS Code? >>>>> >>>>> Harbs >>>>> >>>>> On Dec 1, 2016, at 5:38 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: >>>>> >>>>> Yeah, the "code actions" are pretty cool as a way to provide automated >>>>>> fixes for errors and warnings. I hope to find more places to add those. >>>>>> >>>>> As >>>>> >>>>>> for imports, the newest language server protocol will finally allow me >>>>>> to >>>>>> add imports automatically when IntelliSense completes a type name, so >>>>>> I'm >>>>>> looking forward to upgrading the library and implementing that feature. >>>>>> >>>>>> - Josh >>>>>> >>>>>> On Dec 1, 2016 12:02 AM, "Harbs" <harbs.li...@gmail.com> wrote: >>>>>> >>>>>> I tried to comment on your Patreon post, but Patreon is not letting me >>>>>>> login in for some reason. >>>>>>> >>>>>>> It looks really good! Big improvement! >>>>>>> >>>>>>> The help tip to add imports is really helpful as well! >>>>>>> >>>>>>> Thanks for your great work! >>>>>>> >>>>>>> Harbs >>>>>>> >>>>>>> On Dec 1, 2016, at 12:10 AM, Josh Tynjala <joshtynj...@gmail.com> >>>>>>> >>>>>> wrote: >>>>>> Hello, Flex community! >>>>>>>> A couple of months ago, I introduced a new extension for the Visual >>>>>>>> >>>>>>> Studio >>>>>>> >>>>>>>> Code text editor that adds language support for ActionScript. The >>>>>>>> >>>>>>> extension >>>>>>> >>>>>>>> includes tons of code intelligence features for ActionScript, like >>>>>>>> IntelliSense, find all references, goto definition, variable renaming, >>>>>>>> >>>>>>> and >>>>>>> >>>>>>>> more. >>>>>>>> >>>>>>>> I didn't officially announce the project to the Apache Flex community >>>>>>>> >>>>>>> right >>>>>>> >>>>>>>> away because, at the time, the extension only supported ActionScript, >>>>>>>> >>>>>>> and I >>>>>>> >>>>>>>> hadn't started yet on MXML features. As we all know, MXML is pretty >>>>>>>> >>>>>>> vital >>>>>> for Flex applications! >>>>>>>> Today, I'm happy to announce that the newest version of the NextGen >>>>>>>> ActionScript extension for Visual Studio Code includes all the same >>>>>>>> >>>>>>> great >>>>>> features for MXML. You can install the extension right inside Visual >>>>>>> Studio >>>>>>> >>>>>>>> Code. Simply search for "NextGen ActionScript" in the Extensions view. >>>>>>>> >>>>>>>> For more information about the NextGenAS extension, visit the website: >>>>>>>> >>>>>>>> https://nextgenactionscript.com/vscode/ >>>>>>>> >>>>>>>> For instructions about how to create a new project, set up the >>>>>>>> >>>>>>> compiler, >>>>>> and even debug Apache FlexJS apps in a web browser, visit the Github >>>>>>> wiki: >>>>>>> >>>>>>>> https://github.com/BowlerHatLLC/vscode-nextgenas/wiki >>>>>>>> >>>>>>>> With the community's help, I can continue working on useful developer >>>>>>>> >>>>>>> tools >>>>>>> >>>>>>>> for ActionScript and MXML. Please join my Patreon campaign to lend a >>>>>>>> >>>>>>> hand! >>>>>>> >>>>>>>> https://www.patreon.com/josht >>>>>>>> >>>>>>>> Thank you, and happy coding! >>>>>>>> >>>>>>>> Josh Tynjala >>>>>>>> NextGen ActionScript >>>>>>>> >>>>>>>> Note: I am an Apache Flex committer and PMC member, but this VSCode >>>>>>>> extension is not an Apache project. Today, I am simply posting as a >>>>>>>> >>>>>>> member >>>>>>> >>>>>>>> of the community who wants to share a cool, independent project that >>>>>>>> >>>>>>> others >>>>>>> >>>>>>>> might enjoy. >>>>>>>> >>>>>>> >
