Closed jdev082 closed 2 years ago
@JaydenDev I could help, wait a moment. Currently running npm install
@JaydenDev Finished install, looking at it. Just wondering, how do you feel about loading the Chromium system stylesheet for now, just to get a good color scheme?
@hello-smile6 I'm fine with the userchrome.css configuration in config/
@hello-smile6 I'm fine with the userchrome.css configuration in config/
Could I import it from https://cursive.apps.chrome/chrome-apps-a4_202111181400_RC00_prod/a4_cros_stylesheet.css or somewhere? It'd just add environment variables for colors.
Any CSS file will work with FreeCat, although the bloat might not be great :/. Maybe release it as an addon, or add it as an addon.
Any CSS file will work with FreeCat, although the bloat might not be great :/. Maybe release it as an addon, or add it as an addon.
If you'd be okay with it, I could add a build script that loads dependencies like that from a list, and uses empty files for dependencies that are not installed. Also, I'm wanting to make an installer. Would that be okay?
An installer isn't needed, packages and binaries are easily available.
An installer isn't needed, packages and binaries are easily available.
Could I build binaries using https://npmjs.com/package/pkg ?
DEB64, RPM64, DEB32, RPM32, RPMARM64, DEBARM64, EXE, and *.app files can be created with the build system
npm run make
DEB64, RPM64, DEB32, RPM32, RPMARM64, DEBARM64, EXE, and *.app files can be created with the build system
npm run make
What about packaged copies of dev builds?
dev builds aren't priority for packaging.
dev builds aren't priority for packaging.
Oh.
@JaydenDev Just letting you know:
- Make the search bar and go button on same line
Any suggestions?
Item 1 is fixed by #16 (Yes, I added <!DOCTYPE html>
again, but test it first)
The creator of the PR is required to test it, I don't want broken PRs being merged.
The creator of the PR is required to test it, I don't want broken PRs being merged.
I already tested it, but just don't want it ignored.
testing PR now.
Great UI, things are just wayyy too small
Great UI, things are just wayyy too small
Okay. I'll have a fix in 10 minutes, hopefully. I'll also add environment variables to make UI size changes easier.
Were you on a 1080p monitor?
Were you on a 1080p monitor?
Here's screen
Screen {availWidth: 1366, availHeight: 738, width: 1366, height: 768, colorDepth: 24, …}
availHeight: 738
availLeft: 0
availTop: 0
availWidth: 1366
colorDepth: 24
height: 768
orientation: ScreenOrientation
angle: 0
onchange: null
type: "landscape-primary"
[[Prototype]]: ScreenOrientation
pixelDepth: 24
width: 1366
[[Prototype]]: Screen
Did you make the UI small by preference, or monitor config
Did you make the UI small by preference, or monitor config
Preference. I like small menus.
Small menus can generally be bad, small UI = harder to read
Small menus can generally be bad, small UI = harder to read
Oh, I'll try to make it look better.
i think half the size of a firefox tab is good
i think half the size of a firefox tab is good
Okay, I'll install Firefox (or check the source) and try to add that.
That'd be 36px, I think.
half of the size?
half of the size?
18px. That's 2px less than my config.
great so far
great so far
Since env.css
is in .gitignore
, there should be a defaults.css
loaded before it so the UI doesn't look weird.
default config
Commenting from freecat!
@JaydenDev Could you enable GitHub Discussions?
Yeah yeah, but discussions feels kinda bloated compared to the issues tab. Also more people are familiar with issues.
does freecat handle cookies properly? do you stay logged in?
does freecat handle cookies properly? do you stay logged in?
Not sure, I assume it wouldn't.
Ninetails does it just fine, which uses the same technologies almost
Would it be possible to implement a reload feature?
Yeah yeah, but discussions feels kinda bloated compared to the issues tab. Also more people are familiar with issues.
However, issues can quickly get off-topic. Also, it can get hard to decide when to close an issue that's more of a discussion. As an added reason, many websites related to github use the number of open issues to judge repository quality.
Would it be possible to implement a reload feature?
Probably. I'll look at it.
soo... more issues = better software? doesn't really make sense
soo... more issues = better software? doesn't really make sense
It's just a factor they might consider. Also, it gets frustrating when people open issues that are just to ask questions about something.
well this'll work for now, can't be puttin that much effort into a hobby project.
well this'll work for now, can't be puttin that much effort into a hobby project.
Why not? You just have to enable it in the repo settings, it takes less than 30 seconds. Also, this could go beyond a hobby project. Just look at https://beakerbrowser.org/ (another electron browser)
who's gonna use a browser with barely any features made by a kid?
who's gonna use a browser with barely any features made by a kid?
It doesn't have to stop there. How about this?
Who's going to use a browser with more features than Chromium that uses less memory, has bookmarklet APIs designed to allow full access to webpage contexts, and allows the JS stack, DOM, and element focus state to be saved to a file, and happens to be made by a kid?
Everyone. If you put the effort in, you'll get better results.
I put plenty of effort in, it is just a HTML UI with web views after all.
I put plenty of effort in, it is just a HTML UI with web views after all.
It can be more. And it should become more over time.
Any suggestions?