Re: Karamba vs. SuperKaramba

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Karamba vs. SuperKaramba
by Rodion on Monday 05/May/2003, @11:32

This really doesn't make much sense at all. In what ways are the aims of Karamba and SuperKaramba different? Sooner or later, the two projects are going to have to merge, or else one will die off--doesn't it make sense to merge them now and avoid wasting time before the inevitable?

Related Links

·   Articles on Graphics and Art
·   Also by Rodion
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Karamba vs. SuperKaramba
by Dave on Saturday 10/May/2003, @08:24

Sure

[ Reply To This | View ]

Re: Karamba vs. SuperKaramba
by HiltonT on Saturday 07/Jun/2003, @17:17

Hhmmm - a thread entitled Karamba vs. SuperKaramba that totally ignores the aim. Not handy. So, is anyone actually going to dare approach the topic of this thread and actually DETAIL the differences?

- HiltonT

[ Reply To This | View ]

Re: Karamba vs. SuperKaramba
by Miles on Thursday 23/Oct/2003, @17:16

I guess not, huh? and here I am, after googling "karamba vs. superkaramba" months later, and void of information because of it!

For shame!

[ Reply To This | View ]

Re: Karamba vs. SuperKaramba
by Datschge on Thursday 23/Oct/2003, @23:44

Karamba uses perl for its theme scripts while SuperKaramba (without space gets you more hits when searching) mainly uses python instead.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I always have things in progress." -- Kurt Granroth
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.