unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* porting GNU Emacs to kde (?)
@ 2004-03-09 21:34 Giannis Georgalis
  2004-03-14  2:56 ` Richard Stallman
  0 siblings, 1 reply; 25+ messages in thread
From: Giannis Georgalis @ 2004-03-09 21:34 UTC (permalink / raw)



Hello !

I was thinking of trying to port GNU Emacs to the KDE[1] environment
in the near future. The main incentive for this decision, is my
desire to start using kdevelop[2] as my IDE (which is impossible
without Emacs ;-)). This is possible in KDE (and kdevelop in specific)
through the KPart[3] interface. This roughly means that Emacs should
become a shared object and export some functionality that implements a
well defined Editor interface. This way, Emacs can be used throughout
the KDE environment WHEREVER an editor is needed[4].

This is quite a complex task. And as I see it, it could be done in
two steps:
a) Make Emacs use the kde libraries as done with the gtk2 port.
b) "Organize" Emacs in a way that it can elegantly implement the
Editor interface mentioned above.

Note, that I'm familiar with the effort of Marco Correia (that also
send a mail to this list with a similar context), who begun (but
stopped eventually) to implement an Emacs KPart[3], using the
emacs-server interface.
Though Marco's approach (as he told me) is possible, IMHO it is
better to follow the former method because it can achieve far better
integration with the kde environment, while implementing all the
necessary "hooks" (and knowledge/code base) for a similar integration
with the GNOME environment (ORBit(?)), which I suspect, follows a
similar pattern.

As I'm not able to estimate the difficulties/complexity of such an
approach (I'm not familiar with the emacs internals), I firstly would
like to ask your opinion on the above matters and whether you think
this whole project would be useful from the "Emacs perspective".
Lastly, are there any other parameters, that would make this project
more difficult/impossible (eg. policy / ideological issues)?

Thank you,
Giannis

References:

[1] http://www.kde.org
[2] http://kdevelop.org
[3] http://en.wikipedia.org/wiki/KPart
[4] see also vimpart.

-- 
question = ( to ) ? be : ! be;
                -- Wm. Shakespeare

^ permalink raw reply	[flat|nested] 25+ messages in thread
* porting GNU Emacs to kde (?)
@ 2004-03-11 15:55 Giannis Georgalis
  2004-03-14  5:39 ` Masatake YAMATO
  0 siblings, 1 reply; 25+ messages in thread
From: Giannis Georgalis @ 2004-03-11 15:55 UTC (permalink / raw)



Hello !

I was thinking of trying to port GNU Emacs to the KDE[1] environment
in the near future. The main incentive for this decision, is my
desire to start using kdevelop[2] as my IDE (which is impossible
without Emacs ;-)). This is possible in KDE (and kdevelop in specific)
through the KPart[3] interface. This roughly means that Emacs should
become a shared object and export some functionality that implements a
well defined Editor interface. This way, Emacs can be used throughout
the KDE environment WHEREVER an editor is needed[4].

This is quite a complex task. And as I see it, it could be done in
two steps:
a) Make Emacs use the kde libraries as done with the gtk2 port.
b) "Organize" Emacs in a way that it can elegantly implement the
Editor interface mentioned above.

Note, that I'm familiar with the effort of Marco Correia (that also
send a mail to this list with a similar context), who begun (but
stopped eventually) to implement an Emacs KPart[3], using the
emacs-server interface.
Though Marco's approach (as he told me) is possible, IMHO it is
better to follow the former method because it can achieve far better
integration with the kde environment, while implementing all the
necessary "hooks" (and knowledge/code base) for a similar integration
with the GNOME environment (ORBit(?)), which I suspect, follows a
similar pattern.

As I'm not able to estimate the difficulties/complexity of such an
approach (I'm not familiar with the emacs internals), I firstly would
like to ask your opinion on the above matters and whether you think
this whole project would be useful from the "Emacs perspective".
Lastly, are there any other parameters, that would make this project
more difficult/impossible (eg. policy / ideological issues)?

Thank you,
Giannis

References:

[1] http://www.kde.org
[2] http://kdevelop.org
[3] http://en.wikipedia.org/wiki/KPart
[4] see also vimpart.

-- 
question = ( to ) ? be : ! be;
                -- Wm. Shakespeare

^ permalink raw reply	[flat|nested] 25+ messages in thread

end of thread, other threads:[~2004-03-30 19:30 UTC | newest]

Thread overview: 25+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-09 21:34 porting GNU Emacs to kde (?) Giannis Georgalis
2004-03-14  2:56 ` Richard Stallman
2004-03-18 11:15   ` Masatake YAMATO
2004-03-19  6:12     ` Danilo Segan
2004-03-19 14:08       ` Giannis Georgalis
2004-03-20  4:49     ` Richard Stallman
2004-03-19 14:05   ` Giannis Georgalis
2004-03-19 15:59     ` David Kastrup
2004-03-20  6:46       ` Danilo Segan
2004-03-20 18:26         ` mr mike
2004-03-21  4:59         ` Richard Stallman
2004-03-21  7:09           ` Lars Brinkhoff
2004-03-20 20:05       ` Giannis Georgalis
2004-03-21  4:58       ` Richard Stallman
2004-03-26 15:24         ` Giannis Georgalis
2004-03-26 17:17           ` Jan D.
2004-03-27 14:58             ` Giannis Georgalis
2004-03-29  6:44               ` Jan D.
2004-03-29 21:23                 ` Giannis Georgalis
2004-03-30 19:30                   ` Jan D.
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 15:55 Giannis Georgalis
2004-03-14  5:39 ` Masatake YAMATO
2004-03-15  4:57   ` Richard Stallman
2004-03-15  6:40     ` Masatake YAMATO
2004-03-16 19:03       ` Richard Stallman

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).