Hey - I now have a video https://youtu.be/9EPaBi1_pwo
It explains in more detail how "Code Seeker" could work. And I included a couple of your suggestions.
Hope you can take a look and give me some additional feedback.
Thanks
I love abstractions, although at times they become a barrier to edge use cases. I guess the art is determining how much to abstract.
Perhaps I am oversimplifying the way I was imagining the search. In my mind it could simply be a pattern match (including special characters) and return the results.
Then the zoom in/out capability would allow you to determine if the result is applicable.
Agreed - copy and paste can definitely be problematic.
DRY typically is discussed as it relates to a single project.
What are your thoughts on this? Code reused across projects or repos is not the same. We can and should have duplicated code but why write it from scratch? For a simple example if I always want to have an Avatar in a navbar, why not make it easy to find and reuse in another project.
We though we may be able to actually show the license type as well. However keeping it simple to start with and just track new ideas/improvements.
The Code Seeker feature would not actually apply changes, it will allow you to import into whichever IDE you are using and the mechanism or VCS you currently use will still apply. Does this make sense or am I not understanding the Control matters part?
Indexing and Searchability are going to be interesting to implement. I use IntelliJ and Rubymine and at times the indexing is too heavy handed and they are only indexing the current project.