Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flipbooks with only images #122

Open
markknol opened this issue Jul 30, 2014 · 7 comments
Open

Flipbooks with only images #122

markknol opened this issue Jul 30, 2014 · 7 comments

Comments

@markknol
Copy link

It would be nice to have a bit smarter flipbook layer where it does not only take a snapshot of every keyframe, but also takes in account which bitmaps are on that layer, to avoid duplicated sprites in the texture.

Example timeline:
[bitmap1 - bitmap2 - bitmap3 ---- bitmap2 - bitmap1]

Now ouputs:
[clip_flipbook_0 - clip_flipbook_1 - clip_flipbook_2 - clip_flipbook_3 - clip_flipbook_4]

Ideal ouput:
[clip_flipbook_0 - clip_flipbook_1 - clip_flipbook_2 - clip_flipbook_1, clip_flipbook_0]

I think it would be doable to check how unique a flipbook frame is (based on bitmap/symbol-name), maybe even with multiple layers, but I would be ok if it fails when shapes/lines are used.

@tconkling
Copy link
Owner

This is a good idea. I'm not able to put much time into Flump at the moment
except for issues that directly affect my current project, but I can offer
pointers if you want to take a stab at the implementation?

On Wed, Jul 30, 2014 at 12:56 AM, Mark Knol [email protected]
wrote:

It would be nice to have a bit smarter flipbook layer where it does not
only take a snapshot of every keyframe, but also takes in account which
bitmaps are on that layer, to avoid duplicated sprites in the texture.

Example timeline:
[bitmap1 - bitmap2 - bitmap3 ---- bitmap4 ---- bitmap2 - bitmap1]

I think it would be doable to check how unique a flipbook frame is (based
on bitmap/symbol-name), maybe even with multiple layers, but I would be ok
if it fails when shapes/lines are used.


Reply to this email directly or view it on GitHub
#122.

@markknol
Copy link
Author

I already downloaded the project to provide some updates/tweaks. but I found it hard to even build and get it running, it has a quite different setup from what I'm used to (scary maven-stuff that installs things i never heard of), so some pointers would be nice :)

@tconkling
Copy link
Owner

Which step are you getting stuck on?

On Thu, Sep 11, 2014 at 1:38 PM, Mark Knol [email protected] wrote:

I already downloaded the project to provide some updates/tweaks. but I
found it hard to even build and get it running, it has a quite different
setup from what I'm used to (scary maven-stuff that installs things i never
heard of), so some pointers would be nice :)


Reply to this email directly or view it on GitHub
#122 (comment).

@tconkling
Copy link
Owner

Also, what is your normal setup? Do you use an IDE? The maven stuff just
automatically downloads the swcs that Flump depends on, but you can set
that stuff up manually in your IDE as well (I do this myself).

On Thu, Sep 11, 2014 at 1:50 PM, Tim Conkling [email protected] wrote:

Which step are you getting stuck on?

On Thu, Sep 11, 2014 at 1:38 PM, Mark Knol [email protected]
wrote:

I already downloaded the project to provide some updates/tweaks. but I
found it hard to even build and get it running, it has a quite different
setup from what I'm used to (scary maven-stuff that installs things i never
heard of), so some pointers would be nice :)


Reply to this email directly or view it on GitHub
#122 (comment).

@markknol
Copy link
Author

I prefer FlashDevelop, but I have experience with FDT too. I had no idea how to start with both. Would be nice if there was a projectfile for one of those.

@tconkling
Copy link
Owner

I'm not opposed to hosting project files for common IDEs, though I don't
have either FlashDevelop or FDT.

You'll want to create a project for the runtime that includes the source
files in the runtime directory. If you look at runtime/pom.xml, you can see
the libraries that the runtime depends on: react-as3 (1.1), starling
(1.4.1), and fzip. Get these three libraries - they're all hosted in my
maven repo:

https://github.com/tconkling/maven-repo/raw/master/com/timconkling/react-as3/1.1/react-as3-1.1.swc
https://github.com/tconkling/maven-repo/raw/master/com/gamua/starling-framework/1.4.1/starling-framework-1.4.1.swc
https://github.com/tconkling/maven-repo/raw/master/deng/fzip/a5430bd/fzip-a5430bd.swc

And you should be good to go.

The exporter is a similar process - again, look at exporter/src for all the
source files, and exporter/pom.xml to see which libraries you need to grab.

On Thu, Sep 11, 2014 at 11:55 PM, Mark Knol [email protected]
wrote:

I prefer FlashDevelop, but I have experience with FDT too. I had no idea
how to start with both. Would be nice if there was a projectfile for one of
those.


Reply to this email directly or view it on GitHub
#122 (comment).

@Zamaroht
Copy link

Hello, this would be really helpful, did it get implemented?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants