|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Keeping scripts out of webERPHi all: We reached the feared point. We do have some modifications in some
scripts (1 so far...) very particular to the way we use webERP and I’m
afraid would not be accepted under standard webERP (If I were Tim or Phil for
sure I would reject them). I guess most of you reached this point
sometime in the past... Which is the best way to deal with “own
modified scripts”? Keep the same name and each revision check
the differences? Use the modified one with a differenr name
and just change index.php? For all of you with more experience in the
field... What should I do to maintain the installation up-to-date but with our “minor”
fixes? Thanks, Ricard ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Web-erp-developers mailing list Web-erp-developers@... https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
|
|
Re: Keeping scripts out of webERPI generally recommend to people that they keep a diff file of the
differences. Then when a new version of the file is released they apply the patch file to the new version, and generate a new diff file. Does this make sense? Tim 2009/11/5 Pak Ricard <pakricard@...>: > Hi all: > > > > We reached the feared point. > > > > We do have some modifications in some scripts (1 so far...) very particular > to the way we use webERP and I’m afraid would not be accepted under standard > webERP (If I were Tim or Phil for sure I would reject them). > > > > I guess most of you reached this point sometime in the past... > > > > Which is the best way to deal with “own modified scripts”? > > > > Keep the same name and each revision check the differences? > > Use the modified one with a differenr name and just change index.php? > > > > For all of you with more experience in the field... What should I do to > maintain the installation up-to-date but with our “minor” fixes? > > > > Thanks, > > Ricard > > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Web-erp-developers mailing list > Web-erp-developers@... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Web-erp-developers mailing list Web-erp-developers@... https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
|
|
Re: Keeping scripts out of webERPi have the same problem, i changed quite a few files from a previous
version. this could be considered a branch, but a local branch. i see a few options: 1. keep the same filename, compare each time a new version is out. Could be time consuming, and if conflicts arise, difficult to solve.. (tim's solution below) 2. keep the development in a different file, which is called from the standard script (you would have only a include file or function call to maintain in the standard file). this is not always easy, as the system is not so OO developed. 3. change the filename, include in svn ignore, and take care to follow new functionalities in the standard file. risky, as we could forget to check :-) 4. try to include the changes in the project, almost always someone else would need them. while i think 4 is the best, it is not always fesible. maybe there is more, please comment. bogdan Tim Schofield wrote: > I generally recommend to people that they keep a diff file of the > differences. Then when a new version of the file is released they > apply the patch file to the new version, and generate a new diff file. > Does this make sense? > > Tim > > > 2009/11/5 Pak Ricard <pakricard@...>: > >> Hi all: >> >> >> >> We reached the feared point. >> >> >> >> We do have some modifications in some scripts (1 so far...) very particular >> to the way we use webERP and I’m afraid would not be accepted under standard >> webERP (If I were Tim or Phil for sure I would reject them). >> >> >> >> I guess most of you reached this point sometime in the past... >> >> >> >> Which is the best way to deal with “own modified scripts”? >> >> >> >> Keep the same name and each revision check the differences? >> >> Use the modified one with a differenr name and just change index.php? >> >> >> >> For all of you with more experience in the field... What should I do to >> maintain the installation up-to-date but with our “minor” fixes? >> >> >> >> Thanks, >> >> Ricard >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Web-erp-developers mailing list >> Web-erp-developers@... >> https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> >> >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Web-erp-developers mailing list > Web-erp-developers@... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Web-erp-developers mailing list Web-erp-developers@... https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
|
|
Re: Keeping scripts out of webERP
I've keep my changes in a git repository and pull the weberp changes in this. Done a merge to check for any issues, then pushed it to the webserver.
Now we have a real stable branch this process should be even easier - I'll just pull with git-svn from the stable branch. Nicholas ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Web-erp-developers mailing list Web-erp-developers@... https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
| Free embeddable forum powered by Nabble | Forum Help |