Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Intergrate the nativeparser_base to our parsertest project
ollydbg:
--- Quote from: MortenMacFly on July 08, 2012, 05:15:50 am ---
--- Quote from: ollydbg on July 08, 2012, 03:38:01 am ---so it is a mess up when I need to select all the changed files in TortoiseSVN, and generate a diff file. For me, the simplest way is just select a folder like "codecompletion", and generate the diff file. :)
--- End quote ---
If you are using TortoiseSVN IMHO is should be possible even from trunk to only select the files in question. If not, I am using SmartSVN where you have a "flat view", meaning that the files are shown in a big list as if there were not directories from the root folder. Then you can select only the files you want to create a diff from. I am not sure if TortoiseSVN has a similar feature.
--- End quote ---
Yes, TortoiseSVN has this feature, but I'm a bit lazy because that there are too many changed files show in the listed in the root folder. ;)
MortenMacFly:
--- Quote from: ollydbg on July 08, 2012, 06:14:46 am ---Yes, TortoiseSVN has this feature, but I'm a bit lazy because that there are too many changed files show in the listed in the root folder. ;)
--- End quote ---
That's where "flat view" comes into play again: You can still sort by folder as a second sort criteria. Then you have it all aligned again and can easily select a certain sub-set of files.
Jenna:
But with svn you run into trouble, if you work on the same file for different patches.
you can easily select single files, but not single changed lines with svn.
But you can use either different local branches wih git or pull single changed lines or hunks to be committed or to be removed from a commit.
But as alaways it's also a matter of taste, and it should be clear that patches we attach for testing purposes should be usable by svn, as this is the software we use for our vcs.
MortenMacFly:
--- Quote from: jens on July 08, 2012, 10:07:31 am ---But with svn you run into trouble, if you work on the same file for different patches.
--- End quote ---
That is true. I have nothing against GIT itself. Just the combination we do here between SVN and GIT. If we all agree we should consider moving towards GIT completely if most of the devs use it anyways. I recall we were discussing this already, just not why we didn't do it (was it the lack of support from BerliOS?!).
I wonder if some of you already did a migration from SVN to GIT. I mean in terms of keep existing branches and (of course) the whole history...?!
I recall the time when I personally migrated from CVS to SVN. It wasn't easy, but doable if you had the right tools at hand.
BTW: We are getting OT... ;-)
ollydbg:
For the record:
This works Ok currently.
Code:
--- Code: ---class wxWindow
{
int aaaaa;
};
// The template parameter W must be a wxWindow-derived class.
template <class W>
class wxNavigationEnabled
{
public:
W m_T;
};
wxNavigationEnabled<wxWindow> ccccc;
--- End code ---
Statement:
--- Code: ---ccccc.m_T.aaaaa;
--- End code ---
To solve the problem stated here:Re: CodeCompletion wxWidgets, we need to solve below:
--- Code: ---class wxWindow
{
int aaaaa;
};
// The template parameter W must be a wxWindow-derived class.
template <class W>
class wxNavigationEnabled : public W
{
public:
typedef W BaseWindowClass;
};
class wxPanelBase : public wxNavigationEnabled<wxWindow>
{
};
wxPanelBase ccccc;
--- End code ---
Statement:
--- Code: ---ccccc.aaaaa;
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version