WA_ infront of the foldername

Hi,

when will the WA_ be put infront of the foldername? Why was that changed? All extension got that WA_ why not that one?

Thanks
Denis

I am moving this request to the wishlist forum. I cannot say when or if that will be added back.

It was an engineering decision to remove it, I do not know the reason.

I'll agree that some standards need to be kept for organization. I've been advocating that all extensions bet placed into an "includes" folder or even a "wa_includes" since "includes" could interfere with other programs and scripts.

I don't like having all these extra folders dropped in the root of my website(s), but at least when "wa_" was at the start they were all lumped together. Now they are starting to drop randomly throughout my root folders, some starting with "wa_", some with "css_" and some just by name.

Please create a standard approach and stick to it, preferably my approach - in a "wa_includes" folder :)

/wa_includes/htmleditor
/wa_includes/dynamicwebcharts
/wa_includes/ecart
etc.. etc.. etc...

My second choice would be in agreement with "Cologne" - put back the wa_ in front of all, so we know at a glance it's a WA Generated Folder.

Originally Said By: Jason Byrnes

  I am moving this request to the wishlist forum. I cannot say when or if that will be added back.

It was an engineering decision to remove it, I do not know the reason.  

Does enginerring build sites, or the tools that make the sites?
Pilots don't build airplanes, but they know what needs to be where. Heaven forbid should "engineering" move a rudder pedal :)

Hi Jason (and others),

The issue of folder names/locations is a biggie to me. I created a thread on this a while back but unfortunately didnt get a response from WA:

showthread.php?t=5092

My instinct is that adding the functionality to let us specify the location of the WA extension files wouldnt be too big a job (though I could of course be wrong), and it would solve an issue that is potentially harmful to the image of us developers who share projects.

Could you give an indication of how likely this functionality is to be considered?

Thanks!

I have been considering the request and have given it quite a bit of thought.

Some people used to complain that they don't like seeing "WA_" in front of the folder names, so we stopped doing that, which lead to people complaining that they did like "WA_" in front of the names, so we didn't follow through and remove it from all of them. Which lead us to the inconsistancy you point out where some do and some don't now.

Letting each user set their own would be possible, but would hurt the portability, if you were to build a site with your structure and send it to someone with another it wouldn't behave properly, or you might end up with multiple folders.

Maybe the best solution would be to always use a root "WebAssist" folder and add subfolders under that. That seems to fix the clutter problem some have complained about, but I'm afraid there are too many drawbacks to actually allowing a user to specify their own directory when it comes to portability.

We will have to update it one extension at a time and in major releases since there will be a lot of testing involved, but I will certainly keep it in mind as we move forward.

Hi Ray,

Thanks for the response on this one. I appreciate the mammoth testing of all extensions needed if you start altering folder names, so I'm sure nobody expects instant changes.

The suggestion of having all extension folders under one main web assist folder (ideally '/wa/') would be pretty perfect. If this can be phased in, I for one would be MASSIVELY appreciative!

Fingers crossed.

I for two, would love this as well. I'm a neat freak!!!

jc

Hi

I too support the idea of a '/wa/' folder to house all WA scripts.

Alistair