calculuschild on SwappableThemes-ReorganizeFolderStructure
Make dropdown close on clickout… (compare)
dependabot[bot] on npm_and_yarn
Bump @babel/preset-env from 7.1… (compare)
dependabot[bot] on npm_and_yarn
dependabot[bot] on npm_and_yarn
Bump react-frame-component from… (compare)
dependabot[bot] on npm_and_yarn
Bump @babel/plugin-transform-ru… (compare)
dependabot[bot] on npm_and_yarn
Bump @babel/preset-react from 7… (compare)
either no vertical black line between undo/redo and the editors, or there should be no padding between the highlight gray and the black line
The line is to differentiate between "action buttons (undo/redo/more later) vs "editor tabs". We can look at visual tweaks later but I think its important that hose are separated.
Also, there is a reddit post about certain pages not showing in Chrome's print dialog, despite showing in the preview window.
The share link prints just fine for me. It could possibly that issue where pixel differences between one or more views are shuffling things around, and maybe the PDF render is experiencing a similar thing? Not sure.
If I take a Legacy brew, and Clone to New, it sometimes (always?) opens in v3
I suspect it's opening in whatever renderer you selected last time you were in New. Clone overwrites the text and style panels but I don't think it copies over any of the metadata so it might be stuck using your old metadata. Put this in an Issue if you haven't already.
But further, if I don't save and click through to Get PDF the /Print/ page shows something completely different.
The print page shows a previous "new" brew where I was just testing stuff and don't think I saved.
Is this only if you don't edit the file at all? I think the print page just grabs whatever the latest text saved to the localStorage, and cloning a page doesn't overwrite localstorage until you start typing on it.
i think my PR for the page number pseudo elements in the editor should be reverted. Something funky happens to the count as you scroll.
Make an issue for it and we can take a look.
npm run dev
seems to consistently throw an error and not start-- is that normal or is there something up with my install? Happy to elaborate if that's not expecteddev
script is actually working - I've always used node scripts/buildHomebrew.js --dev
instead, which enables a watchDirectory and auto live rebuild. In theory this should probably work from a npm run build
prompt as well, but I can't say that I've actually ever tested it.
re:docker: Gotcha -- so I've done a couple things that have made my workflow with it a bit easier, definitely curious of your thoughts (not sure how helpful this would be for the group)
buildHomebrew.js
has both a --dev
and a --watch
. With just --dev
it will watch the files and update the build
folder as they're changed, but it doesn't start up the server.build
folder to the homebrewery docker image, so now when I change a file it'll pick up those changes as the buildHomebrew
script updates the build
folder without needing to be restarted. Just have to refresh the browser to pick up the changesre:linting: that's a great tip, definitely will be sure to run that!
--dev
option set up to both watch files and start up a server for that very reason you mention: The server it starts will automatically pick up updates in the build folder and you only have to refresh the browser to see the changes. Since we don't normally do our dev work inside a Docker container we have never had a need to separate the livereload server out.
Are you able to get a coutn of how many users there are with no linked google account?
Logging in with reddit account (if possible) and github account should be allowed, since those are the platforms in which homebrewery engages with users for reports, feature requests, updates, etc.
And if the GMB discord is any indication, I think more people are going to start moving to HB over time--- Their developer hadn't replied to messages for 6 months until last week when their SSL cert expired for a few hours and most of the active people are advising newcomers that it is abandonware.
Kind of funny since the Homebrewery is the original, then GMBinder took our source code (it is open-source so... good for them?), tweaked a few features, and then slapped a subscription model on it. Granted, we did have a lull for a year or so when the original owner was leaving the project before I joined which is what led a lot of people to switching over, but we've been pretty active lately and are seeing more traffic back this way again.
Not that we are trying to "win" anything, but it does mean people are watching our progress more these days, so more help is always welcome.
right, but I think we can likely all agree that it is a little "icky" that they don't provide support for a paid (and especially subscription-based) app. And they haven't completed their well-funded kickstarter goals. But I try not dwell on it or take a HB vs GMB mindset since I really have no horse in the race, though I do indulge in a bit of schadenfreude occasionally.
And then there is Norn--- I'm skeptical, but interested to see what happens since it is a very different approach to the same cause.