On Wed, Apr 28, 2010 at 09:52, egervari <[email protected]> wrote: > With just components and no framework, you are responsible for tying > them together to make something useful. While you save time and code > by reusing components, the common infrastructure elements will > repeat.
Thank you for that valuable input - I like your thinking on how to separate component and framework usage patterns. On Wed, Apr 28, 2010 at 09:53, egervari <[email protected]> wrote: > Oh, and I do want to say that when a framework prescribes a specific > use of components and isn't very flexible, then I'd say it is no > longer a framework - but is a "platform". And yes, that is also a very good "definition". Not sure if there is an "official" one from wikipedia or so but I like your simple description very much. Best regards, Martin. -- Martin Wildam -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
