Development environment
Rob LeVine
Nouveau membre
Posts: 7
il y a 10 ans 4 mois #149
par Rob LeVine
Réponse de Rob LeVine sur le sujet Development environment
Hi Andres,
I think I'm not communication my question/desire well or maybe you're answering it and it's just not what I want to hear.
Let me cite a simple example to try to illustrate my question. Let's say I have a component with 1 table. So I go into Component Creator UI and do all the necessary stuff and create my wonderful Admin and UI pages. In doing so, I manually edit, post-build, several files so that they are now different from the Component Creator gave me. Now we get to the important part. Let's say I want to add table #2 to my component. I go into Component Creator and add the second table and once again create Admin and UI pages. When I build the component again, should it be my expectation that, if I were to not backup all my files from table #1, that they will all get overwritten? NOTE: The same example can be "I have table #1, build, modify files and then add a single column to table #1".
I have to admit that I find that problematic if I have to store my manual changes and merge them into the code each time I rebuild. I'm not saying that I have any great solution for that, only that's a real pain to do so.
So the bottom line is that, aside from source control, it would be nice to know what the expectation is for a Component Creator user doing incremental changes. Actually I do see how source control code, in theory, help by being able to refresh from source control into the build directory and copy over the manually changed files that I made post-build, so maybe that's the answer.
Regards,
Rob
I think I'm not communication my question/desire well or maybe you're answering it and it's just not what I want to hear.
Let me cite a simple example to try to illustrate my question. Let's say I have a component with 1 table. So I go into Component Creator UI and do all the necessary stuff and create my wonderful Admin and UI pages. In doing so, I manually edit, post-build, several files so that they are now different from the Component Creator gave me. Now we get to the important part. Let's say I want to add table #2 to my component. I go into Component Creator and add the second table and once again create Admin and UI pages. When I build the component again, should it be my expectation that, if I were to not backup all my files from table #1, that they will all get overwritten? NOTE: The same example can be "I have table #1, build, modify files and then add a single column to table #1".
I have to admit that I find that problematic if I have to store my manual changes and merge them into the code each time I rebuild. I'm not saying that I have any great solution for that, only that's a real pain to do so.
So the bottom line is that, aside from source control, it would be nice to know what the expectation is for a Component Creator user doing incremental changes. Actually I do see how source control code, in theory, help by being able to refresh from source control into the build directory and copy over the manually changed files that I made post-build, so maybe that's the answer.
Regards,
Rob
Connexion ou Créer un compte pour participer à la conversation.
Søren Beck Jensen
Administrateur
Posts: 73
il y a 10 ans 4 mois #150
par Søren Beck Jensen
Søren Beck Jensen
Founder, Component-Creator.com
Réponse de Søren Beck Jensen sur le sujet Development environment
Hi Rob,
You are correct that if you have modified the files that is built by Component Creator and re-install the component (modified or not) you file modifications will be overwritten. You can relatively easily re-apply these manual changes again after re-installation using version control. We are working on writing a guide for doing this using git.
If you are a premium member your database data will be maintained and incremental modifications will be made to the database every time you modify your component, rebuild and re-install.
So the bottom line is, I guess. That you should plan your component in detail before building, then test and make sure you have everything you want for the base before you start modifying files. And when you start modifying files then make sure you use version control.
You are correct that if you have modified the files that is built by Component Creator and re-install the component (modified or not) you file modifications will be overwritten. You can relatively easily re-apply these manual changes again after re-installation using version control. We are working on writing a guide for doing this using git.
If you are a premium member your database data will be maintained and incremental modifications will be made to the database every time you modify your component, rebuild and re-install.
So the bottom line is, I guess. That you should plan your component in detail before building, then test and make sure you have everything you want for the base before you start modifying files. And when you start modifying files then make sure you use version control.
Søren Beck Jensen
Founder, Component-Creator.com
Connexion ou Créer un compte pour participer à la conversation.
Rob LeVine
Nouveau membre
Posts: 7
il y a 10 ans 4 mois #151
par Rob LeVine
Réponse de Rob LeVine sur le sujet Development environment
Hi Søren,
Thanks for the clarification. I understand that no software can be absolutely perfect especially after the user customizes parts of it. As a professional software developer of 25 years I can tell you that despite one's best efforts to design something perfectly up front that things change, all the time, even the slightest of things. I truly enjoy using Component Creator so much that I would like it to have no flaws, at least for me
So my final suggestion to you guys is to at least consider the possibility of adding a feature that will (and let me be clear that I don't even know if this is possible) to only install the files that the user denotes as changed when installing the newly built component. Let me explain, since that barely even made sense to me. Let's take my example from before where I have Table #1 and I build and customize files and then I add Table #2 and re-build. If there was some way I could tell the component's installation files to only install the files from Table #2 so as not to disturb Table #1, that would be great. I'm not at all versed in Joomla installation files so I don't even know if that's possible.
Anyway, keep up the good work and I will continue to research GIT.
Regards,
Rob
Thanks for the clarification. I understand that no software can be absolutely perfect especially after the user customizes parts of it. As a professional software developer of 25 years I can tell you that despite one's best efforts to design something perfectly up front that things change, all the time, even the slightest of things. I truly enjoy using Component Creator so much that I would like it to have no flaws, at least for me
So my final suggestion to you guys is to at least consider the possibility of adding a feature that will (and let me be clear that I don't even know if this is possible) to only install the files that the user denotes as changed when installing the newly built component. Let me explain, since that barely even made sense to me. Let's take my example from before where I have Table #1 and I build and customize files and then I add Table #2 and re-build. If there was some way I could tell the component's installation files to only install the files from Table #2 so as not to disturb Table #1, that would be great. I'm not at all versed in Joomla installation files so I don't even know if that's possible.
Anyway, keep up the good work and I will continue to research GIT.
Regards,
Rob
Connexion ou Créer un compte pour participer à la conversation.
Søren Beck Jensen
Administrateur
Posts: 73
il y a 10 ans 4 mois #155
par Søren Beck Jensen
Søren Beck Jensen
Founder, Component-Creator.com
Réponse de Søren Beck Jensen sur le sujet Development environment
Hi Rob,
Thank you for your feedback. We have spent considerable time investigating how to implement what you are asking for, and it is hugely complicated and would make the whole project much more complex and thus slow down future feature releases, so we have decided not to pursue this feature at the moment.
You can accomplish the functionality by using version control or in the case you specified, you could simply (from Component Creator) delete the old table that you have made changes to on your site and it will be left untouched when you re-install. A bit of a hack, but it should work.
Thank you for your feedback. We have spent considerable time investigating how to implement what you are asking for, and it is hugely complicated and would make the whole project much more complex and thus slow down future feature releases, so we have decided not to pursue this feature at the moment.
You can accomplish the functionality by using version control or in the case you specified, you could simply (from Component Creator) delete the old table that you have made changes to on your site and it will be left untouched when you re-install. A bit of a hack, but it should work.
Søren Beck Jensen
Founder, Component-Creator.com
Connexion ou Créer un compte pour participer à la conversation.
Rob LeVine
Nouveau membre
Posts: 7
il y a 10 ans 4 mois #157
par Rob LeVine
Réponse de Rob LeVine sur le sujet Development environment
Hi,
OK, thanks for the explanation and workaround. I'm glad I'm not crazy and that my idea was good, though not practical.
Speaking of source control, is there one in particular you recommend?
Regards,
Rob
OK, thanks for the explanation and workaround. I'm glad I'm not crazy and that my idea was good, though not practical.
Speaking of source control, is there one in particular you recommend?
Regards,
Rob
Connexion ou Créer un compte pour participer à la conversation.
Søren Beck Jensen
Administrateur
Posts: 73
il y a 10 ans 4 mois #158
par Søren Beck Jensen
Søren Beck Jensen
Founder, Component-Creator.com
Réponse de Søren Beck Jensen sur le sujet Development environment
Yeah, by far the most popular is git. The client from github.com/ is very good for PC.
Once you get your head around git, you will be asking yourself how you ever developed without it. Promise.
Once you get your head around git, you will be asking yourself how you ever developed without it. Promise.
Søren Beck Jensen
Founder, Component-Creator.com
Connexion ou Créer un compte pour participer à la conversation.
Temps de génération de la page : 0.101 secondes