How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread psybear83
Hey everybody

I wonder how to structure my shared components, behaviors, plugins
etc. in my Subversion repository? I include them as externals in many
different projects, and because I can't point to single files as
externals (but only to directories) I can't simply use a structure
like

- components/
- behaviors/
- plugins/

etc. So at the moment my repository is cluttered up with folders and
subfolders but misses a clean structure... Are there any rules of
thumb or best practices on how to structure it? How do you guys do
it?

Thanks a lot for help
Josh

Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en


Re: How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread AD7six


On Jan 4, 12:33 pm, psybear83 psybea...@gmail.com wrote:
 Hey everybody

 I wonder how to structure my shared components, behaviors, plugins
 etc. in my Subversion repository? I include them as externals in many
 different projects, and because I can't point to single files as
 externals (but only to directories) I can't simply use a structure
 like

 - components/
 - behaviors/
 - plugins/

 etc. So at the moment my repository is cluttered up with folders and
 subfolders but misses a clean structure... Are there any rules of
 thumb or best practices on how to structure it? How do you guys do
 it?

use plugins.

AD

Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en


Re: How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread Joshua Muheim
Short answer! I will look into it. Thanks. :-)

On Tue, Jan 4, 2011 at 1:12 PM, AD7six andydawso...@gmail.com wrote:


 On Jan 4, 12:33 pm, psybear83 psybea...@gmail.com wrote:
 Hey everybody

 I wonder how to structure my shared components, behaviors, plugins
 etc. in my Subversion repository? I include them as externals in many
 different projects, and because I can't point to single files as
 externals (but only to directories) I can't simply use a structure
 like

 - components/
 - behaviors/
 - plugins/

 etc. So at the moment my repository is cluttered up with folders and
 subfolders but misses a clean structure... Are there any rules of
 thumb or best practices on how to structure it? How do you guys do
 it?

 use plugins.

 AD

 Check out the new CakePHP Questions site http://cakeqs.org and help others 
 with their CakePHP related questions.

 You received this message because you are subscribed to the Google Groups 
 CakePHP group.
 To post to this group, send email to cake-php@googlegroups.com
 To unsubscribe from this group, send email to
 cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
 http://groups.google.com/group/cake-php?hl=en


Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en


Re: How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread euromark
yep,
i use a tools plugin containing all those files
one svn:external for all :)

On 4 Jan., 13:24, Joshua Muheim psybea...@gmail.com wrote:
 Short answer! I will look into it. Thanks. :-)







 On Tue, Jan 4, 2011 at 1:12 PM, AD7six andydawso...@gmail.com wrote:

  On Jan 4, 12:33 pm, psybear83 psybea...@gmail.com wrote:
  Hey everybody

  I wonder how to structure my shared components, behaviors, plugins
  etc. in my Subversion repository? I include them as externals in many
  different projects, and because I can't point to single files as
  externals (but only to directories) I can't simply use a structure
  like

  - components/
  - behaviors/
  - plugins/

  etc. So at the moment my repository is cluttered up with folders and
  subfolders but misses a clean structure... Are there any rules of
  thumb or best practices on how to structure it? How do you guys do
  it?

  use plugins.

  AD

  Check out the new CakePHP Questions sitehttp://cakeqs.organd help others 
  with their CakePHP related questions.

  You received this message because you are subscribed to the Google Groups 
  CakePHP group.
  To post to this group, send email to cake-php@googlegroups.com
  To unsubscribe from this group, send email to
  cake-php+unsubscr...@googlegroups.com For more options, visit this group 
  athttp://groups.google.com/group/cake-php?hl=en

Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en


Re: How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread Joshua Muheim
@Mark: this does seem very pragmatic. But what if you want to provide
your stuff to others so that they can use different parts of your
tools and don't want to include everything into your project? But
certain parts are depending on each other, so you can't just provide a
download to every single file?

Maybe soft links are the solution? Can SVN/GIT manage something like that?

On Tue, Jan 4, 2011 at 4:14 PM, euromark dereurom...@googlemail.com wrote:
 yep,
 i use a tools plugin containing all those files
 one svn:external for all :)

 On 4 Jan., 13:24, Joshua Muheim psybea...@gmail.com wrote:
 Short answer! I will look into it. Thanks. :-)







 On Tue, Jan 4, 2011 at 1:12 PM, AD7six andydawso...@gmail.com wrote:

  On Jan 4, 12:33 pm, psybear83 psybea...@gmail.com wrote:
  Hey everybody

  I wonder how to structure my shared components, behaviors, plugins
  etc. in my Subversion repository? I include them as externals in many
  different projects, and because I can't point to single files as
  externals (but only to directories) I can't simply use a structure
  like

  - components/
  - behaviors/
  - plugins/

  etc. So at the moment my repository is cluttered up with folders and
  subfolders but misses a clean structure... Are there any rules of
  thumb or best practices on how to structure it? How do you guys do
  it?

  use plugins.

  AD

  Check out the new CakePHP Questions sitehttp://cakeqs.organd help others 
  with their CakePHP related questions.

  You received this message because you are subscribed to the Google Groups 
  CakePHP group.
  To post to this group, send email to cake-php@googlegroups.com
  To unsubscribe from this group, send email to
  cake-php+unsubscr...@googlegroups.com For more options, visit this group 
  athttp://groups.google.com/group/cake-php?hl=en

 Check out the new CakePHP Questions site http://cakeqs.org and help others 
 with their CakePHP related questions.

 You received this message because you are subscribed to the Google Groups 
 CakePHP group.
 To post to this group, send email to cake-php@googlegroups.com
 To unsubscribe from this group, send email to
 cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
 http://groups.google.com/group/cake-php?hl=en


Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en


Re: How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread Miles J
@Joshua - Yes but if you put everything into a single plugin, then the
problem is solved. You are *not* including all those files in the app,
you are just making them available. They are included once you add
them to the $helpers, $components array, etc. A great example is the
CakeDC utils plugin: https://github.com/CakeDC/utils

On Jan 4, 7:42 am, Joshua Muheim psybea...@gmail.com wrote:
 @Mark: this does seem very pragmatic. But what if you want to provide
 your stuff to others so that they can use different parts of your
 tools and don't want to include everything into your project? But
 certain parts are depending on each other, so you can't just provide a
 download to every single file?

 Maybe soft links are the solution? Can SVN/GIT manage something like that?

 On Tue, Jan 4, 2011 at 4:14 PM, euromark dereurom...@googlemail.com wrote:
  yep,
  i use a tools plugin containing all those files
  one svn:external for all :)

  On 4 Jan., 13:24, Joshua Muheim psybea...@gmail.com wrote:
  Short answer! I will look into it. Thanks. :-)

  On Tue, Jan 4, 2011 at 1:12 PM, AD7six andydawso...@gmail.com wrote:

   On Jan 4, 12:33 pm, psybear83 psybea...@gmail.com wrote:
   Hey everybody

   I wonder how to structure my shared components, behaviors, plugins
   etc. in my Subversion repository? I include them as externals in many
   different projects, and because I can't point to single files as
   externals (but only to directories) I can't simply use a structure
   like

   - components/
   - behaviors/
   - plugins/

   etc. So at the moment my repository is cluttered up with folders and
   subfolders but misses a clean structure... Are there any rules of
   thumb or best practices on how to structure it? How do you guys do
   it?

   use plugins.

   AD

   Check out the new CakePHP Questions sitehttp://cakeqs.organdhelp others 
   with their CakePHP related questions.

   You received this message because you are subscribed to the Google 
   Groups CakePHP group.
   To post to this group, send email to cake-php@googlegroups.com
   To unsubscribe from this group, send email to
   cake-php+unsubscr...@googlegroups.com For more options, visit this group 
   athttp://groups.google.com/group/cake-php?hl=en

  Check out the new CakePHP Questions sitehttp://cakeqs.organd help others 
  with their CakePHP related questions.

  You received this message because you are subscribed to the Google Groups 
  CakePHP group.
  To post to this group, send email to cake-php@googlegroups.com
  To unsubscribe from this group, send email to
  cake-php+unsubscr...@googlegroups.com For more options, visit this group 
  athttp://groups.google.com/group/cake-php?hl=en

Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en


Re: How do you guys structure your shared components/behaviors/plugins repository (Subversion)? --psybear

2011-01-04 Thread Joshua Muheim
I'll take a look at that, thanks! :-)

On Tue, Jan 4, 2011 at 7:24 PM, Miles J mileswjohn...@gmail.com wrote:
 @Joshua - Yes but if you put everything into a single plugin, then the
 problem is solved. You are *not* including all those files in the app,
 you are just making them available. They are included once you add
 them to the $helpers, $components array, etc. A great example is the
 CakeDC utils plugin: https://github.com/CakeDC/utils

 On Jan 4, 7:42 am, Joshua Muheim psybea...@gmail.com wrote:
 @Mark: this does seem very pragmatic. But what if you want to provide
 your stuff to others so that they can use different parts of your
 tools and don't want to include everything into your project? But
 certain parts are depending on each other, so you can't just provide a
 download to every single file?

 Maybe soft links are the solution? Can SVN/GIT manage something like that?

 On Tue, Jan 4, 2011 at 4:14 PM, euromark dereurom...@googlemail.com wrote:
  yep,
  i use a tools plugin containing all those files
  one svn:external for all :)

  On 4 Jan., 13:24, Joshua Muheim psybea...@gmail.com wrote:
  Short answer! I will look into it. Thanks. :-)

  On Tue, Jan 4, 2011 at 1:12 PM, AD7six andydawso...@gmail.com wrote:

   On Jan 4, 12:33 pm, psybear83 psybea...@gmail.com wrote:
   Hey everybody

   I wonder how to structure my shared components, behaviors, plugins
   etc. in my Subversion repository? I include them as externals in many
   different projects, and because I can't point to single files as
   externals (but only to directories) I can't simply use a structure
   like

   - components/
   - behaviors/
   - plugins/

   etc. So at the moment my repository is cluttered up with folders and
   subfolders but misses a clean structure... Are there any rules of
   thumb or best practices on how to structure it? How do you guys do
   it?

   use plugins.

   AD

   Check out the new CakePHP Questions sitehttp://cakeqs.organdhelp others 
   with their CakePHP related questions.

   You received this message because you are subscribed to the Google 
   Groups CakePHP group.
   To post to this group, send email to cake-php@googlegroups.com
   To unsubscribe from this group, send email to
   cake-php+unsubscr...@googlegroups.com For more options, visit this 
   group athttp://groups.google.com/group/cake-php?hl=en

  Check out the new CakePHP Questions sitehttp://cakeqs.organd help others 
  with their CakePHP related questions.

  You received this message because you are subscribed to the Google Groups 
  CakePHP group.
  To post to this group, send email to cake-php@googlegroups.com
  To unsubscribe from this group, send email to
  cake-php+unsubscr...@googlegroups.com For more options, visit this group 
  athttp://groups.google.com/group/cake-php?hl=en

 Check out the new CakePHP Questions site http://cakeqs.org and help others 
 with their CakePHP related questions.

 You received this message because you are subscribed to the Google Groups 
 CakePHP group.
 To post to this group, send email to cake-php@googlegroups.com
 To unsubscribe from this group, send email to
 cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
 http://groups.google.com/group/cake-php?hl=en


Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en