Intellisense issues with Beta 6 + some nice to have suggestions.

[frank]

I am working with Amethyst for a week and I am finding it a life saver for my action scripts projects.
Great Job!

I have found also an annoying issue with the intellisense:

If you have a line of code like:

a.myproperty = "hello";

and you realize that "hello" should be assigned to "mysecondproperty" rather than "myproperty", if you delete the word "myproperty" and trigger again the intellisense having the cursor after the fullstop but before "= "hello";" the intellisense gets confused and if you select any property it replaces the variable with the property that you have selected leaving you with a line like:

mysecondproperty. = "hello";

I have a nice to have:

1) An entry inside project settings for the default namespace.
1b) When I create a folder with a sub folder, if I create a new action script class in it it would be nice to have the class created with the package directive pointing at the base namespace concatenated to the path that correspond to the folders path (like C# does).

E.g.

If I have a project with a default namespace "myproj" and I create a folder called "ui" that has inside another folder called "components". If I click on the folder "components" and I create a new actionscript class inside it.
It will be nice to find the package directive like this:
package myproj.ui.components {

   public class Class1 {
   
      public function Class1 () {
      }
   
   }

}

Right now the only work around is to create the class outside the folder and dragging it inside after the creation so that visual studio add the package namespace path automatically.

Anyway these are my 2 cents for an already excellent tool for the Actionscript/Flex developer's community.

Frank

[Dermot]

Thanks for the feedback ...


We've done a whole lot of gremlin fixing in the IntelliSense and I've fixed that one  - I've just tested it again to make sure .

The next beta does 1b) but why do you want a default namespace? I can do it easily - but I cant quite see how you would use it. The Flex compilers use the package to locate the file one disk. So a package like 'myproj.ui.components' would  locate the file in the directory 'myproj\ui\components'. The root directory is given to the compiler
by the 'Main source folder' and this is typically 'src' but you can set it to whaever you like (e.g. 'myproj').

Dermot

[frank]

Hello Dermot,

The next beta does 1b) but why do you want a default namespace? I can do it easily - but I cant quite see how you would use it.

That was mostly a minor convenience because I usually keep separate projects for different set of classes and everytime I have a bunch of empty folders in my projects.

For example:
One VS project can contain a set of classes inside "mynamespace.UI" and another set of classes inside "mynamespace.network" while another VS project can contain a set of classes inside "mynamespace.flashUI".

If I am in this kind of situation, usually, I have to create the projects with an empty folder called mynamespace and have my classes inside the subfolders.

Having the possibility to specify the root will give me the possibility to save the VS projects inside the folder "mynamespace" (or getting rid completely of complex structures of empty nested folders) and having just folders that contain the classes in my projects.
Usually the compiler doesn't complain if I am working with classes inside the same namespace and the folder scope is not starting from the root of the namespace path.

Like I said this is mostly a minor convenience to me (and probably I am really used to it because C# allows me to do that  ) but the most important feature was 1b) and I am glad that you have fixed it.

Do you have already a date scheduled for the release of the intellisense fixes?
If not anytime soon, are you accepting an extra tester? 

Thanks,
Frank

[frank]

Hello,
Amethyst seems to act weird when no folder is specified for the option "Main Source Folder".
When I create a class in a subfolder of the root it works correctly creating the code with the correct namespace but if I create a new class inside a folder that is a child folder of the folder in the root a blank file gets created.
It seems that the folder with an odd position from the route are working while the even ones aren't.

Speaking of intellisense... strange things happen with the import statement...
1. If I type "import fl.sh" another line gets created with "import flash"
2. If I type "import fl.video.FLVPlayback" a duplicated line appear below it. This is not happen always but with certain classes from adobe a certain classes that I have made in some projects.

Frank

[frank]

I have noticed that if I create a function inside a class that return an instance of the same class that I am editing (like when you create the static function CreateInstance in a singleton implementation) the intellisense add an import that includes the class that you are editing.

I don't know if this can lead to problems but in the best case I think that it is redundant.

Frank

[Dermot]

Thanks - I'll fix it. (trac #205).

I've added the odd behaviour with Main source Folder to Trac as well  (#206).

I'll fix these before our next 'edge' release (hopefully sometime in the next week).

Dermot

[frank]

That's great!

Thanks a lot,
Frank