On Mon, 06 May 2013 15:18:17 -0500 "Darrell Anderson" darrella@hushmail.com wrote:
We received an enhancement request to add some superkaramba widgets prepackaged as part of Trinity:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1487
A primary advantage for prepackaging is ease-of-use for end-users.
Should we do this?
If we do this, do we package the widgets separately or merge
them into the superkaramba sources in tdeutils?
- If we do this, what guidelines do we establish for selecting
which widget candidates to prepackage and support?
- As there are many such widgets, even for KDE3, should we instead
host a wiki page for installing widgets, such as from kde- look.org? Seems many of the older KDE3 widgets still function in Trinity. In
addition to generic instructions, a wiki page could include tips for cleaning or massaging problematic widgets to work with Trinity.
Comments and suggestions appreciated! :-)
No opinions?
Darrell
I'm all for it!
On 9 May 2013 11:51, Darrell Anderson darrella@hushmail.com wrote:
On Mon, 06 May 2013 15:18:17 -0500 "Darrell Anderson" darrella@hushmail.com wrote:
We received an enhancement request to add some superkaramba widgets prepackaged as part of Trinity:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1487
A primary advantage for prepackaging is ease-of-use for end-users.
Should we do this?
If we do this, do we package the widgets separately or merge
them into the superkaramba sources in tdeutils?
- If we do this, what guidelines do we establish for selecting
which widget candidates to prepackage and support?
- As there are many such widgets, even for KDE3, should we instead
host a wiki page for installing widgets, such as from kde- look.org? Seems many of the older KDE3 widgets still function in Trinity. In
addition to generic instructions, a wiki page could include tips for cleaning or massaging problematic widgets to work with Trinity.
Comments and suggestions appreciated! :-)
No opinions?
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Mon, 06 May 2013 15:18:17 -0500 "Darrell Anderson" darrella@hushmail.com wrote:
We received an enhancement request to add some superkaramba widgets prepackaged as part of Trinity:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1487
A primary advantage for prepackaging is ease-of-use for end-users.
Should we do this?
If we do this, do we package the widgets separately or merge
them into the superkaramba sources in tdeutils?
- If we do this, what guidelines do we establish for selecting
which widget candidates to prepackage and support?
- As there are many such widgets, even for KDE3, should we instead
host a wiki page for installing widgets, such as from kde- look.org? Seems many of the older KDE3 widgets still function in Trinity. In
addition to generic instructions, a wiki page could include tips for cleaning or massaging problematic widgets to work with Trinity.
Comments and suggestions appreciated! :-)
No opinions?
Darrell
Sorry I could not get to this earlier!
I would recommend creating a superkaramba-extras module in GIT, then adding suitable widgets to that module. Both licensing and functionality must be verified before a widget is added to GIT.
Tim
-
Calvin Morrison -
Darrell Anderson -
Timothy Pearson