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

add steps api functions #293

Merged
merged 8 commits into from
Jul 25, 2018
Merged

add steps api functions #293

merged 8 commits into from
Jul 25, 2018

Conversation

tech4GT
Copy link
Member

@tech4GT tech4GT commented Jun 12, 2018

@jywarren Added all functions🎉
Can you please elaborate on listeners.
Signed-off-by: tech4GT [email protected]

@ghost ghost assigned tech4GT Jun 12, 2018
@ghost ghost added the in-progress label Jun 12, 2018
},

getHeight : function(callback){
getPixels(this.getStep(-1).output.src,function(err,pixels){
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would using getPixels require parsing the whole image? I wonder if that'd be an expensive thing to do and if there are any reasonable alternatives. What do you think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm...yeah now that you have mentioned this, yes I'll change this!! Let's get the Module requirements PR merged in and rebase this before making any more changes, then we can bump a major version!!

@jywarren
Copy link
Member

Linking to #242

Very cool!

@tech4GT
Copy link
Member Author

tech4GT commented Jun 15, 2018

@jywarren merged with master!!

@jywarren
Copy link
Member

This looks great. Can we add some tests to demonstrate usage of these? Thank you, great work!

@tech4GT
Copy link
Member Author

tech4GT commented Jun 18, 2018

@jywarren Working on this now!!

@tech4GT
Copy link
Member Author

tech4GT commented Jun 18, 2018

@jywarren Actually most of these are functions which are scoped inside the module... So I would either have to write a test module which uses all of these or we can add tests as we develop modules which use these, which way should we go?

@jywarren
Copy link
Member

jywarren commented Jun 18, 2018 via email

@tech4GT
Copy link
Member Author

tech4GT commented Jun 19, 2018

@jywarren Working on this now!!

@tech4GT
Copy link
Member Author

tech4GT commented Jun 19, 2018

@jywarren I got an idea while working on this!! Should we implement the importModule functionality first? I mean like we discussed in the dynamic modules idea, that way we won't have to bundle this test module with the source code, we can just register it inside the tests file and run the sequencer with it(we will keep this module inside the test folder as well)

@tech4GT
Copy link
Member Author

tech4GT commented Jun 19, 2018

This makes a lot of sense to me since for the implementation of met-modules I have in mind this will be a welcome functionality!! Please see the meta-modules I made a flow over there...

@tech4GT
Copy link
Member Author

tech4GT commented Jun 19, 2018

And sorry we are postponing meta-modules again and again but I think once we are done with dynamic modules core(not completely, like we can include installing from npm part later) it would help with meta-modules since meta-modules are themselves dynamic

@jywarren
Copy link
Member

jywarren commented Jun 19, 2018 via email

@tech4GT
Copy link
Member Author

tech4GT commented Jun 19, 2018

@jywarren So Should we merge this in right now or rebase this over dynamic modules pr?

@jywarren
Copy link
Member

Let's delay this until we can include the dynamic test module. Is that ok?

@tech4GT
Copy link
Member Author

tech4GT commented Jun 19, 2018

@jywarren Sure!! So now I am doing this in a way that just by adding a few lines to the existing module file it can be made dynamically loadable!!

@jywarren
Copy link
Member

jywarren commented Jun 19, 2018 via email

@tech4GT
Copy link
Member Author

tech4GT commented Jul 18, 2018

Rebasing and adding tests!!

tech4GT added 3 commits July 18, 2018 19:57
Signed-off-by: tech4GT <[email protected]>
Signed-off-by: tech4GT <[email protected]>
Signed-off-by: tech4GT <[email protected]>
@tech4GT
Copy link
Member Author

tech4GT commented Jul 18, 2018

@jywarren This is ready too!!🎉

@tech4GT
Copy link
Member Author

tech4GT commented Jul 18, 2018

@jywarren I'll try to put in the meta-modules pr as soon as possible now!!

this.getInput(1);
this.getOutput(1);
this.getOptions();
this.getFormat();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we assert anything with these?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jywarren I thought we just wanted to check if they throw an error or not, actually som of these like height I can hardcode at best, will that be ok?

Signed-off-by: tech4GT <[email protected]>
@ghost ghost added the in-progress label Jul 24, 2018
@tech4GT
Copy link
Member Author

tech4GT commented Jul 24, 2018

@jywarren Done!!

@tech4GT tech4GT closed this Jul 24, 2018
@tech4GT tech4GT reopened this Jul 24, 2018
@ghost ghost added in-progress and removed in-progress labels Jul 24, 2018
@tech4GT
Copy link
Member Author

tech4GT commented Jul 24, 2018

@jywarren Please merge this in. Thanks

@tech4GT tech4GT mentioned this pull request Jul 25, 2018
@jywarren jywarren merged commit 10e4765 into publiclab:master Jul 25, 2018
@jywarren
Copy link
Member

🎉

@tech4GT
Copy link
Member Author

tech4GT commented Jul 25, 2018

Awesome!!!

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

Successfully merging this pull request may close these issues.

2 participants