Tweet
I know this is a monumental shift in how NAB apps are built but I would like to see a more local development strategy for apps within NAB. That could work with GIT. I"m not even sure this is possible with NAB but the more i write code locally on my PC (Node on IBM, RPGLE in Code4i storing source in GIT and local computer, the more I like it. As our NAB apps get bigger and more complex I find it nerve wracking when I am requested to add a major feature or major change to the app, because I don't really have a point I can revert back too like I can using GIT if mistakes are made or things don't work out with the new features. Sure, I have two instances so I work on the development instance, but there are times I want to play around even when I'm developing and try something in the development instance. So what I have to do is make a copy of the app and all the widgets in the development instance, in case my idea doesn't work out. If I'm using GIT, I could just make new branch or revert my code back to a certain commit. Again, I know this is a huge change but I personally would like to see NAB start working in that direction. I also know I could just save copies to tape but this seems like a very outdated strategy. How could we use NAB with source control ?? thanks!
-
-
Sorry for the delayed response. We have actually been working on a new Check Out/Check In process for NAB. Additionally, this process includes the ability to link your NAB items to a Git repository.
To give you some insight into what’s coming: You can check out data sources, widgets, and apps, then work with them. The changes you make while checked out are only visible to you. It’s then up to you to check them back in with your changes or not. Once checked in, everyone will see those changes.
If Git is enabled, you will be required to enter a commit message when checking changes in and will have the ability to roll back to an older commit on a data source, widget, or app.
Comment