[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quanta-devel
Subject:    Re: [quanta-devel] KDE 4.0 release plan
From:       Andras Mantia <amantia () kde ! org>
Date:       2007-03-16 12:03:10
Message-ID: 200703161403.14802.amantia () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

On Friday 16 March 2007, Andrew Lowe wrote:
> Andras,
> Things are starting to quieten down in my house (baby number 3 is now
> 9 weeks old and sleeping much better)...

I know the feeling, altough I can sleep quite well with a screaming 
baby. ;)

> From what I understand KDevelop rewrite was causing code to be very
> unstable and writing the Quanta plugins would have been pretty much
> impossible due to a moving target?

Not impossible, but there was a time when things were so broken, that we 
abandoned the porting and started to write a new parser instead.

> Has this changed - is KDevelop at 
> a pretty stable state, or are they still making major changes?

They should be more stable now, but I cannot really comment as I didn't 
follow the commits lately (13000 unread mails from kde-commits list...)

> I guess I am saying I would like to help, but need some guidence as
> to what you want me to do, and how to do it...
>
> I will look into what I can do on the CSS editor over the weekend and
> let you know what I think I can do.  I take it the existing code all
> lives at: kdewebdev/quanta/components/csseditor/ and you want it to
> become a plugin for KDevelop?

Porting the CSS Editor is something that I think can be done relatively 
independently from the rest of Quanta. Actually that part was 
completely written by one developer, and I don't really know the code. 
The only real connection to the Quanta "core" is 
QuantaApp::slotInsertCSS() (in the old code, of course), which finds 
what part of the document should be passed to the CSS editor.
The idea would be to make a KDevelop plugin which has an interface where 
you can invoke the editor with a text as an argument. Altough written 
for KDevelop 3, the DESIGN file from kdewebdev/quanta (from turnk 
version) desribes how this plugin based development is done, and for 
example the tagdialogs plugin (and the lib/tagdialogsif.* files) can 
give you an idea how communication between different plugins can be 
implemented. Has the "core" of Quanta itself is a plugin, such 
communication will be needed.

And yes, the css editor lies in the part you mentioned. As it was never 
ported to the plugin infrastructure, it means that it must be also 
converted to use Qt and KDE4 classes.

Andras



-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

[Attachment #5 (application/pgp-signature)]

_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel


[prev in list] [next in list] [prev in thread] [next in thread]