home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Plugin Development
SQLiteDatabase Plugin for MP2
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MJGraf" data-source="post: 1026251" data-attributes="member: 17886"><p>I'm planning to add the source code of this plugin to a feature branch in our git repo when I find the time, to make it easier for others to contribute. But I have three questions (maybe directed at @[USER=48495]morpheus_xx[/USER] and / or @[USER=10438]chefkoch[/USER]):</p><ul> <li data-xf-list-type="ul">In what directory shall I put this database plugin? \Incubator or \Source\Backend\Database ? I think this plugin is not "rtm" until we have solved the EntityFramework CodeFirst problem with TVE 3.5 so the incubator would be the natural choice. On the other hand, we also have ScimoreDB and FirebirdDatabase in \Source\Backend\Database which AFAIK are anything but "rtm". Besides that having it in \Source\Backend\Database would mean that we don't have to move it around when it is rtm and as long as we keep it in a separate branch, it doesn't hurt. I'm fine with everything, so please advise...</li> <li data-xf-list-type="ul">In the separate branch, shall I deactivate the MSSQLCE plugin and activate this plugin in the solution settings? Since the branch deals with this plugin it would certainly make sense to do so because you are unlikely to use the MSSQLCE plugin when you compile this branch. On the other hand when we later merge this into dev, we would have to undo these changes (at least until we make this the standard database, but this will take a while and a lot more testing...). Is there a best practice?</li> <li data-xf-list-type="ul">My plan is to keep this plugin always updated to the latest dev branch. My conclusion from many threads about git usage is that at least when pushing to dev (which I will not do), I should do a local fetch/rebase before. What about such a feature branch? Shall I regularly do a local fetch/rebase and push it to this feature branch to keep it updated to the current dev branch? On the other hand my understanding is that this deletes part of the branch history - so other who have pulled the feature branch before may have problems. Please advise...</li> </ul><p>Sorry for the potentially stupid questions, but I'm trying to get used to Git and how we use it for MP2.</p><p>Thanks,</p><p>Michael</p></blockquote><p></p>
[QUOTE="MJGraf, post: 1026251, member: 17886"] I'm planning to add the source code of this plugin to a feature branch in our git repo when I find the time, to make it easier for others to contribute. But I have three questions (maybe directed at @[USER=48495]morpheus_xx[/USER] and / or @[USER=10438]chefkoch[/USER]): [LIST] [*]In what directory shall I put this database plugin? \Incubator or \Source\Backend\Database ? I think this plugin is not "rtm" until we have solved the EntityFramework CodeFirst problem with TVE 3.5 so the incubator would be the natural choice. On the other hand, we also have ScimoreDB and FirebirdDatabase in \Source\Backend\Database which AFAIK are anything but "rtm". Besides that having it in \Source\Backend\Database would mean that we don't have to move it around when it is rtm and as long as we keep it in a separate branch, it doesn't hurt. I'm fine with everything, so please advise... [*]In the separate branch, shall I deactivate the MSSQLCE plugin and activate this plugin in the solution settings? Since the branch deals with this plugin it would certainly make sense to do so because you are unlikely to use the MSSQLCE plugin when you compile this branch. On the other hand when we later merge this into dev, we would have to undo these changes (at least until we make this the standard database, but this will take a while and a lot more testing...). Is there a best practice? [*]My plan is to keep this plugin always updated to the latest dev branch. My conclusion from many threads about git usage is that at least when pushing to dev (which I will not do), I should do a local fetch/rebase before. What about such a feature branch? Shall I regularly do a local fetch/rebase and push it to this feature branch to keep it updated to the current dev branch? On the other hand my understanding is that this deletes part of the branch history - so other who have pulled the feature branch before may have problems. Please advise... [/LIST] Sorry for the potentially stupid questions, but I'm trying to get used to Git and how we use it for MP2. Thanks, Michael [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
SQLiteDatabase Plugin for MP2
Contact us
RSS
Top
Bottom
