[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    [kde-promo] Re: The Future of our Frameworks
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2011-06-26 16:55:39
Message-ID: 201106261855.45347 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 21 June 2011, Sebastian Kügler wrote:
> On Tuesday, June 07, 2011 12:17:08 Pau Garcia i Quiles wrote:
> > I had exactly the same question because IMHO there is a confusion
> > between "framework" and "library" here.
> > 
> > Library = set of related functions and helper methods and classes
> > 
> > Framework = Library + a "way" of working with it (i. e. workflow,
> > tools you need to use, conventions, etc). For instance, Rails is a
> > framework because it imposes a set of conventions you cannot change
> > (and you webapps will not work unless you follow them)
> > 
> > I'd say with the modularization we are splitting into *libraries*,
> > not into frameworks because we do not impose a set of rules,
> > tools, workflow, etc to work with it.
> 
> It's "vague on purpose", as we refer to libraries, but also more
> complex things such as Akonadi.

I had a look at what Wikipedia says about frameworks. AFAICT the 
definition of "software framework" [1] is a good fit for what we mean.


Regards,
Ingo

[1] http://en.wikipedia.org/wiki/Software_framework

["signature.asc" (application/pgp-signature)]

_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.



[prev in list] [next in list] [prev in thread] [next in thread]