Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 23 Jun 2018, 23:46
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
HowTo dCoreDog: Puppified dCore-Xenial
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 2 [23 Posts]   Goto page: Previous 1, 2
Author Message
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Fri 24 Mar 2017, 01:38    Post subject:  

Though Puppies traditionally uses a JWM window manager and Rox filemanager combination, many other options have become available of late. In terms of Puppyfying the tinycore/dCore system, it is probably more difficult to get Puppy utilities running than changing the window manager.

The newly added STEPS 24 up to 31 therefore document installation of gtkdialog/bash and a couple of Puppy-style utilities weX and weav as part of that tinycore/dCore Puppyfication process. weX is a particularly good test of the overall system since it needs audio (alsa with pulseaudio) and video recording subsystem (video4linux) to be functioning (audio and video playback being relatively much easier to get going):

http://murga-linux.com/puppy/viewtopic.php?p=946639#946639

Again. please let me know if I missed any detail required in what is a somewhat more difficult configuration procedure.

William
Back to top
View user's profile Send private message Visit poster's website 
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Thu 30 Mar 2017, 06:21    Post subject:  

PREVIOUS STEP at http://www.murga-linux.com/puppy/viewtopic.php?p=946639#946639


Some tips and polish

Converting an existing tinycore tcz file to a dCore sce (when no sce is otherwise available)

Example. Installing Mike Lockmoore's flit:

Quote from:

https://sites.google.com/site/lockmoorecoding/downloads/flit

"Flit is an applet 'tray', currently offering clock, master sound volume control, and battery monitor. It is written to be small and low-overhead, using the FLTK user interface library, so it is especially efficient on Tiny Core Linux".

Using lxtask, I found that flit uses near zero percent CPU load (unlike most volume controls). If you also want lxtask on your system: sce-import -br lxtask, to get it, followed by sce-load lxtask.

I tried sce-import to get flit, but found that flit isn't currently available as a dCore sce. However, you can get it as a tcz from tinycore tcz repository.

Converting tcz to sce is simply a matter of changing tcz extension to sce and producing a .md5.txt file as follows:

STEP 32:

The current tinycore 7.x repository for tcz files is at:

http://distro.ibiblio.org/tinycorelinux/7.x/x86/tcz/

Download flit.tcz from there and save it to /home/tc/Downloads.

STEP 33:

Open a terminal at /home/tc/Downloads and rename flit.tcz to flit.sce, create the flit.sce.md5.txt file, and move the resulting two files to /etc/sysconfig/tcedir/sce/ (you do this as a normal user, for example, user tc):

Code:
mv flit.tcz flit.sce
md5sum flit.sce > flit.sce.md5.txt
cp flit.sce /etc/sysconfig/tcedir/sce/
cp flit.sce.md5.txt /etc/sysconfig/tcedir/sce/


You should now be able to load flit with command:

Code:
sce-load


and you can Run it from a terminal with command:

Code:
flit &



It turns out that flit doesn't get run automatically on reboot at X start.
First problem is that, for some reason..., an entry hasn't been automatically added to sceboot.lst, so:

STEP 34:

Open /etc/sysconfig/tcedir/sceboot.lst in a text editor (say fltk-editor) and add flit as an entry just after the wbar entry.

Then you need to either add a "flit &" entry to /home/tc/.xinitrc (just before "wait $DESKPID') or to /opt/bootlocal.sh or add a flit startup script to /home/tc/.X.d

Since it is an X startup program, I've chosen to use the dCore-provided method of adding a flit startup script to /home/tc/.X.d (which is actually called up by .xinitrc anyway):

STEP 35:

Open a terminal at /home/tc/.X.d and create an executable shell script containing the following commands:

Code:
#!/bin/sh
flit &


Make sure it is executable by entering the following command from the same terminal:

Code:
chmod +x flit


flit panel should now always appear on booting into X.

Last edited by mcewanw on Thu 30 Mar 2017, 06:56; edited 11 times in total
Back to top
View user's profile Send private message Visit poster's website 
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Thu 30 Mar 2017, 06:21    Post subject: Allowing ntfs partition writes; file associations in fluff  

Further polishing. Install ntfs-3g to allow dCore to write to ntfs partitions since can otherwise only read from them; associate applications with file types in fluff filemanager.

STEP 36. Download/import ntfs-3g:

a.
Code:
sce-import -br ntfs-3g


and then

b.
Code:
sce-load ntfs-3g



STEP 37. Associate applications with file types in fluff filemanager:

For simplicity, I'll use example of associating application mpv with files that have .mp4 extension.


Example 1 (associating mp4 files with mpv player).

a. As normal user, open fluff.

b. Locate and single-click on a file that has a .mp4 extension.

c. Press "Props" (Properties) button in fluff.

d. Press "Type" button in Properties window.

e. If a pop-up window appears at this stage asking you to "Enter a short descriptive name..." then easiest to just enter the file extension here (without the dot), which for this example is mp4, and press OK button.

f. In resultant "Manage File Types and Hints" window, press "Associate apps..." button

g. If there are existing "Associated applications for filetype file" then you can click on any of these and modify its contents (e.g. Action label to View or Run or Edit or whatever you wish to call the action along with the exact commandline you want).

h. For this mp4 example, the Action label can be "Play" (without the quotes) and the command:

Code:
mpv %s &


i. All the above file association info will be saved in file /home/tc/.fluff.conf once you gradually close all the open windows back till you reach the open fluff window again.

Double-clicking any .mp4 file in fluff should now automatically start it playing in mpv player.


Example 2. Associating firefox with pdf files

Firefox versions greater than 18 come with an inbuilt pdf viewer, which if set up to do so works for both locally stored pdfs and for online pdf file links. It doesn't require an internet connection to view locally stored pdf files.

Of course you could instead install a separate pdf viewer program, but the Firefox included one works very well in my tests.

First, make sure Firefox has the internal pdf reader enabled by:

a. Opening Firefox Preferences -> Applications, and highlight Applications entry "Portable Document Format (PDF)". By default, in the dCore installed Firefox, it probably already says "Preview in Firefox" - if not, simply use drop down arrow and select that.

b. Then, in fluff, single-click highlight a pdf file stored on your system and press fluff "Props." button.

c. In resultant "Properties" window, press "Type" button.

d. In the resultant pop-up window enter the short descriptive name: pdf and press OK button.

e. In "Manage File Types and Hints" window, press "Associated apps..." button.

f. In resultant "Manage Associations" window, either modify any existing Associated app or press "Add new" button:

g. In "Action label" box, put "View" (without the quotes).
In "Command line" box, put command:

Code:
firefox %s &


h. Finally close all the open fluff windows and the new configuration should be automatically stored in /home/tc/.fluff.conf

Double-clicking any .pdf file should now automatically start up firefox and use its internal pdf viewer.


Remember to select Backup when your shutdown your system (or do it now via ControlPanel) or you will lose your new settings.

William

Last edited by mcewanw on Sun 02 Apr 2017, 04:40; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website 
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Thu 30 Mar 2017, 06:22    Post subject:  

Reserved for possible additional steps
Back to top
View user's profile Send private message Visit poster's website 
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Thu 30 Mar 2017, 06:22    Post subject:  

Reserved for possible additional steps
Back to top
View user's profile Send private message Visit poster's website 
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Thu 30 Mar 2017, 06:48    Post subject:  

Reserved for possible additional steps
Back to top
View user's profile Send private message Visit poster's website 
mcewanw

Joined: 16 Aug 2007
Posts: 3198

PostPosted: Tue 11 Jul 2017, 05:00    Post subject:  

NOTICE OF MOVE TO GITHUB

Future development work of my projects (including dCoreDog, weX, scrox, Precord, pAVrecord, Premote, DoMyCommand, DoMyFIle, xhippo-mod and those I haven't mentioned) will be moving off the forum to a to-be-opened github account.

Don't think most if any of the Puppy-usable apps/scripts themselves are accessed thru woof-CE anyway and not used in most if any current Puppies.

William
Back to top
View user's profile Send private message Visit poster's website 
wiak

Joined: 11 Dec 2007
Posts: 857
Location: not Bulgaria

PostPosted: Sat 28 Apr 2018, 21:58    Post subject: Installing standard tiny core linux rather than dcore  

For anyone interested in using standard tinycorelinux (rather than Dcore), you may find the installation steps detailed in following (Other Distros) link useful:

http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130

I'm planning to build a tiny Lua/IUP development system using the above. The resulting distro should end up quite tiny still (and very powerful since Lua/IUP very powerful and flexible) though will need various gtk2 libs added to make it work. Very small IUP/Lua dotpets for pups at:

http://www.murga-linux.com/puppy/viewtopic.php?p=987611#987611

wiak
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 2 [23 Posts]   Goto page: Previous 1, 2
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0981s ][ Queries: 14 (0.0062s) ][ GZIP on ]