search

HaxeFoundation / intellij-haxe

Haxe plugin for IntelliJ Platform based IDEs (IDEA, Android-Studio)
http://intellij-haxe.org
Apache License 2.0
222 stars 99 forks source link

Name of autogenerated dependency (Haxelib) #102

Open boozook opened 9 years ago

boozook commented 9 years ago

Plugin version: latest build.

Currently we have a path as name of library. Name we can get from haxelib.json. screen shot 2015-01-11 at 17 54 43 On the screenshot second library was automatically generated by mention in build.hxml.

as3boyan commented 9 years ago

We already have name, we can extract version number from path, but currently, more important is to store information that that lib was added automatically(mark it somehow) and path to lib. Path should be stored also in lib classpaths, so it may be changed to haxelib|Signal 1.0.0 if it will work in a proper way.

boozook commented 9 years ago

You can save any info (like settings) in .idea directory as any file.

On 13 ÿíâ. 2015 ã., at 22:01, as3boyan notifications@github.com wrote:

We already have name, we can extract version number from path, but currently, more important is to store information that that lib was added automatically(mark it somehow) and path to lib. Path should be stored also in lib classpaths, so it may be changed to haxelib|Signal 1.0.0 if it will work in a proper way.

— Reply to this email directly or view it on GitHub.

as3boyan commented 9 years ago

Good, but I would prefer something like storing such data in some data attribute of library if there is such.

EBatTiVo commented 9 years ago

So, marking it with "haxelib|" is good enough to know that it was added automatically. Whether we use a path or a name to display is really irrelevant to it's functioning; it's a nicety for the user.

So, is the request here simply to use the nice name and leave the "haxelib|" intact, or is it to remove even that marking?