Hi, Yi: For the modification submitting stuff: 1. Find out the root cause of an issue; 2. Try to give a workable and nice solution for it; 3. Do some verification test on the solution by your self; 4. Prepare a short technical description about the issue, like why it happens, when it happens and what is your solutions; 5. Attach a patch inside the bugzilla with above description as comments, and mark it to "?" for requesting review;
Thanks a lot! 2013/1/14 Fan Zheng <zheng.easy...@gmail.com> > Hi Yi: > > Sorry I missed you mail before. > > The tools you have are already enough for debugging and development in AOO > now. > > I agree that AOO is different from the COMMON projects for some > cross-platform reason, but trust me, it is not hard to get it in your hand. > > When you trying to start with the source codes, I suggest you that not to > envolve all the source codes debugged together, for 2 reasons, 1, commonly > it is not necessary; 2, it is too slow anyway; > > Indicate your question that where should be the first point to get in, > with the wiki page I recommended you, I also suggest you add tracking point > in the construction method of key classes, SwDoc/SwDocShell for example. > And the SwNodes initialization and operation also would be a good hint for > you to reach the performing on node list inside SW module. > > I am so happy to working with all community guys especially with the new > comers like you. So feel free for any detailed questions. > > ZhengFan > > 2013/1/8 2 <laoyi...@126.com> > >> Fan Zheng, >> >> I got my own build on Windows XP, with MSVC++ 2008 Express. If I >> wanna modify the souce code, which tools do I need? VC++2008 is enough? >> Which tools do you use in your development? I do not kown how to open the >> whole project source code, whether I need do that ? >> I don't kown How to start in the code and debug the code if I >> change, and how to submit the code to community? Because openoffice source >> code project is different from the conventional project. >> Shenfeng told me that you have a lot of experience on Writer, so I >> think you can tell me more details, thanks all of you >> Yi >> >> >> >> >> >> >> At 2013-01-07 21:31:53,"Fan Zheng" <zheng.easy...@gmail.com> wrote: >> >Welcome in anytime. >> > >> >2013/1/7 2 <laoyi...@126.com> >> > >> >> Hi Fan Zheng, >> >> Thank you for your help! >> >> I am so luck to get the link: >> wiki.services.openoffice.org/wiki/Writer, >> >> it is very useful, I will read it throughly,I will ask you If I have >> >> questions >> >> >> >> Kind regards >> >> Yi >> >> >> >> At 2013-01-07 11:40:38,"Fan Zheng" <zheng.easy...@gmail.com> wrote: >> >> >So happy that got a new comer from China, and interested in SW! >> >> >I encourage you take a look on the WIKI page about the technical >> design of >> >> >SW, which maybe helping you understanding the whole stuff. But >> >> >occasionally, the AOO WIKI will be unavailable, so good luck… >> >> >Here is the link: wiki.services.openoffice.org/wiki/Writer. >> >> >Follow the describes of the issue you picked up, I guess the issue is >> >> >related to the document nodes arrangement, for you reference. >> >> >Thanks! >> >> >在 2013/1/7 10:49 AM，"2" <laoyi...@126.com>写道： >> >> > >> >> >> Hi Regina, >> >> >> >> >> >> I am interested in >> >> >> Bug 97481 -Undo on sorting in nesed tables crashes Writer >> >> >> >> >> >> >> >> >> Kind regards >> >> >> Yi >> >> >> >> >> >> At 2013-01-07 07:00:43,"Regina Henschel" <rb.hensc...@t-online.de> >> >> wrote: >> >> >> >Hi Yi, > >2 schrieb: >> Hello All, My name is Yi, from China, >> >> interested >> >> >> in joining the >> opensource community to gain some experience. My >> >> interest >> >> >> lies in >> C++. I have got my own build on Windows XP with a MSVC >> 2008 >> >> >> Express >> .I am interested in Writer. What can I do next? > >You >> can >> >> look >> >> >> into Bugzilla [1], whether there is a bug, that you are >> >interested in. >> >> >> Use the 'Advanced search'. You can narrow the search by >project >> "word >> >> >> processor" and by a component. Severity should be >'trivial' or >> >> 'minor', >> >> >> so that there is no pressure to fix it. The status >should be >> >> 'Confirmed', >> >> >> so that you are sure it is really a bug and not >an user error. >> You can >> >> >> also use 'Accepted', if the last activity is more >than two years >> ago, >> >> >> because that was before the move to Apache. If you >have found one >> (or >> >> >> more) issues you are interested in, then tell it >here. The >> experienced >> >> >> developers can likely judge, whether such b >> >> >> ug is >suitable to begin and they can give you a hint, where to >> start >> >> in >> >> >> the code. > >We have quite recently introduced a category >> "Difficulty", >> >> so >> >> >> there are >only few issues at all already sort in and therefore >> "easy" >> >> has >> >> >> only few >bugs. If it need not be Writer, you might find suitable >> >> issues >> >> >> via this >category too. > >[1] >> https://issues.apache.org/ooo/query.cgi >> >> >> > >
