While the master codes and tests I would like to offer the following idea for a future version. This I believe would make XYP even more powerful and attractive to the power user. The example I have given below is in it's simplistic form merely to describe the concept. Power users (which I am not) could better provide the detail needs.
Worth consideration for a future feature in XYplorer?
-------------------------------------------
Power Tasks:
A power task in this context is the ability to repeat common tasks
with just a single click! If you like it is analogous to the macro
facility in many programs but for XYP it is done using a pre-forma
along the lines:
Each Power Task would reside in the Catalogue.
Task xyz (user named)
This would on selection (R Click) present options
Create profile ( presents a dialogue window for completion - see below)
Run task (preforms the task(s))
Delete Task (removes the task from the Catalogue)
----------------------
Dialogue window......
Task xyz
Include: (user copies by drag & drop folders/files in the profile window)
Rename: (user specifies rename requirements) Could include existing
rename preview
Destination:
New Single [check box] (user enters name/loc)
Existing Single [check box] (user presented with list of existing used locations to select one)
Multi [check box] (user presented with list if previously used
to tick those required followed by option
to add more to list and select)
Action: Move [check box]
Copy [check box]
Report: emulates panel report options
Save: Task profile saved or canceled
(clearly the profile tasks could be enlarged for future enhancement)
Power Tasks
-
jacky
- XYwiki Master
- Posts: 3106
- Joined: 23 Aug 2005 22:25
- Location: France
- Contact:
I think an easier/simpler (and maybe more powerful) way to achieve such things is already planned, on the roadmap, under "scriptability"
With scripting capacity we users will have access to almost every feature/command of XY, so we will be able to start a sequence of many operations (file, rename, copy, etc) with only one click or KS.
Obviously though, that's not for tomorrow.
With scripting capacity we users will have access to almost every feature/command of XY, so we will be able to start a sequence of many operations (file, rename, copy, etc) with only one click or KS.
Obviously though, that's not for tomorrow.
Proud XYplorer Fanatic
-
j_c_hallgren
- XY Blog Master
- Posts: 5826
- Joined: 02 Jan 2006 19:34
- Location: So. Chatham MA/Clearwater FL
- Contact:
For reference on this topic, here's what may likely be the best prior thread (was before graham joined forum):
http://www.xyplorer.com/xyfc/viewtopic.php?t=1520
As I understand it, this will give access to even more choices in functions than are available currently, as it may give ability to execute selected portions of some commands instead of just the complete command.
There's some info in this other thread about this concept:
http://www.xyplorer.com/xyfc/viewtopic.php?t=1608
http://www.xyplorer.com/xyfc/viewtopic.php?t=1520
As I understand it, this will give access to even more choices in functions than are available currently, as it may give ability to execute selected portions of some commands instead of just the complete command.
There's some info in this other thread about this concept:
http://www.xyplorer.com/xyfc/viewtopic.php?t=1608
Still spending WAY TOO much time here! But it's such a pleasure helping XY be a treasure!
(XP on laptop with touchpad and thus NO mouse!) Using latest beta vers when possible.
(XP on laptop with touchpad and thus NO mouse!) Using latest beta vers when possible.
-
graham
- Posts: 457
- Joined: 24 Aug 2007 22:08
- Location: Isle of Man
Thanks, I had not seen these references to scripts - you must have some super filing method or a fantastic memory to recall these links!
Yes I can see how scripts answer the need to do a lot of almost everything. I was, in times past a programmer/analyst coding in Cobol, PL11 and C++ and various other odd languages, most now history. From experience, the perennial problem is that whilst script code can be learned and relatively easily applied it can also start to become tiresome when things don't always work out as intended. Take SQL as an example - seems easy but once you start to get clever then it can be a pig especially if you use these things occasionally and forget the clever bits. As a result many organisations employ coding specialist to to this. Remember RPG - designed as a managers report tool - now look at the latest iterations of RPG and it is not at all friendly!
What I was suggesting was not a replacement for scripts but rather a complimentary simple dialogue approach which required zero programming or tech speak ability. I think it is fair to remember that power users are not all from an IT or programming background and many are from finance or business management and just want the ease and speed to do things quickly and reliably - no time to test results or debug.
The pro forma dialogue approach offers a more limited scope yet also provides massive amount of 'standard' basic file procedure manipulation. The implementation, for example, of the rename preview in XYP is imo an example of such a dialogue which offers users the ability to get reassurance whilst others more accomplished can simply enter the code directly and run.
It seemed to me that my proposed concept was relatively easy to implement given that it does not break new ground and 'gathers' together most of the routines already built as modules. Having said that I am not that out of touch to appreciate the build and implement task requires a very special knowledge only available to Don and development time.
Ok, it was just an idea for consideration but I still think it has some merit and could live happily alongside a script or macro facility.
Yes I can see how scripts answer the need to do a lot of almost everything. I was, in times past a programmer/analyst coding in Cobol, PL11 and C++ and various other odd languages, most now history. From experience, the perennial problem is that whilst script code can be learned and relatively easily applied it can also start to become tiresome when things don't always work out as intended. Take SQL as an example - seems easy but once you start to get clever then it can be a pig especially if you use these things occasionally and forget the clever bits. As a result many organisations employ coding specialist to to this. Remember RPG - designed as a managers report tool - now look at the latest iterations of RPG and it is not at all friendly!
What I was suggesting was not a replacement for scripts but rather a complimentary simple dialogue approach which required zero programming or tech speak ability. I think it is fair to remember that power users are not all from an IT or programming background and many are from finance or business management and just want the ease and speed to do things quickly and reliably - no time to test results or debug.
The pro forma dialogue approach offers a more limited scope yet also provides massive amount of 'standard' basic file procedure manipulation. The implementation, for example, of the rename preview in XYP is imo an example of such a dialogue which offers users the ability to get reassurance whilst others more accomplished can simply enter the code directly and run.
It seemed to me that my proposed concept was relatively easy to implement given that it does not break new ground and 'gathers' together most of the routines already built as modules. Having said that I am not that out of touch to appreciate the build and implement task requires a very special knowledge only available to Don and development time.
Ok, it was just an idea for consideration but I still think it has some merit and could live happily alongside a script or macro facility.
-
j_c_hallgren
- XY Blog Master
- Posts: 5826
- Joined: 02 Jan 2006 19:34
- Location: So. Chatham MA/Clearwater FL
- Contact:
graham wrote:Thanks, I had not seen these references to scripts - you must have some super filing method or a fantastic memory to recall these links!
I can definitely relate to that! If you look at my profile, you'll see what I used to do: COBOL!graham wrote:I was, in times past a programmer/analyst coding in Cobol, PL11 and C++ and various other odd languages, most now history.
Remember RPG - designed as a managers report tool - now look at the latest iterations of RPG and it is not at all friendly!
I did that for about 25+- yrs, with some IBM 370 Assembler mixed in, did RPG as my first summer job in '77, and most recently, learned some PERL to handle my other website which is a chat-room for/about the town where I spend the summers.
I just wanted to give you the benefit of some of what had been discussed here before...I wasn't saying your idea didn't have merit, ok? But jacky and myself think that we'll let Don guide us as to what he can do best, as I see it...graham wrote:Ok, it was just an idea for consideration but I still think it has some merit and could live happily alongside a script or macro facility.
Still spending WAY TOO much time here! But it's such a pleasure helping XY be a treasure!
(XP on laptop with touchpad and thus NO mouse!) Using latest beta vers when possible.
(XP on laptop with touchpad and thus NO mouse!) Using latest beta vers when possible.
XYplorer Beta Club