plasmate's roadmap

[Tsiapaliwkas Giorgos]

On Friday, April 15, 2011 09:49:24 PM Farhad Hedayati-Fard wrote:
> IMHO displaying documentaion for the current keyword (like the one in
> kdevelop) is a good! 

+1

On Thursday, April 14, 2011 05:41:42 PM Shantanu Tushar Jha wrote:
> The reason I asked that was because Qt Designer can only be used to create
> QWidget based UIs (correct me if I am wrong),

If you create a qml file you can edit it with the Qt Designer.

On Friday, April 15, 2011 04:17:21 PM Sebastian Kügler wrote:
> More interesting would be to look at lighthouse, and Qt Creator for parts
> which would make hacking QML easier.
> 
> Cheers,

+1

On Saturday, April 16, 2011 01:07:30 PM Sebastian Kügler wrote:
> My gut feeling suggests that we'd be more likely to integrate kdevelop
> pieces  into Plasmate (but that's my biased POV probably), since Plasmate
> is very much a workflow-driven tool, so for the purpose of plasmate,
> kdevelop's UI is probably a bad choice. That's not a problem, just
> something we have to keep in mind, Plasmate and KDevelop serve similar
> goals and target groups (maybe comparable to Quanta vs. KDevelop)

IMHO i would prefer if plasmate was gone be made a plugin to kdevelop.
I think that we all agree in the one way or the other that plasmate and 
kdevelop has to share some code.

When this thread comes to an end,we should change the context of this page to 
the one we want.

http://community.kde.org/Plasma/PlasMate

P.S.:Is it possible kdevelop and plasmate to share some code which will change 
automatically after a patch??