headers
weiwufeng | 12 May 2007 03:26
Favicon

Re: Still no System.Windows.Forms in monodoc.


cd monodocs/class
        make update-dir ASSEMBLY=System.Windows.Forms \
                DIR=System.Windows.Forms 

where can I find the directory?
--

-- 
View this message in context: http://www.nabble.com/Still-no-System.Windows.Forms-in-monodoc.-tf3384425.html#a10441797
Sent from the Mono - Documentation mailing list archive at Nabble.com.

_______________________________________________
Mono-docs-list maillist  -  Mono-docs-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-docs-list
Permalink | Reply | 0 comments |
headers
weiwufeng | 11 May 2007 09:47
Favicon

how to configure monodoc-http


I want to access the monodoc-http from other computer.
But the monodoc-http listen on 127.0.0.1.
How do I configure the monodoc-http to listen on other address.
--

-- 
<weiwufeng <at> sohu.com>
_______________________________________________
Mono-docs-list maillist  -  Mono-docs-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-docs-list
Permalink | Reply | 1 comment |
headers
weiwufeng | 13 May 2007 01:21
Favicon

Re: how to configure monodoc-http


weiwufeng-2 wrote:
> 
> 
> I want to access the monodoc-http from other computer.
> But the monodoc-http listen on 127.0.0.1.
> How do I configure the monodoc-http to listen on other address.
> -- 
> <weiwufeng <at> sohu.com>
> _______________________________________________
> Mono-docs-list maillist  -  Mono-docs-list <at> lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-docs-list
> 
> 

I have edited the monodoc-http file.
So I solve the problem.

Now this file content is 

#!/bin/bash
export LANG=C
unset port

port=6140
while test -z "$port" ; do
   port=$RANDOM
   if [ $port -lt 1025 ] || netstat -a -n | grep -q :$port ; then
      unset port
   fi
(Continue reading)

Permalink | Reply | 0 comments |
headers
Valentin Sawadski | 14 May 2007 20:53
Picon
Picon

Cleaning Up the Developer Resource Category

Hello Everybody,

lately there has been some talk on the mailing lists that the Docs and the 
Wiki is pretty messed up and useless (All the good stuff is hidden somewhere, 
links end up in nowhere or point to old places, ...).

Therefore I wanted to make a first clean up proposal. Relying on the 
less-is-more-philosophy I wanted to remove several Pages from the Developer 
Resource Category. Mostly all the gtk-stuff.

The streamlined dev-resource category would only consist of all the "Entry 
Articles" to a certain topic. For example http://mono-project.com/WinForms 
and http://mono-project.com/GtkSharp. Articles which involved in a certain 
topic would then be only available in the subcategory (for example WinForms).

This could probably help new users to find their way through the wiki.
However since this is a pretty large change I would like to hear some 
suggestions and thoughts regarding it.

If there is no opposition to the thought I will later write a more detailed 
information about my restructuring plan.

Kind Regards,
Valentin
_______________________________________________
Mono-docs-list maillist  -  Mono-docs-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-docs-list
Permalink | Reply | 0 comments |
headers
Valentin Sawadski | 15 May 2007 20:23
Picon
Picon

Intended Audiance of Developer Resource Category?

Hello,

I've got a short and simple question. For whom is the Developer Resource 
Category for? People who want to develop apps by using Mono, or Mono-Hackers 
themselves?

If it is a mixup of both I would suggest to separate this into three 
categories.
1. Developer Resource: For people developing in mono.
and
2. Mono Hacker Resources: For people hacking mono directly.
3. Windows Porting: For dev from the windows world who would like to run their 
app on mono. (Just to have a single entry point for all the stuff that is 
currently spread across the wiki.) (This is maybe a subcategory of cat.2)

Because articles like http://www.mono-project.com/Compacting_GC are just to 
much for the ordinary developer who would like to run it's app on mono. In 
addition I'm also thinking of splitting the mono-framework category into a 
part which is of interest to the "normal" user who just wants to run his apps 
on mono and the "power" user who is interested in a deeper knowledge of mono.

I have to ask this question since I'm trying to work out a way to reorganize 
the Developer Resource Category in a way that makes it easier to understand 
and which will help people to find the information they need more quickly.

Kind Regards,
Valentin Sawadski
_______________________________________________
Mono-docs-list maillist  -  Mono-docs-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-docs-list
(Continue reading)

Permalink | Reply | 0 comments |
headers
mono.docs.list | 16 May 2007 17:44
Picon

ASP.NET example primed for mono-project postgreSQL page

hi,

I saw the C# example on http://www.mono-project.com/PostgreSQL using Npgsql 
and found it very useful in testing installation.

I thought it would benifit others if I refactored it into ASP.NET/C# as this 
was why I setup postgreSQL.
So I was a bit surprised when found I could not edit the page or even register 
an account.

Code follows as a single .aspx file run to run on monos xsp/2, if anyone can 
put it on the webpage I think it would help.

<% <at>  Page Language="c#" Title="postgres via Npgsql" %>
<% <at>  Assembly name="System" %>
<% <at>  Assembly name="System.Data" %>
<% <at>  Assembly name="Npgsql" %>

<script runat="server">
		protected void Page_Load(object sender, EventArgs e) 
		{
			if (!Page.IsPostBack)
			{
		      string connectionString =
          		"Server=localhost;" +
          		"Database=test;" +
          		"User ID=postgres;" +
          		"Password=fun2db;";
		      	System.Data.IDbConnection dbcon;
		       	dbcon = new Npgsql.NpgsqlConnection(connectionString);
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adrien Dessemond | 17 May 2007 04:06
Picon

Re: Intended Audiance of Developer Resource Category?

Hello!

 >I've got a short and simple question. For whom is the Developer Resource
 >Category for? People who want to develop apps by using Mono, or Mono-Hackers
 >themselves?

 >If it is a mixup of both I would suggest to separate this into three
 >categories.
 >1. Developer Resource
 >2. Mono Hacker Resources: For people hacking mono directly.
 >3. Windows Porting

This is good idea ! The pit to not fall into is to have a too 
complicated structure at the end (the MSDN library suffers of that).

Beyond your suggestion, could I express a more personal point of 
view  ? I apologize if was previously discussed and/or conflict with 
some project orientations. I am curious to get some feedback about it 
and by the way, may it will bring some ideas too.

<personal point of view>

I am following (from a far away point of view) the Mono project for 
more than 2 years and started to seriously use Mono for a personal 
project a couple a weeks ago. Because writing and dealing with 
documentation is my everyday job, I was led to the following reflection :

My personal and professional experiences told me that even you have 
the most advanced/robust/complete/flexible product, it will rejected 
by some of your users if it does not have robust (clear/concise/....)
(Continue reading)

Permalink | Reply | 2 comments |
headers
markaoki | 17 May 2007 05:48

Re: Intended Audiance of Developer ResourceCategory?

This is interesting.
I hope to hear more on this discussion.

If I am lucky I will be able to contribute to mono in a few weeks
when my other Linux writing project is complete.
I would love to write about mono:)

have a good day,
-yoshiro (mark) aoki

----- Original Message ----- 
From: "Adrien Dessemond" <adrien.dessemond <at> softhome.net>
To: <mono-docs-list <at> lists.ximian.com>
Sent: Wednesday, May 16, 2007 10:06 PM
Subject: Re: [Mono-docs-list] Intended Audiance of Developer 
ResourceCategory?

> Hello!
>
> >I've got a short and simple question. For whom is the Developer Resource
> >Category for? People who want to develop apps by using Mono, or 
> >Mono-Hackers
> >themselves?
>
> >If it is a mixup of both I would suggest to separate this into three
> >categories.
> >1. Developer Resource
> >2. Mono Hacker Resources: For people hacking mono directly.
> >3. Windows Porting
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Valentin Sawadski | 17 May 2007 12:10
Picon
Picon

Re: Intended Audiance of Developer Resource Category?

Hello,

On Thursday 17 May 2007 04:06, Adrien Dessemond wrote:
> Hello!
>
> This is good idea ! The pit to not fall into is to have a too
> complicated structure at the end (the MSDN library suffers of that).

I believe that Mono won't fall in such a pit because, it is not as large as 
the MSDN, we simply do not have that much content to structure into 
uncountable categories. But still that's something we have to keep in mind.

> Beyond your suggestion, could I express a more personal point of
> view  ? I apologize if was previously discussed and/or conflict with
> some project orientations. I am curious to get some feedback about it
> and by the way, may it will bring some ideas too.
>
> <personal point of view>
>
> I am following (from a far away point of view) the Mono project for
> more than 2 years and started to seriously use Mono for a personal
> project a couple a weeks ago. Because writing and dealing with
> documentation is my everyday job, I was led to the following reflection :

Glad to hear that a person who has experience in dealing with documentation is 
interested in the Mono-Documentation Projects. Hopefully others will follow 
and it will gain a little bit momentum now. (It has been creeping for a 
looong time now...)

> My personal and professional experiences told me that even you have
(Continue reading)

Permalink | Reply | 0 comments |
headers
Miguel de Icaza | 17 May 2007 17:09
Picon
Favicon

Re: Intended Audiance of Developer ResourceCategory?

Hello,

> For example:
> Use case 1: Develop Cross Plattform Apps.
> Use case 2: Develop Web Apps.
> Use case 3: Port an App from Windows to Linux.
> Use case 4: Embedd Mono into your App.
> Use case 5: Something completely different.

This is a good idea, but I would start by writing the content, and then
updating the page.

Another thing that I find useful myself are the various "Waltkthroughs"
or "Howtos" that are typically available on the Microsoft documentation.

We are lacking a lot of these.   

_______________________________________________
Mono-docs-list maillist  -  Mono-docs-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-docs-list
Permalink | Reply | 1 comment |

Gmane