[ 
https://issues.apache.org/jira/browse/S4-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212082#comment-13212082
 ] 

Leo Neumeyer commented on S4-5:
-------------------------------

Great feedback, thanks!

* "onField" refers to the field name in the PE class that has a reference to a 
target Stream array. That's why I call it onField. "onStream" seems to imply 
the name of the stream which would be misleading. "onField" is not required 
when there is no ambiguity. That is: all stream fields in the PE are 
parametrized with different Event types. In that case the EDSL will figure out 
what field to use. This is the best idea I came up with, if anyone has an 
alternative, we can change. Perhaps we can call it "usePEField"?

* I will look into using a variable number of args for to()

* so you would use something like onStream(SomeStream.class, 
SomeKeyFinder.class).usePEField("someField") [I don't think I can overload the 
method so the optional "usePEField" method would have to be separate. What do 
people think?

* edsl is a completely separate and optional project that depends on core but 
core doesn't depend on edsl. This pattern will help create alternate UIs. So I 
don't think we want UI code in core. The unit tests cases should be in the 
examples or in edsl projects.





                
> Prototype app builder
> ---------------------
>
>                 Key: S4-5
>                 URL: https://issues.apache.org/jira/browse/S4-5
>             Project: Apache S4
>          Issue Type: New Feature
>    Affects Versions: 0.5
>            Reporter: Leo Neumeyer
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: s4-app.png, s4-fluent.pdf
>
>
> Extend Guice AbstractModule to create a simple application builder layer. The 
> idea is to evaluate if we can use Guice to do all the wiring including PEs 
> and Streams and Apps.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to