CEDET

I'm currently finalizing the 'to-emacs' and 'from-emacs' branches for
proper merging, and I think this would be a good time to start removing
some packages from CEDET trunk and move their development over to
Emacs. I think the following two packages would be good candidates:

- Speedbar, namely the two files 'speedbar.el' and 'sb-image.el'. The
  other Speedbar modules would stay in CEDET, but we should take a good
  look at them - if they are working and useful, they might be good
  additions to Emacs, otherwise we should move them to obsolete (like we
  already did with sb-w3 and sb-gud).

- ezimage.el, together with the xpm images

I also thought about moving EIEIO, but that would mean that we have to
drop support for Emacs 23.1. So I would suggest to keep it for now, but
in the future, patches to EIEIO should be directed to emacs-devel. Most
EIEIO development in the past two years was done in Emacs trunk anyway.

-David

Re: [CEDET-devel] Moving development of certain packages to Emacs trunk From: Eric M. Ludlam <ericludlam@gm...> - 2012-09-13 00:07 On 09/12/2012 03:50 PM, David Engster wrote: > I'm currently finalizing the 'to-emacs' and 'from-emacs' branches for > proper merging, and I think this would be a good time to start removing > some packages from CEDET trunk and move their development over to > Emacs. I think the following two packages would be good candidates: > > - Speedbar, namely the two files 'speedbar.el' and 'sb-image.el'. The > other Speedbar modules would stay in CEDET, but we should take a good > look at them - if they are working and useful, they might be good > additions to Emacs, otherwise we should move them to obsolete (like we > already did with sb-w3 and sb-gud). The file dframe.el is core to speedbar also. > - ezimage.el, together with the xpm images That is a good idea too. > I also thought about moving EIEIO, but that would mean that we have to > drop support for Emacs 23.1. So I would suggest to keep it for now, but > in the future, patches to EIEIO should be directed to emacs-devel. Most > EIEIO development in the past two years was done in Emacs trunk anyway. I have wondered about that also and agree it may be too soon to drop it. Eric

Re: [CEDET-devel] Moving development of certain packages to Emacs trunk From: <emacs18@gm...> - 2012-09-13 06:19 I would love to see eieio moved to emacs. Why? If cedet did not have eieio, then cedet can be packaged so people can install cedet with `M-x package-install'. With EIEIO being part of cedet, there is a conflict. To execute package-install eieio is required. However cedet refuses to be installed when eieio is already loaded. The obvious solution it seems like to me is to migrate eieio out of cedet. ----------------------- On Wed, Sep 12 2012, Eric M. Ludlam wrote: On 09/12/2012 03:50 PM, David Engster wrote: > I'm currently finalizing the 'to-emacs' and 'from-emacs' branches for > proper merging, and I think this would be a good time to start removing > some packages from CEDET trunk and move their development over to > Emacs. I think the following two packages would be good candidates: > > - Speedbar, namely the two files 'speedbar.el' and 'sb-image.el'. The > other Speedbar modules would stay in CEDET, but we should take a good > look at them - if they are working and useful, they might be good > additions to Emacs, otherwise we should move them to obsolete (like we > already did with sb-w3 and sb-gud). The file dframe.el is core to speedbar also. > - ezimage.el, together with the xpm images That is a good idea too. > I also thought about moving EIEIO, but that would mean that we have to > drop support for Emacs 23.1. So I would suggest to keep it for now, but > in the future, patches to EIEIO should be directed to emacs-devel. Most > EIEIO development in the past two years was done in Emacs trunk anyway. I have wondered about that also and agree it may be too soon to drop it. Eric ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Cedet-devel mailing list Cedet-devel@... https://lists.sourceforge.net/lists/listinfo/cedet-devel

Re: [CEDET-devel] Moving development of certain packages to Emacs trunk From: Eric M. Ludlam <ericludlam@gm...> - 2012-09-13 11:14 The various CEDET tools no longer develop in lock-step with EIEIO features. We could probably post a stand-alone EIEIO, and CEDET separately, and let that last EIEIO stand in for Emacs 23.1 users. The last two times I worked on EIEIO in any depth (performance, and safely loading saved files,) it was about adding a feature without breaking anything else in CEDET. I would expect that trend to continue. Eric On 09/13/2012 02:18 AM, Richard Kim wrote: > I would love to see eieio moved to emacs. Why? If cedet did not have > eieio, then cedet can be packaged so people can install cedet with > `M-x package-install'. > > With EIEIO being part of cedet, there is a conflict. To execute > package-install eieio is required. However cedet refuses to be > installed when eieio is already loaded. The obvious solution it seems > like to me is to migrate eieio out of cedet. > > > ----------------------- > On Wed, Sep 12 2012, Eric M. Ludlam wrote: > > On 09/12/2012 03:50 PM, David Engster wrote: >> I'm currently finalizing the 'to-emacs' and 'from-emacs' branches for >> proper merging, and I think this would be a good time to start removing >> some packages from CEDET trunk and move their development over to >> Emacs. I think the following two packages would be good candidates: >> >> - Speedbar, namely the two files 'speedbar.el' and 'sb-image.el'. The >> other Speedbar modules would stay in CEDET, but we should take a good >> look at them - if they are working and useful, they might be good >> additions to Emacs, otherwise we should move them to obsolete (like we >> already did with sb-w3 and sb-gud). > > The file dframe.el is core to speedbar also. > >> - ezimage.el, together with the xpm images > > That is a good idea too. > >> I also thought about moving EIEIO, but that would mean that we have to >> drop support for Emacs 23.1. So I would suggest to keep it for now, but >> in the future, patches to EIEIO should be directed to emacs-devel. Most >> EIEIO development in the past two years was done in Emacs trunk anyway. > > I have wondered about that also and agree it may be too soon to drop it. > > Eric > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cedet-devel mailing list > Cedet-devel@... > https://lists.sourceforge.net/lists/listinfo/cedet-devel > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Cedet-devel mailing list > Cedet-devel@... > https://lists.sourceforge.net/lists/listinfo/cedet-devel >

1 message has been excluded from this view by a project administrator.