[Feedhenry-raincatcher] Raincatcher feedback from a newbie

[Summers Pittman]

>
>
>>> 2.  Angular is a huge, opinionated framework with lots of gotchas, and
>>> Angular went the route of "Let's add a bunch of custom tags and attributes
>>> to html elements".  This has the effect of breaking lots of tools and
>>> making learning Raincatcher even harder.
>>>
>> I agree that these frameworks adds to the learning curve, but I think we
>> also fail on being idiomatic in the context of angular and other frameworks
>> as in someone who knows angular would still have a bit of a hard time
>> understanding how to use the modules.
>>
>> For angular some of our modules supply directives (i.e. custom tags) that
>> take no arguments and do a bunch of stuff, being manipulated by their own
>> controllers and interacting through the sparsely documented mediator
>> topics. This is quite opaque.
>> For express the modules grab the application and add a bunch of routes to
>> it, as opposed to exporting routers and middleware that the client code can
>> control and mount as it sees fit.
>>
>
> [Niall] I don't see any problem with being opinionated about we build a
> project. What we are building is effectively micro services in a single
> applications that communicate over a bus (mediator).
>
> I do think we have some work to do around how we structure the module
> functionality between business and display logic. I'm not sure the modules
> should be providing Angular services to other modules that have  lot of the
> business logic required for the applications. Ideally, all of the business
> logic for the modules would be completely UI framework agnostic and the UI
> code would just publish and subscribe to mediator topics. This needs some
> spikes to flesh this out.
>
> At the very least, each of the modules need to adhere to a common
> structure or developers will get really confused when switching between
> modules.
>

I'm not really sure what you meant.  What would Raincatcher provide to the
business logic tier if we aren't exposing it through Angular services?

Also, I don't think you can decouple the UI toolkit.  Angular is a broad a
deep framework that leaks into everything.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20170127/f50b2cc6/attachment.htm>