Showing posts with label quanta. Show all posts
Showing posts with label quanta. Show all posts

Saturday, January 23, 2010

KDevelop/Quanta4 Css Language Support

I'm currently working on a important part of Quanta4, Css Language support. The only thing supported for now is code completion for standalone css files:


But that is the most useful feature a Web IDE can have.


Still on my todo list is:
  • validation (should be easy with the existing parser)
  • Outline navigation (should be not that hard either)
  • Support <style> tags and inline styles in html files
A few notes on how I implemented the plugin:
  • I reused WebKit's flex lexer
  • then wrote a parser using kdevelop-pg-qt based on WebKits bison grammar. A major difference is that it successfully parses incomplete Css - as it is during writing in the editor.
  • The code completion parses the file on invocation and goes through the Ast (resulting from the parser) to find the correct type to show.
  • Then, using an XML file borrowed from Aptana's code assist, the shown completion items are determined.

How to test (feedback is very welcome!)
  • install kdevelop
  • install trunk/playground/devtools/kdevelop4-extra-plugins/css
Ruan recently recently announced on kdevelop-devel that he will work on html/xml language support. There is hope for Quanta4!

Sunday, October 11, 2009

Quanta4 xdebug plugin

Hi Planet,

first, a short introduction: My name is Niko Sams, I'm from Austria. I have contributed to KDE for a while and ever since I planned blogging about - so here I am.

As a web developer and KDE user I need a good IDE. I use the great Quanta3 for years now, but it's dead now. So I started contributing to Quanta4 - well indirectly though various kdevelop plugins - those all will be used by Quanta4.
Yes - Quanta4 is not dead - we just need time (and developers).

What I've been working on recently is a XDebug (php debugger) plugin.


I started on this quite some time ago by creating a generic debugger infrastructure for kdevplatform - and port the kdevelop gdb plugin to that. In kdevelop3 every debugger plugin had it's own set of toolbars, views and everything - you can imagine how this looks like when you have 3 debuggers installed :D

For kdevplatform the common actions and views are now shared across debuggers.

Another important part was the new launch framework apaku introduced, with that we can have one Run » Launch Debug action that works for all debuggers. (Perhaps someone remembers the "Debug - Not yet working" action we had at the time of our latest KDevelop hack sprint)


You can follow the development here:

trunk/playground/devtools/kdevelop4-extra-plugins/xdebug
(for now only debugging local cli php scripts is supported)