importing XML, CSS, Upload, Xdebug, Execute Script, Execute Browser etc. pp. plugins into Quanta
mail at milianw.de
Mon Jun 7 12:32:22 UTC 2010
Hello Ruan and Niko,
I'd like to incorporate most of the webdev related plugins in playground into
Quanta and continue improving them there.
I've talked with Andris and I'll probably remove most of the existing code in
Quanta and replace it by implementations that reuse the existing frameworks
better. I still hope to be able to reuse some old code, but most of the
existing code seems to reproduce exiting code in KDevplatform, often in a
quite different way though, making the porting non-trivial.
Anyhow, since I hope to get a halfway working Quanta ready in the next two
months, I wanted to incorporate the useful plugins. By getting rid of the old
cruft I could concentrate better on improving what we have. The next step
would then be looking at the old Quanta3 for _important_ features that are
missing and port them / reimplement them.
Andras: Are you OK with me moving most of the Quanta code to the 'UNPORTED'
Looking at the existing plugins in Quanta that are halfway working I can say:
KDevHTMLPreview - sounds useful but is probably superseeded by executebrowser,
or Niko? Do users really need/want a inline HTML preview? Anyhow, the plugin
needs to be ported properly (its not doing anything right now).
KDevStructureTree - nice idea and people might be used to it. It heavily
depends on the DTEP stuff though and I want to get rid of that. I'd rather try
to implement a "context-outline" or similar thats shown in a toolview. That
way it would also work for Cpp etc.
KDevUserToolbars - Some UI is working, but it's messy and the actual actions
don't seem to work at all. Anyhow, I do see the need to run a script quickly
or insert a tag. But: To me it would make more sense to associate actions with
Snippets, Launch Configurations (e.g. Execute Script, Execute Browser, ...)
then to have this toolbar plugin reinventing the wheel. Still, creating new
toolbars would still be needed for those that really want an icon for the
actions. Hence that part of the plugin should stay, but the rest should try to
reuse the KActionCollection(s) and simply offer the user to add actions from
the usual "configure toolbars" page... Maybe we should even request such a
"add toolbar" feature inside KDELibs directly.
KDevTemplatesTree - Again, needs to be ported to work properly and it should
be merged with Snippets probably. We have project templates but - beside the
"add class" wizard - no way create a new file from a snippet. This seems to be
very useful to me and I'm willing to make that work properly.
KDevQuantaCore - Imo, this should die. We have TextDocuments,
CodeRepresentation etc. pp. inside KDevplatform that would supersede the
EditorSource. The rest is DTEP related or even "background parser" like and
should all be removed. Instead plugins (e.g. the XML one) should contain the
required actions and - if required for e.g. the "insert tag" actions - install
an interface _just for that_.
So, I kinda feel bad but I really have to ask this: May I move more or less
_all_ the Quanta files to UNPORTED and start "clean" with the current plugins
(xml, css, upload, ...) we have? I hope that this would increase my
productivity and make it possible to have something that is actually useful.
Of course, users will complain again about missing features etc. pp. but well,
porting all of Quanta3 massive feature set is simply a too huge task for this
short time and a single person.
PS: I also plan to start a poll about the most useful feature in Quanta3 to
make sure that it's still useful for the people out there.
mail at milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: This is a digitally signed message part.
More information about the KDevelop-devel