You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by Dan Debrunner <dj...@debrunners.com> on 2016/03/22 23:53:59 UTC
Source code for recipes?
It's good to see the cookbook started up and recipes being added.
Any thoughts on if each recipe should ideally have its source code in the code repo under the existing samples?
Look likes that will be the case with QUARKS-16.
Looking at the Hello Quarks! code it's missing the import statements, which a Java developer should be able to figure out, but maybe an inexperienced developer wouldn't?
So having the full source available through a link to the repo might help them out.
Dan.
Re: Source code for recipes?
Posted by Queenie Ma <qu...@gmail.com>.
I agree, it would be a good idea to have the recipe applications exist as
Quarks samples. However, I think for some of the recipes that might not be
necessary. For instance, "Applying different processing against a single
stream" (QUARKS-36) is a subset of "Splitting a stream to applying different
processing against streams and combining the resulting streams into a single
stream" (QUARKS-16). In these cases, I think it would be suitable to put the
entire application at the bottom of the recipe in a code block.
\--
Queenie
> On Mar 22 2016, at 3:54 pm, Dan Debrunner <djd@debrunners.com> wrote:
>
> It's good to see the cookbook started up and recipes being added.
>
> Any thoughts on if each recipe should ideally have its source code in the
code repo under the existing samples?
Look likes that will be the case with QUARKS-16.
>
> Looking at the Hello Quarks! code it's missing the import statements, which
a Java developer should be able to figure out, but maybe an inexperienced
developer wouldn't?
So having the full source available through a link to the repo might help them
out.
>
> Dan.