El Dimarts, 28 de gener de 2014, a les 19:47:59, Kevin Krammer va escriure: > On Tuesday, 2014-01-28, 11:51:06, Sebastian Gottfried wrote: > > Hi David, > > > > > I don't want to start a naming bikeshed so if it is already too late > > > > > to consider renaming, just dismiss these comments: > > No, that's still okay. Nothing is set in stone yet. > > > > > The first thing I thought of when I read the name of the plugin is > > > that it did graph rendering, like OGDF QML[0], and I was in desperate > > > need for such a library a couple of months ago. I think graph is > > > confusing for a couple of reasons: > > > > > > > > > * There is already a concept of graphs associated to QML, as in QML > > > Graph Scene (which is apparently the most common result I get from > > > searching "QML Graph") > > > > Never thought about that. > > > > > * In KDE, Rocs deals with Graphs and KmPlot deals with these kinds of > > > graphs. * There is a Qt Charts[1] thing that does something similar. > > > > > > So I would consider renaming this to something with plot/chart. > > > > I like charts better and would consider renaming it to kqmlchartsplugin. > > The QML import would be 'org.kde.charts' then. > > > > Are there any more opinions on the naming issue? > > If this uses QtQuick I would suggest that it be part of the name. > > QML is a more generic term, used for thing that can be used by a QML engine. > Usually components without UI, like data sources, sensors, models, timers > etc. Things that can be used outside a UI context or with any UI component > set (QtQuick, Cascasdes, Widgets and so on).
+1 QML is the language, QtQuick is the "toolkit" Cheers, Albert > > Cheers, > Kevin