Closed cedivad closed 3 years ago
wasn't released because of politics or something.
the reason is time and effort and red tape
Can we revive this project? I'd be interested in helping
Contact @matryer here or on twitter
I no longer maintain BitBar because of time constraints on my end, and a big change in professional focus. There was a rewrite into Swift going on but it never got finished, and this shifts focus back onto the Obj-C code.
I am also a fan of minimalist apps, so there are lots of things I say "no" to in BitBar. But not fixes like vertical text alignment etc. We do want those.
I am more than happy for new maintainers to help out. @mpicard Are you interested?
Yea I'm also not interested in "adding" too much features just the bug fixes and quality of life stuff (like the text align thing) so if you want help let me know I can help get those PRs merged and maybe get CI back up and running
nice to see activity again! It's a nifty little project that, I agree, does not require a lot of new feature but yes a little love :-)
Thanks in any case!!!
Getting the CI fixed would be great.
Andy On 10 Jul 2019, 17:31 +0200, Martin Picard notifications@github.com, wrote:
Yea I'm also not interested in "adding" too much features just the bug fixes and quality of life stuff (like the text align thing) so if you want help let me know I can help get those PRs merged and maybe get CI back up and running — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I couldn't make my plugin read from env variable. It would be awesome to see that feature in BitBar.
@eldemcan please start a new issue about this and I can help you with it
@cedivad One thing that seems off is that your binary is 13.2MB while the binary in this repo is only 4.2MB. Maybe some debug options were left in during the compilation?
@xixixao yeah, most likely. The biggest problem I have with my binary is the popup that displays on screen from one of the dependencies every couple of days bothering me with a "your app is unsigned" message. I just hit ok, it's fine by me.
There eversion I built (release version through Xcode Archive command) is 3.1MB — I also just click the "unsigned" warning every so often. But it works well
The repo https://github.com/guillaumewuip/bitbar is unavailable.
If @matryer no longer has the time to maintain this project, perhaps the necessary permissions to publish releases should be transferred to someone else?
rashidkpc/bitbar is a fork that I used to build on newer versions of Xcode. Last time I built was back in May 2019 but I just tested it again and it still compiles and runs using Xcode11 + Catalina.
I’m happy to give more permissions where appropriate.
Mat
On Mon, 21 Oct 2019 at 13:24, Luke Hamburg notifications@github.com wrote:
rashidkpc/bitbar https://github.com/rashidkpc/bitbar is a fork that I used to build on newer versions of Xcode. Last time I built was back in May 2019 but I just tested it again and it still compiles and runs using Xcode11 + Catalina.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/matryer/bitbar/issues/513?email_source=notifications&email_token=AAAY2G23C4OHIIVIFCJPV23QPWNPTA5CNFSM4H4KD532YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB2EGSI#issuecomment-544490313, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAY2G6QHDY6FKH5ICKNKNDQPWNPTANCNFSM4H4KD53Q .
The repo https://github.com/guillaumewuip/bitbar is unavailable.
The binary here is working: https://github.com/cedivad/bitbar-binary
The binary here is working: cedivad/bitbar-binary
Why should I trust cedivad (nothing personal)? What was the problem to put the source code with the binary?
I didn't bother with the source code because I spent my time writing a detailed step by step tutorial on how to replicate my same result using someone else's.
The original source code got pulled, so I'm between a rock and hard place at the moment. What I can absolutely guarantee is that I didn't do anything malicious with it, but I understand if you didn't want to trust me. I myself have been using it for a few months now and I didn't have my credit card details stolen just yet.
*edit, I had commented from my work account.
Fork of https://github.com/matryer/bitbar with patches https://github.com/matryer/bitbar/pull/496 and https://github.com/matryer/bitbar/pull/503 works. Thank you for the instruction! Can't believe I can see the BitBar without an alignment problem.
So much work just to realign text one pixel 🙄
So, just to make sure I’m summarizing things correctly:
@tjluoma
the source code is no longer available?
Not sure why you think that? Here is the source: https://github.com/matryer/bitbar/tree/master/App
Actually, we don't need to open it using Xcode and compile it. We can just run make
directly. I will write down the complete step below:
git clone https://github.com/matryer/bitbar.git
https://github.com/rashidkpc/bitbar/blob/fix/build/Makefile
https://github.com/rashidkpc/bitbar/blob/fix/build/App/BitBar.xcodeproj/project.pbxproj
make
in the root directory. The compiled file BitBar.app will be generated under bitbar/App/build/Release/
.Done!
But macOS will complain about that version not being signed, right?
It's running perfectly so far on my machine and I don't see any errors.
The error appears when Sparkle auto-update happens.
Backdate the SULastCheckTime
in com.matryer.BitBar.plist
to force it to do an update check where you'll see the error.
You may want to do a personal build that disables the Sparkle update mechanism.
@gingerbeardman Thanks. If I don't use the auto-update feature and don't run "Check for Update", and instead when I want to update it I git fetch and re-build it, I won't be affected by the error you mentioned, right? BTW, yesterday I tried to install bitbar from homebrew and the "Check for Update" brought an error either.
Correct.
I'm not aware of any way to switch of SUEnableAutomaticChecks without rebuilding, any changes to the plist are overwritten on every launch.
I was excited about this project until I saw the text was vertically misaligned, then couldn't believe a fix has been published since forever but wasn't released because of politics or something.
So here is how you can build this project yourself, approximative guide. Will save you 30 minutes of your time. I myself had no clue so it took that long.
1) Fetch either the updated repository or the one with a fix you care about, say the one in #496. You need to use --recursive and git clone (my first mistake)
git clone --recursive https://github.com/guillaumewuip/bitbar.git
(this is not the official repository)! 2) Replace the Makefile with what's suggested in this other pr: #503 3) Do the same for App/BitBar.xcodeproj/project.pbxproj 4) Open the project in xcode, compile it 5) Go back to the root directory and run make 6) The compiled file will be in App/build/Release/BitBar.app, move that to /Applications and you are doneNow if you really trust me for some reason or another you can fetch the binary directly from here - please note that while I have no malicious intention and I kinda trust the code I downloaded I might have been fooled.
https://github.com/cedivad/bitbar-binary
Cheers Davide