Updating fluff, flit, and flpicsee updates to fltk-1.4

[Leee]

I've tried the new fluff_testing.tcz both with my baregui.lst config (using flwm) and with my regular onboot.lst that loads tons of other stuff (using jwm) and the problem appears to be gone.

I also tried it with fluff zoomed in to 150% and still no problems.

[MikeLockmoore]

I've tried the new fluff_testing.tcz both with my baregui.lst config (using flwm) and with my regular onboot.lst that loads tons of other stuff (using jwm) and the problem appears to be gone.

I also tried it with fluff zoomed in to 150% and still no problems.

Great!   

[Leee]

@MikeLockmoore - not  "bugs" in fluff,  but some suggestions:

On the fluff button bar, there are the "Action 1" and Action 2" buttons, right next to the "Quit" button, with actions tat vary  depending upon the type of the selected file...

Is there any chance you could add one or two (or several) additional buttons, similarly programmable via .fluff.conf, that -don't- change with the file type but which could be used to run any arbitrary command or script against the selected files and/or directories?  Given that extra buttons would crowd the button bar a bit, maybe the quit button could be much smaller, or even removed completely.

Separately, whenever an external process removes a highlighted file, a warning dialog pops up with "One or more selected items have been either moved or deleted!" and requires a click of its "Close" button to dismiss.  This seems pointless, especially in as much as there's nothing you can do about it at that point anyway.

[MikeLockmoore]

@MikeLockmoore - not  "bugs" in fluff,  but some suggestions:

On the fluff button bar, there are the "Action 1" and Action 2" buttons, right next to the "Quit" button, with actions tat vary  depending upon the type of the selected file...

Is there any chance you could add one or two (or several) additional buttons, similarly programmable via .fluff.conf, that -don't- change with the file type but which could be used to run any arbitrary command or script against the selected files and/or directories?  Given that extra buttons would crowd the button bar a bit, maybe the quit button could be much smaller, or even removed completely.

Separately, whenever an external process removes a highlighted file, a warning dialog pops up with "One or more selected items have been either moved or deleted!" and requires a click of its "Close" button to dismiss.  This seems pointless, especially in as much as there's nothing you can do about it at that point anyway.

Leee: Thanks for the suggestions. The "moved or deleted" warning should be easy... I agree, it really doesn't serve much purpose.

I suppose Quit is a bit redundant, I guess I was following the "bigger targets are easier to hit" approach.  Non-type-specific options would be nice I suppose at least for multi-file selections (e.g. "compress this group of files into a .tar.gz"). 

I do want to add at least two small buttons for going back to a previous directory and up in the folder hierarchy, maybe forward too if we can go back.  I can use the FLTK button symbol codes to make these look like little triangle shapes (like PLAY and REWIND buttons on a media player) instead of using a full text word, so they won't take up much space.

[MikeLockmoore]

In other updates, I've modified Flit to only use the FLTK fractional scaling and removed the custom fractional scaling code I had put into it in previous (perhaps unreleased) versions.  I've redone the WiFi symbol and the sound volume control to look cleaner and better take advantage of current FLTK features, although not going as far as using SVG icons ... my first experiment did not go well ... maybe not all SVGs are created equal(ly compatible).

Screenshots attached of a a very zoomed-up Flit with two of the "tooltip" pop-up text messages.

 

[MikeLockmoore]

@MikeLockmoore - not  "bugs" in fluff,  but some suggestions:

... whenever an external process removes a highlighted file, a warning dialog pops up with "One or more selected items have been either moved or deleted!" and requires a click of its "Close" button to dismiss.  This seems pointless, especially in as much as there's nothing you can do about it at that point anyway.

Leee: I've removed this warning in my current WIP version (1.1.4).  I've also removed some references to things that perhaps used to exist but do not now (e.g. /opt/.tce_dir), which can cause error messages on the console if you start fluff that way.

I'm going to work on some command button stuff.  First the general navigation buttons, then perhaps the generic file action buttons that you suggested. I think I will also re-order the position of the buttons so that Home is the farthest to the left.

[Leee]

@MikeLockmoore - not  "bugs" in fluff,  but some suggestions:

... whenever an external process removes a highlighted file, a warning dialog pops up with "One or more selected items have been either moved or deleted!" and requires a click of its "Close" button to dismiss.  This seems pointless, especially in as much as there's nothing you can do about it at that point anyway.

Leee: I've removed this warning in my current WIP version (1.1.4).  I've also removed some references to things that perhaps used to exist but do not now (e.g. /opt/.tce_dir), which can cause error messages on the console if you start fluff that way.

I'm going to work on some command button stuff.  First the general navigation buttons, then perhaps the generic file action buttons that you suggested. I think I will also re-order the position of the buttons so that Home is the farthest to the left.

Thanks, Mike.  I'm ready to test whenever you have an update.

[Rich]

Hi MikeLockmoore
fluff_testing (1.1.5)  and  flit_testing (1.5.2)  .tcz and .tcz.dep have been posted to:
http://tinycorelinux.net/16.x/x86_64/tcz/testing

[Rich]

Hi Leee and other testers
If you have fluff or flit loaded, reboot without loading them before
attempting to load fluff_testing and/or flit_testing.

Source tarballs can be found in:
http://tinycorelinux.net/16.x/x86_64/tcz/testing/src

Those tarballs also contain .tcz.info and others if interested.

MikeLockmoore will be traveling starting tomorrow and will not
be able to respond to feedback until he returns, so:
Please be patient.

[MikeLockmoore]

Hi MikeLockmoore
fluff_testing (1.1.5)  and  flit_testing (1.5.2)  .tcz and .tcz.dep have been posted to:
http://tinycorelinux.net/16.x/x86_64/tcz/testing

Thanks Rich!

Hi Leee and other testers
If you have fluff or flit loaded, reboot without loading them before
attempting to load fluff_testing and/or flit_testing.

Source tarballs can be found in:
http://tinycorelinux.net/16.x/x86_64/tcz/testing/src

Those tarballs also contain .tcz.info and others if interested.

MikeLockmoore will be traveling starting tomorrow and will not
be able to respond to feedback until he returns, so:
Please be patient.

True... I only have a little time this evening US time if anything pops up  immediately.  I'll try to monitor the forum but may not be able to directly reply for several days starting tomorrow.

@Leee: I don't have your "general" file/directory action button(s) idea implemented yet, but did drop the unneeded warning.

I did receive some suggestions from another TC user privately have have been incorporated.  Not too much drastic in Fluff besides the button layout, dropping Quit button and adding the path history navigation buttons.  Hope people like the updates!  Both these applications are working much better for me with the updates over the past two weeks. -Mike

[Leee]

Hi MikeLockmoore
fluff_testing (1.1.5)  and  flit_testing (1.5.2)  .tcz and .tcz.dep have been posted to:
http://tinycorelinux.net/16.x/x86_64/tcz/testing

Thanks Rich!

Hi Leee and other testers
If you have fluff or flit loaded, reboot without loading them before
attempting to load fluff_testing and/or flit_testing.

Source tarballs can be found in:
http://tinycorelinux.net/16.x/x86_64/tcz/testing/src

Those tarballs also contain .tcz.info and others if interested.

MikeLockmoore will be traveling starting tomorrow and will not
be able to respond to feedback until he returns, so:
Please be patient.

True... I only have a little time this evening US time if anything pops up  immediately.  I'll try to monitor the forum but may not be able to directly reply for several days starting tomorrow.

@Leee: I don't have your "general" file/directory action button(s) idea implemented yet, but did drop the unneeded warning.

I did receive some suggestions from another TC user privately have have been incorporated.  Not too much drastic in Fluff besides the button layout, dropping Quit button and adding the path history navigation buttons.  Hope people like the updates!  Both these applications are working much better for me with the updates over the past two weeks. -Mike

Thanks #MikeLockmoore.

I'll grab the latest and beat it up some.

It's late here right (I'm still running on Saturday evening's coffee) now so I probably won't do much tonight.

---
(20 minutes later)...
Got it.  Tried it.  At first glance, it looks great.  More testing tomorrow.

[MikeLockmoore]

Thanks #MikeLockmoore.

I'll grab the latest and beat it up some.

It's late here right (I'm still running on Saturday evening's coffee) now so I probably won't do much tonight.

---
(20 minutes later)...
Got it.  Tried it.  At first glance, it looks great.  More testing tomorrow.

That’s good to hear. I figured out the login from my phone, so I can reply if questions pop up.

@Rich- I understand about the moving the extension talk here. Thanks for linking it from the RC thread.

[Leee]

Thanks #MikeLockmoore.

I'll grab the latest and beat it up some.

It's late here right (I'm still running on Saturday evening's coffee) now so I probably won't do much tonight.

---
(20 minutes later)...
Got it.  Tried it.  At first glance, it looks great.  More testing tomorrow.

That’s good to hear. I figured out the login from my phone, so I can reply if questions pop up.

@Rich- I understand about the moving the extension talk here. Thanks for linking it from the RC thread.

In the latest fluff, there's an issue with not resetting the file list display when using the back button.  For instance, I...

• start with the window sized big enough to display a couple dozen items in the file list
• navigate to /home/ where there are three user directories
• descend into /home/tc/ where there are a hundred or so items
• scroll down a page or two
• click the back button to return to /home/

At this point the file list is trying to show the correct directory contents but the few items in /home/ are scrolled up above the top of the window so the window appears to be empty.  If I click on the scroll bar handle and slide it up, the "list" scrolls up until the contents become visible and then the scroll bar disappears.

I think when the back button is clicked it should either re-select the previously selected file in the target directory or should reset the file list display to the to the first file in the list (as determined by the sort order).

[MikeLockmoore]

In the latest fluff, there's an issue with not resetting the file list display when using the back button.  For instance, I...

• start with the window sized big enough to display a couple dozen items in the file list
• navigate to /home/ where there are three user directories
• descend into /home/tc/ where there are a hundred or so items
• scroll down a page or two
• click the back button to return to /home/

At this point the file list is trying to show the correct directory contents but the few items in /home/ are scrolled up above the top of the window so the window appears to be empty.  If I click on the scroll bar handle and slide it up, the "list" scrolls up until the contents become visible and then the scroll bar disappears.

I think when the back button is clicked it should either re-select the previously selected file in the target directory or should reset the file list display to the to the first file in the list (as determined by the sort order).

Thanks for the report, I’ll look to fix this when I can work on the code again in a day or two! (It will take a bit more “bookkeeping” to remember scroll positions, so maybe I will just make sure position is reset to show first item.)

[Juanito]

Looking good, a few comments:

Maybe the configuration files would be better saved in ~/.config/name (i.e. ~/.config/flit/flit.conf) rather than ~/?

If there is no sound enabled (the default for me) saving the flit config results in a seg fault and an empty conf file

If I open a large image in flpicsee it selects 25% zoom, but the title bar is off the screen with 1366x768 using flwm classic and I need to use <ctrl-m> x2 to get it back.