Page 4 of 134, showing 100 records out of 13,394 total, starting on record 301, ending on 400
| # | Username | Text | |
|---|---|---|---|
| # | Feb 18th 2009, 13:57 | d1rk | maybe, if there is something like a web-callback in thechaw i would deploy it for myself on a test-instance, somewhere.... |
| # | Feb 18th 2009, 13:58 | jperras | d1rk: you can implement your own post-commit hooks in git for test running very easily |
| # | Feb 18th 2009, 13:58 | jperras | and even a pre-commit to make sure your tests pass before you do a push |
| # | Feb 18th 2009, 13:58 | d1rk | jperras: oh, really? how do i do that? |
| # | Feb 18th 2009, 13:59 | d1rk | jperras: sounds great. could you give me a hint how to do that? |
| # | Feb 18th 2009, 13:59 | jperras | d1rk: create a pre-commit file in $BOOK_PROJECT/.git/hooks/pre-commit |
| # | Feb 18th 2009, 14:00 | jperras | and populate it with the code in the bin: |
| # | Feb 18th 2009, 14:01 | jperras | http://bin.cakephp.org/view/1733483502 |
| # | Feb 18th 2009, 14:02 | jperras | actually, that might need a little tweak; I'm not sure if the testsuite shell returns an exit value of 1 when a test fails |
| # | Feb 18th 2009, 14:02 | jperras | of course, you need to have the cake shell in your $PATH as well |
| # | Feb 18th 2009, 14:09 | alkemann | to me it sounds a little overkill, but i would be happy for the experience of doing this :) |
| # | Feb 18th 2009, 14:11 | d1rk | alkemann: if it is setup once, it makes the devs and all project-related persons happy :) |
| # | Feb 18th 2009, 14:12 | d1rk | jperras: thank you. It looks promising |
| # | Feb 18th 2009, 14:13 | jperras | alkemann: I tend to agree to some extent. for cont. integration to be useful, you need to maintain ~80% or better code coverage at all times |
| # | Feb 18th 2009, 14:14 | d1rk | jperras: it can be unrelated to code-coverage... |
| # | Feb 18th 2009, 14:15 | alkemann | i love tdd, but so far i have only made tests for behaviors, components and helpers. app tests seems like not so good in the reward/work area |
| # | Feb 18th 2009, 14:15 | jperras | d1rk: not really. what's the point of having cont. integration to run all your tests if you're not writing tests as you develop more features? |
| # | Feb 18th 2009, 14:16 | jperras | in any case, I think this is a very unimportant point at this time, since individuals can create their own pre-commit hooks to ensure they haven't broken anything |
| # | Feb 18th 2009, 14:17 | d1rk | jperras: you are right, there is need for tests. but i like the process of an automatic deployment to an online.webserver so i (and others) can always check the current state of development as oposed everybody has to fetch latest sources and test them in their own environment... |
| # | Feb 18th 2009, 14:17 | d1rk | jperras: yeah - it is of no importance right now. I was just curious... |
| # | Feb 18th 2009, 14:18 | jperras | d1rk: you make some good points, for sure. but yeah, I think we can drop this for the moment |
| # | Feb 18th 2009, 14:20 | alkemann | being able to checkout the dev branch to an online server could be useful for sure |
| # | Feb 18th 2009, 14:20 | d1rk | jperras: yeah - hehe. lets see if i can stretch this very day to 36 hours... uhm, no.. failed.. so... |
| # | Feb 18th 2009, 14:21 | d1rk | alkemann: yes, especially if talking about features, but we have to do something before that, so if development cycles get shorter one could setup ci. |
| # | Feb 18th 2009, 14:26 | d1rk | gotta go, see you all later. |
| # | Feb 18th 2009, 14:26 | d1rk | jperras: what do you think the wireframes will be ready? |
| # | Feb 18th 2009, 15:31 | alkemann | g'nite |
| # | Feb 19th 2009, 02:19 | jperras | alkemann: you there? |
| # | Feb 19th 2009, 02:20 | alkemann | yes |
| # | Feb 19th 2009, 02:20 | alkemann | good morning |
| # | Feb 19th 2009, 02:21 | jperras | alkemann: heh, kinda |
| # | Feb 19th 2009, 02:21 | alkemann | 9:40 am here |
| # | Feb 19th 2009, 02:21 | jperras | EST time here, so 3:40am |
| # | Feb 19th 2009, 02:22 | jperras | my sleep schedule is pretty messed up |
| # | Feb 19th 2009, 02:22 | alkemann | up late heh.. working on wires? |
| # | Feb 19th 2009, 02:22 | jperras | partly, yes |
| # | Feb 19th 2009, 02:22 | jperras | http://drop.io/jperras |
| # | Feb 19th 2009, 02:22 | alkemann | .io ? |
| # | Feb 19th 2009, 02:23 | jperras | yeah, I have no idea which ICANN country that belongs to |
| # | Feb 19th 2009, 02:23 | jperras | but it's a pretty good app for filesharing |
| # | Feb 19th 2009, 02:24 | alkemann | have to dl to see full size? |
| # | Feb 19th 2009, 02:24 | jperras | alkemann: yes |
| # | Feb 19th 2009, 02:25 | alkemann | ok looking at it |
| # | Feb 19th 2009, 02:25 | alkemann | u want to give most space for a timeline? |
| # | Feb 19th 2009, 02:26 | jperras | well, I think it's a good compromise for the many different types of articles we currently show on the front page |
| # | Feb 19th 2009, 02:26 | jperras | there are just too many boxes, currently |
| # | Feb 19th 2009, 02:27 | jperras | and some of them are stale for weeks |
| # | Feb 19th 2009, 02:27 | alkemann | yes |
| # | Feb 19th 2009, 02:27 | jperras | so a timeline-type of view is a way of correcting those flaws |
| # | Feb 19th 2009, 02:27 | alkemann | but im unsure about timeline. i do use the footer on the current bakery, but i think i have never read or used the contents of the "Recent articles.." |
| # | Feb 19th 2009, 02:28 | alkemann | i think gwoo wants to keep tag cloud on home page as well |
| # | Feb 19th 2009, 02:28 | jperras | most of those articles actually appear in the top boxes first, irrc |
| # | Feb 19th 2009, 02:28 | jperras | iirc* |
| # | Feb 19th 2009, 02:29 | jperras | alkemann: ok, tag cloud can stay at the same spot above the 'hottest stuff' |
| # | Feb 19th 2009, 02:31 | jperras | really, I just want to get away from the mishmash of boxes |
| # | Feb 19th 2009, 02:31 | jperras | if you have ideas, I'm all ears ;-) |
| # | Feb 19th 2009, 02:33 | alkemann | i agree on the boxes. but im unsure about timeline. im thinking using more space for hottest articles. maybe auto "feature" highest scoring stuff |
| # | Feb 19th 2009, 02:33 | jperras | that could work |
| # | Feb 19th 2009, 02:34 | jperras | with an override for special announcements when they come up |
| # | Feb 19th 2009, 02:34 | alkemann | yea |
| # | Feb 19th 2009, 02:35 | alkemann | you should include the footer in ur write though |
| # | Feb 19th 2009, 02:35 | jperras | good point |
| # | Feb 19th 2009, 02:36 | jperras | k, well I'm going to get a few hours of sleep. feel free to leave comments on the drop.io page, or on the wiki itself. |
| # | Feb 19th 2009, 02:36 | jperras | the other mockups will be forthcoming, after we smooth out a few details from this one |
| # | Feb 19th 2009, 02:36 | alkemann | ok. sleep well |
| # | Feb 19th 2009, 02:37 | jperras | thanks. g'night |
| # | Feb 19th 2009, 06:59 | alkemann | i really like debuggable.com 's feature of deprecating articles. I think we should include this feature. letting author's and moderators set this tag instead of deleting |
| # | Feb 19th 2009, 07:35 | poLK | +1 vote |
| # | Feb 19th 2009, 07:36 | alkemann | did i say include? i meant shamelessly steal off course .p |
| # | Feb 19th 2009, 07:37 | poLK | I doubt debuggable guys will sue CSF ;) |
| # | Feb 19th 2009, 07:38 | alkemann | that would be weird :p |
| # | Feb 19th 2009, 09:34 | jperras | for all those interested, a first draft mockup of the bakery is viewable at http://drop.io/jperras . Comments are welcome and encouraged. |
| # | Feb 19th 2009, 09:36 | jperras | more mockups based on use cases will follow, once I get some feedback on this initial one |
| # | Feb 19th 2009, 10:20 | AD7six | jperras: you got a minute now, or a bit later? |
| # | Feb 19th 2009, 10:21 | AD7six | well I'll state the problem/doubt/idea for mulling over: |
| # | Feb 19th 2009, 10:21 | jperras | I got some time |
| # | Feb 19th 2009, 10:23 | AD7six | the book makes no joins between its own data and the users table. the book in reality needs its own user-profile or user-role or simply acl tables for disassociating book data, roles and everything else from simple 'a user'. I think the bakery should be designed to do the same - i.e. it should be possible to use the users table/model in any app on cakephp.org without assuming they have the same role/profile/requirements/whatever that |
| # | Feb 19th 2009, 10:23 | AD7six | they setup for the bakery. |
| # | Feb 19th 2009, 10:24 | AD7six | there's a term for what that means in terms of db queries which escapes me, instead of select * from posts left join users (author) you'd do 2 selects, which is simpler but more imprtantly means the users table can be in a different db from the app's data. |
| # | Feb 19th 2009, 10:24 | AD7six | a) know what I mean? b) thoughts |
| # | Feb 19th 2009, 10:25 | gwoo | AD7six: i would prefer to see a unified plugin that provides the same access to information across all the sites |
| # | Feb 19th 2009, 10:26 | gwoo | so if you click on your account name on the book you get your profile and do not have to go back to the bakery |
| # | Feb 19th 2009, 10:26 | jperras | gwoo: right now they're all separate accounts, correct? |
| # | Feb 19th 2009, 10:26 | gwoo | AD7six: multiple selects are already done across the different db |
| # | Feb 19th 2009, 10:26 | gwoo | jperras: no |
| # | Feb 19th 2009, 10:26 | gwoo | they are all bakery accounts |
| # | Feb 19th 2009, 10:26 | gwoo | jperras: the bakery plugin i built for thebook |
| # | Feb 19th 2009, 10:26 | jperras | ok, so accounts on book are really bakery accounts? |
| # | Feb 19th 2009, 10:27 | jperras | k |
| # | Feb 19th 2009, 10:27 | gwoo | is a step in the direction |
| # | Feb 19th 2009, 10:27 | AD7six | gwoo: multiple selects are desirable is what I'm saying and the bakery code shouldn't assume the user table is in the bakery db. |
| # | Feb 19th 2009, 10:27 | gwoo | AD7six: joins are still handled internally by cake |
| # | Feb 19th 2009, 10:27 | gwoo | so it has the appearance of being the same |
| # | Feb 19th 2009, 10:28 | AD7six | I'm not sure if your missing my point. if the bakery uses the plugin that the book uses (and the plugin's user model uses a different datasouce from $default) that by design addresses what I'm trying to point out. |
| # | Feb 19th 2009, 10:29 | AD7six | maybe that's inline with what you first said (?) |
| # | Feb 19th 2009, 10:30 | AD7six | don't know if 'your profile' should mean your-one-and-only profile or your book-profile, your bakery-profile, your xyz-profile |
| # | Feb 19th 2009, 10:31 | jperras | why have more than one profile accross multiple cakephp.org apps? |
| # | Feb 19th 2009, 10:31 | gwoo | AD7six: yes thats what i was saying |
| # | Feb 19th 2009, 10:31 | AD7six | gwoo: cool. |
| # | Feb 19th 2009, 10:32 | gwoo | AD7six: profile is the one and only profile |