Subject: New Login.php at SVN - msg#00022

Previous Message by Date: click to view message preview

Re: Fwd: Patch: import that deals with duplicates

Am Mittwoch, 7. MÃrz 2007 schrieb xavier dutoit: > On 3/7/07, Dirk Gorny <Dirk.Gorny@xxxxxxxxx> wrote: > > Am Mittwoch, 7. MÃrz 2007 schrieb xavier dutoit: > > > I would like to know how to update my local copy to 5.0.3 from svn (cf > > > my previous mail). > > > > If you want to get all files you only have to do a svn export > > http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/./$LOCALDI > >RECTORY > > Is this how you use it ? No. I use: svn diff --old=http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@$OLDRELEASE --new=http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@HEAD And patch it by hand. Then you look for DB changes and change the database if needed. > It should be as simple as a "svn update", even between branches, shouldn't > it ? No. > The thing is that I don't know how to change from one branch to another > without having to do a full checkout. How do you do that ? look ahead. > Because of changes in the structure of the source between the checked out > > > source and the deployment you have to build a diff if you want to update > > a working deployment and update by "patch". > > Well, svn should deal with the change on the source, that's its job. But your deployment differs with the source. > Sure, that's normal to have to change the db by hand. > Is there any place where the changes are documented ? Look at: http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/schema/DatabaseSchema.xml Best regards, Dirk _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com

Next Message by Date: click to view message preview

Re: Fwd: Patch: import that deals with duplicates

> > If you want to get all files you only have to do a svn export> > http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/./$LOCALDI> >RECTORY>> Is this how you use it ?No. I use:svndiff --old= http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@$OLDRELEASE --new=http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/@HEAD And patch it by hand. Then you look for DB changes and change the database ifneeded.> It should be as simple as a "svn update", even between branches, shouldn't> it ?No. Ok, based on my experience with other projects, I know for a fact that it is possible to keep your local modifications and benefit from svn updates  without having to create patches between versions. > Because of changes in the structure of the source between the checked out >> > source and the deployment you have to build a diff if you want to update> > a working deployment and update by "patch".>> Well, svn should deal with the change on the source, that's its job. But your deployment differs with the source.Yes, but again it shouldn't be a problem. Can we imagine two seconds a use case scenario ?I've fixed a bug on the 5.0.2 and there is a new 5.0.3 version. I want to use it, but, of course, to be sure my patch is still existing.They are three scenarios:1) The bug is still on the 5.0.3 (and my fix still work)2) They have applied it as offered and I need to "forget" my patch 3) They have fixed it, but with a different patch than what I submitedOnly the last case should need my intervention. I expect the SCM to deal with the others smoothly. I think the problem is that you are expected to change your working branches for every minor version. In other OSS softwares, the main versions ( 4.2, 5 and 5.1) are branched before the dev, and the minor ones after (as mainstones while producing the patches, new tar distos).ie. you always work in the same branch 5.n for all its live and you only svn update, and have to branch only when you go from 5.0 and 5.1.I mentioned something like that a few months ago, would it be possible to consider it or am I the only one thinking that would be saving a lot of time without any additional problem ? Look at:http://vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/5.0.3/schema/DatabaseSchema.xml Brilliant, thanks.  Could you recommend a way of using these to generate mysql commands with the diffs ?X+ _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com

Previous Message by Thread: click to view message preview

A happy day for PHP

Yay, finally my biggest gripe has a nice simple solution.  The last time I seriously coded was with SQL and Delphi 7.  When I started working on vTiger I tested out a lot of IDEs and often would resort to VIM.  OMG.  I've been keeping an eye out and see that this product is soon to be released.   http://www.codegear.com/Products/Delphi/DelphiforPHP/tabid/237/Default.aspx   I give you guys a lot of credit if you're using non WYSIWYG environments.  You are extremely patient. :-)   Just sharing.      Brian Laughlin _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com

Next Message by Thread: click to view message preview

Re: New Login.php at SVN

Hi Frank, We do have internationalised the label's username,password, language and theme in the login page. Do get back to us if you come across any issue in transaltion in the label while using our latest svn code. Regards, Philip Frank Piepiorra wrote: > I saw the new v5.0.3 Login page at the SVN. Looks much nicer but raises an > i18n issue. The expressions for username, password, language and theme are > now hardcoded. Before these could be changed by the default language. Sure > it is a minor issue but since you put so much effort in the > internationalisation of vtiger it is worth to mention. > > Regards, > Frank > > www.crm-now.com > > _______________________________________________ > Reach hundreds of potential candidates - http://jobs.vtiger.com > > _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com