Thanks for the detailed instructions - will do.

On Jun 27, 6:19 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com>
wrote:
> On Jun 27, 4:36 pm, dlypka <dly...@gmail.com> wrote:
>
> > Great. Thanks so much!
>
> > However, I've never accessed the 'trunk' before.
>
> > I don't think I have access.
>
> You do - it's distributed SCM - you have read-only access
>
>
>
> > Do I need to do a get from Mercurial source control?
>
> > I have WING IDE, which I believe supports Mercurial.
>
> Wing supports mercurial thru a wing interface - you have to have
> mercurial (which is a python app) on your system for wing to call it.
>
> Get murcurial athttp://mercurial.selenic.com/
>
> Then you can get the trunk fromhttp://code.google.com/p/web2py/ -
> the command line for getting a copy ("clone") of the trunk is there:
>
> hg clonehttp://web2py.googlecode.com/hg/ web2py-trunk   # or
> whatever local directory you want to put it in
>
> Once you do that, you can just go into that directory, and issue:
>
> hg status   # to see if you made any local changes
> hg commit   # to commit local changes
> hg pull     # to update from where you cloned this - i.e. to pull in
> changes
> #  or, if you've made changes locally:
> hg merge   # to get and merge any changes...
>
> Since cloning is quick and easy, you want to consider keeping a
> "clean" clone of the master, and for any local work / tests you have,
> make a local clone, e.g.  from where you can see th web2py-trunk  that
> you cloned from google code:
>
> hg clone web2py-trunk my-patch-test
>
> This will make it easy to make changes that are small, that you can
> easily throw away, and keep a "clean" copy locally if you want to
> start over on a test, or try another test.
>
> If you prefer "visual" tools, there is gnome integration on ubuntu,
> and  for windows you might enjoy TortoiseHG:  http://tortoisehg.bitbucket.org/
>
> It's quick; it's easy;  it's a nice way to keep your work under hg
> (which - as you've noticed - if your project is under hg, then you can
> see changes from wing).
>
> Regards,
> - Yarko
>
>
>
>
>
> > On Jun 27, 3:28 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > Maybe just add a new property dynamically to the row
> > > > We could call it 'nativeRef'
>
> > > > Would it be something like:
> > > >     self.nativeRef = tmp     # Python can add new properties 
> > > > 'on-the-fly', right?
>
> > > > as the new 2nd last statement of insert()?
>
> > > If that is useful we can do it. I just did it in trunk so you can test
> > > it but I called self._last_reference to avoid possible naming
> > > conflicts.
>
> > > Massimo

Reply via email to