Daily Build Descriptions

[Christopher_Bishop]

I know this has been said before but can someone give some better descriptions on the daily builds?

Note: Transitions 2.0 <-Don’t get me wrong, I am all for being cryptic and keeping them guessing but jeez would it hurt to at least give us a 1-2 line description…

I get the whole it might invite more questions and that odds are you will do a blog on the subject however that doesn’t help on “daily” builds.

I really don’t think giving a couple line description is that hard of a thing to do and I for one think it would be a welcome change for developers.

All in all I think Corona is doing a wonderful job but teasing us with Graphics 2.0 and then adding Transitions 2.0 and Easing 2.0 without any further details is wrong on so many levels

[aukStudios]

I agree, especially given the fact that, based on some other posts in the forums, the Transition 2.0 and Easing 2.0 changes (whatever they are) introduced some breaking changes.

• Andrew

[Joshua_Quick]

The documentation for these updated libraries can be found here…

   http://docs.coronalabs.com/daily/guide/media/transitionLib/index.html

   http://docs.coronalabs.com/daily/api/library/easing/index.html

   http://docs.coronalabs.com/daily/api/library/transition/index.html

There are not supposed to be any breaking changes with these updated libraries (that I’m aware of).  If you run into any issues, then please let us know.

[Christopher_Bishop]

Thanks Joshua,

These are just the docs and already reviewed them trying to find out what has changed.

If there are no changes then why the 2.0 prefix? 

I have already tested out the daily build and, it didn’t break anything but nor did anything change, if I run 2 simulators side by side on 2 different machines the results are identical (memory footprint etc.) and I highly doubt i am just that efficient

I am not trying to be a trouble maker just trying to get some information on these changes as “no where” is it listed on what was changed to give it a 2.0 prefix.

Hell, I would settle for “We just called it 2.0 because of the Graphics 2.0 stuff, but that was the only change.” but can’t even get that. 

Just looking for a little info thats all

[Stephen_Lewis]

Hi Joshua,

The daily docs you linked to are identical to the current public release docs so are we to assume that “2.0” easing and transitions are functionally identical to 1.0?  

Also, did you see this thread?  

http://forums.coronalabs.com/topic/39518-transitioneasing-20/

A few people (including me) are having problems with the builds after the 2.0 changes were introduced.

[alexf]

@cbishop: The 2.0 prefix is there because the functionality was extended. Josh was referring to breaking changes ( backwards compatibility ). The new docs will be here soon.

Alex

[Christopher_Bishop]

Alex,

I figured as much but back to my original question, any chance we can get a 1-2 line description on some key points or a 50ft overview?

It has been my experience that the docs don’t tend to add whats new etc., not asking for a break down just a general overview and I promise I won’t have any follow up questions lol

@HardBoiled:: I haven’t seen the errors you guys are getting on your thread and I am using some pretty hairy transition/easing calls but if you want to post a brief example (code or no code) I can plug it in and check to see if it breaks my stuff as well.

Chris

[alexf]

Chris, sure thing.

Transition 2.0 builds on the existing functionality of 1.0, implementing:

New transition.to params ( tag - for grouping transitions in tags, iterations - the number of transition iterations you want to have)

Added the ability to pause / resume / cancel transitions by transition object, display object ( all the active transitions on the display object are affected), by tag, by sequence or all of them if no param is passed )

Ability to add sequences ( sequence = a table of transitions with an extra param, mode = “withPrevious” or mode=“afterPrevious” )

new event listeners ( onRepeat, onPause, onResume )

Convenience methods (moveBy, moveTo, scaleBy, scaleTo, fadeIn, fadeOut, blink)

Easing 2.0 includes all the functions from Robert Penner’s library ( 43 functions )

Alex

[Christopher_Bishop]

Alex, That was beautiful exactly what i was looking for Thanks a bunch Chris

[alexf]

Sure thing, Chris. For any other questions, don’t hesitate to ask.

Alex

[aukStudios]

I agree, especially given the fact that, based on some other posts in the forums, the Transition 2.0 and Easing 2.0 changes (whatever they are) introduced some breaking changes.

• Andrew

[Joshua_Quick]

The documentation for these updated libraries can be found here…

   http://docs.coronalabs.com/daily/guide/media/transitionLib/index.html

   http://docs.coronalabs.com/daily/api/library/easing/index.html

   http://docs.coronalabs.com/daily/api/library/transition/index.html

There are not supposed to be any breaking changes with these updated libraries (that I’m aware of).  If you run into any issues, then please let us know.

[Christopher_Bishop]

Thanks Joshua,

These are just the docs and already reviewed them trying to find out what has changed.

If there are no changes then why the 2.0 prefix? 

I have already tested out the daily build and, it didn’t break anything but nor did anything change, if I run 2 simulators side by side on 2 different machines the results are identical (memory footprint etc.) and I highly doubt i am just that efficient

I am not trying to be a trouble maker just trying to get some information on these changes as “no where” is it listed on what was changed to give it a 2.0 prefix.

Hell, I would settle for “We just called it 2.0 because of the Graphics 2.0 stuff, but that was the only change.” but can’t even get that. 

Just looking for a little info thats all

[Stephen_Lewis]

Hi Joshua,

The daily docs you linked to are identical to the current public release docs so are we to assume that “2.0” easing and transitions are functionally identical to 1.0?  

Also, did you see this thread?  

http://forums.coronalabs.com/topic/39518-transitioneasing-20/

A few people (including me) are having problems with the builds after the 2.0 changes were introduced.

[alexf]

@cbishop: The 2.0 prefix is there because the functionality was extended. Josh was referring to breaking changes ( backwards compatibility ). The new docs will be here soon.

Alex

[Christopher_Bishop]

Alex,

I figured as much but back to my original question, any chance we can get a 1-2 line description on some key points or a 50ft overview?

It has been my experience that the docs don’t tend to add whats new etc., not asking for a break down just a general overview and I promise I won’t have any follow up questions lol

@HardBoiled:: I haven’t seen the errors you guys are getting on your thread and I am using some pretty hairy transition/easing calls but if you want to post a brief example (code or no code) I can plug it in and check to see if it breaks my stuff as well.

Chris

[alexf]

Chris, sure thing.

Transition 2.0 builds on the existing functionality of 1.0, implementing:

New transition.to params ( tag - for grouping transitions in tags, iterations - the number of transition iterations you want to have)

Added the ability to pause / resume / cancel transitions by transition object, display object ( all the active transitions on the display object are affected), by tag, by sequence or all of them if no param is passed )

Ability to add sequences ( sequence = a table of transitions with an extra param, mode = “withPrevious” or mode=“afterPrevious” )

new event listeners ( onRepeat, onPause, onResume )

Convenience methods (moveBy, moveTo, scaleBy, scaleTo, fadeIn, fadeOut, blink)

Easing 2.0 includes all the functions from Robert Penner’s library ( 43 functions )

Alex

[Christopher_Bishop]

Alex, That was beautiful exactly what i was looking for Thanks a bunch Chris

[alexf]

Sure thing, Chris. For any other questions, don’t hesitate to ask.

Alex