Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] New project model

Hi all,

 

I have posted the initial draft patch for the New Project Model functionality to the Project Model bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=115935

I’ve also attached some short comments on the new Core and UI functionality.

 

Your feed-back is very welcome.

 

Thanks,

Mikhail

 


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Voronin, Mikhail
Sent: Tuesday, January 09, 2007 7:55 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] New project model

 

Hi, Andrew,

 

ETA for draft patch is in two weeks (January, 23).

 

Regards,

Mikhail.

 

 


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew.Ferguson@xxxxxxxxxxx
Sent: Friday, January 05, 2007 2:10 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] New project model


hi Mikhail,

 do you have an ETA for the draft patch?

thanks,
Andrew

> Markus,
>
> UI of "New project model" patch is still mixed with old stuff and would
> be confusing people.
> I have to say that we need to wait till January.
>
> Regards,
> Mikhail.
>  
>
> >-----Original Message-----
> >From: cdt-dev-bounces@xxxxxxxxxxx
> >[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schorn, Markus
> >Sent: Monday, December 04, 2006 1:16 PM
> >To: CDT General developers list.
> >Subject: RE: [cdt-dev] New project model
> >
> >Yes, to be able to look at an unstable patch in December is helpful for
> >us.
> >Markus.
> >
> >-----Original Message-----
> >From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> >On Behalf Of Voronin, Mikhail
> >Sent: Freitag, 01. Dezember 2006 13:55
> >To: CDT General developers list.
> >Subject: RE: [cdt-dev] New project model
> >
> >Markus, will it be useful for you to have unstable patch in December or
> >it will be OK to wait till January (keeping in mind long holidays :))?
> >
> >Regards,
> >Mikhail.
> >
> >
> >>-----Original Message-----
> >>From: cdt-dev-bounces@xxxxxxxxxxx
> >>[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
> >>Sent: Friday, December 01, 2006 3:34 PM
> >>To: CDT General developers list.
> >>Subject: RE: [cdt-dev] New project model
> >>
> >>I don't think the prototype will be stable enough by the end
> >>of December
> >>to be committed to the database.
> >>The only thing that might be considered is posting the prototype (that
> >>might be buggy by that time) for review to the bugzilla.
> >>
> >>Mikhail
> >>
> >>-----Original Message-----
> >>From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> >>On Behalf Of Voronin, Mikhail
> >>Sent: Friday, December 01, 2006 3:19 PM
> >>To: CDT General developers list.
> >>Subject: RE: [cdt-dev] New project model
> >>
> >>Is it possible to contribute initial working prototype in december?
> >>
> >>P.S. Mikhail, did you look at abstract I submitted to EclipseCon? Any
> >>comments?
> >>
> >>Regards,
> >>Mikhail.
> >>
> >>
> >>>-----Original Message-----
> >>>From: cdt-dev-bounces@xxxxxxxxxxx
> >>>[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
> >Sennikovsky, Mikhail
> >>>Sent: Friday, December 01, 2006 2:47 PM
> >>>To: CDT General developers list.
> >>>Cc: Brunauer, Walter
> >>>Subject: RE: [cdt-dev] New project model
> >>>
> >>>Hi Markus,
> >>>
> >>>The New Project Model work is in progress now. Most of the new
> >>>functionality is implemented. Since most of the new Project Model
> >>>features depend on each other and affect different areas of
> >>>functionality we can not commit them in peaces to ensure CDT
> >integrity
> >>>and stability.
> >>>
> >>>We are currently planning to perform the major commit
> >>>containing most of
> >>>the primary functionality in the end of January 2007.
> >>>Since the commit is going to be quite big, we are definitely going to
> >>>post patches for review/testing to the New Project Model
> >>>bugzilla before
> >>>committing them.
> >>>
> >>>To bring some clarity to the integration process of the Core
> >>>New Project
> >>>Model with other core functionality here are some of my thoughts
> >>>regarding this:
> >>>
> >>>My plan is to make the integration of the New Project Model
> >with other
> >>>core functionality as painless as possible to avoid merge
> >>conflicts and
> >>>reduce amount of work necessary for integration. From the
> >>indexer point
> >>>of view all "information provider API" used by the indexer currently
> >>>(LanguageManager, ScannerInfoProvider, etc.) will be kept and will be
> >>>used in the normal way:
> >>>- Since the new project model will contain the new per-language
> >>>Includes/Symbols settings functionality that will replace the current
> >>>path entries framework, the new ScannerInfoProvider is
> >>implemented that
> >>>provides the scanner info based upon the New Project Model settings.
> >>>- since the New Project Model will allow language settings
> >>>customization
> >>>(i.e. in case more than one languages are associated with one content
> >>>type, the New Project Model will allow specifying the language to be
> >>>used).
> >>>I have added few new methods to Language manager for getting the
> >>>language e.g. given an IFile, etc. to allow obtaining the necessary
> >>>language for the file. I have also modified the
> >>LanguageManager clients
> >>>to use these new methods.
> >>>
> >>>Please let me know if you have any questions or concerns about
> >>>the dates
> >>>or integration details. We could discuss them by phone if necessary
> >>>(e.g. on the next Indexer call)
> >>>
> >>>Regards,
> >>>Mikhail
> >>>
> >>>
> >>>-----Original Message-----
> >>>From: cdt-dev-bounces@xxxxxxxxxxx
> >[mailto:cdt-dev-bounces@xxxxxxxxxxx]
> >>>On Behalf Of Schorn, Markus
> >>>Sent: Friday, December 01, 2006 12:16 PM
> >>>To: CDT General developers list.
> >>>Cc: Brunauer, Walter
> >>>Subject: [cdt-dev] New project model
> >>>
> >>>Hi Mikhail!
> >>>I am wondering what the current progress on the new project model is.
> >>>I'd like to understand when you are planning to commit the changes to
> >>>CVS.
> >>>Is it going to be a all-in-one commit (which milestone?), or are you
> >>>planning a couple of independent steps? Can we get early access to
> >>>patches, so that we can try out things up front?
> >>>
> >>>Markus.
> >>>_______________________________________________
> >>>cdt-dev mailing list
> >>>cdt-dev@xxxxxxxxxxx
> >>>https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>>_______________________________________________
> >>>cdt-dev mailing list
> >>>cdt-dev@xxxxxxxxxxx
> >>>https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>>
> >>_______________________________________________
> >>cdt-dev mailing list
> >>cdt-dev@xxxxxxxxxxx
> >>https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>_______________________________________________
> >>cdt-dev mailing list
> >>cdt-dev@xxxxxxxxxxx
> >>https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>
> >_______________________________________________
> >cdt-dev mailing list
> >cdt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >_______________________________________________
> >cdt-dev mailing list
> >cdt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev


************************************
********************************** Symbian Software Ltd is a
company registered in England and Wales with registered number
4190020 and registered office at 2-6 Boundary Row, Southwark,
London, SE1 8HP, UK. This message is intended only for use by the
named addressee and may contain privileged and/or confidential
information. If you are not the named addressee you should not
disseminate, copy or take any action in reliance on it. If you have
received this message in error please notify postmaster@xxxxxxxxxxx
and delete the message and any attachments accompanying it
immediately. Neither Symbian nor any of its Affiliates accepts
liability for any corruption, interception, amendment, tampering or
viruses occurring to this message in transit or for any message
sent by its employees which is not in compliance with Symbian
corporate policy. *************************************************
*********************


Back to the top