http://permalink.gmane.org/gmane.comp.gnome.mono.documentation hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1989 <pre>Yeah, it is kind of obscuring everything else. In part, because any Linux user hitting a Silverlight site is being redirected there. Realistically, I think it can be ignored. On Wed, Jan 23, 2013 at 1:48 PM, Peter Newhook &lt;peter.newhook&lt; at &gt;gmail.com&gt;wrote: _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Miguel de Icaza 2013-01-23T20:06:44 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1988 <pre>Thanks, I had no idea moonlight was so popular. _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Peter Newhook 2013-01-23T19:48:47 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1987 <pre>This is the report of most visited pages: http://tirania.org/s/4fd24c90.png On Wed, Jan 23, 2013 at 1:07 PM, Peter Newhook &lt;peter.newhook&lt; at &gt;gmail.com&gt;wrote: _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Miguel de Icaza 2013-01-23T19:33:57 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1986 <pre>Is there a way to see the results of Google Analytics and what the most trafficked pages are? I'd like to know where to focus documentation efforts. _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Peter Newhook 2013-01-23T19:07:03 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1985 <pre>It is actually merely a problem with Xamarin. We have a series of products based on 2.10, and have not had a chance to revalidate them all on 3.0, and we do not want our users to get 3.0 by accident. We want to change that, just a matter of time. On Sat, Jan 12, 2013 at 11:19 PM, Peter Newhook &lt;peter.newhook&lt; at &gt;gmail.com&gt;wrote: _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Miguel de Icaza 2013-01-13T04:23:47 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1984 <pre>The download page, http://www.go-mono.com/mono-downloads/download.html, features 2.10.x as 'Stable' and 3.0.3 as 'Beta'. The roadmap (http://www.mono-project.com/Mono_Project_Roadmap) however lists the current release as 2.12 as the current release and confusingly points to to the Mono 3.0 release notes. There's also guidance that even numbered minor releases are stable, so 3.0 should be considered stable. Is 3.0 considered the proper public release and the documentation is just out of date? _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Peter Newhook 2013-01-13T04:19:01 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1983 <pre>Many thanks for all your great work. A note regarding documentation... This page: http://www.mono-project.com/Release_Notes_Mono_3.0 implies (in the section at the bottom titled "Installing Mono 3.0") that this page (which it links to) http://www.go-mono.com/mono-downloads/download.html contains "pre-compiled packages for Linux, Solaris, MacOS X and Windows" for Mono version 3 .... which it does not. (As at today, it contains packages for version 2.1, and a version 3.0 beta package for MacOSX.) Secondly, has anyone made pre-compiled version 3.0 installation packages for windows? Where can I get one? -- View this message in context: http://mono.1490590.n4.nabble.com/pre-compiled-version-3-0-installation-packages-for-windows-tp4657279.html Sent from the Mono - Documentation mailing list archive at Nabble.com. _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> gooisoft 2012-11-05T19:09:34 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1982 <pre>Hi everyone! Once again, the Mono team is happy to announce that we are participating in the Google Summer of Code 2012! Last year was a great success, and we hope this year will be even better! As usual, project ideas and rules are available on our GSoC page at http://mono-project.com/Gsoc . The ideas list has been updated throughout last week, so don't be surprised if some things have moved around or disappeared. Feel free to choose one or more ideas from that page, or come up with your own awesome idea and send us your proposal! This week is all about talking to developers and prospective mentors, discussing your ideas and getting feedback prior to the official student proposal submission phase, which starts on March 26th. Take this time to introduce yourself and get to know the community, and show us how excited you are about coding the summer away! :) This mailing list is a good place to start for Orchard and Documentation ideas. You can also find most devs over at the mono-devel (http://lists.ximi</pre> Andreia Gaita 2012-03-19T15:24:21 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1981 <pre>I tried to find out if a class was implemented but the page throws a lot of Javascript errors such as TreeView_HoverNode is not defined Example page: http://www.go-mono.com/status/status.aspx?reference=4.0&amp;profile=4.0&amp;assembly=System.Web _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Marvin 2011-06-18T10:21:03 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1980 <pre>Hi, I have just found an error in the online documentation about Threading (http://www.mono-project.com/ThreadsBeginnersGuide): In the example code for "Passing Parameters to Threads" with .Net 2.0, Thread myThread = new Thread (delegate (object myValue){ Thread.Sleep (1000); Console.WriteLine (String.Format ("The parameter have" + " a {0} in it's value", myValue)); } should be: Thread myThread = new Thread (delegate (object myValue){ Thread.Sleep (1000); Console.WriteLine (String.Format ("The parameter have" + " a {0} in it's value", myValue)); }); - adding ");" to the last line. Best regards, Marcel Buchholz _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Marcel Buchholz 2010-08-19T13:48:03 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1979 <pre> Could you try using 'mdoc update' instead? That's odd. I don't ever recall seeing this before. Your stack trace sadly doesn't contain line numbers, but EcmaHelpSource.MakeOperatorSignature() only throws it from one place: for overridden operators that weren't properly supported [0]. Perhaps you could provide the XML file that generates the error (or otherwise let us know which operator we're not checking for)? Thanks, - Jon [0] http://anonsvn.mono-project.com/source/branches/mono-2-4-3/mcs/tools/monodoc/Monodoc/ecma-provider.cs _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Jonathan Pryor 2010-04-25T20:53:12 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1978 <pre>_______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Alan Freed 2010-04-24T10:18:50 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1977 <pre> Don't do that. 'cardinal-doc/index.xml' is supposed to contain all the types that are within the assemblies you're documenting. However, it is regenerated each time 'mdoc' runs, and contains only those assemblies which are being processed for that invocation. Result: your second 'mdoc update' command causes index.xml to "lose" all the types that were added by the first 'mdoc update', and the third overwrites the second invocation, and... There are two ways to handle multiple assemblies: 1. List all the assemblies at the same time, thus allowing index.xml to properly contain all the types within the documentation index: mdoc update -o cardinal-doc Cardinal.exe Cardinal.Core.dll \ Cardinal.Interfaces.dll Cardinal.Services.dll 2. Have multiple mdoc repositories, one per assembly: mdoc update -o cardinal-docs/Cardinal Cardinal.exe mdoc update -o cardinal-docs/Cardinal.Core Cardinal.Core.dll # ... I follow (2) within http://gitorious.org/cadenza, placing documen</pre> Jonathan Pryor 2010-02-22T21:44:17 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1976 <pre>Around this time last year, Koushik Dutta and Marc Crichton were doing some cool stuff with Mono on Android, demonstrating a complete working stack and running DLR examples from a simple command prompt. Since then, however, I've had a lot of trouble finding more recent information about what's been happening. See, e.g.: * http://www.koushikdutta.com/2009/01/mono-on-android-with-gratuitous-shaky.html * http://www.koushikdutta.com/2009/01/dalvik-vs-mono.html * http://www.koushikdutta.com/2009/01/building-mono-for-android.html If I wanted to write something in C# today and have it run on Mono on my Android device, what's the easiest way to do this? ~ jf -- John Feminella Principal Consultant, Distilled Brilliance _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> John Feminella 2010-01-31T21:14:47 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1975 <pre> Yes (these are source) and No (they are ALSO generated). Behold the power of XML! Or something. Both humans and mdoc process the *same* XML files. mdoc will add and remove &lt;Type/&gt; and &lt;Member/&gt; elements from the XML (as types and members are added and removed from the assembly), and a whole host of other things. The *only* elements that should be edited by hand are the //Docs elements, and mdoc is written to not change the contents of these nested elements [0]. In general, it seems to work. Yes. Yes. Maybe; depends on the project, and which you want to use as the "canonical source" -- which should people edit, the inline XML or the mdoc repository XML? Having both be "canonical" is a recipe for confusion. (Not to say that this should NEVER be done, but just be careful about it [1].) Mono wants the canonical source to be the **/Documentation/en/* files; other projects may want the canonical source to be inline XML. This will vary by project. You can also use 'monodoc --edit' to *view* the </pre> Jonathan Pryor 2010-01-20T14:36:42 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1974 <pre>Thanks very much for that info, Jonathan; it was immensely helpful. I hope you won't mind if I follow up with a few clarifying questions: * Are these source and not generated files? That is, it was my understanding is that things in a path matching **/Documentation/** are generated by an external documentation-generation tool. If someone later updated the source, wouldn't that cause problems with the resulting generated files? Is this a mistaken view? So, to me it sounds like the take-away conclusion to draw from your earlier e-mail are: * Don't use `monodoc --edit`. * Do use `mdoc update` + documentation stubs. * Maybe use inline XML + `mdoc update -i MyType.xml`. * Chug out docs by filling out the stubs mdoc generates. You can use `mdoc export-html` to see how it all looks once you're making progress. * Find an assembly or two (or perhaps even an ancillary project like Cadenza) and just jump right on it, mailing relevant patches to the appropriate committers as needed. Is that about the gist of it</pre> John Feminella 2010-01-20T05:26:54 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1973 <pre> There's a problematic history here; at one point in time (and currently, afaik) you could edit documentation within the 'monodoc' GUI browser, then upload those contributions via Contributing-&gt;Upload Contributions. There are two problems with this: first, the monodoc editor sucks (at least it does for me [0]), and second, we found that we had to manually review all contributions, as very often people would copy &amp; paste MSDN documentation into monodoc and submit it. The review process is (of course!) manual, was done by miguel, and, well, afaik it overtook him ages ago. The process hasn't changed; we need a better process, but at present no one has had the time/inclination to create said better process (especially a process that can properly deal with copy/paste issues). It may very well be intractable, at least for BCL types. Fortunately monodoc isn't the only way to write documentation... Depends on how you contribute. :-) As mentioned above, monodoc-&gt;Upload Contributions is currently a no-mans land</pre> Jonathan Pryor 2010-01-19T19:10:30 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1972 <pre> hi David thank you for you instruction for user of fedora 9 distro I have been follwoing the step as you wrote But I faced some bug when I update xsp from fc7 to fc9 The command "#yum install --enabledrepo=rawhide xsp" occurs AttributeError The error says AttributeError: 'NoneType' object has no atttribute 'cursor' What can I solve this bug? Any advice do you have? thanks </pre> hapiten 2010-01-14T09:12:16 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1971 <pre>hello Mono-doc-ers, As a relatively avid technical user of Mono and longtime developer, I'd like to give back a little to the Mono documentation. I consider myself relatively adept at constructing technical documentation and things of that sort, so I think tackling a few high-value targets could be beneficial to the community. However, I'm a little bit perplexed about the best place to start. The main Mono pages don't have much to say about the best way to contribute documentation or even the best way to get started with such contributions (e.g. "here's how to set up mdoc so that you can identify areas of spotty coverage" or "here's a link to our continuous-integration reports so that you can see which parts need working on"). I tried a few Google searches to this effect but still didn't turn up anything. (Did I miss a wiki page that has all this somewhere?) When in doubt, hit the mailing list, so here I am with my questions: * Are contributions to the documentation currently being accepted? * How shoul</pre> John Feminella 2010-01-18T20:11:35 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1970 <pre>Playing around with mdoc a little more, I think the best scenario for me right now is to use it as part of the build with -i and --delete options and keep the docs inline for now. I'd forgotten how much I rely on Intellisense for crefs's etc. I guess I'm too much of a Visual studio integration dependent to let me separate my docs from my code until i can make the experience smoothly integrated. Very glad that -i works on repeated imports, so that allows me to use mdoc anyhow. It's a very smooth experience! thanks, Arne Claassen MindTouch San Diego, CA http://twitter.com/sdether On Jan 12, 2010, at 11:45 AM, Jonathan Pryor wrote: _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Arne Claassen 2010-01-12T21:38:31 http://permalink.gmane.org/gmane.comp.gnome.mono.documentation/1969 <pre> True, but if you warn on 'To be added,' that's not actually a problem -- you'll still get a warning/error. Yeah. Semantics. What's "properly documented," particular in a manner that a computer can understand, check for, and enforce. :-) - Jon _______________________________________________ Mono-docs-list maillist - Mono-docs-list&lt; at &gt;lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-docs-list </pre> Jonathan Pryor 2010-01-12T19:45:53 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnome.mono.documentation