We just started using it at my employer, and all of us on the team are finding it very useful so far. We licensed the advanced version.
2 Likes
Do you notice any slow-down issues? On a relatively large FileMaker solution, the plug-in starts OK, but then bogs down -- repeatedly stopping for 5 or 10 minutes to do "something". After an hour, the progress bar is at the right, but it's still not done. I end up force-quitting FMP. Also, there's the plug-in related crash that happens every time I exit FMP 19.2.
For small apps, it's fine, but I need it to work acceptably for the client's app.
So far, the jury is out....
I'm testing the advanced version and I find the REPLACE to be really cool and even more time saving. I have problems with the plug-in with the actual client solution as noted below, but its concept is really good.
We have not noticed any kind of slow downs or crashes, and our solution is large. I'm not yet actually using the plugin for finds, etc. constantly, though it is open all the time.
Well, the slowness only happens when finding text so if you're not using that then it's not a comparable test.
What "may" be at least part of the bogging down issue is that I'm doing the "Find" against the solution which is in FileMaker Server on AWS from the remote FMP app running on my system. I'm not sure that that is the problem since the plug-in starts fine as I would expect. Since I don't have any real experience with this plug-in except for my personal small apps where it works fine, I have no idea.
There doesn't seem to be any way to get statistics or debug info from the plug-in to see what's going on.
The bottom line so far is that it's not going to be helpful since I can't wait over an hour for each search.
Would it be possible for you to install (if you haven't already) the Developer Assistant and do a search for some random text string? Since your solution is so large, I am interested to know if DA bogs down after initially starting off fine. For me, after an hour of waiting for DA's stops and starts, I end up force-quitting. I think DA is a fine tool, but I'm not sure where the problem is that is making it unusable.
I am running DA on an AWS FMS-hosted solution so perhaps there something else going on.
Please let me know if you are able to run this test. Thx.
I only tested it for a few minutes this morning. And it was running fine.
iMac 2019 3.6 GHz Intel Core i9, 128 GB RAM.
FileMaker 19.2.1 ( BaseElements, MBS, 2empowerFM plugins installed ).
It's interesting to me. As I look at it again, I still struggle to find it useful.
- DDR with FMPerception and FMComparison is way more valuable to me for searching and diagnosing.
- I wouldn't use Find/Replace in a single script. They just aren't long enough to take the time to search. We also dev in a duplicated script until it's ready. Then we swap out.
- We use custom functions to handle standard variable names. So we never actually use the variable name in scripts or calcs. ( ScriptParameter, ScriptResult, Logging, Errors, etc ).
- We generate most of our CRUD scripts using something like karbon_generator and a few utilities we have to convert and modify elements to generate the Set Variable and Set Field script steps.
1 Like
It takes a little while before it bogs down. You'd have to go all the way through your solution to really check.
The benefits for me with DA is that I can do regex searches so I can search for either something VERY specific or multiple things at once. Plus,, once you get a list of matches, you can navigate to each one in order or in any order. I've done the Replace many times in my testing and it's always worked fine. It also searches the relationship graph (also, optionally with a regex), the field, and table views. So, if you have a thousand tables all neatly arranged, you can quickly find/navigate to each occurrence.
Having to re-generate the DDR for FM Perception takes 20 to 30 minutes so that's not ideal either for multiple changes over and over.
If you're able to get through your entire solution, how many scripts and script steps does it have? Are you accessing your solution on AWS or locally on a server? I'm trying to understand differences that could account for what I'm seeing.
Currently, for $400, the tool. though I love its concept and how it behaves with small solutions, is a fail for the simple reason that it won't complete after an hour - making it not usable.
If I can figure out why its bogging down then I think DA would be useful with FM Perception as both bring unique strengths.
We generate a DDR weekly. That's really all I need. If I need to run a list of changes, I can just export the results out of FMPerception. But there are also a 1000 other things I can do with FMPerception that DA doesn't do. And I can't get myself to paying for both.
As for the graph, yeah, that can be tough. Anchor-buoy-ish type layout, and a simplified graph is helpful here for us. When you move all your CRUD actions to a single TOG, similar to how Karbon does it., it's way easier. Then UI related TOGs never need to have excessive TOs added just to process data. It's a slightly different mindset than most people have organically developed, but it's made things so much easier for development.
Attached are our stats. Keep in mind this is a 15 year old, organically built custom app. It's been in constant development by 2 devs ( 1 for about 10 years, 2.5 for the last 5 years ). And there are 3 production servers running previous clones of this set of files ( now very divergent as time passes ).
1 Like
I personally love FMPerception. The things you can get with this tool are beyond imagination.
2 Likes
I do not disagree. I too am having a hard time paying for both, but currently, I'm just trying to see if DA will even cut it with a real solution or, if not, where the problem is. If I can get DA to work correctly, then I can make an informed decision.
FM Perception will be there regardless as it's too valuable not to use.
So all that's missing is knowing if you can run DA searching a simple string through the entire app without it bogging down. How long, approximately, did it take? Did DA repeatedly stop and "think" here and there?
Thanks man.
1 Like
What are top things you use FM Perception for? I always feel like I'm just scratching the surface of what that incredible tool can do...
@DaveRamsey does an Office Hours every week on Thursdays at 4pm EST ( 1pm PST ). You should pop in. I am there almost every week, and I still pick up things on a regular basis. There is so much there.
Dave also goes through a lot of possible uses in his Vendor Demo at DevCon 2019 and COFMUG user group.
Very nice! I'll sign up. Thank you.
Are you mainly looking to find something across all scripts in a file? Or within the current script? @MonkeybreadSoftware, is RegEx a possibility for search on scripts?
Right now, I'm just trying to figure out if DA can do a simple search (a simple single word test search) without taking an hour and still not being done. @jormond is helping me there. Thank you.
1 Like
Our search is for containing the words you search for in one line.
We could do more, but since we intercept it on drawing, it should be quick.
I have a tool that I use to do intelligent searching within a DDR file. I've never tested it with a 350 MB file, however -- Largest I've used it for is just shy of 200 MB.
If you have any interest in trying it, I know I'd have interest in seeing whether or not it could tackle the extra volume of data. Feel free to DM me, if so, but no pressure, and no offense taken if you are not interested.
All the best,
-Steve
2 Likes
I can do extremely fast searches of the DDR with BBEdit (not an intelligent tool, but I can usually figure out what I want when Regex is needed).
I am currently only interested to know if the Developer Assistant is capable on a large FMS solution without bogging down like it does for me. (I'm in the 30 day eval phase so I need to figure that out if I'm going to plunk down $400.)
I'll always have FM Perception in my toolbag regardless but I may add DA if I can figure out why it's bogging down to non-usability.
Thank you @steve_ssh for your kind offer.
1 Like
I will reinstall and try to use it more tomorrow and see if I run into what you are seeing. Sounds an awful lot like a memory leak.
1 Like