Log message #901639

# At Username Text
# Jul 20th 2009, 15:41 ProLoser|Work did you guys read my ticket about the repo viewer?
# Jul 20th 2009, 15:40 alkemann author is awol for a time, another person has been updating his fork, others have started requesting commits to this version. at some point it should become the new main code for the article
# Jul 20th 2009, 15:40 ADmad s/could/cause
# Jul 20th 2009, 15:40 ADmad agre.. but this would be after the intial release right.. could it would take quite some time to develop all that shit
# Jul 20th 2009, 15:40 ProLoser|Work wait do you mean a local repo
# Jul 20th 2009, 15:40 ProLoser|Work i thought you guys didn't like that
# Jul 20th 2009, 15:40 alkemann and create forks, branches, patches
# Jul 20th 2009, 15:39 ProLoser|Work ... i was talking about that
# Jul 20th 2009, 15:39 alkemann so people can update easily
# Jul 20th 2009, 15:39 alkemann i think we really need to have all shared code (not code exmaples) in a repo thing
# Jul 20th 2009, 15:39 ADmad i didnt know that part.. then it sounds good
# Jul 20th 2009, 15:38 ProLoser|Work you guys think there should be a master?
# Jul 20th 2009, 15:38 alkemann sure, but code commits would be against branches or forks, the master would merge into the master head
# Jul 20th 2009, 15:38 ADmad yeah that was my understanding too
# Jul 20th 2009, 15:38 alkemann we had some brainstorms in berlin about how to make it a more community tool and one of the ideas i like is that if an author dissapears or wants to give it up, there is a vote or the guy with the most accepted commits becomes the new master
# Jul 20th 2009, 15:37 ADmad alkemann: if you wikify cant anybody make updates ?
# Jul 20th 2009, 15:37 ProLoser|Work with moderation, is that a bad thing?
# Jul 20th 2009, 15:36 alkemann how so?
# Jul 20th 2009, 15:36 ADmad but on the downside you would lose control over your code..
# Jul 20th 2009, 15:35 ADmad yeah the author shouldnt be doged all the time for sharing..
# Jul 20th 2009, 15:33 alkemann http://bakery.cakephp.org/leafs/view/72#comment-3880 - im looking forward to the wikify - make community project part of bakery 2.0 , i dont really feel like continuing to support this
# Jul 20th 2009, 15:33 ADmad with my bitching surely
# Jul 20th 2009, 15:33 alkemann but will i remember tomorrow?
# Jul 20th 2009, 15:32 ADmad what for.. you already know :)
# Jul 20th 2009, 15:32 alkemann post a ticket on my google code :P
# Jul 20th 2009, 15:32 ADmad kiddin :)
# Jul 20th 2009, 15:31 ADmad screw them..
# Jul 20th 2009, 15:30 alkemann but then i think i will leave my code in for backwards compability for now. as there are enough people out there using it, but it would be more effective to ignore the setting and set 'enabled' false
# Jul 20th 2009, 15:29 ADmad there must an eg
# Jul 20th 2009, 15:29 alkemann ok
# Jul 20th 2009, 15:29 ADmad check the test cases
# Jul 20th 2009, 15:28 ADmad https://trac.cakephp.org/browser/branches/1.2.x.x/cake/libs/model/behavior.php#L330
# Jul 20th 2009, 15:28 ADmad as i said you set 'enabled'=>false in config array of actsAs.. it has same effect as calling disable()
# Jul 20th 2009, 15:27 alkemann but where to place that disable() if u want it always?
# Jul 20th 2009, 15:27 ADmad atleast i think so
# Jul 20th 2009, 15:27 ADmad actually yes.. instead of your usage of 'auto' everything can be achieved with enable()/disable()
# Jul 20th 2009, 15:26 ADmad not exactly.. the BehaviorCollection::attach checks if 'enabled' key is false and disables the behavior.. dont think it has any relation with 'enabled' member var of a behavior
# Jul 20th 2009, 15:26 alkemann or are you saying that somehow that would have the same effect?
# Jul 20th 2009, 15:24 alkemann so just a name change?
# Jul 20th 2009, 15:24 ADmad so 'enabled' => false in config array
# Jul 20th 2009, 15:22 alkemann makes more sense to me to disable automatic behavior in the actsAs than to implement model constructor to disable it