Would love to collaborate

[knownasilya]

Hello! Love that others are tackling this as well! We've started a discussion on breach_core and I've started a similar module. See issue here, and project here. There is also this wip PR.

I was going the route of using packages that depend on breach_module packages, since only those can be modules, but the keyword approach was also a possibility. Would love to tackle this in tandem, and not have two so-so implementations :smile:

P.S. I found this project because my module told me there was one new module on npm that used breach_module lol.

[mblarsen]

Hi, happy to hear about this. Yeah sure lets work together on this.

Currently I'm working on the registry part. My first implementation was relying on the local NPM cache. I've almost rewritten it so that the modules maintains its own (but can use it to build initially).

I like the keyword/tag approach better, since the developer then actively commits to the NPM module as being a breach module.

What are your thoughts of integrating it with the browser?

• Overview page, with installed modules, and info to update (similar to the Atom editors)
• Search page
• Browse page -- likely the same thing.

[knownasilya]

I like the keyword/tag approach better, since the developer then actively commits to the NPM module as being a breach module.

I agree, plus it'll be easier to handle, since npm supports searching by tag, but my dependents method is more low level.

Browse page -- likely the same thing.

Agreed. Possibly with a fuzzy search if that is feasible with the speed of npm (maybe using typeahead.js). I think the core team wants to keep the installed modules UI part of breach_core as well as the actual managing of those modules, e.g. add, install, remove, etc.. But I feel like we can build it all into one, making it a better alternative and more manageable (although still using the internal management commands that are given to us).

Which client-side technologies are you looking to use? Breach_core uses angular.

P.S. I like your module name better, so I'll be contributing here, if you don't mind.

[mblarsen]

Today I committed a separation of the user local NPM, checkout the commit. It updates the repo once a day for now (incrementally). The search to match is using a fuzzy search now.

I would love to get started on the interface. Do you have any progress on that?

Should I add you as owner to the project?

Michael Bøcker-Larsen http://www.gofundme.com/plant-a-tree-api http://about.me/mblarsen

On Monday 14 July 2014 at 17:36, Ilya Radchenko wrote:

I like the keyword/tag approach better, since the developer then actively commits to the NPM module as being a breach module.

I agree, plus it'll be easier to handle, since npm supports searching by tag, but my dependents method is more low level.

Browse page -- likely the same thing.

Agreed. Possibly with a fuzzy search if that is feasible with the speed of npm (maybe using typeahead.js). I like your module name better, so I'll be contributing here, if you don't mind.

— Reply to this email directly or view it on GitHub (https://github.com/mblarsen/breach-module-manager/issues/1#issuecomment-48891063).

[knownasilya]

Sorry, I updated my previous comment (slow wifi here on train).

Would love to get a sense of where you were going with the UI, before I jumped in. What technologies were you planning on using, etc..

I would love to get started on the interface. Do you have any progress on that?

Not really, but would love to tackle that as soon as we can decide on layout. I do like the Atom interface, although browsing installed packages is a little tedious, needs some kind of optional grouping, maybe by keyword/category..

Should I add you as owner to the project?

Might be easier that way.

[mblarsen]

Regarding layout, lets just start out using a simple table like view similar to the npm search keyword result.

Angular goes very nicely hand in hand with the modularity of breach.

Might be easier that way.

Done, I've been added as collaborator.

Searching by tag

I can update it to use that method. That will make for a quick init of the module. Will check your repo.

[mblarsen]

Moving trains FTW!!

[mblarsen]

Does https://skimdb.npmjs.com/registry/ support incremental updates?

If not, we can just skip my impl with endKey-date and always fetch from the repo. Since the doc will be really small I guess.

[mblarsen]

Do you have any documentation on this api anyway?

[knownasilya]

@mblarsen there is no docs, it's just couchdb and I had to ask isaacs about how to query it. So it might not be the best option. I think what you're going with is good for now.