ityPermissionFlag.UnmanagedCode specified in order to perform a
P/Invoke.
Programs can't specify this permission, though, they can only request it
(or demand it, and if they can't get it, a SecurityException is
thrown).
Administrators are the people who specify what permissions an
You need:
1. A working mono installation (mcs compiler, etc.).
2. The gtk-sharp CVS module
3. The monodoc CVS module
Compile and install gtk-sharp:
gtk-sharp$ ./autogen.sh --prefix=YOUR INSTALL PREFIX/
gtk-sharp$ make
gtk-sharp$ make install
Compile and install
The latest draft for my managed/unmanaged code interop
documentation is available for perusal at:
http://www.jprl.com/~jon/interop.html
I feel like I'm writing a chapter for a book. It would be nice,
actually; I have yet to see all this information in one place.
Please review. I'd
Well, there *used* to be http://www.go-mono.com/docs/
The difference was that :8080 ran with XSP, and /docs/ ran with
mod_mono. Or vice versa, I forget.
But /docs/ is not running at the moment.
Miguel: can you see why /docs/ isn't running anymore, and re-enable it
if possible?
Thanks,
- Jon
On Mon, 2004-01-26 at 14:36, Miguel de Icaza wrote:
Hey guys,
I had the impression that we had agreed to use the MIT X11 license
for the Monkeyguide instead of the GNU FDL, is that correct?
(the GNU FDL not being free documentation and all that).
Miguel.
Sort of. IIRC, the
Issues, bugs, whatever. They're annoying me. :-)
I'd look into fixing them, but I'm busy painting a house, so...
1. MonoDoc doesn't like properly escaped XML code.
That's the short of it, anyway. Nothing is displayed if I have
documentation like this:
example
code
On Sun, 2004-07-04 at 15:50, Brian Kerrick Nickel wrote:
1. MonoDoc doesn't like properly escaped XML code.
I haven't checked it but this may not be the case. The lt; and gt;
entities need to be defined in the XML doctype. If they aren't defined,
they are invalid and result in broken XML.
I'm thinking of the future, of documenting Mono.Posix. :-)
However, as much of Mono.Posix is just a wrapping over existing
functions, most of which already have their own man pages, I see little
point in duplicating all of this documentation. Thus, two questions:
1. Does monodoc support man
On Tue, 2004-10-26 at 08:10, Joshua Tauberer wrote:
Jonathan Pryor wrote:
1. Does monodoc support man pages yet? If not, when will it?
It would only work in Unix, then. Are the man pages licensed in such a
way as to allow their embedding in Monodoc? That'd be easier, and it
would
-r1.139 ChangeLog
--- browser/ChangeLog 3 Nov 2004 07:26:25 - 1.139
+++ browser/ChangeLog 5 Nov 2004 01:18:44 -
@@ -1,3 +1,13 @@
+2004-11-04 Jonathan Pryor [EMAIL PROTECTED]
+
+ * colorizer.cs: If a language is unrecognized, escape the XML so that it
+ will be properly rendered within
I was getting a NullReferenceException when running
monodocer -assembly:/path/to/Mono.Posix.dll -path:docs/dir
Because Type.Namespace was null within monodocer.cs:GetTypeFileName due
to the internal Locale class. I've committed a patch to avoid the
exception (revision 39775).
Thanks,
On Sat, 2005-02-12 at 17:37 -0500, Miguel de Icaza wrote:
Hey,
Might I suggest mono-tools? It already exists, Type Reflector is
already in it (as is the debugger, but that can change if necessary),
and it has a prototype .spec file for RPM builds.
Mhm, I checked this out today and it
I've encountered two bugs when using `monodoc`:
1. I can't edit namespace summaries (this also exists when not using
--edit as well). For example, select the Class Library/System node,
which displays the text:
The System namespace contains the fundamental types of the
On Mon, 2005-06-06 at 10:33 +0200, Fabian wrote:
just tried to see monodoc's Gtk# browser's code, and I didin't find it
in svn repository.
It was moved out of the `monodoc' module and into the `mono-tools'
module, under the docbrowser directory. See:
On Wed, 2005-08-17 at 21:08 +1000, warwick LAKE wrote:
Help!.. I need the manuals to mono C#, something
like..
The Idiots Guide To The Mono C# Compilor.
What *precisely* do you want to know about Mono C#?
The command line arguments are described within the man page, and are
100% compatible
On Fri, 2005-11-04 at 14:48 +0100, Enrico Zini wrote:
An obvious one would be devel::dotnet, which would be widely recognized.
However we aren't sure if there are trademark issues, nor if in the
Linux world we prefer a different name. If there are not problems with
devel::dotnet, we would go
On Fri, 2006-04-28 at 00:49 -0400, Nate Chadwick wrote:
Reading this was the first time I noticed that the go-mono.com site
was a wiki. It doesn't seem like the create account function works.
Is that by design?
On Mon, 2006-06-19 at 23:17 +0200, Alexandre Grin wrote:
string ui_info =
menubar\n +
menu name=\MenuFile\ action=\firstMenu\ \n +
...
But Monodoc doesn't like it because there are xml structure in it...
Does anyone know how I can get the stuff?
Escape the XML
On Wed, 2006-09-20 at 19:26 -0400, Joshua Tauberer wrote:
Jonathan Pryor wrote:
Attached is a patch to support to monodocs2html for cross-type
hyperlinks.
Skimming it, it looks ok to me. I'm glad to see that problem fixed.
So, does that count as permission to commit? :-)
- Jon
On Wed, 2006-09-20 at 21:30 -0400, Jonathan Pryor wrote:
On Wed, 2006-09-20 at 19:26 -0400, Joshua Tauberer wrote:
Jonathan Pryor wrote:
Attached is a patch to support to monodocs2html for cross-type
hyperlinks.
Skimming it, it looks ok to me. I'm glad to see that problem fixed
At the URL below is a patch to monodoc/tools to add support for Generics
to monodocer.exe and monodocs2html.exe. (Next stop: adding support for
Generics to the documentation browser.)
The patch is available at:
http://balthasar.jprl.com/~jon/tmp/monodoc-tools.patch
The monodocer.cs
On Sun, 2006-10-01 at 07:24 -0400, Joshua Tauberer wrote:
Hey, Jon.
Very nice.
I won't have a chance to look at the patch for a few days but I had two
comments:
The one breaking change to monodocer.exe is that '+' is no longer used
for nested types, but '.' is used instead. That is:
On Sat, 2006-09-30 at 20:37 -0400, Jonathan Pryor wrote:
At the URL below is a patch to monodoc/tools to add support for Generics
to monodocer.exe and monodocs2html.exe. (Next stop: adding support for
Generics to the documentation browser.)
The patch is available at:
http
On Tue, 2006-10-03 at 07:59 -0400, Joshua Tauberer wrote:
Jonathan Pryor wrote:
At the URL below is a patch to monodoc/tools to add support for Generics
to monodocer.exe and monodocs2html.exe. (Next stop: adding support for
Generics to the documentation browser.)
Looks like I should have
I see that you committed your changes, and I'm seeing changes that I
don't understand.
For example, after running the check-monodocer test I see:
- Base
-BaseTypeNameSystem.Object/BaseTypeName
- /Base
+ Base /
+ BaseTypeNameSystem.Object/BaseTypeName
But I don't see any explanation for
On Tue, 2006-10-10 at 07:37 -0400, Joshua Tauberer wrote:
Jonathan Pryor wrote:
I see that you committed your changes, and I'm seeing changes that I
don't understand.
For example, after running the check-monodocer test I see:
- Base
-BaseTypeNameSystem.Object/BaseTypeName
Attached is a patch + unit tests which adds Docs/since elements to any
type/member which was not present in the previous version.
The basic logic is as follows:
- If index.xml exists, read all of the /Overview/Assemblies/Assembly
elements, and store the found @Name and @Version attributes.
On Wed, 2006-10-11 at 06:57 -0400, Joshua Tauberer wrote:
Jonathan Pryor wrote:
(2) Command-line argument approach: add a ``--since name+version=tag''
argument, and if an assembly matching name+version is encountered,
create a since/ element for any *added* types and members.
Rethinking
On Wed, 2006-10-11 at 14:08 -0500, Mike Kestner wrote:
On Wed, 2006-10-11 at 07:28 -0400, Jonathan Pryor wrote:
We could just do `--since Gtk# 2.10', and all new types/members would
get a since version=Gtk# 2.10 / element inserted. It would *only*
apply to added types/members
On Wed, 2006-10-18 at 08:33 -0400, Miguel de Icaza wrote:
email message attachment, Forwarded message - [Mono-dev] monodocer
fails to import slashdoc in 1.1.18
mono 1.1.18 adds generics support for monodocer. Unfortunately,
'importslashdoc' seems to be broken: inline documentation extracted
On Wed, 2006-10-18 at 08:33 -0400, Miguel de Icaza wrote:
email message attachment, Forwarded message - [Mono-dev] monodocer
fails to import slashdoc in 1.1.18
mono 1.1.18 adds generics support for monodocer. Unfortunately,
'importslashdoc' seems to be broken: inline documentation extracted
Currently mdvalidator doesn't like the documentation for generic
types/members, as the XSD that mdvalidator uses hasn't been updated for
the new XML tags like typeparam/. This is to be expected.
However, some non-ECMA tags were added to the output of monodocer, in
particular the
On Wed, 2006-11-01 at 05:50 -0500, Joshua Tauberer wrote:
typeparam duplicates TypeParameters in just the same way param
duplicates Parameter. It happens to be particularly useful when
(type-)parameter names change: It's trivial for monodocer to update the
(Type)Parameter nodes (by deleting
===
--- engine/ChangeLog (revision 67248)
+++ engine/ChangeLog (working copy)
@@ -1,3 +1,19 @@
+2006-11-01 Jonathan Pryor [EMAIL PROTECTED]
+
+ * Makefile.am: Add check, check-validate, check-validate-update targets.
+ * monodoc-ecma.xsd: Update for ECMA-334 and ECMA-335
On Thu, 2006-12-14 at 19:13 +0100, latency wrote:
as I'm working pretty much with the System.Windows.Forms namespace I thought
it would be great to have it's documentation in the mondoc browser.
So I tried to run monodocer and generate the documentation but monodcer fails
and displays the
On Sun, 2006-12-17 at 09:50 +0100, latency wrote:
as I said, I've managed to include the SWF documentation into monodoc. But
that would be a solution which is only available to me. But my intention was
it to find a way where SWF documentation would be shipped with monodoc
automatically.
On Mon, 2006-12-18 at 16:35 -0500, Miguel de Icaza wrote:
We have discovered something in Moma that is probably important to look
into.
In 2.0, a number of new overrides were done, for example, consider
Windows.Forms' Button override for OnMouseEnter:
protected override void
On Sun, 2007-11-25 at 13:56 +0100, Valentin Sawadski wrote:
On Sat, 2007-11-24 at 14:25 -0500, Jonathan Pryor wrote:
On Sat, 2007-11-24 at 16:16 +0100, Valentin Sawadski wrote:
I don't like that idea because this might introduce some since x,
removed in y, reintroduced in z patterns
On Sun, 2007-11-25 at 09:28 -0500, Jonathan Pryor wrote:
The monodocer part should be a fairly minor change, probably 100 LOC.
(Probably 20.) The browser part will be somewhat more involved,
mostly as it deals with XSLT, but I don't think it will be terribly
difficult either.
Sadly, I'm
On Mon, 2007-12-03 at 15:26 -0500, Miguel de Icaza wrote:
I spoke with Lluis Sanchez about using Mono.Addins to extend the
documentation system and it seems a good approach because we will get
all the subsytem for documentation updates and managment (both for
providers and for doc sources)
On Tue, 2007-12-04 at 18:33 +0100, Mario Sopena Novales wrote:
By the way, your changes about adding AssemblyInfo to every members
sounds good to me. The only problem I see is what to do with the
already since tag that we have. Does the implementation collide in
some way?
They don't
On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
I recently tried to work on the generics support in monodocer and
noticed that it has names one and the same type differently.
Eg: If i have a public class TestT monodocer will produce the
following output.
index.xml:
...
On Sun, 2007-12-09 at 12:11 +0100, Mario Sopena Novales wrote:
On 08/12/2007, Jonathan Pryor [EMAIL PROTECTED] wrote:
On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
But then again it seems that the browser uses the Testlt;Tgt;
everywhere. Sometimes it gets parsed
On Sat, 2007-12-08 at 11:03 -0500, Jonathan Pryor wrote:
On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
To streamline all these naming issues my proposal is to use the Test`1
Notation everywhere to be more coherent with the output of Type.Name and
not to introduce too much C
On Mon, 2007-12-10 at 18:12 +0100, Valentin Sawadski wrote:
On Sat, 2007-12-08 at 11:03 -0500, Jonathan Pryor wrote:
Consider:
delegate R FuncR ();
delegate R FuncR,P (P p);
delegate R FuncR,P1,P2 (P1 p1, P2 p2);
Which results in Func`1, Func`2, and Func`3, vs. FuncR
On Mon, 2007-12-10 at 17:57 +0100, Valentin Sawadski wrote:
By the way I think it should be pretty easy to extend monodocer to
generate TypeSignature / and MemberSignature / tags for different
languages. (Like MS does within their docs) This could probably be done
by using Mono.Addins so that
On Sun, 2007-11-25 at 22:05 -0500, Jonathan Pryor wrote:
Attached is a preliminary patch to add this support. The monodocer
change is 66 lines, and generates output like the attached
Environment.xml. monodocs2html has also been updated; Environment.html
is the current output.
I should
On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
But then again it seems that the browser uses the Testlt;Tgt;
everywhere. Sometimes it gets parsed and will be displayed as TestT
but other times not and some ugly HTML-Entities are being shown as the
class name.
After looking into
On Wed, 2007-12-12 at 05:57 -0500, Jonathan Pryor wrote:
On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
But then again it seems that the browser uses the Testlt;Tgt;
everywhere. Sometimes it gets parsed and will be displayed as TestT
but other times not and some ugly HTML
Mike: Didn't GtkHtml# always bind gtkhtml-3.0? Or did it bind 2.x at
some point in time?
On Sat, 2007-12-15 at 13:30 +0100, Mario Sopena Novales wrote:
On 12/12/2007, Jonathan Pryor [EMAIL PROTECTED] wrote:
Perfect test case:
1. Start Monodoc.
2. Click File - Lookup URL, or type Ctrl+L
On Wed, 2007-12-19 at 19:43 +0100, Valentin Sawadski wrote:
On Wed, 2007-12-19 at 13:33 -0500, Jonathan Pryor wrote:
I can't reproduce this. What I'm doing:
1. Navigate to System.Array.BinarySearchT(T[],T).
2. Within the Right pane, Click the IComparablelt;Tgt; link above
While trying to update the contents of monodoc/class, I ran into a
problem: Npgsql contains the following types in the root () namespace:
NpgsqlRowUpdatingEventArgs, and NpgsqlRowUpdatedEventArgs.
The problem is twofold:
1. monodocer generates an error and exits if it sees such a type.
2. What
On Thu, 2007-12-20 at 12:19 +0100, Valentin Sawadski wrote:
Is it possible that the links you're clicking which lead nowhere are of
this malformed type?
No, I checked the console output, it prints:
Trying: T:System.IComparableT
+--+
| Here we
On Tue, 2007-12-25 at 20:55 +0100, Steve Wagner wrote:
Hi, currently i can not checkout the trunk on windows, because in
/monodoc/class/System.Security/en are an file with name
System.Security.Cryptography.Xml and an folder with the same name.
If i try to check out, ive allways get an object
On Wed, 2007-12-26 at 10:32 -0500, Miguel de Icaza wrote:
Suggestions? All I can suggest is that namespace XML files should
contain some character/string that namespaces are highly unlikely to
contain, e.g. instead of en/System.xml for the XML documentation on
the System namespace, use
Joshua et al,
You wrote and contributed to the monodoc module many related
utilities, such as monodocer, monodocs2html, etc., in addition to
monodoc/engine and related documentation providers.
The monodoc module currently claims to be under the GPL, as does
`monodocer --version` and
On Tue, 2008-02-05 at 13:26 +0100, Stefan Noack wrote:
I'm not sure whether this problem is subject to this list but I didn't
find a better place to report my problem.
mono-docs-list is the normal place for this.
I use monodocer with -importslashdoc to import XML documentation from
the files
On Tue, 2008-02-05 at 18:09 +0100, Stefan Noack wrote:
What version of mono is this?
This is strange. I use mono 1.2.6 and the monodoc 1.2.6 gentoo ebuild
which afaik contains monodocer. But it looks strange, though:
[EMAIL PROTECTED] ~/prog/liblamp/trunk $ monodocer --version
Monodocer
On Thu, 2008-02-21 at 06:58 -0500, Joshua Tauberer wrote:
Why not just merge all of the tools into a mdoc.exe (with the new
options parsing library to boot), rather than wrapping them all with a
script?
Because that would imply removing the older tools, which would break any
number of
On Fri, 2008-02-22 at 13:16 +0100, Mario Sopena Novales wrote:
Hi,
the attached path fices the problem with namespaces that cannot be
edited right now as states bug #319116.
Unfortunately, you must rebuild the docs to see it working, because
the editing infrastructure put some
On Fri, 2008-02-22 at 18:08 +0100, Mario Sopena Novales wrote:
Index: provider.cs
===
--- provider.cs (revisión: 96411)
+++ provider.cs (copia de trabajo)
@@ -609,9 +609,13 @@
}
}
-
I've just committed a patch which merges the commonalities between
monodoc/engine/mono-ecma-css.xsl and mono-ecma.xsl into
mono-ecma-impl.xsl, thus allowing most of the code to be shared between
them. This change also improves some of the CSS used so, visually, it
looks unchanged. :-)
If anyone
On Tue, 2008-03-11 at 15:42 -0400, Jonathan Pryor wrote:
Up next I plan on making monodoc/engine/mono-ecma-impl.xsl more like
monodoc/tools/stylesheet.xsl, in particular generating CREF-style
hyperlinks instead of...whatever you want to call the current output.
This will change links
One of the things I'd like to do before the Mono 2.0 release is migrate
monodoc.dll to use C# 2.0 features such as generics in the public API.
For example, instead of Monodoc.Node.Nodes being an ArrayList, it should
be an IEnumerableNode or IListNode, and Monodoc.Node should
implement
On Sun, 2008-06-22 at 21:16 -0700, visor wrote:
I've been looking lately at the mono documentation on the mono website and
even when the msdn documentation is, most of the time, enough for mono
users, I think we should have our own documentation build since many users
see this lack of
This is a heads-up that the monodoc mcs modules are merging for the
Mono 2.2 release.
Why?
The largest reason is so that documentation is closer to the source, in
the hopes that someone other than me will actually update the
documentation stubs and write documentation for the class libraries.
On Sat, 2008-10-18 at 13:10 +0200, Mirco Bauer wrote:
On Fri, 17 Oct 2008 21:10:38 -0400
Jonathan Pryor [EMAIL PROTECTED] wrote:
Unanswered Questions:
What should be done about monodoc/engine/web, the ASP.NET frontend to
monodoc documentation? I don't believe that it's actually
On Sun, 2008-10-19 at 10:20 -0400, Jonathan Pryor wrote:
Apropros monodoc, in debian we are working on a better way (packaging
wise) to integrate documentation from non-Mono projects in monodoc:
http://wiki.debian.org/Teams/DebianMonoGroup/MonodocIntegration
Why not discuss this on mono
their documentation (see the gendarme google group), but the
patches I've seen for that _also_ involve monodoc.xml changes, so the
current monodoc.xml architecture hostile toward 3rd parties...
With luck, we can get this finished for Mono 2.2...
On Mon, 2008-10-20 at 23:18 -0400, Jonathan Pryor wrote
After hunting around for a bit (wondering why my openSUSE monodoc had
mono embedding documentation but not my local build), I found that
mono/mono/docscripts generates the monoapi{.source,.tree.zip} files
needed to display mono embedding documentation within monodoc.
The downside is that these
On Wed, 2008-10-29 at 11:33 -0400, Jonathan Pryor wrote:
After hunting around for a bit (wondering why my openSUSE monodoc had
mono embedding documentation but not my local build), I found that
mono/mono/docscripts generates the monoapi{.source,.tree.zip} files
needed to display mono embedding
Just perusing through the Mono.Simd API, and one question (and a few
other suggestions) occurs to me: Why the non-reliance on method
overloading?
More specifically, many (most?) types have an UnpackLow() method:
public class Vector2L {
public static Vector2l UnpackLow (Vector2l
On Sat, 2009-04-04 at 18:39 +0200, Amrein-Marie Christophe wrote:
I hope that nobody has already asked this question:
Why not merge Mono documentation with original documentation from ECMA
CLILibraryTypes.xml file?
www.ecma-international.org/publications/files/ECMA-ST/ECMA-335.zip
Been
On Fri, 2009-09-11 at 11:25 -0700, Roopa Krishnan wrote:
Mono version info is -
Mono Version: 2.0.50727.1433;
ASP.NET Version: 2.0.50727.1433
That's not a mono version, that's an assembly version.
What's the output of 'mono --version'?
- Jon
On Fri, 2009-08-21 at 13:44 -0700, rk14 wrote:
I am very new to Mono MonoDoc. Apologies if i am missing something very
basic.
Sorry for the delay.
Which version of Mono is this?
We use monodoc to generate internal API documentation. Our monodoc webserver
is ok, but monodoc is unable to
You say you're using xsp?
Please run xsp with MONO_OPTIONS=--debug set, as that will provide line
numbers.
My current guess is that you're missing a monodoc.xml file, which should
be installed to $prefix/lib/monodoc/monodoc.xml.
Thanks,
- Jon
___
On Mon, 2010-01-11 at 16:32 -0800, Arne Claassen wrote:
I've been using the inline Xml Docs for one main reason: Separate
documentation too often leads to documentation rot. I especially like
that I get warnings about missing or extra documentation members as
part of my build. But I have
On Mon, 2010-01-18 at 15:11 -0500, John Feminella wrote:
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
On Tue, 2010-01-19 at 21:32 -0500, John Feminella wrote:
* Are these source and not generated files?
Yes (these are source) and No (they are ALSO generated).
That is, it was my
understanding is that things in a path matching **/Documentation/**
are generated by an external
79 matches
Mail list logo
