I’ve just merged all webdevelopment related plugins except PHP & PHP-Docs into Quanta git. You can get them all in one place now by cloning Quanta: http://gitorious.org/kdevelop/quanta
Since I also moved all halfworking plugins to UNPORTED (they don’t get installed), you should be fine by just installing all of Quanta to get the plugins. If you only want one of them, going into it’s subfolder and building it standalone should hopefully still work though.
In other notes: Thanks to Ruan Styrdom for starting work on a PHP formatter plugin for KDevelop. It uses phpStylist and it’s already somewhat working. Awesome :)
/me is off to more GSOC hacking, bye
Yay I got a GSOC slot :)
So I hope I don’t have to introduce myself anymore to you guys. Instead I’ll show you what I’ve planned to do over the summer:
Motivation for Proposal / Goal:
Back in KDE 3 times, Quanta+ was one of the reasons for me to use KDE. In my eyes it was the IDE for web development out there, and I loved to use it. Sadly it’s bitrotting nowadays without a finished KDE 4 port. That, combined with the fact that more and more distributions drop all KDE 3 packages, makes the need for a port more urgent than ever.
Thankfully, KDevelop 4 is nearing it’s first release and the KDevplatform is mature enough nowadays. This means that during summer I shall finish the port of Quanta+ to KDevplatform and supply it with all the plugins required for a proper webdevelopment IDE. My goal is it to provide a proper IDE for PHP webdevelopment. In more detail:
- make Quanta+ 4 compile
- remove obsolete plugins or code parts in Quanta+
- port required plugins to KDevplatform structure
- polish PHP plugin, including XDebug support
- polish Script Execute plugin
- polish CSS plugin
- get a first working version of a XHTML/XML plugin, if time allows even with HTML (SGML) support
- support autocompletion
- support inline validation
- polish the UI/Workflow for Webdevelopment
- hide KDevelop/C++ specific actions
- add templates for common PHP frameworks
Today at work I had my first contact with Redaxo, a German contact management system written in PHP and based on MySQL. I’ve heard of it before but never used it, there always seemed to exist better solutions - Drupal for example. But the company I work for already committed itself to Redaxo for this client. So no chance to work with Drupal this time - a pity.
But new experience with other solutions is a great thing. I thought Redaxo had its right to exist: its very small.
Here I don’t mean the filesize or whatever - I mean the size of the admin panel to begin with. It has not that many features. It’s very easy to understand. The average John Doe which is not that websavvy wont be confused by a multitude of choices. And I think I got to know pretty much all of Redaxo in just a few hours — which I can’t say about the steep learning curve of Drupal. And since the website of this client will be small I first thought Redaxo will do quite good.
The deeper I dug into Redaxo the more annoyed I got by its shortcomings though: There are modules and addons with which you can do pretty much all you need. But not one module I used was ready out of the box. Always I had to do adjustments. Drupal does much better here. And what you can do with overloading in Drupal is millions of light years ahead of what Redaxo is able to do. Oh and the developers of Redaxo really should take a look at Drupals documentation! After some searching on the official website I stuck to
grep -R "function XXX" . for Api references…
Yes! I’ve finally done it. I’ve moved my website to Drupal, which is so much better than my old 3co stuff. Tons of great modules out there and those I couldn’t find for Drupal 6, which was recently released, I ported. Well not all of them, there are still some I’m really looking forward. On the top of my list are definitely the spam module and the Akismet module. Minutes after my move I got my first spam comment…
Well let’s see how I might get involved into Drupal development. I already filed some patches for the following modules:
- Marksmarty: better GeSHi support and some other minor things, but it doesn’t seem to be what the maintainer wants. I’ll have to move it into another extra-module then. Also some work to separate Smartypants and Markdown into distinct modules. Furtheron I’ve added support for PHP Markdown’s no-markup mode. This as well needs some more work. Maybe it will be dropped again and the pristine Drupal HTML Filter will be used, lets see.
Very funny and a great style of painting, though only webdevs will fully appreciate it.
Yesterday, the latest working draft of XHTML 2.0 was released. Oh my, what would I give to live in the future - like in 5-10 years from now. In a paradise for every web developer where XHTML 2.0 was the common standard and all browsers support it…
Ok, enough of that
day night dreaming. Here are the “Major Differences with XHTML 1” I’m most looking forward:
- Images in every element - no need for fancy image replacement!
- Any element can serve as a link. Very nice! That way you won’t have to use something like
<li href="...">...</li> will do it.
- Navigation lists
- Last but not least the
role attribute. That will be a good replacement for semantic classes such as
<p class="note"> at least if all browsers support CSS 2 selectors (