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

List:       kde-devel
Subject:    Re: [patch] New KEdit ready, please review
From:       Mickael Marchand <m.marcha () alemtid ! asso ! fr>
Date:       2001-11-26 10:41:38
[Download RAW message or body]

Hmm, ok, i can try that then, just give me some example please, i don't know how
to do it :/
actually, i was thinking to use the kregexpeditor implementation from kdeutils, maybe you mean
rewriting it in kdelibs ? but this will add a lot of stuff in kdeui then
actually, using kdeutils' kregexpeditor needs to link with kpart (see
khtml_find in cvs) i think
        m_editorDialog = KParts::ComponentFactory::createInstanceFromQuery<QDialog>(
		"KRegExpEditor/KRegExpEditor", QString::null, this );
this line create the editor, i think it needs to use kpart for that...
is there any other way to 'call' the editor ?

if anyone can point me to a url/example where i can see how to implement
interfaces without linking with kpart, it would be usefull :), i'm quite lost with interfaces now
...

thanks,
Mik

On Mon, Nov 26, 2001 at 10:54:40AM +0100, David Faure wrote:
> On Monday 26 November 2001 10:36, Simon Hausmann wrote:
> > On Mon, Nov 26, 2001 at 10:23:47AM +0100, David Faure wrote:
> > > On Monday 26 November 2001 07:22, Mickael Marchand wrote:
> > > > Sadly, it is not possible to add KRegExpEditor to KEdFind because it   
> > > > would require linking kdeui with kpart, this also prevents us from using
> > > > the KTextEditor interface :/ (kdelibs/interface/ktexteditor/)
> > > 
> > > Really ? kdeui can't link to kparts, for sure, but I thought that the kregexpeditor
> > > was dynamically opened... Can't kdeui dlopen that lib, which itself links to kparts ?
> > > I'm not sure how the regexp-editor interface is structured. Simon ? 
> > 
> > That should work just fine. The regexp editor is a real interface
> > that does not require any extra linkage. 
> 
> Great, I supposed so - Mickael, can you give it a try ?
> In case of problems/questions, ask Simon ;) Hehe :)
> 
> > It doesn't work for the texteditor stuff though because what's contained in 
> > interfaces/ktexteditor are no real interfaces but base classes that 
> > require linkage against a libktexteditor, which in turn links against 
> > kparts. (that sucks, if you ask me :)
> 
> Ah, took me 2 times to understand this. Ok. Well, isn't that like
> BrowserExtension, i.e. we have the problem of the moc-generated files,
> whose symbols shouldn't be duplicated ? There isn't such a problem
> in the regexpeditor interface, right ?
> 
> -- 
> David FAURE, david@mandrakesoft.com, faure@kde.org
> http://perso.mandrakesoft.com/~david/ , http://www.konqueror.org/
> KDE 3.0: Konquering the Desktops
>  
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

-- 
Mickael Marchand
Elève-ingénieur / Engineer student
Ecole des Mines de Douai - France
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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