Hi All,
Just wanted to alert you to Geoffrey's discovery, a lean version of firefox. Some discussion starts here:http://www.murga-linux.com/puppy/viewto ... 691#939691
Googling lead me here for the 64-bit rpm, https://sourceforge.net/projects/lightfirefox/, and here for the 32-bit rpm, https://sourceforge.net/projects/lightf ... 49_gcc232/. Do your own search for latest publications. Menu>Utilities>UExtract will decompress the rpms providing you with a folder you can move anywhere and rename (as in remove version number etc).
Haven't played much, but it appears that light can use some of firefox's addons, and has a couple of its own.
To open the 64bit version, browse to [light-folder]/usr/local/lib/light/ and click one of the binaries named light and light-bin. I'm not sure what the difference between those are.
The attached pet for light(64-bit) will create a menu entry. It calls the binary simply named light. But you'll have to edit the bash script at /root/my-applications/bin so that the path actually points to where ever your light bin file is located.
I thought the icon for light was too non-descript; so stole another.
Edit: I've tried the 32-bit version in 32-bit Tahrpups, Xenialpups and Carolina Vanguard. Worked fine for the former two. Would not open in Carolina, reporting that a libatomic.so.1 was not found. I found an rpm which had it and packaged it as a pet. Installed into Vanguard fixed the problem. I'm posting from it/them, now. I really like this browser. I've attached the pet.
As you may know, Carolina Vanguard was battleshooter's remaster that included newer graphics libraries. Carolina, itself, was based on Saluki, which was a remaster of Racy; and Racy was Barry K's Puppy, companion to Wary, the two differing primarily in the kernel employed. Whether Light (with or without) the missing pet will function on any of Vanguard's forebears is unknown. Worth a trial-run, however.
Further discussion here: http://www.murga-linux.com/puppy/viewto ... 728#939728
mikesLr
Current Browsers for Puppy Linux Developers and Users
Light =Firefox light
- Attachments
-
- lib4Light4Carolina.pet
- lib required to run Light(firefox) under Carolina Vanguard
- (8.65 KiB) Downloaded 897 times
-
- light64_external.pet
- Creates Menu listing for 64-bit Light Webbrowser. But see paragraph about where you've located the light folder
- (28.83 KiB) Downloaded 837 times
Last edited by mikeslr on Sat 18 Feb 2017, 23:47, edited 3 times in total.
-
Pelo
32bits version tested with Pupjibaro Jessie Synaptic..
32bits version tested with Pupjibaro Jessie Synaptic.. No trouble with it. To keep for rescue for Puppies delivered without a browser or with elinks, for instance.
See Musher0 topic about it. Light 49 test by josejp2424, the Pupjibaro Jessie developer feed back.
See Musher0 topic about it. Light 49 test by josejp2424, the Pupjibaro Jessie developer feed back.
-
Pelo
Lib atomic, that is what i am looking for...
Lib atomic, that is what i am looking for...
Version GTK2 32 bits should be worth a try in Slim X-slacko by mistfire.
I am also curious to try rpm packages. No dev thought about a Puppy Fedora ? another way to go the same place..
Version GTK2 32 bits should be worth a try in Slim X-slacko by mistfire.
I am also curious to try rpm packages. No dev thought about a Puppy Fedora ? another way to go the same place..
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Pelo.
If you need libatomic, you can find it here, at my MediaFire a/c:-
http://www.mediafire.com/file/dqjez1q11 ... c-so.1.pet
Hope that helps!
Mike.
If you need libatomic, you can find it here, at my MediaFire a/c:-
http://www.mediafire.com/file/dqjez1q11 ... c-so.1.pet
Hope that helps!
Mike.
Is there any way to eliminate thumbnails saved in cache?
Is there any way to eliminate thumbnails saved in cache in some of the browsers? Just curious.
In FireFox there is this entry in about:config
browser.pagethumbnails.capturing_disabled
Set this to TRUE
PaleMoon and SeaMonkey sould be similar if not the same.
Regards
8Geee
browser.pagethumbnails.capturing_disabled
Set this to TRUE
PaleMoon and SeaMonkey sould be similar if not the same.
Regards
8Geee
Linux user #498913 "Some people need to reimagine their thinking."
"Zuckerberg: a large city inhabited by mentally challenged people."
"Zuckerberg: a large city inhabited by mentally challenged people."
-
oui
I find wrong that the browsers needing frequent upgrades like seamonkey or firefox are included in the main distribution's sfs. some puppy's uses a second sfs (zdrv). it would be better to do the same with the browsers, add a "standard_browser.sfs" in each iso so that users can update themself (or find in the forum) an/that supplementary sfs and enjoy so an actual system concerning browser security!
-
oui
Hi 8Geee
standard_browser is the name used to link in the main.sfs, is a target name
and each file supplying an operable complete standard browser with his good specific environment (can be used by different puppy's) is an adequate "standard_browser.sfs" completing the puppy's awaiting to meet such a file because no browser in it's main sfs file . and this browser found in the "standard_browser.sfs" become the place "defaultbrowser" in /usr/local/bin/defaultbrowser
the main file of the puppy doesn't know which one it will meet in the standard_browser.sfs but know only if it meet that file, if that file is really present in the easy or the frugal installation: it has to contain the standard browser decided by the creator of the iso or, later, the administrator of the system (if he decides to change later the first equipment because of the updating / upgrating of the browser or some plugins).
and it can be each browser decided by that creator or administrator: he, the creator or administrator, has to solve all the problem of adaptation between both!
other supplementary browsers can eventually be installed parallel but they don't get the functions confered to the standard browser. they only appear in the menu.
as the main used browser in official puppy's is seamonkey, that package "standard_browser.sfs" gets also the fonctions "defaultmail", "defaulthtmlviewer", "defaulthtmleditor" and "defaultaddressbook" (possibly also a "default-irc-client", but would be new at /usr/local/bin!).
how is answering after invocation of one of above links is matter of the creator or administrator!
standard_browser is the name used to link in the main.sfs, is a target name
and each file supplying an operable complete standard browser with his good specific environment (can be used by different puppy's) is an adequate "standard_browser.sfs" completing the puppy's awaiting to meet such a file because no browser in it's main sfs file
. and this browser found in the "standard_browser.sfs" become the place "defaultbrowser" in /usr/local/bin/defaultbrowserthe main file of the puppy doesn't know which one it will meet in the standard_browser.sfs but know only if it meet that file, if that file is really present in the easy or the frugal installation: it has to contain the standard browser decided by the creator of the iso or, later, the administrator of the system (if he decides to change later the first equipment because of the updating / upgrating of the browser or some plugins).
and it can be each browser decided by that creator or administrator: he, the creator or administrator, has to solve all the problem of adaptation between both!
other supplementary browsers can eventually be installed parallel but they don't get the functions confered to the standard browser. they only appear in the menu.
as the main used browser in official puppy's is seamonkey, that package "standard_browser.sfs" gets also the fonctions "defaultmail", "defaulthtmlviewer", "defaulthtmleditor" and "defaultaddressbook" (possibly also a "default-irc-client", but would be new at /usr/local/bin!).
how is answering after invocation of one of above links is matter of the creator or administrator!
All my builds do exactly that....oui wrote:I find wrong that the browsers needing frequent upgrades like seamonkey or firefox are included in the main distribution's sfs. some puppy's uses a second sfs (zdrv). it would be better to do the same with the browsers, add a "standard_browser.sfs" in each iso so that users can update themself (or find in the forum) an/that supplementary sfs and enjoy so an actual system concerning browser security!
For LxPupSc, LxPupSc64 and Upup-Artful-Aardvark and Upup-Bionic-Beaver
Light is the browser in the adrv which can be replaced by Chromium, Firefox, FirefoxESR, Palemoon, Seamonkey, Slimjet, Vivaldi, Min etc.
LxPup = Puppy + LXDEMain version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
hamoudoudou
Light 47 For a Slacko
seamonkey, palemoon ... no trouble with them.. But QtWeb no.. i need better.. i am searching for Light 47 For a Slacko remasterized by Hungariand dev (Slegopen)
Light 48 and 49 ask GTK 3 which is too much.
That is just to try LIGHT with a Puppy Slacko . Sure i will not loose my time searching, i saw the answer in the forum.. Searching..
Light 48 and 49 ask GTK 3 which is too much.
That is just to try LIGHT with a Puppy Slacko . Sure i will not loose my time searching, i saw the answer in the forum.. Searching..
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
@kuman11
Open your browser and in the url bar of an empty tab type "about:config" (without the quotation marks but make sure to include the colon between about and config) and hit return.
The first time you do this, you'll be presented with a warning saying something like you'll promise to be careful; just click "OK".
Then in the next window which opens type or paste into the white search bar at the top "browser.pagethumbnails.capturing_disabled" (again without the quotation marks).
This should locate that config line for you which is the one you need to edit,
If its value is showing as "false", double clicking your cursor anywhere on the line will change that value to "true".
Then close the tab, close and restart the browser, and you should be sorted.
Note this line appears in both Firefox & Light browsers' config settings but doesn't seem to exist in Palemoon, so don't bother if you're using that.
Please do be careful whenever you're working in "about:config" and never edit anything you're not totally sure about. There will be no confirmation dialogue boxes
Open your browser and in the url bar of an empty tab type "about:config" (without the quotation marks but make sure to include the colon between about and config) and hit return.
The first time you do this, you'll be presented with a warning saying something like you'll promise to be careful; just click "OK".
Then in the next window which opens type or paste into the white search bar at the top "browser.pagethumbnails.capturing_disabled" (again without the quotation marks).
This should locate that config line for you which is the one you need to edit,
If its value is showing as "false", double clicking your cursor anywhere on the line will change that value to "true".
Then close the tab, close and restart the browser, and you should be sorted.
Note this line appears in both Firefox & Light browsers' config settings but doesn't seem to exist in Palemoon, so don't bother if you're using that.
Please do be careful whenever you're working in "about:config" and never edit anything you're not totally sure about. There will be no confirmation dialogue boxes
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
Do you mean in your ROXfiler file manager, when you open a folder containing images the icons will show a thumbnail of each image in the file? That's a totally different function from the browser thumbnail displays which you just disabled but just as easily fixed.
Will you first please say which Puppy you're using, to be sure?
(Thanks for that info, Fredx181, appreciated, I only checked in my Firefox ESR & Light 49, but it now sounds like it may not be the thumbnails in his browser he's trying to disable)
Will you first please say which Puppy you're using, to be sure?
(Thanks for that info, Fredx181, appreciated, I only checked in my Firefox ESR & Light 49, but it now sounds like it may not be the thumbnails in his browser he's trying to disable)
ROXfiler file manager
Exactly!
It's X-Slacko Slim 4.4
I clear the FF cache periodically so it does the job, anyway.
Btw is Light any good of a browser?
It's X-Slacko Slim 4.4
I clear the FF cache periodically so it does the job, anyway.
Btw is Light any good of a browser?
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
OK, open any window in ROXfiler and right click in an empty space.
From the menu choose "Options".
In the left pane of the window which then opens expand "Filer windows" (if necessary) and click on "Thumbnails", then in the right pane untick the box next to "Show image thumbnails".
It might also be a good idea to click on "Purge thumbnails disk cache" since I know from personal experience this can become a huge file which can rapidly fill up the free space of your save file when you visit folders on your drives containing lots of images.
Click "OK"
Done!
Have a read through this thread which has links to a few different builds of Light 49 and opinions on it.
Or try it for yourself (having first backed up your save file, so nothing lost if you don't get on with it); light-49.0.linux-i686_6.sfs, available here, works "out of the box" loaded in Slacko 6.3.0, on which your X-Slacko Slim 4.4 seems to be based. (I also needed to install "apulse-0.1.11-i686-wz.pet" from here to enable sound in web pages).
From the menu choose "Options".
In the left pane of the window which then opens expand "Filer windows" (if necessary) and click on "Thumbnails", then in the right pane untick the box next to "Show image thumbnails".
It might also be a good idea to click on "Purge thumbnails disk cache" since I know from personal experience this can become a huge file which can rapidly fill up the free space of your save file when you visit folders on your drives containing lots of images.
Click "OK"
Done!
Have a read through this thread which has links to a few different builds of Light 49 and opinions on it.
Or try it for yourself (having first backed up your save file, so nothing lost if you don't get on with it); light-49.0.linux-i686_6.sfs, available here, works "out of the box" loaded in Slacko 6.3.0, on which your X-Slacko Slim 4.4 seems to be based. (I also needed to install "apulse-0.1.11-i686-wz.pet" from here to enable sound in web pages).