Updates to flx.py.

[FlixelCommunityBot]

Issue #189 by: ivangonekrazy

Change to flx.py to make it more cross-platform compatible:

• The script now generates proper file and directory paths
  for Windows, Mac, Linux.

Usability changes:

• Print usage message if no project name is provided.
• The project directory is created if it doesn't yet exist.
• The comment generated in Default.css is now commented out.

Changes to make the script more "Pythonic":

• String literals for the file templates are now just one string
  instead of a list of strings.
• Variables in the templates are interpolated into the strings
  rather than concatenated.

[FlixelCommunityBot]

#ivangonekrazy added a commit: AdamAtomic#189

[Dovyski]

I think we should get rid of flx.py.

It makes no sense to me. If we need to test something, we should have a samples or tests folder containing some code (just like Starling does), or we should have no sample/test folder at all (like FlashPunk and Away3D do, for instance).

[IQAndreas]

I agree, along with build_docs.sh. They could definitely come in handy for the future, but perhaps don't belong in the main repository.

If we need to test something, we should have a samples or tests folder

I think you misunderstand. The script generates the Preloader class, the MenuState class, and the GameState class (and optionally a FlashBuilder CSS file), allowing you a quick way of starting up a new project; It may come in handy for some.

Should we:

• Open a new FlixelCommunity repository named "FlixelUtils" or "FlixelScripts" were we can place all the helper scripts?
• Move them to a separate folder ("utils" or "scripts")?
• Move them to a different "unattached" branch?
• Or leave them where they are?

[Dovyski]

Indeed I misunderstood. I thought it generated a testing code, not a project. I think we should move them to a separate folder ("utils" seems nice to me).

[moly]

fixed in c71377b