That's probably because my understanding is limited AND I am mixing the systems I am talking about.
I wrote my own plugin. I realize that the component table is part of Trac core. My initial question pertained to SimpleMultiProject but I may be quickly getting off topic. Again, partly because my understanding is limited and partly because I have other members of my team pointing me five different directions. This is part of why I have reached out to you guys to set me straight. What controls the feature where an owner is assigned to a component? My understanding was that this was closely tied with functionality within SMP, am I mistaken? Or perhaps I am confused and it is just that SMP currently relies on the current design of component as its own table? For original Trac to support the field 'project', that would currently dictate a new table in the DB called 'project', correct? What other functionality is reliant on 'component' having it's own table? How significant of a change would it be to alter this? Is there a design reason we chose to give component its own table? Could this instead come from a table where all fields and values are a composite key similar to the design for certain other tables? The plugin I was writing was designed to be capable of assigning ownership to any/all fields and their values similar to how the component ownership currently works. But I was asked to look into a better solution as it would conflict with the existing mechanism for configuring ownership for a field/value. I was told SMP had been considering such a change in the future to add this functionality to 'project'. Beyond that, I may be completely mistaken on my original question. This is me attempting to do discovery. Sorry if I was waaaay off. From: "falkb" <fbrettschnei...@baumer.com> To: "Trac Development" <trac-dev@googlegroups.com> Cc: "RjOllos" <rjol...@gmail.com>, lander...@clacorp.com Sent: Tuesday, February 7, 2017 2:37:46 AM Subject: Re: Development on SimpleMultiProject Logan Anderson wrote: > As far as I can currently tell, it appears that my plugin would > contradict/break the upgrade path where a future enhancement would add a > table called project which matches the design of the component table. I don't get that at all, please, describe in other words. SimpleMultiProjectPlugin just adds a db table for all projects, and furthermore it adds several db tables for mapping, that is milestone to projects, versions to projects, components to projects. This shouldn't have to do with any other permission plugins. BTW: If original Trac supported the standard field "project", no additional mapping tables would be necessary, instead we would just extend the standard tables of milestone, version and component by a new column "project". CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
