search

dcchambers / vb4c

vb4c has been archived - please direct all conversation to the original cVim project page: https://github.com/1995eaton/chromium-vim
MIT License
141 stars 13 forks source link

vb4c status update #13

Open dcchambers opened 4 years ago

dcchambers commented 4 years ago

Hi folks, I've posted a status update on my blog: https://chambers.io/vb4c/2020/04/15/vb4c.html

TL;DR - After a bit of life chaos due to COVID-19, work on vb4c is progressing. I am familiarizing myself with the codebase so I can better understand the permissions it needs in order to get it approved for release on the chrome web store.

I have created a project in GitHub for tracking progress on the road to 1.0 release.

Thanks for the patience, and I hope to have good news to share soon.

budRich commented 4 years ago

Great to hear that you are still on. Looking forward to see the roadmap, I got nothing better to do, and will try to help out if i can. cVim/vb4c is such a good extension and by just ironing out some annoying bugs it would be great. (a completely reworked config system would make it perfect (i got some ideas ;).

If you want to "modernize" the code, i see two viable options:

  1. Do a new extension from scratch and clone the functionality, not the code from cVim.
  2. Try to isolate the different parts of the current extension, (GUI, settings parsing, keyboard listener, search engines e.t.c) and "modernize" them individually.

It sounds like you are opting for 2, i think 1 is better and faster and more fun.

fow5040 commented 4 years ago

hey - digging into the code base and making a case for certain permissions is no fun! If you'd like any help on getting this approved I would be happy to help in any way I can. Maybe I can take on a specific permission or two and make a case for it.

cheers

artem-nefedov commented 4 years ago

The fact that you got denied despite requesting the exact same permissions as original extension is kinda ridiculous. I hope this will be resolved successfully.

sangeet commented 4 years ago

Any news regarding the extension approval? I personally don't mind extracting from source and using it even a bit, but I'm sure there are several pre-existing cvim users who would like the convenience of having the extension readily available and have their createHint broken and probably frustated with no way of finding it back.

Maybe see if anyone can get in touch with the original developer and see if he opens up the project to new maintainers. That being said, the original cvim extension is also missing from the Chrome web store so I'm not sure what's up with that (maybe he disabled it, maybe Google nuked it away?).

The original developer has a twitter (inactive since 2018) and an instagram but I'm not sure if he's still active there (got no IG account to verify dates on posts). Maybe he still can push the cvim extension back to the store. If that's possible, then it will save everyone the hassle becuase let's be honest, with the extension having little accessibility without Chrome store, it'll eventually fade away when I believe it still has a lot of room for improvement and growth.

dcchambers commented 3 years ago

Since the original https://github.com/1995eaton/chromium-vim project has been updated to fix the "hints" feature, and I have not had the time to be an active maintainer of this project, I will be placing this repo into archived status. For more details, please see this comment.