'EAT - Frameworks' Released

OK, so since you’ve shared so much since I’ve been here on Corona, and I’ve learned a lot from your code I decided I’d just buy this sight unseen, and hope it supports you a little :slight_smile:

If I install this on both my Macs and then want it on the PC, can I just uninstall it from one mac, and install it or is it a manual (PITA) process. (I use the Mini as the power machine, the mac air for evening ‘relaxation’ and the PC when I’m travelling/working. Not a big deal, just a question.

First glance, looks great! It WILL save hours of work!

To answer the question you asked in the second video, I would like to see more game templates included.  It looks like there is no longer a store to add more modules/plugins/templates like there was in the beta build.

@Graham,

You can simply run it from your Two Macs and PC.  The licensing system is designed to trip for over-registration and it has a margin built-in for cases like yours.

So,  if you have two machines you use a lot and a third you use occasionally, using it on the third machine won’t be a problem.  Worst case,  if someone triggers my ‘too many registrations’ alert, I’ll contact them and see what’s what. 

Thanks for asking!

@tonygod,

Thanks for the input.  Yeah, I decided to completely remove the store idea because it was making the development take a long time and become error laden.  As it was, I took forever to release this.

Now, to additional features and content.

Cheer,

Ed

Absolutely perfect, as thats the case 95% of the time - thanks.

While using EAT on a smaller screen Mac, I lose the ability to see more options. Either a scroll bar or the ability to close sub-items would help.

https://dl.dropboxusercontent.com/u/25547044/EATSS1.png

(I know the values aren’t valid)

@Graham,

Please note, there is an issue with re-sizing desktop apps on OSX.  I am investigating now.  

Because of this issue, I set the OS X version to be non-resizeable.   This is temporary.  

Also, I went with a resolution (for OSX) of 1200 x 675 to ensure the app would fit on smaller screens of 1280 x 800 (got number from answers here).

There will be a new release on 26 APR 2016.  Assuming I don’t resolve the resizing issue by then I’ll make the app a little bigger.

BTW, what does ‘EAT’ mean anyway?

@Graham (and all other OS X users ),
 
There is currently a technical issue with resizing vs scale.  Specifically, adaptive scaling is not supported for OS X Desktop and this create a challenge if one wants to allow resizing while preventing simultaneous rescaling.
 
While I work out a solution, I have an interim bandaid.  There are now two OS X releases:

  • OSX/ - 1778 x 1000 (should fit on a 1920 x 1080 and larger sized monitor.)
  • OSX_SmallScreen/ - 1200 x 675 (should fit on a 1200 x 800 resolution Mac Book monitor.)

@JohnPM - re: What does EAT mean?

I’m terrible at marketing and naming.  Originally, the plan was to call the tool: GDT for Corona SDK.  i.e The very creative ‘Game Developers Toolkit’ for Corona SDK.   :rolleyes:

However, my wife suggested “Ed’s Awesome Tools”.  I joked about this on the Corona Geek hangout and it stuck.  

So, while it seems a little egotistical (Yes, my first name is Ed), please understand that I kept it because it was easy to remember and funny.  

For example, current and soon to be released tools:

  • ‘EAT - Frameworks’ ==> Framework Generator
  • ‘EAT - Utilities’ ==> Utilities Grab Bag (Icon Generator, Launch Image Generator, Particle Editors (Corona, CBE, Prism), … more?
  • ‘EAT - Shorts’ ==> An idea I’m floating for a tool that generates short example answers to the most common questions. i.e. Focused answers with a few tweakable options to get the answer folks need for specific mechanics/usage issues.

I think you will agree the EAT part just sticks in the mind and is amenable to tweaking and variations.

EAT will generate an invalid build.settings file when setting more than one of the “supportsScreen” values to true:

 supportsScreens = { smallScreens = true normalScreens = true largeScreens = true xlargeScreens = true },

The comma separator between table items is missing.

@tonygod,

Fixed and released in version 2016.006.

This post was flagged by the community and is temporarily hidden.