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

Jit renderer #98

Closed
wants to merge 4 commits into from
Closed

Jit renderer #98

wants to merge 4 commits into from

Conversation

brendo
Copy link
Member

@brendo brendo commented Jan 1, 2015

This pull request (and branch) is a major overhaul to the architecture of JIT. Instead of a standalone script, JIT is simply another Renderer which inherits all Symphony functionality. This was made possible by Symphony 2.5, which added the ModifySymphonyLauncher delegate. This alleviates the major limitation of JIT in that it can now use delegates.

I believe this change would make it possible to fix the following by adding in delegates, or with minor changes to the code:

The code in this pull request is far from release quality, but I've pushed up in response to the comment by @jensscherbl that others could probably run with this better than I can. Math and image manipulation are not my strengths, so I'm happy for interested parties to carry on this work and work towards a 2.0 release!

@jensscherbl
Copy link
Member

The launcher thing is interesting. I thought about another approach a while ago and would like to hear your opinion on that.

What if we reuse existing Symphony functionality for this? Using pages with an image page type, URL parameter and image data source to create recipes?

Modifications could then be defined on a data source level, similar to what we're discussing for text formatters.

@brendo
Copy link
Member Author

brendo commented Jan 2, 2015

What if we reuse existing Symphony functionality for this? Using pages with an image page type, URL parameter and image data source to create recipes?

Modifications could then be defined on a data source level, similar to what we're discussing for text formatters.

Interesting. Seems a little cumbersome though? The whole Symphony stack has to be loaded to process an image.

@jensscherbl
Copy link
Member

The whole Symphony stack has to be loaded to process an image.

Wouldn't that be the case anyway for using the ModifySymphonyLauncher delegate?

But yeah, I guess you're right, would be a little cumbersome.

@bernardodiasc
Copy link
Member

This is great!

@jonmifsud
Copy link
Member

@brendo just noticed this - if I understand correctly at this point this does exactly the same thing as JIT currently does right now. And would need to be extended through delegates to tackle the issues you listed correct? If so I can have a look to see if it would help close #97 as I had to add a few other functions when extending the Image class such as a __clone function though that could be added to the main class I presume.

@brendo
Copy link
Member Author

brendo commented Jan 12, 2015

And would need to be extended through delegates to tackle the issues you listed correct?

Yeah correct :)

@nitriques
Copy link
Member

+1000 in this thing @brendo

@nitriques
Copy link
Member

Merged as 0f72a2c...18a2b02

Rebased is identical to original: 3629d85..2d8ed7d...0f72a2c..18a2b02

@nitriques nitriques closed this Mar 22, 2016
nitriques added a commit that referenced this pull request Mar 24, 2016
If another extension previously registered a custom launcher, the
current code would bypass it.

This commit makes sure we can still call the previously registered
launcher before reverting to the default one.

Re #98
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

Successfully merging this pull request may close these issues.

5 participants