LandFX Wizards,
Here's my issue. The selection process for a few paths are restrictive. For instance, while setting up preferences for the detail locations I can only navigate to mapped locations. How old school. I want to go to a server or computer name rather than a mapped drive. Let me explain how this restricts the use of the software rendering it unusable (unless you can solve the issue somehow). Our Irvine office is collaborating on a project with our Sacramento office. We have accelerators and very fast connections now that allow us to work on drawings located on their server. Four of our offices (San Diego, Irvine, San Diego and Petaluma) share a MySQL Server (we're on the cloud) so all of our projects are shared and show up properly in our LandFX Project Manager. We have our various preferences set up and all can access them. The problem is that our LandFX detail folders are located on different servers. Here's the problem. Even though the detail locations are both mapped to the "L:\LandFX\Details" there are two different servers and the paths to get to this mapped drive (really just a folder on their respective servers) are quite different. The problem is that if we're working in Irvine on a Sacramento project, LandFX looks to our "L" drive rather than theirs and so the expected detail is not found (of course not since it's looking in the wrong place). This could easily be solved if the path could be stored differently. Currently the software pulls up an old style dialog box (or whatever it's called) that only lets one navigate locally and doesn't allow one going to a network location or paste in a path. Can you guys change that to an interface that allows us to go to non-mapped locations where we can paste in a file path? I've included the current interface as well as an example of one that could solve this problem. Please let me know what you think. Will this solution solve our problem?
Seaweed
(AKA Steve Cook, Stantec)
Here's my issue. The selection process for a few paths are restrictive. For instance, while setting up preferences for the detail locations I can only navigate to mapped locations. How old school. I want to go to a server or computer name rather than a mapped drive. Let me explain how this restricts the use of the software rendering it unusable (unless you can solve the issue somehow). Our Irvine office is collaborating on a project with our Sacramento office. We have accelerators and very fast connections now that allow us to work on drawings located on their server. Four of our offices (San Diego, Irvine, San Diego and Petaluma) share a MySQL Server (we're on the cloud) so all of our projects are shared and show up properly in our LandFX Project Manager. We have our various preferences set up and all can access them. The problem is that our LandFX detail folders are located on different servers. Here's the problem. Even though the detail locations are both mapped to the "L:\LandFX\Details" there are two different servers and the paths to get to this mapped drive (really just a folder on their respective servers) are quite different. The problem is that if we're working in Irvine on a Sacramento project, LandFX looks to our "L" drive rather than theirs and so the expected detail is not found (of course not since it's looking in the wrong place). This could easily be solved if the path could be stored differently. Currently the software pulls up an old style dialog box (or whatever it's called) that only lets one navigate locally and doesn't allow one going to a network location or paste in a path. Can you guys change that to an interface that allows us to go to non-mapped locations where we can paste in a file path? I've included the current interface as well as an example of one that could solve this problem. Please let me know what you think. Will this solution solve our problem?
Seaweed
(AKA Steve Cook, Stantec)
Hi Steve!
I'll have to discuss this with Jeremiah and get back to you with the optimal solution.
Thanks,
I'll have to discuss this with Jeremiah and get back to you with the optimal solution.
Thanks,
Steve,
The root of the issue here, is that the path to the Detail Library is saved with the Installation, in the install.xml file located in the Landfx folder.
This could conceivably be moved into the Preferences, so that a different Preference Set could access a different detail library.
However I feel this would cause way more harm than good.
To address the first point you raise -- the browse dialog box for setting a detail folder does indeed include the Network item, so you are welcome to browse to a network path.
However, this would be highly discouraged, as of course it will change the detail library for the entire installation.
Instead, why not just embrace the flexibility that mapped drives offer?
In this case, all you would need to do is to decide on an appropriate drive letter that will work. You already have your Landfx folder located on the L drive, so let's say you have the X drive available, and that will be set to your Detail Library.
All offices could then map the X drive to their L:/Landfx/Details location, allowing this to be set at all locations.
And then when you need to work on say a Sacramento project, all you would need to do is to remap that X drive on just your machine, to \\Sacramento\L\Landfx\Details.
Hence the beauty of mapped drive letters!
--J
The root of the issue here, is that the path to the Detail Library is saved with the Installation, in the install.xml file located in the Landfx folder.
This could conceivably be moved into the Preferences, so that a different Preference Set could access a different detail library.
However I feel this would cause way more harm than good.
To address the first point you raise -- the browse dialog box for setting a detail folder does indeed include the Network item, so you are welcome to browse to a network path.
However, this would be highly discouraged, as of course it will change the detail library for the entire installation.
Instead, why not just embrace the flexibility that mapped drives offer?
In this case, all you would need to do is to decide on an appropriate drive letter that will work. You already have your Landfx folder located on the L drive, so let's say you have the X drive available, and that will be set to your Detail Library.
All offices could then map the X drive to their L:/Landfx/Details location, allowing this to be set at all locations.
And then when you need to work on say a Sacramento project, all you would need to do is to remap that X drive on just your machine, to \\Sacramento\L\Landfx\Details.
Hence the beauty of mapped drive letters!
--J
Hi Jer,
Welcome back (assuming that you're back). With the Stantec file standards (MEDAD) certain drives are assigned, others are not. Since the "L" was available we used it and have been advising others to use it too. But since it's an available drive, sometimes the local offices have already used it. I was asked to help another office install LandFX for them. See the response to me suggesting using a particular drive for mapping and you will see the difficulty with "Embracing" the magic of mapping drives:
___This is an excerpt from a message and response that I recieved today:
For instance, if we’re helping your office, or vice versa our LandFX will look for the folders in the correct place. Currently the correct place is L:\landfx, but V:\landfx will be fine too. Just realize that if you place it anywhere but the L:\landfx folder, you will be locking yourself out of being able to effectively work with other offices using LandFX. When we get into discussions about drives, it can be a complex discussion and if that’s necessary, I’ll have that discussion, but it will be over the phone with Adrian if it comes to that. If you load it on the root of a mapped L drive, there’s no discussion necessary and you’ll be like the vast majority of Stantec offices that are using LandFX.
Soon enough this will be a moot point because the LandFX folder will be on a shared OneDrive. There are discussions about this now, but our office won’t be beta testing this until late this year when Stantec’s shared OneDrive folders are rolled out.
Local IT's response: -----
– Our L: drive is confirmed as our archive storage in the Laurel office, and we are not willing to change this drive letter for one piece of software. We should implement one of the other available drive letters that are not part of the MEDAD standard. My understanding is there will be little collaboration with the use of LandFX outside of the Laurel site as far as sharing data, so there is no need for us to make significant changes to 100+ people’s login script in order to comply with one person’s request.
______
LandFX is forward thinking and understands that collaboration is a key for successful projects. LandFX is also not focused purely on the mom & pop boutique design firms. After all, Disney and Stantec were the first two licenses issued. Large forms like ours see the value of this software and as more offices purchase the software, ensuring ease of collaboration is presumably one of LandFX's main goals. Soon we will have shared OneDrives available to us (beta testing later this year). I see various offices, BC's Regions, etc.locating shared detail folders on these off-site storage facilities. I can see a OneDrive being dedicated to Agency Details only. They will have different paths and since we are a global firm embracing interoffice collaboration we will need to be accessing these various drive locations and they will need to be variable in nature, but will be tied to the various projects (not based on installs at all). This is why we, and other firms that want to collaborate, will need the flexibility to tie detail folders to individual projects, not the installation process of a given workstation. Am I correct?
I hope that very soon we will have the detail library tied to our preference set, just like the other variables that we tie to our projects so that we can work around the globe and the drawings look like they're created from the local region.
Its a brave new world! I'm confident that LandFX will continue to lead in this global environment by solving complex issues like this. Their software will lead all others, not because of completion, because there isn't any. But because the people that make up LandFX are truly interested in making their own software better every single day. They evaluate and respond to each and every concept offered by others (this community board is proof), making sure that every customer, whether from a large or small firm, knows that they are important. LandFX has an abundance of goodwill built up due to their own efforts. We don't just love the product because what it does for us, it's also the security of knowing that you really care. The team at LandFX (I call you wizards) shows this to us all the time. That's why when you and Dave (your dad) created this software so many years ago, I knew it would be the product leader that it is and will be in the future.
Please reconsider allowing the detail folder(s) to be tied to the project's preferences (not the install). And if you still believe that it "would cause way more harm than good" then I'll be okay with that. It wont the the first time, nor the last time that I trust you and your view turned out to the best alternative.
Maybe you can recommend a work-around for us that allows the various offices to access details from another server without remapping (or mapping) the folders.
Keep up the great work!
Seaweed
(AKA Steve Cook)
Welcome back (assuming that you're back). With the Stantec file standards (MEDAD) certain drives are assigned, others are not. Since the "L" was available we used it and have been advising others to use it too. But since it's an available drive, sometimes the local offices have already used it. I was asked to help another office install LandFX for them. See the response to me suggesting using a particular drive for mapping and you will see the difficulty with "Embracing" the magic of mapping drives:
___This is an excerpt from a message and response that I recieved today:
For instance, if we’re helping your office, or vice versa our LandFX will look for the folders in the correct place. Currently the correct place is L:\landfx, but V:\landfx will be fine too. Just realize that if you place it anywhere but the L:\landfx folder, you will be locking yourself out of being able to effectively work with other offices using LandFX. When we get into discussions about drives, it can be a complex discussion and if that’s necessary, I’ll have that discussion, but it will be over the phone with Adrian if it comes to that. If you load it on the root of a mapped L drive, there’s no discussion necessary and you’ll be like the vast majority of Stantec offices that are using LandFX.
Soon enough this will be a moot point because the LandFX folder will be on a shared OneDrive. There are discussions about this now, but our office won’t be beta testing this until late this year when Stantec’s shared OneDrive folders are rolled out.
Local IT's response: -----
– Our L: drive is confirmed as our archive storage in the Laurel office, and we are not willing to change this drive letter for one piece of software. We should implement one of the other available drive letters that are not part of the MEDAD standard. My understanding is there will be little collaboration with the use of LandFX outside of the Laurel site as far as sharing data, so there is no need for us to make significant changes to 100+ people’s login script in order to comply with one person’s request.
______
LandFX is forward thinking and understands that collaboration is a key for successful projects. LandFX is also not focused purely on the mom & pop boutique design firms. After all, Disney and Stantec were the first two licenses issued. Large forms like ours see the value of this software and as more offices purchase the software, ensuring ease of collaboration is presumably one of LandFX's main goals. Soon we will have shared OneDrives available to us (beta testing later this year). I see various offices, BC's Regions, etc.locating shared detail folders on these off-site storage facilities. I can see a OneDrive being dedicated to Agency Details only. They will have different paths and since we are a global firm embracing interoffice collaboration we will need to be accessing these various drive locations and they will need to be variable in nature, but will be tied to the various projects (not based on installs at all). This is why we, and other firms that want to collaborate, will need the flexibility to tie detail folders to individual projects, not the installation process of a given workstation. Am I correct?
I hope that very soon we will have the detail library tied to our preference set, just like the other variables that we tie to our projects so that we can work around the globe and the drawings look like they're created from the local region.
Its a brave new world! I'm confident that LandFX will continue to lead in this global environment by solving complex issues like this. Their software will lead all others, not because of completion, because there isn't any. But because the people that make up LandFX are truly interested in making their own software better every single day. They evaluate and respond to each and every concept offered by others (this community board is proof), making sure that every customer, whether from a large or small firm, knows that they are important. LandFX has an abundance of goodwill built up due to their own efforts. We don't just love the product because what it does for us, it's also the security of knowing that you really care. The team at LandFX (I call you wizards) shows this to us all the time. That's why when you and Dave (your dad) created this software so many years ago, I knew it would be the product leader that it is and will be in the future.
Please reconsider allowing the detail folder(s) to be tied to the project's preferences (not the install). And if you still believe that it "would cause way more harm than good" then I'll be okay with that. It wont the the first time, nor the last time that I trust you and your view turned out to the best alternative.
Maybe you can recommend a work-around for us that allows the various offices to access details from another server without remapping (or mapping) the folders.
Keep up the great work!
Seaweed
(AKA Steve Cook)
Steve,
There is no reason that either the Landfx folder or the Detail Library require exclusive use of a drive letter.
So it should be well within the realm of possible to come up with something that works.
We are just talking about looking at drive letters, and possibly mapping an additional one, but probably just strategic use of existing ones.
Any changes to the software, to move the detail library setting from installation to preferences, is going to take a bit of time. So the drive mapping is just a bit of a workaround solution, so that you can ramp up this multi-office solution as soon as possible.
--J
There is no reason that either the Landfx folder or the Detail Library require exclusive use of a drive letter.
So it should be well within the realm of possible to come up with something that works.
We are just talking about looking at drive letters, and possibly mapping an additional one, but probably just strategic use of existing ones.
Any changes to the software, to move the detail library setting from installation to preferences, is going to take a bit of time. So the drive mapping is just a bit of a workaround solution, so that you can ramp up this multi-office solution as soon as possible.
--J
Jer,
I'm sorry. If you described a work-around, I missed it.Here's a simplified version the situation as I see it:
1. Four separate server installs (there's obviously so many more but for now lets just say four).
2. Four separate Preferences (again, we have more than that, but for now lets just say four).
3. Many people in the various server installs working on different projects and using different preference sets.
4. A designer (or designers) in one office are helping with a project that is lead in another office (separate server install).
5. They are sharing the same project database (same MySQL instance) and same preference set.
How can they have their desktops point to the other detail folder (on the other server install) without affecting the other designers in the office that are pointing to their local detail library?
Thanks in advance.
Seaweed
I'm sorry. If you described a work-around, I missed it.Here's a simplified version the situation as I see it:
1. Four separate server installs (there's obviously so many more but for now lets just say four).
2. Four separate Preferences (again, we have more than that, but for now lets just say four).
3. Many people in the various server installs working on different projects and using different preference sets.
4. A designer (or designers) in one office are helping with a project that is lead in another office (separate server install).
5. They are sharing the same project database (same MySQL instance) and same preference set.
How can they have their desktops point to the other detail folder (on the other server install) without affecting the other designers in the office that are pointing to their local detail library?
Thanks in advance.
Seaweed
Steve,
The easiest method would be to set the location to your local detail library to a new drive letter, let's say X.
So that way, when users are working on a typical project, X resolves to their local server, and all is fine.
But user Seaweed needs to work on a project for another office, so he remaps his X drive, to now point to the detail folder at office B.
He should be able to disconnect that drive and remap it to something other than his login script.
--J
The easiest method would be to set the location to your local detail library to a new drive letter, let's say X.
So that way, when users are working on a typical project, X resolves to their local server, and all is fine.
But user Seaweed needs to work on a project for another office, so he remaps his X drive, to now point to the detail folder at office B.
He should be able to disconnect that drive and remap it to something other than his login script.
--J
Jer,
Okay. Now I feel like a numb nut in front of the entire LandFX Community. I still don't see the work-around. Currently Seaweed is pointing to the L: drive for LandFX and a host of other settings in the AutoCAD options as well as a host of other landscape related material that he needs access to during the design process. His details are also on the L: drive (L:\LANDFX\DETAILS). If Seaweed remaps his L: drive, all of his other AutoCAD options, and other files located on to the L: drive will be lost. Right? (I mean, I know that they're not lost, just not located on the mapped L drive. You don't see this as an issue?
Also, How deceiving is it to be in the Preferences>Details and have a location that shows the "Detail Library". It even has a user input button that the user can click on and navigate around the server on. It just won't save the location. It's almost like LandFX had the visioning to allow the user to set this in the preference set, and got so close, but then they had to leave it to make it to the next ASLA show and forgot where they were when thy got back. Right?
I believe that the logical way to have this work is to allow the details library be set with the Preference Set.
Oh and the button that will allow the user to navigate to VARIABLE location (not copying all of the files to a new location) will be a post Windows 7 dialog box. One which allows the user to not just navigate, but also cut and past the UNC. See the two examples. One is the pre-Win7 dialog box and the other is the newer box which does the same thin, only better. I've attached screen shots of both of them. If nothing else, the current dialog box is a testament to how long they've been in business. That's just an outdated user interface.
Please reconsider allowing detail folders to be tied to individual preference sets. Sure the default can be install server, but allow us users to determine how best to collaborate with different offices. I can see the problem and suggest a solution, but you are so forward thinking that I know you will come up with a flexible solution.
Sleep on it. I'll look for a response, or a phone call tomorrow. You've got my number.
Seaweed
Okay. Now I feel like a numb nut in front of the entire LandFX Community. I still don't see the work-around. Currently Seaweed is pointing to the L: drive for LandFX and a host of other settings in the AutoCAD options as well as a host of other landscape related material that he needs access to during the design process. His details are also on the L: drive (L:\LANDFX\DETAILS). If Seaweed remaps his L: drive, all of his other AutoCAD options, and other files located on to the L: drive will be lost. Right? (I mean, I know that they're not lost, just not located on the mapped L drive. You don't see this as an issue?
Also, How deceiving is it to be in the Preferences>Details and have a location that shows the "Detail Library". It even has a user input button that the user can click on and navigate around the server on. It just won't save the location. It's almost like LandFX had the visioning to allow the user to set this in the preference set, and got so close, but then they had to leave it to make it to the next ASLA show and forgot where they were when thy got back. Right?
I believe that the logical way to have this work is to allow the details library be set with the Preference Set.
Oh and the button that will allow the user to navigate to VARIABLE location (not copying all of the files to a new location) will be a post Windows 7 dialog box. One which allows the user to not just navigate, but also cut and past the UNC. See the two examples. One is the pre-Win7 dialog box and the other is the newer box which does the same thin, only better. I've attached screen shots of both of them. If nothing else, the current dialog box is a testament to how long they've been in business. That's just an outdated user interface.
Please reconsider allowing detail folders to be tied to individual preference sets. Sure the default can be install server, but allow us users to determine how best to collaborate with different offices. I can see the problem and suggest a solution, but you are so forward thinking that I know you will come up with a flexible solution.
Sleep on it. I'll look for a response, or a phone call tomorrow. You've got my number.
Seaweed
I'm in no way saying it's not a good idea to put a checkbox near the Detail Library setting, or even just a Yes/No after editing, asking if it should apply to all preference sets or just this one -- I agree that there should be some way of setting it at the PrefSet level.
What I am saying is, we aren't going to make that change for a minimum of about 3 months, probably more.
So in that meantime, it is easily addressed by mapping drive letters.
You would keep your L drive exactly the same. You would only remap your *Detail* library. Then, there in Preferences, all 4 office installations I would imagine, would set their Detail Library location to X:. The users in Sacramento, would have X mapped as \\Sacramento\Landfx\Details, your users would have it going to \\Irvine\Landfx\Details, and so on.
Then you could toggle your X drive, to instead look to a different server, which would then affect only the detail library.
Easy, right?
I'm still not grasping the inability to change the detail library location -- I am able to click the little button there, go to Network, and set it to any network path.
--J
What I am saying is, we aren't going to make that change for a minimum of about 3 months, probably more.
So in that meantime, it is easily addressed by mapping drive letters.
You would keep your L drive exactly the same. You would only remap your *Detail* library. Then, there in Preferences, all 4 office installations I would imagine, would set their Detail Library location to X:. The users in Sacramento, would have X mapped as \\Sacramento\Landfx\Details, your users would have it going to \\Irvine\Landfx\Details, and so on.
Then you could toggle your X drive, to instead look to a different server, which would then affect only the detail library.
Easy, right?
I'm still not grasping the inability to change the detail library location -- I am able to click the little button there, go to Network, and set it to any network path.
--J
Pre-Win7 the windows file explorer used to navigate to our Global Network. The way that they have it set up now it only goes to our local network. However, we have a tool that will allow us to navigate to our global network.That tool also allows us to map their drives. If I could cut and paste a UNC into the interface (like any new "Save As" or "Insert" dialog box does) it should be fine. But now, I can't past anything. Plus, I wouldn't want to now because it's not set to a preference set and wouldn't want ot copy all of my details to that new location.
I now understand your idea as to how best map to a completely different drive. I think that this will work for our small little four office group (our BC), but when we help the others, the chances of having a drive available to both groups could be more difficult.
As far as waiting for "three months, probably more" for this to happen is not a problem. How long would I wait for a change like this from AutoCAD (or any other software developer for that matter). Forget it. We wouldn't even be having this conversation. Good things are sometimes worth waiting for. And so far all of your good things have been worth it!
Thanks for your valuable input.
Seaweed
I now understand your idea as to how best map to a completely different drive. I think that this will work for our small little four office group (our BC), but when we help the others, the chances of having a drive available to both groups could be more difficult.
As far as waiting for "three months, probably more" for this to happen is not a problem. How long would I wait for a change like this from AutoCAD (or any other software developer for that matter). Forget it. We wouldn't even be having this conversation. Good things are sometimes worth waiting for. And so far all of your good things have been worth it!
Thanks for your valuable input.
Seaweed
There are no comments made for this post yet
Okay Jer, I agreed to not bring this up again until mid-November. It's into December so I feel safe in asking where we are on this. I do understand that it may take a lot of code rewriting but we could sure use it now. We have two large college campuses (campi?) that we're beginning work on now. The details and detail templates are coming from various offices for each specific project. Our login includes mapping of our local drives. We've been using the work-around for quite a few months now and it may seem easy for a person like you; however, manually remapping to a separate server's folder for each individual project introduces the human error variable. Plus, if a worker is engaged on two separate projects, pointing to details (and detail templates) on two or more separate servers, it can really take some time and hampers the design flow.
Please do not mention standardizing. when a company grows through acquisitions as we have (and will continue to do as you are aware through noticing all of the license transfers from MWH & RHL, etc.). Of course we all want to standardize, but can you imagine the undertaking? Have you ever been part of a CAD standards group? Even standardizing a single office is a task.
So thank you in advance for your efforts to make our lives easier and more productive while reducing the chance of human error.
When do you think that we will have the details, and detail templates tied to the project preference set rather than the office install?
Seaweed
Please do not mention standardizing. when a company grows through acquisitions as we have (and will continue to do as you are aware through noticing all of the license transfers from MWH & RHL, etc.). Of course we all want to standardize, but can you imagine the undertaking? Have you ever been part of a CAD standards group? Even standardizing a single office is a task.
So thank you in advance for your efforts to make our lives easier and more productive while reducing the chance of human error.
When do you think that we will have the details, and detail templates tied to the project preference set rather than the office install?
Seaweed
What about our preferences pointing to a URL. For instance a OneDrive?
Again, the important thing is that they are NOT tied to lettered drives and that they be tied to project preferences.
Again, the important thing is that they are NOT tied to lettered drives and that they be tied to project preferences.
As we have discussed, it's a fairly minor change -- just adding a checkbox to the Detail Preferences dialog, to allow the Library setting to be saved with the Preferences.
I do agree it is a good option to have.
It can easily happen in early 2018.
--J
I do agree it is a good option to have.
It can easily happen in early 2018.
--J
Will we be able to cut-n-paste URL's in? We can't (or don't know how to) map the shared OneDrives to a letter.
That is something we should do a remote session for, I just don't get why your OneDrives are not visible from the network explorer.
It might become a project for your incredibly capable and competent IT to address.
--J
It might become a project for your incredibly capable and competent IT to address.
--J
- Page :
- 1
There are no replies made for this post yet.
Contact
- Land F/X
Our software tailors AutoCAD® to the needs of landscape architects, irrigation designers, and other professionals. We automate your most tedious tasks and ensure accuracy, giving you more time to design.