Hello, Let me offer my thoughts. I think it's a good idea to somehow refresh the EIP icons/diagrams and contribution is always great. However:
> the diagrams symbolize the essence of what Camel does. Yes, but it also has a broader context: They actually symbolize the essence of what most of the current competitive ESB or integration frameworks do in common. They are symbols of our shared wisdom and best practices on systems integration. > However the graphics don't all seem to be in the same style, and some are missing. I haven't thought they aren't in the same style. Which one do you think so? Please note that in the original EIP book there are good reasons why some icons are rectangles and some are not (and maybe why some are missing originally as well). For example, in my understanding the Control Bus pattern doesn't have a rectangle icon because in the context of the original book it's rather an architectural pattern, while most rectangle patterns are a component-level one. Note also that some are missing just because they are devised (or discovered) after the EIP book. So it might be a good idea to fill the gap and devise a new icon for those new patterns, in the same style as in the EIP book. So, refreshing the icons is a good idea but I hope they won't diverge too far from the original ones, because identity is the key for software patterns in general. Best regards, Tadayoshi On Tue, Nov 8, 2016 at 9:06 PM, Francis Vila <fvila...@gmail.com> wrote: > Hi, > > I am new to both Camel and to open-source contributing, so forgive any > breaches of protocol... > > The page on http://camel.apache.org/enterprise-integration-patterns.html > <http://camel.apache.org/enterprise-integration-patterns.html> shows an > impressive list of patterns. However the graphics don't all seem to be in > the same style, and some are missing. To me (although I don't have an > in-depth understanding of Camel), the diagrams symbolize the essence of > what > Camel does. Maybe a homogeneous, updated styleset would be a good idea? > I think I can contribute to such an task. I've done some tests of different > approaches for the /Message router /pattern. If this effort is deemed > worthwhile by the community, I can go on with the rest. The graphics were > done using Inkscape and are available in svg format. > > This is the simplest version: > <http://camel.465427.n5.nabble.com/file/n5789901/MessageRouter_1.png> > > This version has added endpoints symbolizing the input and output locations > for the origin and destination of the messages : > <http://camel.465427.n5.nabble.com/file/n5789901/MessageRouter_2.png> > > This version encloses the pattern: > <http://camel.465427.n5.nabble.com/file/n5789901/MessageRouter_3.png> > > This version puts emphasis on the the most important part of the diagram, > namely the currently active path: > <http://camel.465427.n5.nabble.com/file/n5789901/MessageRouter_5b.png> > > This version targets the emphasis more closely, to just the "mobile" part > of > the diagram: > <http://camel.465427.n5.nabble.com/file/n5789901/MessageRouter_6.png> > > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Time-for-an-overhaul-of-the-patterns-symbols-tp5789901.html > Sent from the Camel Development mailing list archive at Nabble.com. >
