Logs for #cakephp-bakery

Page 50 of 134, showing 100 records out of 13,394 total, starting on record 4,901, ending on 5,000

# At Username Text
# Jul 20th 2009, 12:36 ProLoser|Work i suppose is where i got confused
# Jul 20th 2009, 12:35 ProLoser|Work well what's the pages controller then?
# Jul 20th 2009, 12:35 ProLoser|Work uh
# Jul 20th 2009, 12:35 markstory no way.
# Jul 20th 2009, 12:35 ProLoser|Work ya for some reason i thought that was a join table lol
# Jul 20th 2009, 12:32 markstory so that should clear things up.
# Jul 20th 2009, 12:32 markstory ProLoser|Work: well there are multi page articles.
# Jul 20th 2009, 11:15 ProLoser|Work but i don't get the article_pages_controller
# Jul 20th 2009, 11:15 ProLoser|Work i'm trying to build a similar setup that pretty much is like a multi-page cms, like 'tutorials' or something, and was looking at how you guys did it
# Jul 20th 2009, 11:14 ProLoser|Work is every post in the bakery an article?
# Jul 20th 2009, 10:53 ProLoser|Work but i'm expecting opposition on that
# Jul 20th 2009, 10:53 ProLoser|Work and i think would help immensely
# Jul 20th 2009, 10:52 ProLoser|Work to me it makes a /lot/ of sense
# Jul 20th 2009, 10:52 ProLoser|Work http://thechaw.com/bakery/tickets/view/9
# Jul 20th 2009, 10:52 ProLoser|Work 1 sec
# Jul 20th 2009, 10:52 gwoo link?
# Jul 20th 2009, 10:52 ProLoser|Work even though #5 is the same thing mainly
# Jul 20th 2009, 10:52 ProLoser|Work addendum to jon's ticket
# Jul 20th 2009, 10:51 gwoo ProLoser|Work: where did you make the proposition?
# Jul 20th 2009, 10:42 ProLoser|Work i made a new proposition for navigation / organization structure in thechaw that may seem a bit strange at first
# Jul 20th 2009, 10:41 alkemann well i gotta go home for some dinner. laters
# Jul 20th 2009, 10:39 gwoo yes
# Jul 20th 2009, 10:39 alkemann especially if we dont put the code bits as part of the article text content
# Jul 20th 2009, 10:39 alkemann probably
# Jul 20th 2009, 10:39 gwoo i think single articles will have less revisions too
# Jul 20th 2009, 10:38 gwoo yeah
# Jul 20th 2009, 10:38 alkemann gwoo: for the public article this will probably be valuable. less so for single author articles. but space is cheap ;)
# Jul 20th 2009, 10:37 ProLoser|Work interesting plugin you guys are working on, i'd like to look into using it on my current app
# Jul 20th 2009, 10:37 gwoo yeah
# Jul 20th 2009, 10:37 alkemann u think it might be better to just export old revisions as more lro less manual cleanup duty?
# Jul 20th 2009, 10:36 alkemann the revision behaviour lets u set a limit, if revisions on a particlular record is made with limit reached, it will delete the oldest
# Jul 20th 2009, 10:35 gwoo once we have tons of revisions
# Jul 20th 2009, 10:35 gwoo later
# Jul 20th 2009, 10:35 gwoo we can do archiving
# Jul 20th 2009, 10:35 alkemann basically a size vs cost of count + delete issue
# Jul 20th 2009, 10:34 alkemann gwoo: what do you think about limiting the number of revisions that is kept?
# Jul 20th 2009, 10:34 gwoo good
# Jul 20th 2009, 10:34 alkemann it may make more sense to change the order of the behaviours
# Jul 20th 2009, 10:34 alkemann atm, revision is created when draft is accepted instead of when the draft is createded
# Jul 20th 2009, 10:33 gwoo ok
# Jul 20th 2009, 10:33 alkemann atm there is a problem with the cooperation of the two behaviours, but i will look into that
# Jul 20th 2009, 10:33 alkemann http://thechaw.com/bakery/source/branches/2.0/tests/cases/models/article_page.test.php#highlight
# Jul 20th 2009, 10:33 alkemann added tests that show application flow around article creation, article page creation and editing, and how drafts and revisions are involved with this process
# Jul 20th 2009, 09:43 ProLoser|Work ah danke
# Jul 20th 2009, 09:43 alkemann userplugins branchg
# Jul 20th 2009, 09:42 ProLoser|Work at least under master
# Jul 20th 2009, 09:42 ProLoser|Work plugins folder is empty
# Jul 20th 2009, 09:42 alkemann thechaw.com/bakery
# Jul 20th 2009, 09:42 ProLoser|Work i'm curious to learn more about this userplugin, is there somewhere i can check it out?
# Jul 20th 2009, 09:39 alkemann heh ur excused ;)
# Jul 20th 2009, 09:38 markstory ACTION apologizes for code pasting.
# Jul 20th 2009, 09:38 markstory put your method name inside ''
# Jul 20th 2009, 09:38 alkemann rigth thanks
# Jul 20th 2009, 09:38 markstory function getTests() {
# Jul 20th 2009, 09:38 markstory return array('start', 'startCase', '', 'endCase', 'end');
# Jul 20th 2009, 09:38 markstory }
# Jul 20th 2009, 09:38 markstory getTests
# Jul 20th 2009, 09:37 alkemann OT. what was that trick to only run one of the tests in a testcase (besides commenting out or renaming)
# Jul 20th 2009, 09:35 alkemann but if gwoo is fine with it, then i guess im too :)
# Jul 20th 2009, 09:35 markstory meh
# Jul 20th 2009, 09:35 alkemann yea git makes me like to work that way. i just felt it a bit unclean pushing these events to the public repo
# Jul 20th 2009, 09:35 markstory so 1.3-bake had about 6 branches on my computer.
# Jul 20th 2009, 09:35 markstory I use lots of small branches personally.
# Jul 20th 2009, 09:34 markstory because I don't care about them. How I got to the end is normally not important.
# Jul 20th 2009, 09:34 markstory and I don't make branch names that others understand
# Jul 20th 2009, 09:34 gwoo both
# Jul 20th 2009, 09:34 markstory I don't squash merges
# Jul 20th 2009, 09:34 alkemann markstory: do u do this? or do you work on the locally tracking branch?
# Jul 20th 2009, 09:34 gwoo alkemann: looks fine to me
# Jul 20th 2009, 09:34 gwoo alkemann: why?
# Jul 20th 2009, 09:32 markstory you can squash the merge commit as well.
# Jul 20th 2009, 09:32 alkemann then maybe these local development branches should be named something that makes sense to public .. like "local-2.0"
# Jul 20th 2009, 09:31 alkemann ok
# Jul 20th 2009, 09:31 markstory at least that's how I understand it.
# Jul 20th 2009, 09:31 markstory because without the merge commit there would be no way to find out the commit's parent previous to the merge.
# Jul 20th 2009, 09:30 gwoo alkemann: ask the git guys not me
# Jul 20th 2009, 09:30 markstory not if there was no merge commit.
# Jul 20th 2009, 09:30 alkemann wouldnt that be checkout the commit before the merged commits?
# Jul 20th 2009, 09:30 markstory so you can undo the merge
# Jul 20th 2009, 09:30 alkemann gwoo: ^
# Jul 20th 2009, 09:28 alkemann paralell conversation.. bit confusing. but about these merges, as i understood it, the merge is just saying that these commits should be associated with this branch, if there are no conflicts, why is there made a commit of the merge?
# Jul 20th 2009, 09:28 ProLoser|Work hey is there a url i can checkout this userplugin you guys are talking about?
# Jul 20th 2009, 09:27 alkemann the speccs for the userplugin as i understood it isnt totally compatible with the "old" as it removes any field that should be in a "profile" model and the group_id isnt part of the users table etc
# Jul 20th 2009, 09:25 gwoo alkemann: unless there is an easy way to upgrade people
# Jul 20th 2009, 09:25 alkemann gwoo: so we must threat the existing plugin and table as legacy code to be compatible with?
# Jul 20th 2009, 09:25 gwoo alkemann: they are part of the history, i just need to check what they merged so i can show it
# Jul 20th 2009, 09:24 Phally gwoo: hehe good morning then :)
# Jul 20th 2009, 09:24 gwoo )
# Jul 20th 2009, 09:24 gwoo Phally: no, just woke up
# Jul 20th 2009, 09:24 alkemann gwoo: and i develop locally in a seperate branch and merge into the 2.0 branch, but i end up with commits like this. which i dont think need to be part of the history on thechaw. http://thechaw.com/bakery/commits/view/07677e87803dd3e50e31cdf27d80e400cabf508b - what do you think?
# Jul 20th 2009, 09:24 Phally gwoo: yes i did, have you checked it out?
# Jul 20th 2009, 09:24 ProLoser|Work you guys are making a usertable plugin?
# Jul 20th 2009, 09:23 gwoo s
# Jul 20th 2009, 09:23 gwoo and he refactoring something
# Jul 20th 2009, 09:23 gwoo i talked to phally about it a bit
# Jul 20th 2009, 09:23 gwoo so it can be used across sites
# Jul 20th 2009, 09:23 gwoo yes it should be as inline with the old plugin as possible
# Jul 20th 2009, 09:23 alkemann gwoo: what do u think abuot the userplug in we are making, should the book be updated to use it, should they use seperate plugins, but the same table? does the new plugin have to use the existing schema ? like the "psword" field
# Jul 20th 2009, 09:21 alkemann ok
# Jul 20th 2009, 09:21 gwoo i have to look into it