Integrate with busy-signal

noseglid / atom-build

:hammer: Build your project directly from the Atom editor

https://atom.io/packages/build

MIT License

248 stars 97 forks source link

Integrate with busy-signal #421

Closed steelbrain closed 8 years ago

steelbrain commented 8 years ago

busy-signal is a base Atom package that allows it's consumers to indicate to the user that something is happening. It has an easy to use API.

The main benefit of using it is that it'll make your own codebase cleaner while providing a unified place for users to see if something is happening.

Edit: Here's a bittersome discussion on the same topic that happened on linter repo

noseglid commented 8 years ago

It's funny. We had the same idea. I'm actually working on something similar right now: https://atom.io/packages/busy

It's not ready yet, but I'll be looking to use that instead

steelbrain commented 8 years ago

Any particular reason of having two packages? We could both collaborate on one

noseglid commented 8 years ago

Not really no. I had just thought about it for a few weeks and wanted to follow through :)

steelbrain commented 8 years ago

Great, I've given you push access to the busy-signal package, which also means publish access on APM. Lets collaborate on just one :)

danielbayley commented 7 years ago

@noseglid @steelbrain So what happened here in the end?

If I have build and linter installed (as many probably do) I have all this extra stuff clogging up the status bar…

mangecoeur commented 7 years ago

Same issue, bit distracting...

rapgenic commented 7 years ago

I'm quite sorry for doing this, but since there are still two different packages, and I need my working environment as clean as possible, I created two bridge packages, which pretend to be busy or busy-signal, but actually just call the other one's API.

atom-busy-unifier-ng for whom wants only @noseglid busy
atom-busy-unifier-sb for whom wants only @steelbrain busy-signal

I hope they soon won't be useful anymore, and will be replaced by a single busy package :)

But for now, they should be useful to resolve the clogging problem...

They should work, but I didn't have enough time to test them thoroughly, so any feedback or bug report is welcomed :)

laughedelic commented 7 years ago

It's been almost a year. Do we really need two packages and two icons in the status bar? Please, guys, just join your forces, I think users mostly don't care which one to use, but having both is inconvenient (and @rapgenic's workaround is not a real solution).

jonyeezs commented 7 years ago

I actually prefer to have two icons. busy-signal to show processes that end automatically

and busy to show long pending processes that may require human intervention to end