[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [cdt-dev] Bad readability: Includes list in Project Explorer | 
- From: Moritz Strübe <moritz.struebe@xxxxxxxxxx>
- Date: Fri, 13 May 2022 16:47:22 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=mathema.de; dmarc=pass action=none header.from=mathema.de; dkim=pass header.d=mathema.de; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=wtuW2zoUO80A/yscptTpapbf0Z1WSlsuHT2xPjSMUKQ=; b=kn7Q/qM06rSJirr2Fy+WDaPa/e3saMBgPgOodALibgn++ziaUmF3I3OleJq5rH6kduTbievAcfnWUBxamWJ6z6CIyhKQpueZ8udylzi18Y44qxY6wSr3p83z7HW9fLVjM54JmefWSjxXe5Fo58xpeKHWOls5ULUCKMkjH+Aad8m205cZkHlRV6H+JoT6lbgj1aQ7oUa3OI37fz0KB81CrLaCEf+w7aUjiBYgkpq4asflWjuvUpv6v1yQHye7DJtcsAY3+t/CfEB8YNdFe0x3QqTB+inEqf8A/Tl+1tlZghEScgYMkSRB400TDM3kbWWU9wuPVm8UiMFstpXId6AAAQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=d9bdYRLjWDLldQkRGyvsbvgpfez9vIZI9uh6tllWWotfw69kL3pWM6kbWoygsRrVNgkgY42xrDOMObt/fZ7KG03s+uLHr+LXvTtDdCQUmzALLE3dE6NfZiPIyTti1LY1RtfXOvoJXq5+NmnrHL9BcYvrPfKcirq//ZYHh+HShcxIbN8/Jbz2p9g7Lcp5PtWzVQJtMWExFs6jHMAmemmnjT5v6ZtnsQ0tIJ5l9cdhQI6IJw0ZuXbZuAP9e0feFKuCijxS2YaVo7yCi58pMnYux9+4/VHBSBz16zb/ofMTv+9jNw/P6MykhjJ4dxkcfge105JwsJwdM/++2cGwUTMkpQ==
- Delivered-to: cdt-dev@xxxxxxxxxxx
- List-archive: <https://www.eclipse.org/mailman/private/cdt-dev/>
- List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
- List-subscribe: <https://www.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
- List-unsubscribe: <https://www.eclipse.org/mailman/options/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
  
    Hey Jonha,
    
    ok I got 3 aggregation-strategies working. Now I'm struggling to
    make them configurable. I was thinking of having a drop-down entry
    for the includes folder. Unfortunately I'm overwhelmed by the
    abstraction layers. Maybe you (or someone else) can point me in the
    right direction. Also where to save the state and connect things. I
    don't think we need to persist things in the project*, but it
    probably doesn't hurt.
    
    Morty
    
    * IMO this should be project option, as the advantages of the
    different strategies depends on the layout of the include
    directories.
    
    
On 26.03.22 02:28, Jonah Graham wrote:
    
    
      
      
      
        Hi Morty,
          
          
          That would be a great improvement. I suppose once upon a
            time when includes were /usr/include having the full name
            all the time wasn't too much of an issue, but I agree the
            docker way is too long.
          
          
          It would be merged (assuming it was well
            written/complete/etc). It is a CDT change - rather than
            point you at where to change, I have thrown together a first
            working version. You can use or discard it - its intention
            is to show you where to start looking:
          
          
          It gives this instead of flat:
          
          
          
          Doing something like JDT where there is a flat or
            hierarchical option may be a good idea:
          
          
          
          
          
          But even better may be a semi-flattened
            semi-hierarchical where all the parents with just one child
            folder are collapsed to the same level in the tree (similar
            to your option 3 mock screenshot?).
          
          
          I also really like your option 1 where in the UI you show
            the docker name of the folders rather than the .metadata
            name where they are copied. Hopefully you can play around to
            see what works best.
          
          
          
          
          
          Let me know how I can help support you getting this
            feature implemented.
          
          
          PS This is a pretty fun bit of the code to work in - you
            get to see visible changes quickly and most of the code
            changes are internal packages of CDT so you don't have some
            of the other headaches of API compatibility. You'll notice
            that this is also some of the oldest parts of CDT, dating
            back to the early 2000s, so feel free to modernize code
            where you find it appropriate. For review sake it would help
            if modernized code was presented in separate commits.
          
          
          Jonah
          
          
          
          
          
          
          
        
          
          
            Hey,
              
              I finally have some time to work on docker improvements.
              One of the things bugging me are the include paths in the
              project. While they are already hard to read when they are
              no systems paths, but things get worse when they are
              copied from a docker image:
              
              
 
              
              Thus: Is there an easy whey to fix this? 
              One of my ideas was to introduce some kind of mapping.
              Showing the actual path within the docker, but listing the
              copied files.
              
              The second was to clip the paths on the left side instead
              of the right. But that is probably far from simple,
              because it breaks the rendering hierarchy, right?
              A third option would be to introduce a hierarchy level.
              Adding one when all paths share the same base-path (or
              some other magic):
              
              
 
              
              Thinking about it, the third option is probably the most
              non-confusing for the end-user, while still being
              implementable with reasonable effort (this is a wild
              guess, though).
              
              Any thoughts? Would a patch be merged? Can this be
              implemented in CDT or do I have to adjust Eclipse?
              Pointers to the code to look at are welcome, too. :)
              
              Morty
              
              
              
-- 
MATHEMA GmbH
Schillerstraße 14 | 90409 Nürnberg
Telefon: +49 (0)911 180778-50
E-Mail: moritz.struebe@xxxxxxxxxx | Web: www.mathema.de
Geschäftsführer: Andreas Hanke, Thomas Haug
Handelsregister: HR B 35517, Nürnberg/Bayern
            
            cdt-dev mailing list
            cdt-dev@xxxxxxxxxxx
            To unsubscribe from this list, visit 
              https://www.eclipse.org/mailman/listinfo/cdt-dev
          
         
       
      
      
      _______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
    
    
    -- 
MATHEMA GmbH
Schillerstraße 14 | 90409 Nürnberg
Telefon: +49 (0)911 180778-50
E-Mail: moritz.struebe@xxxxxxxxxx | Web: www.mathema.de
Geschäftsführer: Andreas Hanke, Thomas Haug
Handelsregister: HR B 35517, Nürnberg/Bayern