Xaml Compiler: SoC Closure status report

Hello folks.

It is now September the Second, 2005, local time, so I'm late, but it's
the antipodes, so there's lots of time relative to those Other Timezones
that aren't holes and I suppose therefore I'm actually running early.

We weren't asked for a final report, but I figure I may as well, so here
it is.

Last time was penultimate, so this is, I suppose, ultimate. How extreme.

I've just made a few changes (mostly to make the code more
comprehensible, at least in theory) and I now think the code is
satisfactory for SoC purposes. I consider the xaml stuff in revision
49270 of the mono svn repos to be the "End Of SoC" revision, I hope
that's vaguely reasonable.

There's a few things that I still plan to do, and I do want to push it
to try to get some use.

Here's what's done:

1. A complete compiler from xaml to code, no known bugs
2. A near-complete interpreter from xaml to an object instance - there's
one feature I only found on monday, which is supported in the compiler
but has a bug in the interpreter. I plan to find and fix that bug
soon-ish, but since the feature is useful mainly for supporting the
styling system I don't see it's lack hurting many people for the time
being. That's the only bug I know of.

Re: Xaml Compiler: SoC Closure status report

On Fri, 2005-09-02 at 00:57 +1000, Iain McCoy wrote:
> I've just made a few changes (mostly to make the code more
> comprehensible, at least in theory) and I now think the code is
> satisfactory for SoC purposes. I consider the xaml stuff in revision
> 49270 of the mono svn repos to be the "End Of SoC" revision, I hope
> that's vaguely reasonable.

And from the spoke-too-soon department, I just realized that I'd
forgotten to add a file to svn. Oops. There were two other forgotten
files as well; they were all boring, but they're in there now. The
revision with those added is r49275; if the stuff doesn't build, there's
probably some other forgotten file. I don't think there is, but I'm not
certain. Let me know if that's the case.

See you later folks,
-Iain

DataGridView: Final report

Hello,

Here is my final report.

I've finished almost all things I've planned and I've tested the
features I've implemented as much as i could.

The files to see my work:

DataGridview.tar.bz2:
    http://pedromj.dyndns.org/publico/DataGridView.tar.bz2

README:
    http://pedromj.dyndns.org/publico/README

TODO:
    http://pedromj.dyndns.org/publico/TODO

DataGridView.diff:
    http://pedromj.dyndns.org/publico/DataGridView.diff

Please take a look at README file, it is explained how to get working
the sources. In the TODO file there is the list of thigs not fully
implemented now.

To "winforms-list":
Please take a look to all of this stuff and if you are not disagree with
this I'll commit to SVN in two or three days, thank you. I will continue
with the developing and the bug fixes of all classes related to

DataGridView: Final report

Hello,

Here is my final report.

I've finished almost all things I've planned and I've tested the
features I've implemented as much as i could.

The files to see my work:

DataGridview.tar.bz2:
    http://pedromj.dyndns.org/publico/DataGridView.tar.bz2

README:
    http://pedromj.dyndns.org/publico/README

TODO:
    http://pedromj.dyndns.org/publico/TODO

DataGridView.diff:
    http://pedromj.dyndns.org/publico/DataGridView.diff

Please take a look at README file, it is explained how to get working
the sources. In the TODO file there is the list of thigs not fully
implemented now.

To "winforms-list":
Please take a look to all of this stuff and if you are not disagree with
this I'll commit to SVN in two or three days, thank you. I will continue
with the developing and the bug fixes of all classes related to

The last bug finding run of the SoC

I ran the double-check locking detector and the bad recursive invocation
detector on the rest of the Mono class libraries. Here are the cases
that look like potential bugs to me (minus the ones I've already
reported). They may or may not really be bugs, on closer inspection.

===================== BAD RECURSION =============================

Commons.Xml.Relaxng.dll
-----------------------------------
Commons.Xml.Relaxng.Inference.RelaxngInference::get_TypeInference
Commons.Xml.Relaxng.Inference.RngInference::ProcessSequence (probably fine)

System.DirectoryServices.dll
----------------------------------------
System.DirectoryServices.SearchResultCollection::Contains

System.Windows.Forms.dll
------------------------------------
System.Windows.Forms.VScrollBar::set_RightToLeft
System.Windows.Forms.DataGrid::CreateGridColumn
System.Windows.Forms.ProgressBar::set_BackColor
System.Windows.Forms.ProgressBar::set_BackgroundImage
System.Windows.Forms.ProgressBar::set_CausesValidation

===================== DOUBLE-CHECK LOCKING ======================

IBM.Data.DB2.dll
----------------------------
IBM.Data.DB2.DB2Environment::get_Instance

Re: XBuild status report #8

Re: XBuild status report #8

Dnia 01-09-2005, czw o godzinie 14:19 -0400, miguel de icaza napisał(a):
> Marek,
> 
>      How can I build xbuild?  
> 
>      How can I test the code?
> 
>      Am now reviewing all the projects
> 

You can load MonoDevelop solution and build it. Then it will make .dll
files and .exe file in xbuild/bin/Debug which you can use to run
'xbuild' in main module directory. This should build it once again using
xbuild this time.

Next thing are various task. You add what you want to <Target> element
like <Message> etc. Should I write .csproj tests for each task?
Generally tasks should be documented on MSDN. Samples for them should be
working. If you are writing separate test you should <Import> file that
contains all UsingTask definitions. Conditions aren't working.
Transforms should work. 

> Miguel.
--

-- 
Marek Sieradzki <marek.sieradzki <at> gmail.com>

Re: XBuild status report #8

Dnia 01-09-2005, czw o godzinie 14:19 -0400, miguel de icaza napisał(a):
> Marek,
> 
>      How can I build xbuild?  

There is MonoDevelop solution. In xbuild/bin/Debug there should be final
program. You must replace paths like "/media/xbuild" with path that
leads to it on your computer. Next you can build Microsoft.Build.csproj
file using xbuild. It won't be properly opened in VS2005 because it's
not VS2005 format. However it should build under msbuild.
> 
>      How can I test the code?
In Microsoft.Build.Tasks there are tasks classes. Every one of them
should have documentation in MSDN. Example from MSDN should work.
(GenerateResource have additional abilities because it was based on
monoresgen)
> 
>      Am now reviewing all the projects

Additional information: Conditions aren't working. Transforms are
working.
> 
> Miguel.
--

-- 
Marek Sieradzki <marek.sieradzki <at> gmail.com>

Re: XBuild status report #8

Re: XBuild status report #8

Dnia 01-09-2005, czw o godzinie 15:42 -0400, miguel de icaza napisał(a):
> Hey,
> 
>         There is MonoDevelop solution. In xbuild/bin/Debug there
>         should be final
>         program. You must replace paths like "/media/xbuild" with path
>         that
>         leads to it on your computer. Next you can build
>         Microsoft.Build.csproj
>         file using xbuild. It won't be properly opened in VS2005
>         because it's 
>         not VS2005 format. However it should build under msbuild.
> 
> 
> For the sake of integrating this in the future into Mono proper, could
> you provide a Makefile that creates XBuild?

I don't have experience in making makefile especially with those which
use autotools. I can try.
> 
> 
>         In Microsoft.Build.Tasks there are tasks classes. Every one of
>         them
>         should have documentation in MSDN. Example from MSDN should
>         work. 
>         (GenerateResource have additional abilities because it was
>         based on
>         monoresgen)
> 
> 
> Do you have some .xbuild or .build files we can try also?
>  
I had some but I always tested using one file. I removed previous
entries and used next task. I'll make some files for tasks today but now
I'm going to school. :)

> 
>         Additional information: Conditions aren't working. Transforms
>         are
>         working.
> 
> 
> Excellent!

--

-- 
Marek Sieradzki <marek.sieradzki <at> gmail.com>