Re: [platform-core-dev] User Settings proposed solution document

["Michael Valenta" <Michael_Valenta@xxxxxxxxxx>]

Sorry. I neglected to mention that I
was assuming that the project was shared in some manner (i.e. through a
repository). The operation that reconciled the local coipy with the remote
would trigger the update. If a project was shared between local workspaces
then refresh local would have to be used.

Michael

Daniel Megert/Zurich/IBM@IBMCH Sent by: platform-core-dev-admin@xxxxxxxxxxx 18/08/2003 09:23 AM Please respond to platform-core-dev

To:        platform-core-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-core-dev] User Settings proposed solution document

Michael,

regarding 1: if I have workspace A and workspace B who will trigger the
delta in B if I change the settings/settings file(s) in A? In other words:
who will trigger the RefreshLocal on the settings file(s)?

Dani


                    
                     
                     
          
             "Michael Valenta"
                     
                     
             <Michael_Valenta@  
                     
                    
             ca.ibm.com>    
                     
                     To
             Sent by:      
           platform-core-dev@xxxxxxxxxxx
      
             platform-core-dev    
                     
               cc 
             -admin@xxxxxxxxxx    
                     
                  
             g        
                     
                     
Subject 
                    
                  Re: [platform-core-dev]
User        
                    
                  Settings
proposed solution document 
             18.08.2003 14:57    
                     
                   
                    
                     
                     
          
                    
                     
                     
          
             Please respond to    
                     
                  
             platform-core-dev    
                     
                  
               @eclipse.org    
                     
                     
                    
                     
                     
          
                    
                     
                     
          





Daniel,

Here are the answers to your questions

1) The shared project settigns can be automatically picked up because they
will live in a project so there will be a delta generated if the contents
change.

2) There will be UI that supports the configuration of where a setting
lives. I agree that it would be benefitial to have the same update
mechanism for both project and platform settings. However, platform
settings cannot have automatic updates since they do not live in a project.
As a user, I would prefer to  have automatic update when possible
so the
proposal is to support this for shared project settings. For platform
settings, the plan is to provide a sync mechanism (similar to Refresh
Local).

3) I have heard different stories on this. The bottom line is that we are
not running on 1.4 now and we don't know when the switch will occur. So,
either we start now on 1.3 or wait for the switch to be thrown on 1.4.
The
plan is to start on 1.3 in a fashion that can easily be converted to 1.4
when the swith does occur.

Michael


                    
                     
                     
          
   Daniel                
                     
                     
     
   Megert/Zurich/IBM@IBMCH           To:
                     
            
   Sent by:                
 platform-core-dev@xxxxxxxxxxx          
      
   platform-core-dev-admin@e         cc:  
                     
          
   clipse.org                
       Subject:        Re:  
                
                    
        [platform-core-dev] User Settings proposed
   
                    
        solution document        
                    
   15/08/2003 04:17 AM              
                     
                
   Please respond to              
                     
                  
   platform-core-dev              
                     
                  
                    
                     
                     
          









After reading through the paper I have the following questions and
concerns:

- the document states that changes made to shared project settings will
be
loaded automatically because the settings will be in contained in the
workspace in one or more IFile(s). How will the automatic update be
achieved? Normally a refresh is either initiated by the user or by the
optional auto-refresh plug-in. Will you add a background job that refreshes
the files?

- how will platform settings be applied to the workspace? Will there be
a
UI that allows me to reject such settings? I think from user perspective
both platform and shared project settings are both shared settings and
should behave more or less the same i.e. update process and UI should be
very similar.

- the JDK level as stated in the 3.0 plan is clearly JDK level 1.4
therefore the statement "...we cannot depend on 1.4 API..." is
not correct.
The design decision should not be impaired just to be 1.3 compatible.


Dani



            "Michael Valenta"
            <Michael_Valenta@
            ca.ibm.com>    
                     
                     To
            Sent by:      
           platform-core-dev@xxxxxxxxxxx
            platform-core-dev    
                     
               cc
            -admin@xxxxxxxxxx
            g        
                     
                     
Subject
                    
                 [platform-core-dev]
User Settings
                    
                 proposed
solution document
            17.07.2003 15:29


            Please respond to
            platform-core-dev
              @eclipse.org







The next document describing a proposed solution has been posted at the
following URL:

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/settings_solution.html



If you have feedback, either annotate the bug report (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36965) or post on the
platform-
core-dev mailing list. It is planned that the implementation will begin
in
3
weeks so please provide feedback before than.

_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev


_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev