Clean up package / naming redundancies

[misterpah]

Clean up package / naming redundancies

[gamedevsam]

Or at least have meaningful package structure, like: ui.NewProject, or core.Compiler

[misterpah]

@gamedevsam : the prefix "plugin" are for grouping. this way, Developer can choose to code in HaxeJS target, pure Javascript or both.

the package name (similar to android) are to reduce plugin duplication. by entering name to the plugin name, it (somewhat) become an unique plugin.

for the lister, it's my practice to include the event's name so that it can be easily traced to the origin. Although it's best to follow the best practice, it (event's name) can be anything.
hmm.. maybe i add a wrapper as it is redundant / repeatable code.

for folder structure, i would love to remove the unnecessary folder prefix (source/plugin/misterpah/* to source/* ). But, i also want to remain the above feature.

[as3boyan]

+1 to Samuel

[misterpah]

@gamedevsam
the beauty of javascript/ECMAscript is you can assign class to a variable.

var prefix = plugin.misterpah.Compiler;
var prefix_str = "plugin.misterpah.Compiler";

Main.message.listen("plugin.misterpah.ProjectTree:compile_Hxml",prefix_str,function(){prefix.compile_to_target("HXML");});

it removes some of the redundancy.
and with the help of hs_event_dashboard() ( which never been told to anyone. sorry about that.. 😄 ) its simplified alot of things. all events registered with Main.message.broadcast & Main.message.listen will be there.

[misterpah]

as for name redundancy, i strongly believe that Haxe Studio will have a lot of 3rd-party (free/paid) plugin (at least 1 3rd-party plugin, from my future company). that if a very good API documentation available.

plugin.<developerName>.pluginName prefix are much better when there's a lot of people expanding Haxe Studio. Plugin developer always have their own plugin-space where he/she doesn't have to worry about other plugin-space.

sample :
plugin.haxefoundation.Debugger
plugin.gamedevsam.HaxeFlixelConsole
plugin.jgranick.StarlingPack
plugin.jgranick.NME
plugin.haxenme.NME
plugin.misterpah.SwimmingFish

user can choose which plugin they want to use (some might be released as MIT licence, others are premium licence) . Some plugin might have a powerful function but with very complex UI, and some have limited function but super easy to use. some plugin, plugin.misterpah.SwimmingFish might be useless for someone, but might be someone like it.