I have started this task, taking the genplugouts subdirs in alpha order - cpp_utilities/
What would be a good way to organize these in the tracker: by function? by compile error? other ideas?
One problem is that where possible I want to identify common changes in all plugouts so it is better to not assign a single plugout to a single person IMHO.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert! I am glad to hear that.
Well, for each porting effort, you may open a report in porting tasks. For example, in porting cpp_utilities, you may add a report named cpp_utilities, and then post any bugs you may find in porting them, if you are not able to solve them yoursef. I agree that the porting task should not be set to only one person, but if we split too much the task it may be harder to work.
IMHO, for each plugout, a person should be in charge, and others may contribute. I think that might work.
Certainly there will be many repeated bugs, thats why we have our porting notes under doc/, we will use that knowledge when needed.
We might work on this one together, I will assist you whenever necessary. What you think? :) I am looking forward to it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
cpp_utilities now compiles! Obviously not tested yet but glad to get to this point - you know how that feels!
The biggest item was disambiguating UmlCom::send_cmd() calls using Q3CString arguments. In the end I think that I identified the simple and reliable cases, details found in conversion-notes/Q3CString_pointers.
Your C++ skills seem light-years ahead of my own so please have a look at how I handled those and offer your own thoughts. The plugouts will all use many such calls so we should be sure!
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I hope the other porting tasks keep simple as this one. You replaced QList by Q3PtrList and solved some ambiguity. Seems alright in my opinion, keep going and we will stabilize this port in no time!
Whats next? :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have started this task, taking the genplugouts subdirs in alpha order - cpp_utilities/
What would be a good way to organize these in the tracker: by function? by compile error? other ideas?
One problem is that where possible I want to identify common changes in all plugouts so it is better to not assign a single plugout to a single person IMHO.
Hello Robert! I am glad to hear that.
Well, for each porting effort, you may open a report in porting tasks. For example, in porting cpp_utilities, you may add a report named cpp_utilities, and then post any bugs you may find in porting them, if you are not able to solve them yoursef. I agree that the porting task should not be set to only one person, but if we split too much the task it may be harder to work.
IMHO, for each plugout, a person should be in charge, and others may contribute. I think that might work.
Certainly there will be many repeated bugs, thats why we have our porting notes under doc/, we will use that knowledge when needed.
We might work on this one together, I will assist you whenever necessary. What you think? :) I am looking forward to it.
Hi Leonardo,
cpp_utilities now compiles! Obviously not tested yet but glad to get to this point - you know how that feels!
The biggest item was disambiguating UmlCom::send_cmd() calls using Q3CString arguments. In the end I think that I identified the simple and reliable cases, details found in conversion-notes/Q3CString_pointers.
Your C++ skills seem light-years ahead of my own so please have a look at how I handled those and offer your own thoughts. The plugouts will all use many such calls so we should be sure!
Thanks!
As I said in the forums, congratulations, it works :)
Oh, I guess you forgot to add/commit the notes, I am interested in seeing it.
I hope the other porting tasks keep simple as this one. You replaced QList by Q3PtrList and solved some ambiguity. Seems alright in my opinion, keep going and we will stabilize this port in no time!
Whats next? :)
Looks like the notes did not commit - sorry, I am also learning SVN as I go - will try again shortly.