| # |
Feb 19th 2009, 10:40 |
AD7six |
unless someone better qualified does it first :) |
| # |
Feb 19th 2009, 10:39 |
jperras |
nice |
| # |
Feb 19th 2009, 10:39 |
AD7six |
btw I volunteer to write whatever db conversion process is necessary such that bakery 2 doesn't need to be held back by anything in the existing schema |
| # |
Feb 19th 2009, 10:38 |
markstory |
I remember seeing some unused fields in the current bakery schema. |
| # |
Feb 19th 2009, 10:38 |
markstory |
or making separate permissions/roles for each app. |
| # |
Feb 19th 2009, 10:37 |
markstory |
AD7six: I think that separating permissions and profile will be for the best in the long run. |
| # |
Feb 19th 2009, 10:34 |
AD7six |
sorting out (for the book) |
| # |
Feb 19th 2009, 10:34 |
AD7six |
which is something I'm going to be sorting out, but the same solution in principle applies to both apps, and any others that come |
| # |
Feb 19th 2009, 10:33 |
AD7six |
a bakery admin isn't necessarily a book admin |
| # |
Feb 19th 2009, 10:33 |
AD7six |
so maybe included in what I'm thinking about is disassociating 'profile' from app settings(like user's role) |
| # |
Feb 19th 2009, 10:32 |
jperras |
true |
| # |
Feb 19th 2009, 10:32 |
AD7six |
jperras: profile includes things like "email me replies to my comments" which would be an app by app thing |
| # |
Feb 19th 2009, 10:32 |
gwoo |
if it needs to be extended for each application then that can happen |
| # |
Feb 19th 2009, 10:32 |
gwoo |
AD7six: profile is the one and only profile |
| # |
Feb 19th 2009, 10:31 |
AD7six |
gwoo: cool. |
| # |
Feb 19th 2009, 10:31 |
gwoo |
AD7six: yes thats what i was saying |
| # |
Feb 19th 2009, 10:31 |
jperras |
why have more than one profile accross multiple cakephp.org apps? |
| # |
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:29 |
AD7six |
maybe that's inline with what you first said (?) |
| # |
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:27 |
gwoo |
so it has the appearance of being the same |
| # |
Feb 19th 2009, 10:27 |
gwoo |
AD7six: joins are still handled internally by cake |
| # |
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 |
is a step in the direction |
| # |
Feb 19th 2009, 10:27 |
jperras |
k |
| # |
Feb 19th 2009, 10:26 |
jperras |
ok, so accounts on book are really bakery accounts? |
| # |
Feb 19th 2009, 10:26 |
gwoo |
jperras: the bakery plugin i built for thebook |
| # |
Feb 19th 2009, 10:26 |
gwoo |
they are all bakery accounts |
| # |
Feb 19th 2009, 10:26 |
gwoo |
jperras: no |
| # |
Feb 19th 2009, 10:26 |
gwoo |
AD7six: multiple selects are already done across the different db |
| # |
Feb 19th 2009, 10:26 |
jperras |
gwoo: right now they're all separate accounts, correct? |
| # |
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: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:24 |
AD7six |
a) know what I mean? b) thoughts |
| # |
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:23 |
AD7six |
they setup for the bakery. |
| # |
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:21 |
jperras |
I got some time |
| # |
Feb 19th 2009, 10:21 |
AD7six |
well I'll state the problem/doubt/idea for mulling over: |
| # |
Feb 19th 2009, 10:20 |
AD7six |
jperras: you got a minute now, or a bit later? |
| # |
Feb 19th 2009, 09:36 |
jperras |
more mockups based on use cases will follow, once I get some feedback on this initial one |