Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: PDP-8 on March 30, 2017, 03:30:20 AM
-
Where did Midori browser go? As a Dillo user, thought Midori - even if scripting is disabled - might be a nice alternative.
I don't do banking with browsers like Dillo and Midori, but still think of them useful for some of the sites I do visit in a pi environment..
XTERM - Until I can figure out my PEBKAC situation with fonts in Aterm, perhaps the ugly, but useful ctrl-right-click to bring up xterm's funky font menu would hold me off until I figure out what's going on with aterm....
I saw lxterminal being mentioned as one alternative a few years back here. But now it's gone from the repos too...
dunno - shows that I'm researching past threads but seeing extensions that no longer exist offered as solutions..
-
You could try fifth.tcz .
-
Outstanding! Fifth browser is *exactly* what I need - no more, no less.
Seems I can crash it with my mouse scrollwheel, so I disable up/down scrolling before I run it and rely solely on pg-up / pg-dn and scrollbars:
xmodmap -e "pointer = 1 2 3 0 0 6 7 8 9 10"
After running fifth browser, I'll just restore as normal with xmodmap again as some simple executables.
I did notice that it throws an error when called from the commandline and this seems to be all over the place when I search
libpng warning ICCP: known incorrect srgb profile
Right now, I'm just ignoring it and not sure if there's anything as a user I *should* do to correct it. Or may it is just a PI thing -- don't know at this point.
Thanks again for the Fifth browser tip - I really dig it.
My 900mhz RPI2 is really flying now with a slim picore running in ram and a fast browser to boot. My Chromebase with an ARM V7l uP running at 2.1ghz is getting scared! :)
-
Fifth browser is kind of an in-house thing, so juanito might be glad to hear about it when he comes by. ;)
-
We know, there's a cairo bug on Picore that crashes it.
-
Yup - and I jumped to conclusions with the keyboard fix.
I suppose this belongs somewhere in the fifth projects bug report area proper, but it isn't the scrollwheel per se. So I have re-enabled it. Using scrollbars, and even the down-arrow key will pop it depending on the site.
Unfortunately, or perhaps fortunately as a repeatable diagnostic, I can force fifth the crash by merely going to the end of this very forum with the mouse, scrollbar, or down arrow key!
Not that I'm complaining - I just wish I had programmer chops to dig into it...
-
Stupid question here--is there any way to run fifth full-screen?
Looking for a js-capable browser I can run in kiosk mode, more or less (full-screen display of a webpage containing digital signage and/or countdown timers on a TV, with no user interaction required). Hoping to just stick a Pi Zero on the back of the TV and power it from a USB port, if I can set this up on PiCore and make it tolerant of hard power-offs.
The timer page, as currently implemented, uses js so dillo isn't an option. fifth displays it perfectly, apart from the display being windowed rather than full screen.
-
Depending on which Window Manager you're using, you might be able to set some rules for certain windows.
E.g when using Openbox, you could add something like this to ~/.config/openbox/rc.xml in the <applications> section.
<applications>
<application class="Firefox" role="browser">
<focus>true</focus>
<maximized>true</maximized>
<decor>false</decor>
<layer>above</layer>
</application>
</applications>
-
With Fifth, nope..
xprop | grep -i role <click-on-fifth-window>
_OB_APP_ROLE(UTF8_STRING) =
xprop | grep -i class <click-on-fifth-window>
_OB_APP_GROUP_CLASS(UTF8_STRING) =
_OB_APP_CLASS(UTF8_STRING) = "FLTK"
WM_CLASS(STRING) = "FLTK", "FLTK"
Sorry.
-
Fifth doesn't have a full-screen mode, but you can easily create a browser like that using WebkitFLTK. With a standalone kiosk webview, there's no risk of the browser functionality intervening, and it will behave exactly as you wish.
See https://github.com/clbr/webkitfltk/blob/fltk/Source/WebKit/fltk/testapp/testapp.cpp for a sample, you'd then order it fullscreen using normal FLTK functions, as well as any other customization you need.
-
Fifth doesn't have a full-screen mode, but you can easily create a browser like that using WebkitFLTK. With a standalone kiosk webview, there's no risk of the browser functionality intervening, and it will behave exactly as you wish.
See https://github.com/clbr/webkitfltk/blob/fltk/Source/WebKit/fltk/testapp/testapp.cpp for a sample, you'd then order it fullscreen using normal FLTK functions, as well as any other customization you need.
Sorry, I'm not quite clear on how to compile testapp.cpp. Do I need to compile the complete WebkitFLTK, or just install webkitfltk-dev.tcz (and Python, Ruby, perl...) and then compile testapp.cpp?
Thanks for your help. Definitely interested in pursuing this for some of the digital signage stuff I'm working on.
-
Sorry, I'm not quite clear on how to compile testapp.cpp. Do I need to compile the complete WebkitFLTK, or just install webkitfltk-dev.tcz (and Python, Ruby, perl...) and then compile testapp.cpp?
Load compiletc, webkitfltk-dev and try
g++ testapp.cpp -lz -pthread -lxslt -lxml2 -ldl -lsqlite3 -lpthread -ldl -lm -L/usr/local/lib -licui18n -licuuc -licudata -lpthread -ldl -lm -lharfbuzz -lharfbuzz-icu -lfreetype -lfontconfig -lcairo -lpng -ljpeg -lrt -lcurl -lssl -lcrypto -lglib-2.0 -L/usr/local/lib -Wl,-rpath,/usr/local/lib -lfltk_images -lpng -lz -ljpeg -lfltk -lXcursor -lXfixes -lXext -lfontconfig -lpthread -ldl -lm -lX11 -static-libgcc -static-libstdc++ -lfltk -lwebkitfltk
See https://github.com/clbr/webkitfltk/blob/fltk/Source/WebKit/fltk/Makefile (https://github.com/clbr/webkitfltk/blob/fltk/Source/WebKit/fltk/Makefile)
There's no URL bar though, not sure how to cope with that. :P
By the way, you can run
./a.out file:///path/to/local/file
-
Sorry, I'm not quite clear on how to compile testapp.cpp. Do I need to compile the complete WebkitFLTK, or just install webkitfltk-dev.tcz (and Python, Ruby, perl...) and then compile testapp.cpp?
Load compiletc, webkitfltk-dev and try
g++ testapp.cpp -lz -pthread -lxslt -lxml2 -ldl -lsqlite3 -lpthread -ldl -lm -L/usr/local/lib -licui18n -licuuc -licudata -lpthread -ldl -lm -lharfbuzz -lharfbuzz-icu -lfreetype -lfontconfig -lcairo -lpng -ljpeg -lrt -lcurl -lssl -lcrypto -lglib-2.0 -L/usr/local/lib -Wl,-rpath,/usr/local/lib -lfltk_images -lpng -lz -ljpeg -lfltk -lXcursor -lXfixes -lXext -lfontconfig -lpthread -ldl -lm -lX11 -static-libgcc -static-libstdc++ -lfltk -lwebkitfltk
See https://github.com/clbr/webkitfltk/blob/fltk/Source/WebKit/fltk/Makefile (https://github.com/clbr/webkitfltk/blob/fltk/Source/WebKit/fltk/Makefile)
There's no URL bar though, not sure how to cope with that. :P
By the way, you can run
./a.out file:///path/to/local/file
It worked, thanks!
I've got some experience with C/gcc in my day job (I'd have probably figured out to use "g++" rather than "gcc" eventually... ;D) so I figured that the makefile had all the required linker flags, just wasn't sure if I needed to compile everything else it wanted to or not.
I'll continue to mess around with the .cpp to bend it to my preferences, but so far so good.