Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on July 09, 2011, 10:37:50 PM
-
The First Release Candidate of Tiny Core v3.8 is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates
tinycore_3.8rc1.iso
tinycore_3.8rc1.iso.md5.txt
Change log:
* New icons for AppBrowser and AppsAudit.
* Updated mnttool - added a refresh button.
* Updated AppsBrowser - clear Search&Provides field upon results.
* Updated Wallpaper - Improved GUI. Now with a single window.
* Updated AppsAudit - updated error reporting and now reports stale extensions.
* Updated tce-load - now allows re-downloading non-installed extensions to better handle download failures.
* Updated tce-setup & tce-load to ensure busybox calls thus avoiding conflicts with gnu utilities.
* Updated rc.shutdown - removed sleep to improve shutdown speed.
-
AppsAudit Fails updates ( I have not researched why yet ).
The problem is that the right pannel is unreadable with "FAILED" overlaying ontop of package names.
-
Found it. Fixed it. Re-posted tinycore.gz & tinycore_v3.8rc1
-
Great. Working now.
Thanks.
-
Please add 'Run in terminal' option to FLRun.
-
In AppsAudit/Updates change button text
"Process Selected Item(s)" to "Download Selected Item(s)"
-
New icons for AppBrowser and and AppsAudit. Use the same grey circle as FLRun has and place arrow and tick in the middle in a bigger size. This would give a unified look and feel to TC icons and easier recognition of buttons.
TCExit icon requires just a small adjustment to be in line.
-
Looks like we are getting down to very fine tuning. ;)
Will consider. I have already requested Dale our Team graphics guy to take a look.
-
Looks like we are getting down to very fine tuning. ;)
TC is getting matured 8)
-
Updated mnttool - added a refresh button.
A refresh button is great but how about open "mnttool" on drive detection? If you connect a USB thumb drive for example, it is detected so why not present the mnttool which is the next expected action of the operator?
It follows that if you connect a drive there must be some intent to use it, no? You could take this one step further and mount the drive considering this is the intention of connecting the drive, whilst leaving the mnttool up for the inevitable removal.
-
Re the AppsAudit how about a simple confirmation box when an extension is selected to be moved from either the select window to the OnBoot/OnDemand window or vice versa.
I hate confirmation boxes but the number of times I've accidentally removed an extension from a menu by selecting some place in the open window bringing the AppsAudit window to the foreground is staggering, when this happens there is no log of which app you accidentally removed. :(
just a thought, because some folks have more than one window open at any given time :)
-
Re the AppsAudit how about a simple confirmation box when an extension is selected to be moved from either the select window to the OnBoot/OnDemand window or vice versa.
I hate confirmation boxes but the number of times I've accidentally removed an extension from a menu by selecting some place in the open window bringing the AppsAudit window to the foreground is staggering, when this happens there is no log of which app you accidentally removed. :(
just a thought, because some folks have more than one window open at any given time :)
+1
-
Re the AppsAudit how about a simple confirmation box when an extension is selected to be moved from either the select window to the OnBoot/OnDemand window or vice versa.
I hate confirmation boxes but the number of times I've accidentally removed an extension from a menu by selecting some place in the open window bringing the AppsAudit window to the foreground is staggering, when this happens there is no log of which app you accidentally removed. :(
just a thought, because some folks have more than one window open at any given time :)
+1
or require a double click to move an item.
With the 2 finger scrolling on some touchpads it is very easy to single click an item when moving fingers back to the top of the pad for the next swipe. Then you have an extension you didn't want removed or added and are back to the top of the list again!
-
Do they always go to the top of the list? I don't think so not always anyhow..
-
Sorry, I didn't make it clear
The extensions are added at the bottom of the list, or removed to their original (alphabetical) position in the list in the left side window.
When an extension is added from the left window to the right window the left windows goes back to the top of the list so you need to scroll back down the entire list to find the extension you were looking for in the first place.
-
This has turned to being ideas and suggestions.
Sorry, I cannot please everyone, but I have no interest in popup dialog confirmation boxes or the dreaded double click. Feature creep towards being like Windows is not in the cards.
-
A refresh button is great but how about open "mnttool" on drive detection? If you connect a USB thumb drive for example, it is detected so why not present the mnttool which is the next expected action of the operator?
It follows that if you connect a drive there must be some intent to use it, no? You could take this one step further and mount the drive considering this is the intention of connecting the drive, whilst leaving the mnttool up for the inevitable removal.
Such popups "I see you put in an usb drive, would you like me to blabla" are really against the idea of TC to me. Also discussed before.
-
i agree,
we should not blow up tinycore,
it 's so unbelievable lean and clean...
one important goal should be to stay this tiny size,
6 or 10mb, packed with such a great environment, don't blow it up!!!!
please don't be offended, although the above mentioned symbolic link per label is rejected:
i really love this idea of symbolic links, especially this LABEL-link,
because i like to have on different platforms (like tinycore-configs, desktops, servers or embedded systems)
the same links, paths, multifunctional environments....
i don't mind to look for a different way to umount this /mnt/LABEL.
perhaps tinycore could mount on the normal mount point, but offers the /mnt/LABEL-link at the same time!?
perhaps there is a way to umount over the normal mount point or the device f.e.
/mnt/sdb2/tce /dev/sdb2 physical device
/mnt/TCE /dev/sdb2 LABEL-link
umount /mnt/sdb2/tce
i would be happy if you could leave this idea in your focus at least for the long future.
thank you.
-
A pop up or double click to select, didn't expect to be taken so literally these were just thoughts, throwing out idea's Really I'm hoping you can come up with some innovative mechanism which is worthy and in keeping with the flavor of TC
;)
-
Wallpaper is much better now. Thanks!
-
A refresh button is great but how about open "mnttool" on drive detection? If you connect a USB thumb drive for example, it is detected so why not present the mnttool which is the next expected action of the operator?
It follows that if you connect a drive there must be some intent to use it, no? You could take this one step further and mount the drive considering this is the intention of connecting the drive, whilst leaving the mnttool up for the inevitable removal.
Such popups "I see you put in an usb drive, would you like me to blabla" are really against the idea of TC to me. Also discussed before.
Exactly it's obnoxious, I hate that too so I'm just throwing out the worst possible idea, leaving the innovative thinking to the experts who are now aware.. just bringing some potential area's where minor improvements wouldn't hurt to your attention and who knows perhaps one day...
I'd say why not simply skip all the steps in the process and just auto mount the USB thumb drive which was connected with the intention of using it right? A mount tool's purpose then becomes a removal tool. I think the steps could be streamlined for a more fluid user experience.
A bit late now but this was probably not the right location for this discussion
-
I'd say why not simply skip all the steps in the process and just auto mount the USB thumb drive which was connected with the intention of using it right? A mount tool's purpose then becomes a removal tool. I think the steps could be streamlined for a more fluid user experience.
I disagree with the automount suggestion. Mounting is not always the proper behaviour. Consider that one might occasionally connect a USB device just in order to get extra info (using lsusb, etc...)
In addition, I believe automount goes against TC's philosophy to empower its users. Automount is enabled by default on turnkey distros because the approach is to guess the user's intention (user probably has the intention of mounting the USB key). On the other hand, TC's approach is to give the user the capability to decide by herself. And thus TC provides a mounting facility UI but does not hide the fact that connecting a USB device and mounting its filesystem are fundamentally different operations.
-
My view is that automount most be provided by higher application levels, for example DE like Xfce or LXDE, not the base.
-
My first thought is that automounting a removable device is a bad idea in almost any circumstance. The only possible exception that comes to (my) mind would be some kind of "device copier" but then the copying application could handle the mounting.
Perhaps some optional method could be devised at the system with specific filesystems designated (by UUID or label) to be automounted when inserted, but (imho) the default should always be to -not- automount. I wouldn't even bother with an optional method myself.
Also, any file system that is autmounted would have to be umounted before being fsck'd.
I find it comforting to know that my filesystems aren't going to get trashed until I explicitly make them available for corruption. :)