Log message #895494

# At Username Text
# Jul 17th 2009, 09:20 ProLoser|Work why maintain? cuz of the test-cases?
# Jul 17th 2009, 09:20 markstory and makes it easier for me to maintain.
# Jul 17th 2009, 09:20 markstory well it makes the code easier for other to get and use.
# Jul 17th 2009, 09:20 ProLoser|Work what was the reason you put your helpers in plugins?
# Jul 17th 2009, 09:19 markstory instead of download tar, sprinkle files.
# Jul 17th 2009, 09:19 ProLoser|Work is that why your helpers are in plugins?
# Jul 17th 2009, 09:19 markstory they have test cases too, so it makes it easier to send out.
# Jul 17th 2009, 09:19 techno-geek According to psuedocoder any code you contribute should be packaged as a plugin with test cases
# Jul 17th 2009, 09:19 markstory I dunno, I have single helpers in plugins.
# Jul 17th 2009, 09:19 ProLoser|Work i didn't think it was necessary to put every component/helper/behavior into a plugin
# Jul 17th 2009, 09:18 ProLoser|Work markstory: well it's been a question we've been wondering about, should we go about bundling all our parts as a plugin?
# Jul 17th 2009, 09:18 ProLoser|Work i'll have to go learn how to do em though
# Jul 17th 2009, 09:18 markstory its 2 dirs
# Jul 17th 2009, 09:18 markstory why not.
# Jul 17th 2009, 09:18 ProLoser|Work test-cases obviously
# Jul 17th 2009, 09:18 ProLoser|Work well i mean the plugin part
# Jul 17th 2009, 09:18 markstory test cases are good.
# Jul 17th 2009, 09:18 techno-geek yeah, why not?
# Jul 17th 2009, 09:17 ProLoser|Work for this component alone?
# Jul 17th 2009, 09:17 techno-geek ProLoser|Work, yeah I agree. I also want to try to convince you to package it as a plugin, write test cases, and also include a simple helper
# Jul 17th 2009, 09:16 ProLoser|Work i know there are a few no-no's i did on some of my code
# Jul 17th 2009, 09:16 ProLoser|Work techno-geek: i think if we want to submit our code or get it officially accepted we should try and revise it to fit the coding standards
# Jul 17th 2009, 08:23 ADmad candybar: http://thechaw.com/bakery/source/branches/usersplugin/plugins/users/config/permissions.php.example#highlight
# Jul 17th 2009, 08:20 ADmad candybar: support or discussion
# Jul 17th 2009, 08:19 candybar i'm not asking for support :/
# Jul 17th 2009, 08:19 ADmad candybar: if you have issues post a ticket
# Jul 17th 2009, 08:19 ADmad candybar: i just cant drop everything and give you support..
# Jul 17th 2009, 08:19 ADmad candybar: i am listening to you
# Jul 17th 2009, 08:18 candybar fine don't listen to me
# Jul 17th 2009, 08:18 ADmad candybar: like i said check the code here http://thechaw.com/bakery/source/branches/usersplugin the persmissions strucutre is already implemented based on that wiki page
# Jul 17th 2009, 07:47 markstory yeah that's all a side effect of removing all the interactive flags. and just using the property.
# Jul 17th 2009, 07:43 alkemann like belongsTo Users.User instead of User
# Jul 17th 2009, 07:43 alkemann i like that it doesnt ask for overwrite, except for model. it needs to ask about overwriting model, since u have to specify association stuff sometimes and rebake
# Jul 17th 2009, 07:42 alkemann ah ok. got it to work
# Jul 17th 2009, 07:41 markstory so more dirs were added.
# Jul 17th 2009, 07:41 markstory because all output from bake is done with templates now, so you can override how all output is generated.
# Jul 17th 2009, 07:41 markstory yeah it treats the dirs in templates as 'themes'
# Jul 17th 2009, 07:41 markstory vendors/shells/templates/{themename}/views|classes|actions
# Jul 17th 2009, 07:41 markstory but its vendors/shells/templates/{themename}/view|classes|actions
# Jul 17th 2009, 07:41 alkemann markstory: it asked for default or views. i selected views, but i got default
# Jul 17th 2009, 07:40 markstory (