Small organization 'clean-up

[Dlf]

Just a small suggestion to 'tidy' up the sources folder. The /components folders are hardly ever modified (when they are, it's for installing a compon}. But just suggesting that one 'component' folder is created and the current folders (with component in the name) be put in. It might tidy up thje /sources folder a bit,

[Mark]

+1

sources
- components
-- admin
-- init
-- location
-- public
-- ucp

would be much better

[Antony]

Rather than having folders how about a folder for each component and files with the appropriate names ie.

Components
-My Component
-- admin.php
-- init.php
-- location.php
-- public.php
-- ucp.php

Much better organised and suited to the way most people would develop a component. :)

[Millar]

I agree with you Antony. A folder for each component seems more suited.

[Dlf]

That may be nice yes, abut that'd probably would get very very messey, if one:

1. IPB does clean the soures folder (and makes a sub-folder of all the compoent folders).
2. There are alot of components right now, atlest 30 (I thuink), that'd be about 30 folders, 1 for each component, with a file in each of the defautl component folders, that's like 300 folders. Not very clean, is it?

[Brandon C]

I agree with Antony, that's a great idea, +1 :)

[Rοb]

Rather than having folders how about a folder for each component and files with the appropriate names ie.

Components

-My Component

-- admin.php

-- init.php

-- location.php

-- public.php

-- ucp.php

Much better organised and suited to the way most people would develop a component. :)

Top idea, i like it :thumbsup:

+1

[Antony]

That may be nice yes, abut that'd probably would get very very messey, if one:

1. IPB

does

clean the soures folder (and makes a sub-folder of all the compoent folders).

2. There are alot of components right now, atlest 30 (I thuink), that'd be about 30 folders, 1 for each component, with a file in each of the defautl component folders, that's like 300 folders. Not very clean, is it?

Personally, I don't find this to be a valid point. If you have 30 components installed on your board, I don't think you can expect anything to be that tidy.

Either the component directories should be within the sources directory or in a subdirectory of the sources directory called components. Of course, the legacy method can still be supported but be deprecated in 2.2 and removed in 3.0.

[Dlf]

Would you want a folder for every component? Eventually it'd probably get really large (the components folder in /sources). Maybe they could 'try' it for a version, if people do not like it, switch it to the current system.


But anyone else want the components_(something) folder to be a /sources/components folder?

[Michael]

The current implementation works fine, I see no need to change.

[Mark]

FuSoYa, 2.1 works fine, 1.3 worked fine. I see/saw no need to change. However I will be upgrading to 2.2

Do you see my point?

[Michael]

No, not really. I say again, it works fine as-is, so why bother changing it? There are bigger fish to fry.

[Antony]

Keep in mind that this would make it much easier for users to control and keep track of their own components. I think the current system, while is perfectly functional is illogical and as a better system can be written with little trouble I don't see why IPS shouldn't take the five minutes that this would need and complete it. Add another quarter of an hour on perhaps for adding a legacy mode.

[Michael]

How often do you need to look in your site's folders to control and keep track of your components? 'Cuz I never have to, and I use several component-based mods on my site. That's the beauty of components, all you have to do is upload the files and let the code worry about how to deal with those files.

Apparently I'm the only one that subscribes to the "If it ain't broke, don't fix it" world view.

[Mark]

Lots of things "ain't broke", in fact, everything in 2.1.7 besides that listed in the bug tracker, but we like to improve them and make them better.

[Antony]

How often do

you

need to look in your site's folders to control and keep track of your components? 'Cuz I never have to, and I use several component-based mods on my site. That's the beauty of components, all you have to do is upload the files and let the code worry about how to deal with those files.

Apparently I'm the only one that subscribes to the "If it ain't broke, don't fix it" world view.

I rarely ever do anything more than install a component by uploading the files via SFTP. I want to drag and drop one folder from my computer to my server. When I'm developing a component I have to create many more folders than I should need to in order to organise my files.

I subscribe to a 'world view' of 'If it is an easy and quick change to implement and makes things simpler rather than complicated, do it.'

[Dlf]

Probably (I think) would just require adding one folder, moving the folders into it, and changing the files (that require_once) the components folder to the correct, URL. That should be hard to do, if that's all that has to be done.

[Antony]

Probably (I think) would just require adding one folder, moving the folders into it, and changing the files (that require_once) the components folder to the correct, URL. That should be hard to do, if that's all that has to be done.

If a change is going to be made then it wouldn't be any more of an effort to implement my suggested change really.

[Dlf]

Yours would probably require more changing of the components system, mine is just moving folders, to organize them better, and to edit (some/the files) that require_once the component_(name) folder to the "correct" URL.