Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on October 30, 2010, 06:01:16 PM
-
The First Release Candidate of v3.3 (tinycore_3.3rc1.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates
tinycore_3.3rc1.iso
tinycore_3.3rc1.iso.md5.txt
Change log for Tiny Core v3.3:
* New FLTK integrated file manager, mfm, file associations, i.e, double click to edit/run directly from file manager.
* New FLTK minimal editor, on System Tools menu, and called via File Manager configurable file associations.
* New tce-run - load and run tcz, e.g., tce-run xmms, This is the association to run .tcz directly from file manager.
* Updated tce-audit to support default pathing and ext (.tcz) greatly improves CLI usage.
* Updated tce-setdrive to support call via AppBrowser.
* Updated AppBrowser - integrated setdrive. A "Set" button is initialized when Cloud Mode is detected.
* New wbarconf replaces wbar_exclude. Manage all icons (system and ondemand), as well as bar placement.
* New wbar_mv_icon for support of wbarconf.
* Updated ondemand generated scripts to pass command line arguments.
* New boot code nozswap - Skip compressed swap in ram.
* Updated and reorganized boot help screens f2 f3 f4
* Updated Control Panel reorganization. Moved more frequently used items to the System Tools menu.
Moved AppsAudit to System Tools menu.
Moved Run Command to System Tools menu.
* Updated System Tools menu reorganization. Moved less frequently used items to Control Panel.
Moved PPI Setup to Control Panel
Moved TermServer Setup to Control panel.
* Updated wbar for new file manager icon, removable via the new wbarconf.
Other file associations can be found in ~/.mfm/mfm.cfg. Associations can be maintained via the file
manager Options->Configurations or edit directly. This simple text file could be easily updated for additional associations via extension start up scripts.
The editor is the demo from the FLTK source. Very limited, but as a starter editor for simply editing a
few config files, I find it useful. It obviously be an improvement over vi for new users unfamiliar with such.
While my impetus was originally for better support for the vi or cli dilemma facing new users as shown the topic area where I posted (http://forum.tinycorelinux.net/index.php?topic=7600.0), the fact that Tiny Core can now offer data centric view ( file associations ) was the tipping point for my decision to include the FileMgr and Editor.
I have also created wbarconf for those of you who already have, or desire, a more fully featured file manager as found in the repository. Simply use the new wbarconf and remove the FileMgr icon.
Note: A new data structure is used for wbarconf so any current wbar_excluded items (xwbar.lst) will need to be remade.
Hope you enjoy the new, but optional, "data centric" capabilities of Tiny Core as much as I have in coding, preparing and using this release.
-- Robert
-
Wow.
There goes the majority of any left over customisations I had still had with tc_3.2. Plus brought in a whole swag of extra stuff *drool *
Robert, looks brilliant. Am testing now...
-
isolinux.cfg is missing the line
F4 f4
-
isolinux.cfg is missing the line
F4 f4
Doh!
Got it!
Thanks.
-
Quick note re. the new 'F4' file: the concepts page (http://tinycorelinux.com/concepts.html) contains "by pressing F2 or F3" so I a minor correction is probably required.
Other than this I had a quick "kicking the tires" trial. Even I as a strong CLI advocate can see the benefit of having a simple GUI filemanager & editor included. So that should put an end to re-occuring suggestions of GUI editor installations as precondition to adjust some system settings.
First impression re. 'mfm': Some of the keyboard shortcuts seem to clash with 'flwm_topside'. I tried 'Alt-F1' (i.e. 'Toggle permission view') and that was clearly caught by the WM and not by 'mfm'. I also managed with another key stroke to crash my WM (i.e. 'flwm_topside'). That was a first for me, and I don't know what key did it, but I think the short cuts used by the default WM and the default file manager need to be mutually exclusive.
-
Is there a way to replace FLTK fonts such as in the new mfm? They look spidery/aliased on my setup. I really like the crisp fonts as found in the file list in AppBrowser for example. The buttons would benefit from such fonts as well.
-
wbarconf bug:
Put mfm on the right to exclude it from wbar. Click apply - icon is removed. Exit X, startx, mfm re-appears.
-
Concepts page edited.
-
wbarconf bug:
Put mfm on the right to exclude it from wbar. Click apply - icon is removed. Exit X, startx, mfm re-appears.
Bugs found. Bugs squashed. Thanks for testing and reporting.
-
Quick note re. the new 'F4' file: the concepts page (http://tinycorelinux.com/concepts.html) contains "by pressing F2 or F3" so I a minor correction is probably required.
Other than this I had a quick "kicking the tires" trial. Even I as a strong CLI advocate can see the benefit of having a simple GUI filemanager & editor included. So that should put an end to re-occuring suggestions of GUI editor installations as precondition to adjust some system settings.
First impression re. 'mfm': Some of the keyboard shortcuts seem to clash with 'flwm_topside'. I tried 'Alt-F1' (i.e. 'Toggle permission view') and that was clearly caught by the WM and not by 'mfm'. I also managed with another key stroke to crash my WM (i.e. 'flwm_topside'). That was a first for me, and I don't know what key did it, but I think the short cuts used by the default WM and the default file manager need to be mutually exclusive.
Original FLWM did not have so many Alt hot keys. They were a recent addition when topside was being made. Personally I don't think WMs should have so many hot keys, as conflicts arise. I had the same issue on that other project I did.
I am open to suggestions to remove some overlapping hotkeys either in flwm or mfm, or both, or if available and supported alternates be suggested.
Hopefully an amicable selection can be worked out during the release cycle.
-
Is there a way to replace FLTK fonts such as in the new mfm? They look spidery/aliased on my setup. I really like the crisp fonts as found in the file list in AppBrowser for example. The buttons would benefit from such fonts as well.
I am not sure I understand. Both mfm and most of my GUIs are using helvetica 14. Areas of text that need alignment use fixed width font courier kinda like the <pre> tag in html.
-
RE:
First impression re. 'mfm': Some of the keyboard shortcuts seem to clash with 'flwm_topside'. I tried 'Alt-F1' (i.e. 'Toggle permission view') and that was clearly caught by the WM and not by 'mfm'.
I have searched both mfm and flwm and Alt-F1 was the only conflict that I found.
I have made adjustments to te FileMgr (mfm) View Menu to prevent this conflict.
-
Here's one I found: alt-f4 is often used for shutting down apps. So pressing alt-f4 in openbox shuts mfm down.
-
OK. I will just drop the Alt-Fn hot keys in the troublesome View Menu Toggle section.
-
OK. I will just drop the Alt-Fn hot keys in the troublesome View Menu Toggle section.
Or maybe replace them with Shift-Fn? These seem to have no special purpose...
-
/usr/share/applications/tinycore-exittc.desktop is missing
-
True. It was producing a duplicate Exit option in the Systems Tools menu and
openbox, icewm, fluxbox, hackedbox, jwm, flwm, and LXDE do not need it.
Instead of having a duplicate exit item, if there is some specific wm/de that needs it, then perhaps it should be included in that particular extension in the usual and supported /usr/local/share/applications/ directory?
-
I am hoping that someone can find me, or even make, a nicer more matching and slightly larger icon for the file manager as was done for the exit icon.
-
Oh. I didn't realize mfm was imminent as a base app. Maybe I would not have started my "Fluff" file manager if I did. Or at least not before trying to live with mfm for a while and only proceed if I saw a compelling reason. :-\
I tried mfm in the 2.x (2.4?) days and was not crazy about it. I don't recall if it was a specific lack of a feature, or something more general, but for some reason, it left me wanting to make a new native-FLTK file manager myself. Maybe I need to check out the mfm as it is in TC 3.3-rc.x now and see if I still feel that way.
Fluff is getting pretty useful, but still has some rough edges. Fluff also does file associations and maybe has many other features in common with mfm. Fluff's executable is about 100K in size. I don't remember how that compares to mfm. Fluff may have to grow a bit more to polish it, assuming I continue development. But the motivation is different if there is already something very similar in the base.
I'll attach a screen capture of my current version of Fluff if anyone is curious.
--
Mike Lockmoore
-
Yes, you have seen mfm, as I shared the code that I had back in 2.x days. Actually I have been toying with the code since pre 1.0 days.
I have not seen nor am I aware of any target date for fluff. The math calculator was higher priority.
I felt that I needed to move ahead with an easy file association edit capability, as I have, more than I should have, to explain.
I would certainly not stop with your efforts with fluff. Once you feel it is ready I would be more than happy to evaluate it for mfm replacement. The screenie you attached looks very promising. Until then.
-
I am hoping that someone can find me, or even make, a nicer more matching and slightly larger icon for the file manager as was done for the exit icon.
Were you thinking of a filing cabinet icon or a folder icon?
I made this one, based on a gnome starting point.
-
Looks good. It is going in for rc2. Thanks!
-
Robert - I think its is great having mfm and a (non-vi) editor in base. While I have always been able and willing to move files around at the command line, and I've actually successfully (if haltingly) used vi a couple of times, I think these two additions are a huge benefit to the less geeky crowd and a great big convenience to the rest of us.
I haven't played with mfm enough yet to really explore its capabilities and limits, but...
MikeLockmoore - I like the look of Fluff from your screenshot. I'm partial to the layout with the directory tree and the directory content in side-by-side panes of the same window. If you choose to continue with that project (and I hope you do), I'll be very interested to try it out.