XYplorer Beta Club

j_c_hallgren wrote:Yes, I've said that...but that also doesn't discount that when a feature continues to keep getting asked for over time by new users, it makes business sense to work on those first and then add other lesser requested features as time allows...so I'm not saying that majority should rule on features, but they certainly can influence the importance of which ones are added and in what order.

Well this doesn't seem to be the case with Recycle Bin, does it?

j_c_hallgren wrote:Same can thus be said for scripting and UDC, right? Win Expl doesn't have these (unless they hid them really well!) but it does have a variant of FVS, so that is more expected.

I must once again quote the example of Recycle Bin. WE very much has it as part of the tree, it's more expected but nowhere to be seen in XY.

ivan wrote:I must once again quote the example of Recycle Bin. WE very much has it as part of the tree, it's more expected but nowhere to be seen in XY.

Huh? XY certainly has it as part of tree, at least on my system! However, the view that is presently when doing so is the 'internal' view instead of the 'user' view, which I actually find to be an advantage! And I can see the 'user' view via Tools menu hook back to WE so I have the best of both worlds...

This was subject of a thread I made a long time ago... http://www.xyplorer.com/xyfc/viewtopic.php?f=3&t=1021

So IF XY presented the same 'user' view, then I'd need to have some way to see the current 'internal' view, thus any improvement in this area needs to not lose the benefits of how it is right now.

j_c_hallgren wrote: Huh? XY certainly has it as part of tree, at least on my system! However, the view that is presently when doing so is the 'internal' view instead of the 'user' view, which I actually find to be an advantage! And I can see the 'user' view via Tools menu hook back to WE so I have the best of both worlds...

The bad thing is that the 'internal' way is not the way RB should have made its way into XY. There is no doubt that 'user' view would take care of the majority, but it clearly doesn't rule there. The 'internal' view takes care of the minority. Saying that

when a feature continues to keep getting asked for over time by new users, it makes business sense to work on those first and then add other lesser requested features as time allows...so I'm not saying that majority should rule on features, but they certainly can influence the importance of which ones are added and in what order.

but then adding that

I'd need to have some way to see the current 'internal' view, thus any improvement in this area needs to not lose the benefits of how it is right now

creates a conflict of contradiction because on one hand you're saying that majority "rules" and on the other you say that minority must be taken care of in order to benefit the majority.

ivan wrote:

...so I'm not saying that majority should rule on features, but they certainly can influence the importance of which ones are added and in what order.

but then adding that

I'd need to have some way to see the current 'internal' view, thus any improvement in this area needs to not lose the benefits of how it is right now

creates a conflict of contradiction because on one hand you're saying that majority "rules" and on the other you say that minority must be taken care of in order to benefit the majority.

Ok...let me try one last time, because you've now appear to have misquoted my position and I'll not let that go by...

As I now bolded, I have not said that the majority rules, and I also have not said that minority must be taken of to benefit the majority! I did say that existing functionality needs to be retained but as to how that is done, I'm not that concerned, and should that hold up a 'user' view? Well, only because, although it may not be the ultimate in convenience, the existing functions handle it for either type of user, and Don usually doesn't remove an feature in order to add another, so relocating or swapping the existing 'internal' view with a 'user' view might be one option.

It's a extremely minor issue in the overall scheme of things and I just don't see why this Recycle Bin is such a problem for your usage...maybe I'm dense, but it's pointless to continue with this.

And as I wrote long ago, having this 'internal' view is REALLY an advantage that other programs don't offer, and has proved VERY valuable to me...would I like a built-in 'user' view? Yes...but it's not at the top of my list, given what other options are available....I'd much rather Don spent time on features that do NOT exist anywhere else!

j_c_hallgren wrote: It's a extremely minor issue in the overall scheme of things and I just don't see why this Recycle Bin is such a problem for your usage...maybe I'm dense, but it's pointless to continue with this.

And as I wrote long ago, having this 'internal' view is REALLY an advantage that other programs don't offer, and has proved VERY valuable to me...would I like a built-in 'user' view? Yes...but it's not at the top of my list, given what other options are available....I'd much rather Don spent time on features that do NOT exist anywhere else!

We've strayed from the main topic: the main matter of scripting not being able to tell if a task has finished so the script can carry on. It can't even do it if the process's name is known. It is important for scripting to be able to do that as soon as possible otherwise for me scripting adds very little efficiency.