- User Since
- Aug 22 2016, 1:56 PM (168 w, 3 d)
Yes, I agree.
It is however, a problem having two apps using same native mimetype for realy different content.
I would certainly think it was worth it if flow had really good support for flow charts,
but it is really just the minimum needed to create a pageapp.
All functionallity is in the plugins, so flow does not offer any advantage over karbon or words.
What about bugs.kde.org?
Mon, Nov 11
If flow had some special functionallity that made it much easier to crate flow charts, I would also be reluctant to just remove it.
As it stands flow has nothing special, it is only a few line of code actually, and as I see it, the karbon ui is very similar to flow.
Granted, karbon can do a lot more, but I don't think it is disturibing the user as this is 'hidden' in separate menus.
Remove unused include
Fri, Nov 8
Remove commented code
Wed, Nov 6
Tue, Nov 5
Mon, Nov 4
KarbonView: Add slot to handle replaceActivePage
SvgImport: Add the new layer to the page
Sun, Nov 3
Sat, Nov 2
Fri, Nov 1
Handle removing pages from a pageapp properly