GSoC wxUniv overall summary

[Sun]

Hi all,

This is the overall summary mail of GSoC wxUniv. The mail maybe relatively long,

but I think this is necessary if I want to make a clearly description.

The first part is technical relative issues.

*Tests:

When I start for wxUniv, I want to build and run the tests, try to find which

test is failed. But the tests could not even been build. So the first thing is

make the test of wxUniv could been build. After that, I am start to fix the

error and failures in the test.

For summary, according the weekly summary. In the time of GSoC, the errors and

failures reduced to 16. Total number of eliminated is 80.

-Note:

--The initial test result only contain 308 tests. After I make some fixes. The

test could run 518 tests by now. So the number of fixed include the tests that

"reenabled".

--The number list in above just the fixed failures that we can count in weekly

summary, some of fixing not include it. For example, in one week, 308 total,

48 failed. I fixed 3, 45 failures left. Then re-enable 100 tests, 408 total,

40 left in the end of week. So I only count 8 fixed. Sorry about that, but I

didn't count it when I enable more tests in the middle of week. The number of

it may between 7-15. So the true number is bigger than 80.

--The number of fixed include the situation of "find the problem in wxUniv,

but the problem fixed in master branch", the listbox sorting issue is that case.

This impact 3 tests failures.

The remaining test result list in attached file[1]. And also have 3 tests

disabled. The MessageDialog in DialogTestCase, the ExecTestCase, The MenuEvent

function in Propagation test. Dialog is because wxInfoBar get segmentation

fault. ExecTestCase is because AddSourceFD not implement under wxX11. MenuEvent

is because it get segmentation fault that by unknwn reason...

*Sample:

The sample fixed could not count directly. And describe each one is too long.

But here I list the samples that improved/fixed:

Validate, Widgets, STC, Printing, VScroll.

The remaning sample issue list in attached file[2].

*Misc:

In the coding time, the biggest problem is clipboard support under x11. I don't

familiar with the clipboard mechanism under x11 at the beginning. The clipboard

nearly took me almost 2 weeks. But I think this is nessesary. And I write some

comments in x11 clipboard files. So the person who want continue to improve the

x11-clipboard will save time.

Appearance only have minor improvements. I want to add a new theme in coding

time.

*Plan:

I want to continue to make contribution after GSoC. I will create a new branch,

leave SOC2014_UNIV untouch from now.

After GSoC, I have several goals, list in below(Poriority from high to low):

*Use cairo replace xlib as drawing backend in wxUniv/x11.

*Fix the drawing issues that list in the sample result[2].

*Improve the appearance.

*Fix the rest of tests failures.

==================

To Catalin, Vadim, and the community.

I appreciated the opportunity to participate the project. Thanks for Catalin,

Vadim, and other friends to help me solve the technical problems.

I really enjoyed the coding time with community. Code for public felling

very good!

Catalin is a very responsible, patient, and polite mentor. Many times he point

the error or unsuitable things in code. And many times I argue with him about

technical route. I must admit: most of time, he was right.

During the time that we communicate, I'm not adapt for one thing at first.

That is: When I try to point or refer a generic thing, Catalin always ask:

"Which one?". But I adapt it when we communicate a lot. And I also try to not

refer generic things.

Vadim gave me a lot of help and information, let me know the mechanism and

internal things of wxWidgets. Without his help. I definitely could not solve

some problems.

I try to continue to make my contribution to wxUniv/x11. I want to know how

to make it possible after GSoC.

PS: Sorry for the grammar mistakes that in the content...

Regards,

Sun

[Igor Korot]

Sun,

Thank you for the contribution.
I followed closely as my current goal is to eliminate the really old
bugs as much as possible.
Some bugs are referred to X11 port and they are directly referenced to
this project. And some
are referred to Motif port which also uses many classes from wxUniv/wxX11.

The bug/ticket list can be found at trac.wxwidgets.org.
I will be waiting for a merge of you branch into the official
repository of wxWidgets and will verify
the outstanding bugs against you work.
Hopefully your project helped eliminate a lot of them and the ticket
list will be reduced even more.

Thank you.

>
> PS: Sorry for the grammar mistakes that in the content...
>
> Regards,
> Sun
>

> --
> To unsubscribe, send email to wx-dev+un...@googlegroups.com
> or visit http://groups.google.com/group/wx-dev
>

[Vadim Zeitlin]

On Tue, 19 Aug 2014 01:33:47 -0700 (PDT) Sun wrote:

S> This is the overall summary mail of GSoC wxUniv.

Hello,

Sorry for the delay with the reply, but I've only merged your branch into
svn trunk today, so it's now part of svn trunk, thanks for your work!

It's a bit disappointing that the minimal sample, which is really the
first thing anyone would try when testing wxWidgets, still doesn't really
work -- there are plenty of asserts when using menus and it crashes on
exit. Fixing this should IMHO really be the priority if we want people to
take wxUniv seriously and if you could look into this, it would definitely
be great.

TIA,
VZ

[Boxiang Sun]

Hi,

It's a bit disappointing that the minimal sample, which is really the
first thing anyone would try when testing wxWidgets, still doesn't really
work -- there are plenty of asserts when using menus and it crashes on
exit. Fixing this should IMHO really be the priority if we want people to
take wxUniv seriously and if you could look into this, it would definitely
be great.

I will continue to improve wxUniv. But I'm not have

enough time recently. But I will back in sometime, maybe two weeks.

I will create a new branch in my repo to continue to improve wxUniv. When

I archive a milestone, I will inform it in wx-dev. Then you or other friends

could review or merge it. Is that suitable?

Regards,

Sun

[Vadim Zeitlin]

On Wed, 24 Sep 2014 13:50:12 +0800 Boxiang Sun wrote:

BS> I will create a new branch in my repo to continue to improve wxUniv. When
BS> I archive a milestone, I will inform it in wx-dev. Then you or other friends
BS> could review or merge it. Is that suitable?

Yes, sure. You can also submit your patches to Trac as usual, which will
work fine if there are not too many of them. If you are going to make a lot
of changes, then using Github is indeed better.

TIA,
VZ

[Boxiang Sun]

Got it, thanks!

Regards,

Sun