|
Post by Stefan on Aug 30, 2022 4:11:08 GMT -5
Robert, Great idea and a pretty nifty implementation, indeed!
I did say previously that I would be a user of this.
I have already several files whose type is, strictly-speaking, .TXT but for which I want different AUTO higlighting or different Tab stops, Bounds, etc. I achieve the desired effects by 'faking' the filetype, (which fools Windows) or by specifying an IMACRO for the general type to check the filename and set an appropriate environment if applicable.
An example known to many SPFLite users is the CFGMAINT -EXPORT file. My TXT.AUTO file is a bit iffy when displaying some other 'real' text files! Messy!
Here's a CFG_TXT.AUTO that does the job without affecting normal text files (will need updating following recent new SPFLite version).
EFT will manage all these situations without such shenanigans.
Some other things that spring to mind...
I assume the difference between * and ? in match-codes is that * means "one or more chars" and ? and "exactly one char", as usual? If/When George supports the use of ; comment, would it be possible to extend this to the SET variable lines also, please? They already work on AUTO files (except for the QUOTED entry)
Macros: Function Get_Profile$(NAME) may need slight amendment to cope with EFT as well as, or instead of, USING
Are we likely to need some sort of EFT equivalent to the GET_SETVAR$ and SET_SETVAR functions?
|
|
|
Post by George on Aug 31, 2022 16:29:00 GMT -5
Robert: We skipped dinner tonight, too many drinks + hor d'oerves to then go for a full dinner. So checked the forum. As usual, you've been busy. Basically, looking good. Currently on the way to Horta, go check your Google maps.
George
|
|
|
Post by Stefan on Sept 1, 2022 6:02:04 GMT -5
Robert, I see what you're saying about "Unique File Type" but I think the formal 'compartmentalisation' of terms will only serve to confuse users (It sure confuses me!).
Assuming I read it correctly, the syntax you outlined earlier already supports a 'UFT' use case. Taking the example of a CFGMAINT.EXP <date-time-stamp>.TXT file, I can assign the required profile by "focusing" on CFGMAINT or CFGMAINT.EXP parts of the filename. I see no need for another level of explanation for such a use case.
It is similar to my alternative use of COMMENT entries in AUTO files, which isn't specifically described in the SPFLite documentation.
The fact that one can (and I do in my BAT.AUTO file) use a line like
COMMENT8 6 % % ; User variable To highlight user variables in a BAT file is a useful capability. It isn't what it was designed for but it works and doesn't require further explanation.
|
|
|
Post by George on Sept 2, 2022 4:20:40 GMT -5
Robert: had another quick read, I don't like the use of <*> why not just another single character, like !
George
|
|
|
Post by Stefan on Sept 4, 2022 12:33:11 GMT -5
Robert,
I wonder if the 'ignore' string could be simpler, given that by definition, the ignore string isn't actually in a 'flinename' pattern as such, but in the profile name template.
So you could use a pair of symbols which are 'legal if unusual' in a filename to mean 'ignore' in the profile name template. You would simply designate the chosen pair of chars as 'not valid in a profile name'. Then you can avoid the use of <...> and just deploy a single char (or multiples thereof) to mean 'ignore' in the profile template.
Given that the chars would be 'infrequently used' in a file name, I see no problem from excluding them when forming a profile name (which presumaby just needs to be legal for use in the CFG)
|
|
|
Post by Stefan on Sept 5, 2022 8:46:38 GMT -5
FWIW... If you decide to use '=' in the syntax, (and this may be just the way MY mind works) I would find the 'keep' and 'ignore' chars easier to remember if "=" meant 'keep' instead of 'ignore'.
|
|
|
Post by George on Sept 5, 2022 19:58:22 GMT -5
I hope you guys simplify this, I'm not concerned about the coding (I'm sure Robert can make it work), but my brain hurts just reading this. I think we're into overkill-land.
|
|
|
Post by George on Sept 6, 2022 12:40:13 GMT -5
Robert: Much better. I had an alternative way in mind, but yours does just fine.
George
P.S. Odd ship - this is the first one ever where pizza is not available in the buffet, or up on the pool deck. Nor on any restaurant menu.
Turns out its available 24 hrs/day from room service, so we just had one, washed down with champagne of course. We're in Bermuda (St Georges) and it's hot and humid - Icky! Off toward New York this afternoon.
|
|
|
Post by George on Sept 7, 2022 8:47:24 GMT -5
Robert: I think your latest is just fine, mine would not have been as flexible. Stick with what you've got. George
|
|
|
Post by George on Sept 24, 2022 13:36:58 GMT -5
Robert: I've never had a problem with your latest EFT stuff, finish it off and I'll replace the current one, change everything to EFT (from FTX) and get a Beta out you can play with.
As to your Session/LOGON idea, well that was simply way too big a change. Redesigning things to accommodate your ideas was simply a 'bridge too far'. Startup and Instance management as it is, is non-trivial, what you were asking for would frankly be too much for me.
Please don't lump one 'forget it' into a blanket shutdown.
George
|
|
|
Post by George on Sept 24, 2022 14:17:28 GMT -5
Robert: I downloaded the Working With Doc, got to page 4 (of 11) and my head hurts, and my eyes are drooping.
If this is in any way destined for the user documentation, it's overwhelming. If it's for me, it's only 'just a bit much'.
You're very thorough, but If I were a user, and explored this, I'd close the cover and go back to normal work. Maybe you understand syntax diagrams like this but I sure don't, it's gibberish to me (considering I DO understand what it's trying to impart)
I think you're too much into the detailed "SPECS", that the coder needs to know. And since that's you, I don't need to know anything other that what other SPFLite changes you want to go with it.
What I'd like to see is what the "Working with ..." looks like for the final Help file. Hopefully it's short and succinct.
I'll try and work through the remaining pages and try and figure out just what it is you expect of me.
[UPDATE] Just hit your Fwd/Bkwd labels description. Can't tell you how much I hate it. Bkwd is simply NOT NEEDED.
[/UPDATE]
[UPDATE2] Ditto for those unlabelled wild cards, you're killing this with complexity.
[/UPDATE2]
[UPDATE3] SORT routine WILL NOT be updated for SORT EFT. Period.
[/UPDATE3]
George
|
|
|
Post by George on Oct 7, 2022 14:41:20 GMT -5
Just for any of you following this thread.
There is progress, Robert and I have been busy in the background and thrashing things out. Hopefully a Beta can be rolled out soon.
George
|
|
|
Post by Stefan on Oct 8, 2022 5:20:50 GMT -5
Well, I for one am definitely looking forward to it. On the simplest level, it will avoid me having to invent a different file extension for a perfectly normal file just to give it an Imacro or Emacro or some other slightly alternative presentation treatment.
(Please) Rock On, fellas!
|
|
|
Post by George on Oct 15, 2022 12:46:05 GMT -5
Robert:
Your thoughts on the current "Use DEFAULT for these file-types". (Options => General)
As it sits with EFT, the EFT creates the Profilename, and THAT name is matched against the DEFAULT list.
e.g. If the DEFAULT list contained BILL and EFT contained .FRED = BILL then the .FRED file will be opened with the DEFAULT profile, not the BILL profile.
If we get rid of the DEFAULT list, it means users will need many more entries in the EFT list that say .AAA = DEFAULT .BBB = DEFAULT etc. etc.
George
|
|
|
Post by George on Oct 15, 2022 15:23:31 GMT -5
Robert: My main concern with multiple EFT entries in the EFT list is still performance(and we don't know the impact yet). The EFT search for a Profile means scanning the EFT list for a match. The FM Refresh function means calling the EFT search for every item in the folder being displayed, and a refresh is done frequently. Maybe systems now are fast enough for it not to matter, we don't know that yet. The caching of 'does a Profile have STATE ON' can only be done AFTER the EFT search, not before.
The DEFAULT search itself is a nit, it's a single, simple INSTR test, it can remain.
I don't like the idea of adding another layer of complexity to the EFT list, the management and searching of the list would be getting to the ridiculous stage.
Remember, I have to modify all that code that handles when a 'profile' doesn't exist, it's messy as it is, I don't need it to get worse. You have an isolated "does 'A' = 'B'" to handle, I wish my side were as easily defined as that.
George
|
|