зеркало из https://github.com/mono/mail-archives.git
Import monodevelop-devel-list
This commit is contained in:
Duncan Mak
Родитель
0d492112df
Коммит
70c76cb7fc
|
|
@ -0,0 +1,88 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Looping through the Project documents
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Looping%20through%20the%20Project%20documents&In-Reply-To=766cb57b0808280744x6c785340ya686052b2f3e24ec%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Looping through the Project documents</H1>
|
||||
<B>"Andrés G. Aragoneses"</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Looping%20through%20the%20Project%20documents&In-Reply-To=766cb57b0808280744x6c785340ya686052b2f3e24ec%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Looping through the Project documents">aaragoneses at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Aug 28 11:18:37 EDT 2008</I>
|
||||
<P><UL>
|
||||
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#27">[ date ]</a>
|
||||
<a href="thread.html#27">[ thread ]</a>
|
||||
<a href="subject.html#27">[ subject ]</a>
|
||||
<a href="author.html#27">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>I'm forwarding this to monodevelop-*devel* list.
|
||||
|
||||
laas, take a look at the code in this file:
|
||||
|
||||
trunk/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui.Search/WholeCombineDocumentIterator.cs
|
||||
|
||||
I bet it will give you some clues ;)
|
||||
|
||||
Andrés
|
||||
|
||||
|
||||
laas wrote:
|
||||
><i> Hi Mike,
|
||||
</I>><i> I've never used the collection Project.Files. Does it contains all the
|
||||
</I>><i> solution document ? Also documents (cs, xml and so on) in project
|
||||
</I>><i> subfolder ?
|
||||
</I>><i>
|
||||
</I>><i> Best regards,
|
||||
</I>><i> LAAS
|
||||
</I>><i>
|
||||
</I>><i> On Thu, Aug 28, 2008 at 4:27 PM, Mike Kestner <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkestner at gmail.com</A>
|
||||
</I>><i> <mailto:<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkestner at gmail.com</A>>> wrote:
|
||||
</I>><i>
|
||||
</I>><i> On Thu, 2008-08-28 at 11:39 +0200, laas wrote:
|
||||
</I>><i> > Hi all,
|
||||
</I>><i> > developing for Monodevelop, I'm using the following collection:
|
||||
</I>><i> >
|
||||
</I>><i> > IdeApp.Workbench.Documents
|
||||
</I>><i> >
|
||||
</I>><i> > in order to loop through all the documents that are currently open.
|
||||
</I>><i> > Is there a collection that can be used to loop through ALL the
|
||||
</I>><i> project (or solution) documents (open and closed) ?
|
||||
</I>><i>
|
||||
</I>><i> Maybe I'm not understanding what you mean by documents, but there's
|
||||
</I>><i> Project.Files.
|
||||
</I>><i>
|
||||
</I>><i> Mike
|
||||
</I></PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#27">[ date ]</a>
|
||||
<a href="thread.html#27">[ thread ]</a>
|
||||
<a href="subject.html#27">[ subject ]</a>
|
||||
<a href="author.html#27">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list August 2008 Archive by author</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>August 2008 Archives by author</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Messages:</b> 1<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000027.html">[Monodevelop-devel] Looping through the Project documents
|
||||
</A><A NAME="27"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Thu Aug 28 11:19:10 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list August 2008 Archive by date</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>August 2008 Archives by date</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Messages:</b> 1<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000027.html">[Monodevelop-devel] Looping through the Project documents
|
||||
</A><A NAME="27"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Thu Aug 28 11:19:10 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list August 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>August 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Messages:</b> 1<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01219936717- -->
|
||||
<LI><A HREF="000027.html">[Monodevelop-devel] Looping through the Project documents
|
||||
</A><A NAME="27"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Thu Aug 28 11:19:10 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list August 2008 Archive by subject</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>August 2008 Archives by subject</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Messages:</b> 1<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000027.html">[Monodevelop-devel] Looping through the Project documents
|
||||
</A><A NAME="27"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Thu Aug 28 11:19:10 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list August 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>August 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Messages:</b> 1<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01219936717- -->
|
||||
<LI><A HREF="000027.html">[Monodevelop-devel] Looping through the Project documents
|
||||
</A><A NAME="27"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Thu Aug 28 11:18:37 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Thu Aug 28 11:19:10 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,62 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] MD roadmap page
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20MD%20roadmap%20page&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
|
||||
<LINK REL="Next" HREF="000090.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] MD roadmap page</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20MD%20roadmap%20page&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] MD roadmap page">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Fri Dec 12 13:11:49 EST 2008</I>
|
||||
<P><UL>
|
||||
|
||||
<LI>Next message: <A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#89">[ date ]</a>
|
||||
<a href="thread.html#89">[ thread ]</a>
|
||||
<a href="subject.html#89">[ subject ]</a>
|
||||
<a href="author.html#89">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>I created this page where I'll be updating the roadmap for MD:
|
||||
|
||||
<A HREF="http://www.monodevelop.com/Development_Roadmap">http://www.monodevelop.com/Development_Roadmap</A>
|
||||
|
||||
I'll update it with more specific dates when approaching a release.
|
||||
|
||||
Lluis.
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
|
||||
<LI>Next message: <A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#89">[ date ]</a>
|
||||
<a href="thread.html#89">[ thread ]</a>
|
||||
<a href="subject.html#89">[ subject ]</a>
|
||||
<a href="author.html#89">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,64 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Patch%3A%20Fixes%20to%20compile%20with%20csc&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000089.html">
|
||||
<LINK REL="Next" HREF="000091.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Patch: Fixes to compile with csc</H1>
|
||||
<B>Jonathan Pobst</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Patch%3A%20Fixes%20to%20compile%20with%20csc&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Patch: Fixes to compile with csc">monkey at jpobst.com
|
||||
</A><BR>
|
||||
<I>Wed Dec 17 18:24:44 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#90">[ date ]</a>
|
||||
<a href="thread.html#90">[ thread ]</a>
|
||||
<a href="subject.html#90">[ subject ]</a>
|
||||
<a href="author.html#90">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>The attached patch fixes some errors received when compiling MD with
|
||||
csc. This is bug #421838 filed against mcs.
|
||||
|
||||
Jonathan
|
||||
-------------- next part --------------
|
||||
An embedded and charset-unspecified text was scrubbed...
|
||||
Name: mdpatch1.patch
|
||||
Url: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081217/3a464dd7/attachment.pl">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081217/3a464dd7/attachment.pl</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#90">[ date ]</a>
|
||||
<a href="thread.html#90">[ thread ]</a>
|
||||
<a href="subject.html#90">[ subject ]</a>
|
||||
<a href="author.html#90">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,109 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Patch%3A%20Fixes%20to%20compile%20with%20csc&In-Reply-To=49498A3C.1000603%40jpobst.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000090.html">
|
||||
<LINK REL="Next" HREF="000092.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Patch: Fixes to compile with csc</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Patch%3A%20Fixes%20to%20compile%20with%20csc&In-Reply-To=49498A3C.1000603%40jpobst.com"
|
||||
TITLE="[Monodevelop-devel] Patch: Fixes to compile with csc">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Dec 18 10:35:49 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#91">[ date ]</a>
|
||||
<a href="thread.html#91">[ thread ]</a>
|
||||
<a href="subject.html#91">[ subject ]</a>
|
||||
<a href="author.html#91">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Fixed. Thanks!
|
||||
|
||||
El dc 17 de 12 de 2008 a les 17:24 -0600, en/na Jonathan Pobst va
|
||||
escriure:
|
||||
><i> The attached patch fixes some errors received when compiling MD with
|
||||
</I>><i> csc. This is bug #421838 filed against mcs.
|
||||
</I>><i>
|
||||
</I>><i> Jonathan
|
||||
</I>><i> fitxer adjunt document de text pla (mdpatch1.patch)
|
||||
</I>><i> Index: addins/Mono.Texteditor/Mono.TextEditor/DocumentLocation.cs
|
||||
</I>><i> ===================================================================
|
||||
</I>><i> --- addins/Mono.Texteditor/Mono.TextEditor/DocumentLocation.cs (revision 121639)
|
||||
</I>><i> +++ addins/Mono.Texteditor/Mono.TextEditor/DocumentLocation.cs (working copy)
|
||||
</I>><i> @@ -42,7 +42,7 @@
|
||||
</I>><i> }
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i> - public DocumentLocation (int line, int column)
|
||||
</I>><i> + public DocumentLocation (int line, int column) : this ()
|
||||
</I>><i> {
|
||||
</I>><i> this.Line = line;
|
||||
</I>><i> this.Column = column;
|
||||
</I>><i> Index: core/MonoDevelop.Projects/MonoDevelop.Projects.Dom/DomLocation.cs
|
||||
</I>><i> ===================================================================
|
||||
</I>><i> --- core/MonoDevelop.Projects/MonoDevelop.Projects.Dom/DomLocation.cs (revision 121639)
|
||||
</I>><i> +++ core/MonoDevelop.Projects/MonoDevelop.Projects.Dom/DomLocation.cs (working copy)
|
||||
</I>><i> @@ -55,7 +55,7 @@
|
||||
</I>><i> }
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i> - public DomLocation (int line, int column)
|
||||
</I>><i> + public DomLocation (int line, int column) : this ()
|
||||
</I>><i> {
|
||||
</I>><i> this.Line = line;
|
||||
</I>><i> this.Column = column;
|
||||
</I>><i> Index: core/MonoDevelop.Projects/MonoDevelop.Projects.Dom/DomRegion.cs
|
||||
</I>><i> ===================================================================
|
||||
</I>><i> --- core/MonoDevelop.Projects/MonoDevelop.Projects.Dom/DomRegion.cs (revision 121639)
|
||||
</I>><i> +++ core/MonoDevelop.Projects/MonoDevelop.Projects.Dom/DomRegion.cs (working copy)
|
||||
</I>><i> @@ -55,7 +55,7 @@
|
||||
</I>><i> {
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i> - public DomRegion (int startLine, int startColumn, int endLine, int endColumn)
|
||||
</I>><i> + public DomRegion (int startLine, int startColumn, int endLine, int endColumn) : this ()
|
||||
</I>><i> {
|
||||
</I>><i> this.Start = new DomLocation (startLine, startColumn);
|
||||
</I>><i> this.End = new DomLocation (endLine, endColumn);
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#91">[ date ]</a>
|
||||
<a href="thread.html#91">[ thread ]</a>
|
||||
<a href="subject.html#91">[ subject ]</a>
|
||||
<a href="author.html#91">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,66 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Patch%3A%20Another%20fix%20to%20compile%20with%20csc&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000091.html">
|
||||
<LINK REL="Next" HREF="000093.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Patch: Another fix to compile with csc</H1>
|
||||
<B>Jonathan Pobst</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Patch%3A%20Another%20fix%20to%20compile%20with%20csc&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Patch: Another fix to compile with csc">monkey at jpobst.com
|
||||
</A><BR>
|
||||
<I>Thu Dec 18 11:36:49 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#92">[ date ]</a>
|
||||
<a href="thread.html#92">[ thread ]</a>
|
||||
<a href="subject.html#92">[ subject ]</a>
|
||||
<a href="author.html#92">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>The attached patch fixes some errors received while compiling MD with
|
||||
csc. This is bug #370414 filed against mcs. You may want to name the
|
||||
variables something different than what I chose, however the existing
|
||||
ones conflict.
|
||||
|
||||
Jonathan
|
||||
-------------- next part --------------
|
||||
An embedded and charset-unspecified text was scrubbed...
|
||||
Name: mdpatch2.patch
|
||||
Url: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081218/601259eb/attachment.pl">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081218/601259eb/attachment.pl</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#92">[ date ]</a>
|
||||
<a href="thread.html#92">[ thread ]</a>
|
||||
<a href="subject.html#92">[ subject ]</a>
|
||||
<a href="author.html#92">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,70 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20make%20app-dir%20target%20for%20MonoDevelop&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000092.html">
|
||||
<LINK REL="Next" HREF="000094.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] make app-dir target for MonoDevelop</H1>
|
||||
<B>Rusty Howell</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20make%20app-dir%20target%20for%20MonoDevelop&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] make app-dir target for MonoDevelop">rhowell at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Dec 18 15:35:43 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#93">[ date ]</a>
|
||||
<a href="thread.html#93">[ thread ]</a>
|
||||
<a href="subject.html#93">[ subject ]</a>
|
||||
<a href="author.html#93">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hey guys,
|
||||
|
||||
Marc and I would like to start working on a Makefile target to create a
|
||||
app directory for MonoDevelop (for Mac OSX).
|
||||
Currently, building the app dir for OSX isn't streamlined and takes some
|
||||
additional time on our part. If no one is already
|
||||
working on this, I'd like to put a bit of time into it. I have the MD
|
||||
source but am not too familiar with it. I was thinking about
|
||||
doing most of the work in monodevelop/main/build/Makefile.am since that
|
||||
dir seems to have the built binaries.
|
||||
|
||||
If anyone has suggestions or tips, that would be great.
|
||||
|
||||
Rusty
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#93">[ date ]</a>
|
||||
<a href="thread.html#93">[ thread ]</a>
|
||||
<a href="subject.html#93">[ subject ]</a>
|
||||
<a href="author.html#93">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,75 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20make%20app-dir%20target%20for%20MonoDevelop&In-Reply-To=494AB41F.6070707%40novell.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000093.html">
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] make app-dir target for MonoDevelop</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20make%20app-dir%20target%20for%20MonoDevelop&In-Reply-To=494AB41F.6070707%40novell.com"
|
||||
TITLE="[Monodevelop-devel] make app-dir target for MonoDevelop">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Fri Dec 19 13:09:52 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#94">[ date ]</a>
|
||||
<a href="thread.html#94">[ thread ]</a>
|
||||
<a href="subject.html#94">[ subject ]</a>
|
||||
<a href="author.html#94">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dj 18 de 12 de 2008 a les 13:35 -0700, en/na Rusty Howell va
|
||||
escriure:
|
||||
><i> Hey guys,
|
||||
</I>><i>
|
||||
</I>><i> Marc and I would like to start working on a Makefile target to create a
|
||||
</I>><i> app directory for MonoDevelop (for Mac OSX).
|
||||
</I>
|
||||
That's great news :)
|
||||
|
||||
><i> Currently, building the app dir for OSX isn't streamlined and takes some
|
||||
</I>><i> additional time on our part. If no one is already
|
||||
</I>><i> working on this, I'd like to put a bit of time into it. I have the MD
|
||||
</I>><i> source but am not too familiar with it. I was thinking about
|
||||
</I>><i> doing most of the work in monodevelop/main/build/Makefile.am since that
|
||||
</I>><i> dir seems to have the built binaries.
|
||||
</I>
|
||||
A better place would be monodevelop/main/Makefile.am, since that's the
|
||||
main MD makefile.
|
||||
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#94">[ date ]</a>
|
||||
<a href="thread.html#94">[ thread ]</a>
|
||||
<a href="subject.html#94">[ subject ]</a>
|
||||
<a href="author.html#94">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,77 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list December 2008 Archive by author</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>December 2008 Archives by author</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Fri Dec 12 13:11:49 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Messages:</b> 6<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A><A NAME="89"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="91"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="94"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="93"> </A>
|
||||
<I>Rusty Howell
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="90"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A><A NAME="92"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Fri Dec 19 13:10:10 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,77 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list December 2008 Archive by date</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>December 2008 Archives by date</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Fri Dec 12 13:11:49 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Messages:</b> 6<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A><A NAME="89"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="90"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="91"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A><A NAME="92"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="93"> </A>
|
||||
<I>Rusty Howell
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="94"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Fri Dec 19 13:10:10 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,87 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list December 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>December 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Fri Dec 12 13:11:49 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Messages:</b> 6<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01229105509- -->
|
||||
<LI><A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A><A NAME="89"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--0 01229556284- -->
|
||||
<LI><A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="90"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01229556284-01229614549- -->
|
||||
<LI><A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="91"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01229618209- -->
|
||||
<LI><A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A><A NAME="92"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<!--0 01229632543- -->
|
||||
<LI><A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="93"> </A>
|
||||
<I>Rusty Howell
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01229632543-01229710192- -->
|
||||
<LI><A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="94"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Fri Dec 19 13:10:10 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,77 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list December 2008 Archive by subject</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>December 2008 Archives by subject</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Fri Dec 12 13:11:49 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Messages:</b> 6<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="93"> </A>
|
||||
<I>Rusty Howell
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="94"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A><A NAME="89"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A><A NAME="92"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="90"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="91"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Fri Dec 19 13:10:10 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,87 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list December 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>December 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Fri Dec 12 13:11:49 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Messages:</b> 6<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01229105509- -->
|
||||
<LI><A HREF="000089.html">[Monodevelop-devel] MD roadmap page
|
||||
</A><A NAME="89"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--0 01229556284- -->
|
||||
<LI><A HREF="000090.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="90"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01229556284-01229614549- -->
|
||||
<LI><A HREF="000091.html">[Monodevelop-devel] Patch: Fixes to compile with csc
|
||||
</A><A NAME="91"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01229618209- -->
|
||||
<LI><A HREF="000092.html">[Monodevelop-devel] Patch: Another fix to compile with csc
|
||||
</A><A NAME="92"> </A>
|
||||
<I>Jonathan Pobst
|
||||
</I>
|
||||
|
||||
<!--0 01229632543- -->
|
||||
<LI><A HREF="000093.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="93"> </A>
|
||||
<I>Rusty Howell
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01229632543-01229710192- -->
|
||||
<LI><A HREF="000094.html">[Monodevelop-devel] make app-dir target for MonoDevelop
|
||||
</A><A NAME="94"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Fri Dec 19 13:09:52 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Fri Dec 19 13:10:10 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,74 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Insufficient Requirement Checks
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
|
||||
<LINK REL="Next" HREF="000008.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Insufficient Requirement Checks</H1>
|
||||
<B>Valentin Sawadski</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Insufficient Requirement Checks">valentin.sawadski at googlemail.com
|
||||
</A><BR>
|
||||
<I>Sat Jul 12 10:43:11 EDT 2008</I>
|
||||
<P><UL>
|
||||
|
||||
<LI>Next message: <A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#2">[ date ]</a>
|
||||
<a href="thread.html#2">[ thread ]</a>
|
||||
<a href="subject.html#2">[ subject ]</a>
|
||||
<a href="author.html#2">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi,
|
||||
|
||||
is it possible, that the new build system does not stop if a requirement
|
||||
of a selected package is not met? Or do the packages not check for all
|
||||
requirements?
|
||||
|
||||
Because today, I ran into a couple of missing missing libraries when
|
||||
compiling but autogen.sh didn't tell me that they were missing in the
|
||||
first place. (e.g. monodoc which is used by the documentation plugin).
|
||||
|
||||
Kind Regards,
|
||||
Valentin
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: not available
|
||||
Type: application/pgp-signature
|
||||
Size: 197 bytes
|
||||
Desc: This is a digitally signed message part
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080712/25b66d36/attachment.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080712/25b66d36/attachment.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
|
||||
<LI>Next message: <A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#2">[ date ]</a>
|
||||
<a href="thread.html#2">[ thread ]</a>
|
||||
<a href="subject.html#2">[ subject ]</a>
|
||||
<a href="author.html#2">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,83 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000010.html">
|
||||
<LINK REL="Next" HREF="000004.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [Path] Updated ASP.NET Templates</H1>
|
||||
<B>Valentin Sawadski</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] [Path] Updated ASP.NET Templates">valentin.sawadski at googlemail.com
|
||||
</A><BR>
|
||||
<I>Sat Jul 12 12:05:53 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#3">[ date ]</a>
|
||||
<a href="thread.html#3">[ thread ]</a>
|
||||
<a href="subject.html#3">[ subject ]</a>
|
||||
<a href="author.html#3">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi,
|
||||
|
||||
I noticed, that the current ASP.NET templates are outdated and can not
|
||||
be used out of the box anymore. (e.g. the CodeBehind attribute is
|
||||
obsolete and the CodeFile is not present, this stops the application
|
||||
from compiling). Attached is a patch containing the updated templates to
|
||||
fix this.
|
||||
|
||||
Kind Regards,
|
||||
Valentin
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: updatedTemplates.diff
|
||||
Type: text/x-patch
|
||||
Size: 10900 bytes
|
||||
Desc: not available
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080712/d1a9a35d/attachment.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080712/d1a9a35d/attachment.bin</A>
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: not available
|
||||
Type: application/pgp-signature
|
||||
Size: 197 bytes
|
||||
Desc: This is a digitally signed message part
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080712/d1a9a35d/attachment-0001.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080712/d1a9a35d/attachment-0001.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#3">[ date ]</a>
|
||||
<a href="thread.html#3">[ thread ]</a>
|
||||
<a href="subject.html#3">[ subject ]</a>
|
||||
<a href="author.html#3">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,78 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=1215878753.21661.13.camel%40pi1536.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000003.html">
|
||||
<LINK REL="Next" HREF="000005.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [Path] Updated ASP.NET Templates</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=1215878753.21661.13.camel%40pi1536.site"
|
||||
TITLE="[Monodevelop-devel] [Path] Updated ASP.NET Templates">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 14 09:41:05 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#4">[ date ]</a>
|
||||
<a href="thread.html#4">[ thread ]</a>
|
||||
<a href="subject.html#4">[ subject ]</a>
|
||||
<a href="author.html#4">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Sat, Jul 12, 2008 at 12:05 PM, Valentin Sawadski
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">valentin.sawadski at googlemail.com</A>> wrote:
|
||||
><i> Hi,
|
||||
</I>><i>
|
||||
</I>><i> I noticed, that the current ASP.NET templates are outdated and can not
|
||||
</I>><i> be used out of the box anymore. (e.g. the CodeBehind attribute is
|
||||
</I>><i> obsolete and the CodeFile is not present, this stops the application
|
||||
</I>><i> from compiling). Attached is a patch containing the updated templates to
|
||||
</I>><i> fix this.
|
||||
</I>
|
||||
Actually, the CodeFile attribute is only needed when the codebehind
|
||||
files are intended to be compiled on the server (as VS Express <
|
||||
2008sp1) does it. The full VS (and VS Express 2008sp2) supports Web
|
||||
Projects, where the CodeBehind is compiled beforehand. MonoDevelop
|
||||
uses the latter model.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#4">[ date ]</a>
|
||||
<a href="thread.html#4">[ thread ]</a>
|
||||
<a href="subject.html#4">[ subject ]</a>
|
||||
<a href="author.html#4">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,100 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=aec34c770807140641q7ed18299qd990a8077291cc0b%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000004.html">
|
||||
<LINK REL="Next" HREF="000006.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [Path] Updated ASP.NET Templates</H1>
|
||||
<B>Valentin Sawadski</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=aec34c770807140641q7ed18299qd990a8077291cc0b%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] [Path] Updated ASP.NET Templates">valentin.sawadski at googlemail.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 14 12:36:22 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#5">[ date ]</a>
|
||||
<a href="thread.html#5">[ thread ]</a>
|
||||
<a href="subject.html#5">[ subject ]</a>
|
||||
<a href="author.html#5">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Mon, 2008-07-14 at 09:41 -0400, Michael Hutchinson wrote:
|
||||
><i> On Sat, Jul 12, 2008 at 12:05 PM, Valentin Sawadski
|
||||
</I>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">valentin.sawadski at googlemail.com</A>> wrote:
|
||||
</I>><i> > Hi,
|
||||
</I>><i> >
|
||||
</I>><i> > I noticed, that the current ASP.NET templates are outdated and can not
|
||||
</I>><i> > be used out of the box anymore. (e.g. the CodeBehind attribute is
|
||||
</I>><i> > obsolete and the CodeFile is not present, this stops the application
|
||||
</I>><i> > from compiling). Attached is a patch containing the updated templates to
|
||||
</I>><i> > fix this.
|
||||
</I>><i>
|
||||
</I>><i> Actually, the CodeFile attribute is only needed when the codebehind
|
||||
</I>><i> files are intended to be compiled on the server (as VS Express <
|
||||
</I>><i> 2008sp1) does it. The full VS (and VS Express 2008sp2) supports Web
|
||||
</I>><i> Projects, where the CodeBehind is compiled beforehand. MonoDevelop
|
||||
</I>><i> uses the latter model.
|
||||
</I>><i>
|
||||
</I>Thats odd, because MSDN
|
||||
(<A HREF="http://msdn.microsoft.com/en-us/library/ydy4x04a(VS.80">http://msdn.microsoft.com/en-us/library/ydy4x04a(VS.80</A>).aspx) does not
|
||||
mention this. It only states that:
|
||||
|
||||
"This attribute is included for compatibility with previous
|
||||
versions of ASP.NET, to implement the code-behind feature. In
|
||||
ASP.NET version 2.0, you should instead use the CodeFile
|
||||
attribute to specify the name of the source file, along with the
|
||||
Inherits attribute to specify the fully qualified name of the
|
||||
class."
|
||||
|
||||
Anyways, this does not change the fact that the current Templates do not
|
||||
work with xsp and xsp2 out of the box. Adding CodeFile to them fixes
|
||||
this.
|
||||
|
||||
Kind Regards,
|
||||
Valentin
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: not available
|
||||
Type: application/pgp-signature
|
||||
Size: 197 bytes
|
||||
Desc: This is a digitally signed message part
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080714/398d41fb/attachment-0001.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080714/398d41fb/attachment-0001.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#5">[ date ]</a>
|
||||
<a href="thread.html#5">[ thread ]</a>
|
||||
<a href="subject.html#5">[ subject ]</a>
|
||||
<a href="author.html#5">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,132 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=1216053382.3361.3.camel%40pi1536.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000005.html">
|
||||
<LINK REL="Next" HREF="000007.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [Path] Updated ASP.NET Templates</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BPath%5D%20Updated%20ASP.NET%20Templates&In-Reply-To=1216053382.3361.3.camel%40pi1536.site"
|
||||
TITLE="[Monodevelop-devel] [Path] Updated ASP.NET Templates">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 14 22:10:23 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#6">[ date ]</a>
|
||||
<a href="thread.html#6">[ thread ]</a>
|
||||
<a href="subject.html#6">[ subject ]</a>
|
||||
<a href="author.html#6">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Mon, Jul 14, 2008 at 12:36 PM, Valentin Sawadski
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">valentin.sawadski at googlemail.com</A>> wrote:
|
||||
>><i> Actually, the CodeFile attribute is only needed when the codebehind
|
||||
</I>>><i> files are intended to be compiled on the server (as VS Express <
|
||||
</I>>><i> 2008sp1) does it. The full VS (and VS Express 2008sp2) supports Web
|
||||
</I>>><i> Projects, where the CodeBehind is compiled beforehand. MonoDevelop
|
||||
</I>>><i> uses the latter model.
|
||||
</I>>><i>
|
||||
</I>><i> Thats odd, because MSDN
|
||||
</I>><i> (<A HREF="http://msdn.microsoft.com/en-us/library/ydy4x04a(VS.80">http://msdn.microsoft.com/en-us/library/ydy4x04a(VS.80</A>).aspx) does not
|
||||
</I>><i> mention this. It only states that:
|
||||
</I>><i>
|
||||
</I>><i> "This attribute is included for compatibility with previous
|
||||
</I>><i> versions of ASP.NET, to implement the code-behind feature. In
|
||||
</I>><i> ASP.NET version 2.0, you should instead use the CodeFile
|
||||
</I>><i> attribute to specify the name of the source file, along with the
|
||||
</I>><i> Inherits attribute to specify the fully qualified name of the
|
||||
</I>><i> class."
|
||||
</I>
|
||||
The CodeBehind attribute is only used by Visual Studio 2002/2003. All
|
||||
versions of ASP.NET are aware of it, and totally ignore it. It can be
|
||||
omitted, and won't affect anything.
|
||||
|
||||
The CodeFile attribute is used by ASP.NET 2.0 for the "2005" model,
|
||||
where the CodeBehind class is compiled on the server. It specifies the
|
||||
CodeBehind file that should be compiled when the page is compiled. In
|
||||
this model, a partial class is generated and compiled together with
|
||||
the CodeBehind class that's defined in the CodeFile.
|
||||
|
||||
The Inherits attribute is used in ALL compilation models to specify
|
||||
the class from which the compiled page should inherit. It can be
|
||||
System.Web.UI.Page or ANY class that derives from this, in ANY of the
|
||||
referenced assemblies. If you have the CodeFile attribute, it can be
|
||||
defined in a file compiled on the fly. Having these classes "grouped"
|
||||
in the IDE (Default.aspx.cs etc) with the corresponding is simply a
|
||||
convenience that MonoDevelop and Visual Studio provide. Ultimately
|
||||
they all get compiled down into on application dll from which the aspx
|
||||
compiler can reference them.
|
||||
|
||||
Note that although the CodeFile ("Web Site") model was introduced with
|
||||
ASP.NET 2.0 and VS 2005, many developers considered it to be inferior
|
||||
for serious applications, and hence Microsoft introduced an addin for
|
||||
2005 that added support for the old-style "Web Projects", and included
|
||||
it with 2008 by default. They've even added it to VS Express in
|
||||
2008sp1, since the "web projecy" model is required for the upcoming
|
||||
MVC style of development.
|
||||
|
||||
><i> Anyways, this does not change the fact that the current Templates do not
|
||||
</I>><i> work with xsp and xsp2 out of the box. Adding CodeFile to them fixes
|
||||
</I>><i> this.
|
||||
</I>
|
||||
They work just fine, as long as you compile the project first. MD
|
||||
doesn't yet explicitly support the "web site" model. I plan to support
|
||||
it to some extent (but maybe only as an importer -- I have a limited
|
||||
amount of time, and MVC is likely to become the most important
|
||||
development style anyway).
|
||||
|
||||
When designing the initial ASP.NET support for MD back in 2006, I
|
||||
investigated the ASP.NET compilation models very thoroughly, and I'm
|
||||
glad the one I chose seems to have become the preferred choice for
|
||||
future development. The "web site" model is cute but it's not really
|
||||
suited to serious development (VCS, deployment, etc). It was basically
|
||||
an attempt to make ASP.NET more like PHP ;-)
|
||||
|
||||
I'd be happy to add your templates as an alternate set but they won't
|
||||
replace the existing ones. I'm not sure how to prevent confusion
|
||||
between the two kinds though :-/
|
||||
|
||||
Thanks,
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#6">[ date ]</a>
|
||||
<a href="thread.html#6">[ thread ]</a>
|
||||
<a href="subject.html#6">[ subject ]</a>
|
||||
<a href="author.html#6">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,75 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BFwd%3A%20Monodevevelop%201.9%20Error%20when%20opening%20old%0A%09Gtk%23%20Project%5D&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000006.html">
|
||||
<LINK REL="Next" HREF="000011.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]</H1>
|
||||
<B>"Andrés G. Aragoneses"</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BFwd%3A%20Monodevevelop%201.9%20Error%20when%20opening%20old%0A%09Gtk%23%20Project%5D&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]">aaragoneses at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Jul 17 09:59:29 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#7">[ date ]</a>
|
||||
<a href="thread.html#7">[ thread ]</a>
|
||||
<a href="subject.html#7">[ subject ]</a>
|
||||
<a href="author.html#7">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>This seems to be a bug in Stetic right? It should parse anything with
|
||||
the InvariantCulture.
|
||||
|
||||
Regards,
|
||||
|
||||
Andrés
|
||||
|
||||
--
|
||||
|
||||
-------------- next part --------------
|
||||
An embedded message was scrubbed...
|
||||
From: lordphoenix <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lordphoenix at tuxfamily.org</A>>
|
||||
Subject: Monodevevelop 1.9 Error when opening old Gtk# Project
|
||||
Date: Thu, 17 Jul 2008 15:21:04 +0200
|
||||
Size: 5688
|
||||
Url: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080717/1700c705/attachment.eml">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080717/1700c705/attachment.eml</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#7">[ date ]</a>
|
||||
<a href="thread.html#7">[ thread ]</a>
|
||||
<a href="subject.html#7">[ subject ]</a>
|
||||
<a href="author.html#7">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,77 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Insufficient Requirement Checks
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=1215873791.21661.5.camel%40pi1536.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000002.html">
|
||||
<LINK REL="Next" HREF="000009.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Insufficient Requirement Checks</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=1215873791.21661.5.camel%40pi1536.site"
|
||||
TITLE="[Monodevelop-devel] Insufficient Requirement Checks">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Fri Jul 18 18:16:18 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#8">[ date ]</a>
|
||||
<a href="thread.html#8">[ thread ]</a>
|
||||
<a href="subject.html#8">[ subject ]</a>
|
||||
<a href="author.html#8">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Sat, Jul 12, 2008 at 10:43 AM, Valentin Sawadski
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">valentin.sawadski at googlemail.com</A>> wrote:
|
||||
><i> Hi,
|
||||
</I>><i>
|
||||
</I>><i> is it possible, that the new build system does not stop if a requirement
|
||||
</I>><i> of a selected package is not met? Or do the packages not check for all
|
||||
</I>><i> requirements?
|
||||
</I>
|
||||
The top-level configure will fail in any of the packages fail to
|
||||
configure. However, it's possible that some packages may not check for
|
||||
everything they need in their configure scripts.
|
||||
|
||||
><i> Because today, I ran into a couple of missing missing libraries when
|
||||
</I>><i> compiling but autogen.sh didn't tell me that they were missing in the
|
||||
</I>><i> first place. (e.g. monodoc which is used by the documentation plugin).
|
||||
</I>
|
||||
Do you have a list of the missing checks handy?
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#8">[ date ]</a>
|
||||
<a href="thread.html#8">[ thread ]</a>
|
||||
<a href="subject.html#8">[ subject ]</a>
|
||||
<a href="author.html#8">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,91 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Insufficient Requirement Checks
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=aec34c770807181516m735d56bao6229f2db17748c66%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000008.html">
|
||||
<LINK REL="Next" HREF="000010.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Insufficient Requirement Checks</H1>
|
||||
<B>Valentin Sawadski</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=aec34c770807181516m735d56bao6229f2db17748c66%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Insufficient Requirement Checks">valentin.sawadski at googlemail.com
|
||||
</A><BR>
|
||||
<I>Sat Jul 19 05:46:21 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#9">[ date ]</a>
|
||||
<a href="thread.html#9">[ thread ]</a>
|
||||
<a href="subject.html#9">[ subject ]</a>
|
||||
<a href="author.html#9">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Fri, 2008-07-18 at 18:16 -0400, Michael Hutchinson wrote:
|
||||
><i> On Sat, Jul 12, 2008 at 10:43 AM, Valentin Sawadski
|
||||
</I>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">valentin.sawadski at googlemail.com</A>> wrote:
|
||||
</I>><i> > Hi,
|
||||
</I>><i> >
|
||||
</I>><i> > is it possible, that the new build system does not stop if a requirement
|
||||
</I>><i> > of a selected package is not met? Or do the packages not check for all
|
||||
</I>><i> > requirements?
|
||||
</I>><i>
|
||||
</I>><i> The top-level configure will fail in any of the packages fail to
|
||||
</I>><i> configure. However, it's possible that some packages may not check for
|
||||
</I>><i> everything they need in their configure scripts.
|
||||
</I>><i>
|
||||
</I>><i> > Because today, I ran into a couple of missing missing libraries when
|
||||
</I>><i> > compiling but autogen.sh didn't tell me that they were missing in the
|
||||
</I>><i> > first place. (e.g. monodoc which is used by the documentation plugin).
|
||||
</I>><i>
|
||||
</I>><i> Do you have a list of the missing checks handy?
|
||||
</I>><i>
|
||||
</I>The only thing I can remember right now is gecko-sharp. I think the
|
||||
aspnet-addin uses it but does not check for it. Because MD crashes due
|
||||
to some Missing-Dll-Exception whenever I click the designer button of
|
||||
aspx-Files.
|
||||
|
||||
But I will check for more dependencies later.
|
||||
|
||||
Kind Regards,
|
||||
Valentin
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: not available
|
||||
Type: application/pgp-signature
|
||||
Size: 197 bytes
|
||||
Desc: This is a digitally signed message part
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080719/d82888b8/attachment.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080719/d82888b8/attachment.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#9">[ date ]</a>
|
||||
<a href="thread.html#9">[ thread ]</a>
|
||||
<a href="subject.html#9">[ subject ]</a>
|
||||
<a href="author.html#9">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,79 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Insufficient Requirement Checks
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=1216460781.3824.3.camel%40pi1536.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000009.html">
|
||||
<LINK REL="Next" HREF="000003.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Insufficient Requirement Checks</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Insufficient%20Requirement%20Checks&In-Reply-To=1216460781.3824.3.camel%40pi1536.site"
|
||||
TITLE="[Monodevelop-devel] Insufficient Requirement Checks">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Sat Jul 19 08:49:00 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#10">[ date ]</a>
|
||||
<a href="thread.html#10">[ thread ]</a>
|
||||
<a href="subject.html#10">[ subject ]</a>
|
||||
<a href="author.html#10">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Sat, Jul 19, 2008 at 5:46 AM, Valentin Sawadski
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">valentin.sawadski at googlemail.com</A>> wrote:
|
||||
>><i> > Because today, I ran into a couple of missing missing libraries when
|
||||
</I>>><i> > compiling but autogen.sh didn't tell me that they were missing in the
|
||||
</I>>><i> > first place. (e.g. monodoc which is used by the documentation plugin).
|
||||
</I>>><i>
|
||||
</I>>><i> Do you have a list of the missing checks handy?
|
||||
</I>>><i>
|
||||
</I>><i> The only thing I can remember right now is gecko-sharp. I think the
|
||||
</I>><i> aspnet-addin uses it but does not check for it. Because MD crashes due
|
||||
</I>><i> to some Missing-Dll-Exception whenever I click the designer button of
|
||||
</I>><i> aspx-Files.
|
||||
</I>
|
||||
AspNetEdit requires it, but it looks like it's checking:
|
||||
<A HREF="http://anonsvn.mono-project.com/viewcvs/trunk/monodevelop/extras/AspNetEdit/configure?view=markup.">http://anonsvn.mono-project.com/viewcvs/trunk/monodevelop/extras/AspNetEdit/configure?view=markup.</A>
|
||||
It looks like the main configure checks for MonoDoc too:
|
||||
<A HREF="http://anonsvn.mono-project.com/viewcvs/trunk/monodevelop/main/configure.in?view=markup">http://anonsvn.mono-project.com/viewcvs/trunk/monodevelop/main/configure.in?view=markup</A>
|
||||
|
||||
Maybe the assemblies are in your pkg-config path but not the GAC? Did
|
||||
you install MonoDoc and Gecko# from source?
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#10">[ date ]</a>
|
||||
<a href="thread.html#10">[ thread ]</a>
|
||||
<a href="subject.html#10">[ subject ]</a>
|
||||
<a href="author.html#10">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,85 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20the%20future%20of%20Prebuild%20and%20xbuild&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000007.html">
|
||||
<LINK REL="Next" HREF="000012.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] the future of Prebuild and xbuild</H1>
|
||||
<B>C.J. Adams-Collier</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20the%20future%20of%20Prebuild%20and%20xbuild&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] the future of Prebuild and xbuild">cjac at colliertech.org
|
||||
</A><BR>
|
||||
<I>Sun Jul 27 19:32:51 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#11">[ date ]</a>
|
||||
<a href="thread.html#11">[ thread ]</a>
|
||||
<a href="subject.html#11">[ subject ]</a>
|
||||
<a href="author.html#11">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hey folks,
|
||||
|
||||
When I was in MA in January, mhutch and I talked about converging the
|
||||
codebases of prebuild and monodevelop. It seems that monodevelop will
|
||||
be using 'xbuild,' which is the Mono version of msbuild. On IRC
|
||||
today, mhutch, sontek an I talked about making things a bit more
|
||||
concrete.
|
||||
|
||||
It seems a wise move to me to alter prebuild to depend on xbuild and
|
||||
hand all of the heavy lifting off to it, providing only the same
|
||||
command line interface.
|
||||
|
||||
Perhaps during a deprecation phase, a warning could be printed and the
|
||||
old back-end could be used. This will allow folks to alter their code
|
||||
while still picking up the latest version of ours.
|
||||
|
||||
Thoughts? ankit, lluis, I hear you're a couple of folks we should get
|
||||
feedback from.
|
||||
|
||||
Cheers,
|
||||
|
||||
C.J.
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: not available
|
||||
Type: application/pgp-signature
|
||||
Size: 189 bytes
|
||||
Desc: Digital signature
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080727/32fdb979/attachment.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080727/32fdb979/attachment.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#11">[ date ]</a>
|
||||
<a href="thread.html#11">[ thread ]</a>
|
||||
<a href="subject.html#11">[ subject ]</a>
|
||||
<a href="author.html#11">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,75 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20gmcs%20bug%20affecting%20MD%20from%20SVN%20%28was%3A%20Re%3A%20HEADS%0A%20UP%3A%20Linear%20IR%20branch%20merge%29&In-Reply-To=488D9E64.10504%40seznam.cz">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000011.html">
|
||||
<LINK REL="Next" HREF="000013.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)</H1>
|
||||
<B>"Andrés G. Aragoneses"</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20gmcs%20bug%20affecting%20MD%20from%20SVN%20%28was%3A%20Re%3A%20HEADS%0A%20UP%3A%20Linear%20IR%20branch%20merge%29&In-Reply-To=488D9E64.10504%40seznam.cz"
|
||||
TITLE="[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)">aaragoneses at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 07:11:35 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#12">[ date ]</a>
|
||||
<a href="thread.html#12">[ thread ]</a>
|
||||
<a href="subject.html#12">[ subject ]</a>
|
||||
<a href="author.html#12">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Marek Safar wrote:
|
||||
><i> Hello,
|
||||
</I>>><i> Arghh, same issue with gmcs from SVN. Marek, are you already aware of
|
||||
</I>>><i> this issue or do you want me to file a bug..?
|
||||
</I>>><i>
|
||||
</I>><i> No, please fill a bug report.
|
||||
</I>
|
||||
Thanks for your reply Marek!:
|
||||
<A HREF="https://bugzilla.novell.com/show_bug.cgi?id=412595">https://bugzilla.novell.com/show_bug.cgi?id=412595</A>
|
||||
|
||||
I'll try to cook a smaller testcase if I have enough time.
|
||||
|
||||
FYI: checkout monodevelop rev 108914 as a workaround to this problem.
|
||||
|
||||
Regards,
|
||||
|
||||
Andrés
|
||||
|
||||
--
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#12">[ date ]</a>
|
||||
<a href="thread.html#12">[ thread ]</a>
|
||||
<a href="subject.html#12">[ subject ]</a>
|
||||
<a href="author.html#12">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,95 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BMonoDevelop%5D%20Current%20SVN%20version%20may%20be%0A%09buggy/dom%20changes&In-Reply-To=1217155919.14035.5.camel%40Shattrath.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000012.html">
|
||||
<LINK REL="Next" HREF="000019.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BMonoDevelop%5D%20Current%20SVN%20version%20may%20be%0A%09buggy/dom%20changes&In-Reply-To=1217155919.14035.5.camel%40Shattrath.site"
|
||||
TITLE="[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 14:30:57 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#13">[ date ]</a>
|
||||
<a href="thread.html#13">[ thread ]</a>
|
||||
<a href="subject.html#13">[ subject ]</a>
|
||||
<a href="author.html#13">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Sun, Jul 27, 2008 at 6:51 AM, Mike Krüger <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkrueger at novell.com</A>> wrote:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> Today I've submitted my latest dom changes. Do not use the current SVN
|
||||
</I>><i> version for daily use. I've tested the changes and work with the
|
||||
</I>><i> version.
|
||||
</I>><i>
|
||||
</I>><i> We'll add nice features like C#3 support, instant code completion and a
|
||||
</I>><i> new code completion database backend based on sqlite. (Also the new code
|
||||
</I>><i> completion should be faster on large files - but I need to test it)
|
||||
</I>><i> Currently all refactoring support is broken. I think I've fixed it next
|
||||
</I>><i> week. The next weeks I'll work on stabilizing the new changes and adding
|
||||
</I>><i> c#3 support.
|
||||
</I>
|
||||
The DOM changes have resulted in severe regressions in the ASP.NET
|
||||
binding, among many other things (including C# completion,
|
||||
refactoring, stetic, etc). The CodeBehind member generation is
|
||||
completely broken, and will have to be ported to use the new DOM, as
|
||||
will the BindingService and CodeRefactorer that it uses.
|
||||
|
||||
More importantly, the Parser infrastructure and the type/member lookup
|
||||
used by the ASP.NET code completion is totally non-operational. As I'm
|
||||
working on the ASP.NET code completion, this makes things difficult
|
||||
for me. I can work around it for now, but I need this stuff to be
|
||||
operational soon.
|
||||
|
||||
How soon are these likely to be fixed? Could we have a summary of the
|
||||
changes that need to be made to existing code to port it to the new
|
||||
parser infrastructure and DOM?
|
||||
|
||||
If these won't be fixed soon, I suggest that we move the changes into
|
||||
a svn branch, and revert the changes on trunk. We could then remove
|
||||
the old DOM and parser infrastructure in order to track down *ALL* the
|
||||
places that need to be fixed, before merging back to trunk.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#13">[ date ]</a>
|
||||
<a href="thread.html#13">[ thread ]</a>
|
||||
<a href="subject.html#13">[ subject ]</a>
|
||||
<a href="author.html#13">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,110 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000019.html">
|
||||
<LINK REL="Next" HREF="000015.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 16:59:08 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#14">[ date ]</a>
|
||||
<a href="thread.html#14">[ thread ]</a>
|
||||
<a href="subject.html#14">[ subject ]</a>
|
||||
<a href="author.html#14">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi,
|
||||
|
||||
This discussion should have been done before committing anything to
|
||||
trunk, but here it is anyway.
|
||||
|
||||
Migrating to SQLite only makes sense if it provides noticeable
|
||||
improvements in performance and memory use. Guessing that it will be
|
||||
better is not enough. We need real numbers before taking the decision to
|
||||
switch, and only do it if the numbers are so much better that pay off
|
||||
the burden of having a dependency on SQLite.
|
||||
|
||||
I might be wrong, but I don't believe that SQLite will be better than
|
||||
the ad-hoc database we are using in MD 1.0. I spent a lot of time tuning
|
||||
up the parser database, and I'm quite happy about how is it performing.
|
||||
|
||||
The old .pidb files are split in two sections. The first section is an
|
||||
index of the database contents. It has the names of all types in the
|
||||
project/assembly, sub-class relations, the hierarchy of namespaces, the
|
||||
source code files, and all the relations between them. This index is
|
||||
fully loaded in memory and has enough information for the most common
|
||||
queries: type lookup, getting types in a namespace or file, querying
|
||||
subclasses, etc.
|
||||
|
||||
The second section contains the full information for every class. This
|
||||
section is never fully loaded in memory. Every class entry in the index
|
||||
contains the file offset of the full information of the class in the
|
||||
second section. When needed, that class information is loaded using an
|
||||
ad-hoc binary serializer, which is as fast as it can be. The number of
|
||||
classes which are fully loaded in memory is limited to 100. Only the
|
||||
most 100 recently used classes are fully kept in memory. This limit
|
||||
prevents the parser database from using too much memory and still keep a
|
||||
good performance.
|
||||
|
||||
However, all this infrastructure is transparent to the database user.
|
||||
For example, the method GetSubclasses will return a list of IClass
|
||||
objects, but those IClass objects are not fully loaded, they are just
|
||||
'proxies'. They only contain information from the index, that is, the
|
||||
class name, namespace and visibility flags. This is all the information
|
||||
needed to fill the code completion window for the 'new' keyword, for
|
||||
example. If more information is requested, such as the class
|
||||
documentation or the list of members, all that information is lazily
|
||||
loaded from the database.
|
||||
|
||||
The result is that queries on the database are fast (because in many
|
||||
cases the required information is already in memory), and have a good
|
||||
memory use (because the biggest section of the database is never fully
|
||||
loaded). Could it be better? maybe, but I think it is good enough
|
||||
(especially regarding memory use, it is much better than Visual Studio
|
||||
and #develop).
|
||||
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#14">[ date ]</a>
|
||||
<a href="thread.html#14">[ thread ]</a>
|
||||
<a href="subject.html#14">[ subject ]</a>
|
||||
<a href="author.html#14">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,100 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217278748.3843.136.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000014.html">
|
||||
<LINK REL="Next" HREF="000017.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217278748.3843.136.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 17:44:53 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#15">[ date ]</a>
|
||||
<a href="thread.html#15">[ thread ]</a>
|
||||
<a href="subject.html#15">[ subject ]</a>
|
||||
<a href="author.html#15">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> This discussion should have been done before committing anything to
|
||||
</I>><i> trunk, but here it is anyway.
|
||||
</I>><i>
|
||||
</I>><i> Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>><i> improvements in performance and memory use. Guessing that it will be
|
||||
</I>><i> better is not enough. We need real numbers before taking the decision
|
||||
</I>><i> to
|
||||
</I>><i> switch, and only do it if the numbers are so much better that pay off
|
||||
</I>><i> the burden of having a dependency on SQLite.
|
||||
</I>><i>
|
||||
</I>><i> I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>><i> the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>><i> tuning
|
||||
</I>><i> up the parser database, and I'm quite happy about how is it
|
||||
</I>><i> performing.
|
||||
</I>><i>
|
||||
</I>
|
||||
Some more benefits for using a real database over an own implementation:
|
||||
|
||||
- It's reliable. Atomic transactions, threading - all solved.
|
||||
- It's easy to look into the data using a command line client and SQL
|
||||
statements
|
||||
|
||||
Its not just pure performance. Using a database will allow us for
|
||||
example to switch the database software to a new implementation. And
|
||||
databases and SQL are very easy to understood and to change.
|
||||
|
||||
I had to think about it too (I implemented the #develop database some
|
||||
years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
after thinking about it the decision was easy - A database makes it
|
||||
easier to change the model and to make complicated querys more
|
||||
efficient.
|
||||
|
||||
There are many more reasons using database software instead of own data
|
||||
storage solutions - otherwise the whole database software would be
|
||||
obsolete.
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#15">[ date ]</a>
|
||||
<a href="thread.html#15">[ thread ]</a>
|
||||
<a href="subject.html#15">[ subject ]</a>
|
||||
<a href="author.html#15">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,117 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000017.html">
|
||||
<LINK REL="Next" HREF="000021.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 18:08:36 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#16">[ date ]</a>
|
||||
<a href="thread.html#16">[ thread ]</a>
|
||||
<a href="subject.html#16">[ subject ]</a>
|
||||
<a href="author.html#16">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi,
|
||||
|
||||
On Mon, Jul 28, 2008 at 2:44 PM, Mike Krüger <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkrueger at novell.com</A>> wrote:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>>><i> This discussion should have been done before committing anything to
|
||||
</I>>><i> trunk, but here it is anyway.
|
||||
</I>>><i>
|
||||
</I>>><i> Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>>><i> improvements in performance and memory use. Guessing that it will be
|
||||
</I>>><i> better is not enough. We need real numbers before taking the decision
|
||||
</I>>><i> to
|
||||
</I>>><i> switch, and only do it if the numbers are so much better that pay off
|
||||
</I>>><i> the burden of having a dependency on SQLite.
|
||||
</I>>><i>
|
||||
</I>>><i> I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>>><i> the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>>><i> tuning
|
||||
</I>>><i> up the parser database, and I'm quite happy about how is it
|
||||
</I>>><i> performing.
|
||||
</I>>><i>
|
||||
</I>><i>
|
||||
</I>><i> Some more benefits for using a real database over an own implementation:
|
||||
</I>><i>
|
||||
</I>><i> - It's reliable. Atomic transactions, threading - all solved.
|
||||
</I>
|
||||
While I'm happy with either solution, lets keep in mind that sqlite is
|
||||
not thread-safe by default (requires SQLITE_THREADSAFE=1 at compile
|
||||
time). So we will need to queue queries via a single-thread unless we
|
||||
can guarantee our sqlite version.
|
||||
|
||||
Perhaps the sqlite wrappers take care of that now, I really haven't checked.
|
||||
|
||||
><i> - It's easy to look into the data using a command line client and SQL
|
||||
</I>><i> statements
|
||||
</I>><i>
|
||||
</I>><i> Its not just pure performance. Using a database will allow us for
|
||||
</I>><i> example to switch the database software to a new implementation. And
|
||||
</I>><i> databases and SQL are very easy to understood and to change.
|
||||
</I>><i>
|
||||
</I>><i> I had to think about it too (I implemented the #develop database some
|
||||
</I>><i> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>><i> after thinking about it the decision was easy - A database makes it
|
||||
</I>><i> easier to change the model and to make complicated querys more
|
||||
</I>><i> efficient.
|
||||
</I>><i>
|
||||
</I>><i> There are many more reasons using database software instead of own data
|
||||
</I>><i> storage solutions - otherwise the whole database software would be
|
||||
</I>><i> obsolete.
|
||||
</I>><i>
|
||||
</I>><i> Regards
|
||||
</I>><i> Mike
|
||||
</I>><i>
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>><i>
|
||||
</I></PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#16">[ date ]</a>
|
||||
<a href="thread.html#16">[ thread ]</a>
|
||||
<a href="subject.html#16">[ subject ]</a>
|
||||
<a href="author.html#16">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,94 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000015.html">
|
||||
<LINK REL="Next" HREF="000016.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Federico Di Gregorio</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">fog at initd.org
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 18:06:38 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#17">[ date ]</a>
|
||||
<a href="thread.html#17">[ thread ]</a>
|
||||
<a href="subject.html#17">[ subject ]</a>
|
||||
<a href="author.html#17">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Il giorno lun, 28/07/2008 alle 23.44 +0200, Mike Krüger ha scritto:
|
||||
><i> I had to think about it too (I implemented the #develop database some
|
||||
</I>><i> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>><i> after thinking about it the decision was easy - A database makes it
|
||||
</I>><i> easier to change the model and to make complicated querys more
|
||||
</I>><i> efficient.
|
||||
</I>
|
||||
Actually a standard query language allow to make complicated queries
|
||||
easier to understand but almost never more efficient. We use SQL because
|
||||
it has a very stable and well-know mathematical foundation and very good
|
||||
implementations but a specialized storage format is almost always
|
||||
faster.
|
||||
|
||||
><i> There are many more reasons using database software instead of own data
|
||||
</I>><i> storage solutions - otherwise the whole database software would be
|
||||
</I>><i> obsolete.
|
||||
</I>
|
||||
In fact we use specialized storage formats for a lot of application
|
||||
domains where standard SQL would be too slow. The fact that most of the
|
||||
problems can be solved by SQL doesn't mean that SQL is good for
|
||||
anything.
|
||||
|
||||
Said that, probably SQLite would be fast enough.
|
||||
|
||||
--
|
||||
Federico Di Gregorio <A HREF="http://people.initd.org/fog">http://people.initd.org/fog</A>
|
||||
Debian GNU/Linux Developer <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">fog at debian.org</A>
|
||||
INIT.D Developer <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">fog at initd.org</A>
|
||||
E tu usa il prefisso corretto Re: non R:, questa è una ML seria.
|
||||
-- cosmos, su debian-italian
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: not available
|
||||
Type: application/pgp-signature
|
||||
Size: 197 bytes
|
||||
Desc: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio
|
||||
firmata digitalmente
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080729/2cdd9ed7/attachment.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20080729/2cdd9ed7/attachment.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#17">[ date ]</a>
|
||||
<a href="thread.html#17">[ thread ]</a>
|
||||
<a href="subject.html#17">[ subject ]</a>
|
||||
<a href="author.html#17">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,157 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Some new DOM guidance
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Some%20new%20DOM%20guidance&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000026.html">
|
||||
<LINK REL="Next" HREF="000020.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Some new DOM guidance</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Some%20new%20DOM%20guidance&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Some new DOM guidance">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 18:23:16 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#18">[ date ]</a>
|
||||
<a href="thread.html#18">[ thread ]</a>
|
||||
<a href="subject.html#18">[ subject ]</a>
|
||||
<a href="author.html#18">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
Ok. I tried to make it easy to convert old dom code over to new dom
|
||||
code.
|
||||
|
||||
|
||||
Basically it's:
|
||||
|
||||
not longer:
|
||||
using MonoDevelop.Projects.Parser;
|
||||
|
||||
instead:
|
||||
using MonoDevelop.Projects.Dom;
|
||||
|
||||
not longer: IClass instead: IType
|
||||
|
||||
Parser registration (with the addin tree):
|
||||
|
||||
<Extension path = "/MonoDevelop/Ide/DomParser">
|
||||
<Class class = "MonoDevelop.CSharpBinding.DomParser" />
|
||||
</Extension>
|
||||
|
||||
The parser must extend the MonoDevelop.Projects.Dom.Parser.IParser
|
||||
interface. I recommend inheriting from
|
||||
MonoDevelop.Projects.Dom.Parser.AbstractParser which makes changes in
|
||||
the interface more easy.
|
||||
|
||||
Generally I tried to move functions from some services to the objects
|
||||
directly. For example - monodoc documentation could be now accessed by
|
||||
System.Xml.XmlNode GetMonodocDocumentation (); instead of the
|
||||
documentation service. Or the icon could be get by
|
||||
string StockIcon { get; } instead of using the IconService. I'll add
|
||||
more functions to the dom. The goal is to make it easier to find
|
||||
functions and bring back some responsibility to the objects.
|
||||
|
||||
|
||||
GETTING PARSE INFOS:
|
||||
|
||||
MonoDevelop.Ide.Gui.Document
|
||||
|
||||
now contains:
|
||||
public ICompilationUnit CompilationUnit {
|
||||
get;
|
||||
}
|
||||
In former versions the document contained only the text contents, now it
|
||||
contains the most recent parse information too.
|
||||
|
||||
|
||||
For the rest - look at:
|
||||
MonoDevelop.Projects.Dom.Parser.ProjectDomService
|
||||
|
||||
There you have functions like:
|
||||
IParser GetParserByMime (string mimeType);
|
||||
IParser GetParserByFileName (string fileName);
|
||||
|
||||
ICompilationUnit Parse (Project project,
|
||||
string fileName,
|
||||
string mimeType)
|
||||
|
||||
|
||||
For projects:
|
||||
ProjectDom GetDatabaseProjectDom (Project project);
|
||||
The ProjectDom contains the project parser info (was ParserContext in
|
||||
former versions)
|
||||
|
||||
The Projects will contain the ProjectDom as property, but currently I
|
||||
had already too many name clashes. After removing the old infrastructure
|
||||
I'll do some refactorings to make the access easier. (I could need some
|
||||
input here - maybe someone has new ideas what's missing. Like
|
||||
the CompilationUnit inside the Document).
|
||||
|
||||
The project dom contains some functions old dom users will find very
|
||||
familiar (like GetNamespaceContents, SearchType).
|
||||
|
||||
|
||||
I've converted much old code - most is done with renaming and switch
|
||||
over the usings. If you've more questions feel free to ask.
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#18">[ date ]</a>
|
||||
<a href="thread.html#18">[ thread ]</a>
|
||||
<a href="subject.html#18">[ subject ]</a>
|
||||
<a href="author.html#18">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,96 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BMonoDevelop%5D%20Current%20SVN%20version%20may%0A%09be%09buggy/dom%20changes&In-Reply-To=aec34c770807281130x17401769td9861548573c697%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000013.html">
|
||||
<LINK REL="Next" HREF="000014.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5BMonoDevelop%5D%20Current%20SVN%20version%20may%0A%09be%09buggy/dom%20changes&In-Reply-To=aec34c770807281130x17401769td9861548573c697%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 19:15:00 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#19">[ date ]</a>
|
||||
<a href="thread.html#19">[ thread ]</a>
|
||||
<a href="subject.html#19">[ subject ]</a>
|
||||
<a href="author.html#19">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Mike, can you give the estimated number of days it will take you to fix
|
||||
all this?
|
||||
|
||||
El dl 28 de 07 de 2008 a les 14:30 -0400, en/na Michael Hutchinson va
|
||||
escriure:
|
||||
><i> On Sun, Jul 27, 2008 at 6:51 AM, Mike Krüger <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkrueger at novell.com</A>> wrote:
|
||||
</I>><i> > Hi
|
||||
</I>><i> >
|
||||
</I>><i> > Today I've submitted my latest dom changes. Do not use the current SVN
|
||||
</I>><i> > version for daily use. I've tested the changes and work with the
|
||||
</I>><i> > version.
|
||||
</I>><i> >
|
||||
</I>><i> > We'll add nice features like C#3 support, instant code completion and a
|
||||
</I>><i> > new code completion database backend based on sqlite. (Also the new code
|
||||
</I>><i> > completion should be faster on large files - but I need to test it)
|
||||
</I>><i> > Currently all refactoring support is broken. I think I've fixed it next
|
||||
</I>><i> > week. The next weeks I'll work on stabilizing the new changes and adding
|
||||
</I>><i> > c#3 support.
|
||||
</I>><i>
|
||||
</I>><i> The DOM changes have resulted in severe regressions in the ASP.NET
|
||||
</I>><i> binding, among many other things (including C# completion,
|
||||
</I>><i> refactoring, stetic, etc). The CodeBehind member generation is
|
||||
</I>><i> completely broken, and will have to be ported to use the new DOM, as
|
||||
</I>><i> will the BindingService and CodeRefactorer that it uses.
|
||||
</I>><i>
|
||||
</I>><i> More importantly, the Parser infrastructure and the type/member lookup
|
||||
</I>><i> used by the ASP.NET code completion is totally non-operational. As I'm
|
||||
</I>><i> working on the ASP.NET code completion, this makes things difficult
|
||||
</I>><i> for me. I can work around it for now, but I need this stuff to be
|
||||
</I>><i> operational soon.
|
||||
</I>><i>
|
||||
</I>><i> How soon are these likely to be fixed? Could we have a summary of the
|
||||
</I>><i> changes that need to be made to existing code to port it to the new
|
||||
</I>><i> parser infrastructure and DOM?
|
||||
</I>><i>
|
||||
</I>><i> If these won't be fixed soon, I suggest that we move the changes into
|
||||
</I>><i> a svn branch, and revert the changes on trunk. We could then remove
|
||||
</I>><i> the old DOM and parser infrastructure in order to track down *ALL* the
|
||||
</I>><i> places that need to be fixed, before merging back to trunk.
|
||||
</I>><i>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#19">[ date ]</a>
|
||||
<a href="thread.html#19">[ thread ]</a>
|
||||
<a href="subject.html#19">[ subject ]</a>
|
||||
<a href="author.html#19">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,194 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Some new DOM guidance
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Some%20new%20DOM%20guidance&In-Reply-To=1217283796.9571.21.camel%40Shattrath.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000018.html">
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Some new DOM guidance</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Some%20new%20DOM%20guidance&In-Reply-To=1217283796.9571.21.camel%40Shattrath.site"
|
||||
TITLE="[Monodevelop-devel] Some new DOM guidance">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 19:54:31 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#20">[ date ]</a>
|
||||
<a href="thread.html#20">[ thread ]</a>
|
||||
<a href="subject.html#20">[ subject ]</a>
|
||||
<a href="author.html#20">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi!
|
||||
|
||||
Let's explicitly set the rule (although I think it is obvious): if
|
||||
somebody does a big change or refactoring in the MD core, he is
|
||||
responsible for ensuring that *all* projects in MD (including everything
|
||||
in extras) can be properly built and work as expected (modulo bugs to be
|
||||
fixed as soon as possible when arise). You should take into account that
|
||||
you are not working alone in the project, and that other people have
|
||||
better thing to do than tracking api breakages.
|
||||
|
||||
For a big change such as the project dom change, the correct process
|
||||
would be this:
|
||||
|
||||
* Create a branch.
|
||||
* Do all changes in the branch, removing old code and adding the
|
||||
new one.
|
||||
* While doing the changes, merge back to the branch the commits
|
||||
done by other people in trunk ('svn merge' is very helpful for
|
||||
this).
|
||||
* Fix all projects using the old code, change them to use the new
|
||||
api.
|
||||
* Do the basic tests to ensure that everything is working fine.
|
||||
* Announce the availability of the new branch, and open the branch
|
||||
for testing, so that other developers can ensure that there are
|
||||
no issues with their own projects.
|
||||
* Dogfooding: install and use the new MD for at least a couple of
|
||||
weeks.
|
||||
* At least one day before the merge to trunk, announce the
|
||||
upcoming massive change, so people have time to commit pending
|
||||
changes.
|
||||
* Resolve the final conflicts caused by last minute commits.
|
||||
* Do the merge and announce it.
|
||||
|
||||
Lluis.
|
||||
|
||||
El dt 29 de 07 de 2008 a les 00:23 +0200, en/na Mike Krüger va escriure:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> Ok. I tried to make it easy to convert old dom code over to new dom
|
||||
</I>><i> code.
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> Basically it's:
|
||||
</I>><i>
|
||||
</I>><i> not longer:
|
||||
</I>><i> using MonoDevelop.Projects.Parser;
|
||||
</I>><i>
|
||||
</I>><i> instead:
|
||||
</I>><i> using MonoDevelop.Projects.Dom;
|
||||
</I>><i>
|
||||
</I>><i> not longer: IClass instead: IType
|
||||
</I>><i>
|
||||
</I>><i> Parser registration (with the addin tree):
|
||||
</I>><i>
|
||||
</I>><i> <Extension path = "/MonoDevelop/Ide/DomParser">
|
||||
</I>><i> <Class class = "MonoDevelop.CSharpBinding.DomParser" />
|
||||
</I>><i> </Extension>
|
||||
</I>><i>
|
||||
</I>><i> The parser must extend the MonoDevelop.Projects.Dom.Parser.IParser
|
||||
</I>><i> interface. I recommend inheriting from
|
||||
</I>><i> MonoDevelop.Projects.Dom.Parser.AbstractParser which makes changes in
|
||||
</I>><i> the interface more easy.
|
||||
</I>><i>
|
||||
</I>><i> Generally I tried to move functions from some services to the objects
|
||||
</I>><i> directly. For example - monodoc documentation could be now accessed by
|
||||
</I>><i> System.Xml.XmlNode GetMonodocDocumentation (); instead of the
|
||||
</I>><i> documentation service. Or the icon could be get by
|
||||
</I>><i> string StockIcon { get; } instead of using the IconService. I'll add
|
||||
</I>><i> more functions to the dom. The goal is to make it easier to find
|
||||
</I>><i> functions and bring back some responsibility to the objects.
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> GETTING PARSE INFOS:
|
||||
</I>><i>
|
||||
</I>><i> MonoDevelop.Ide.Gui.Document
|
||||
</I>><i>
|
||||
</I>><i> now contains:
|
||||
</I>><i> public ICompilationUnit CompilationUnit {
|
||||
</I>><i> get;
|
||||
</I>><i> }
|
||||
</I>><i> In former versions the document contained only the text contents, now it
|
||||
</I>><i> contains the most recent parse information too.
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> For the rest - look at:
|
||||
</I>><i> MonoDevelop.Projects.Dom.Parser.ProjectDomService
|
||||
</I>><i>
|
||||
</I>><i> There you have functions like:
|
||||
</I>><i> IParser GetParserByMime (string mimeType);
|
||||
</I>><i> IParser GetParserByFileName (string fileName);
|
||||
</I>><i>
|
||||
</I>><i> ICompilationUnit Parse (Project project,
|
||||
</I>><i> string fileName,
|
||||
</I>><i> string mimeType)
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> For projects:
|
||||
</I>><i> ProjectDom GetDatabaseProjectDom (Project project);
|
||||
</I>><i> The ProjectDom contains the project parser info (was ParserContext in
|
||||
</I>><i> former versions)
|
||||
</I>><i>
|
||||
</I>><i> The Projects will contain the ProjectDom as property, but currently I
|
||||
</I>><i> had already too many name clashes. After removing the old infrastructure
|
||||
</I>><i> I'll do some refactorings to make the access easier. (I could need some
|
||||
</I>><i> input here - maybe someone has new ideas what's missing. Like
|
||||
</I>><i> the CompilationUnit inside the Document).
|
||||
</I>><i>
|
||||
</I>><i> The project dom contains some functions old dom users will find very
|
||||
</I>><i> familiar (like GetNamespaceContents, SearchType).
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> I've converted much old code - most is done with renaming and switch
|
||||
</I>><i> over the usings. If you've more questions feel free to ask.
|
||||
</I>><i>
|
||||
</I>><i> Regards
|
||||
</I>><i> Mike
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#20">[ date ]</a>
|
||||
<a href="thread.html#20">[ thread ]</a>
|
||||
<a href="subject.html#20">[ subject ]</a>
|
||||
<a href="author.html#20">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,153 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000016.html">
|
||||
<LINK REL="Next" HREF="000022.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 21:36:06 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#21">[ date ]</a>
|
||||
<a href="thread.html#21">[ thread ]</a>
|
||||
<a href="subject.html#21">[ subject ]</a>
|
||||
<a href="author.html#21">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dl 28 de 07 de 2008 a les 23:44 +0200, en/na Mike Krüger va escriure:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> > This discussion should have been done before committing anything to
|
||||
</I>><i> > trunk, but here it is anyway.
|
||||
</I>><i> >
|
||||
</I>><i> > Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>><i> > improvements in performance and memory use. Guessing that it will be
|
||||
</I>><i> > better is not enough. We need real numbers before taking the decision
|
||||
</I>><i> > to
|
||||
</I>><i> > switch, and only do it if the numbers are so much better that pay off
|
||||
</I>><i> > the burden of having a dependency on SQLite.
|
||||
</I>><i> >
|
||||
</I>><i> > I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>><i> > the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>><i> > tuning
|
||||
</I>><i> > up the parser database, and I'm quite happy about how is it
|
||||
</I>><i> > performing.
|
||||
</I>><i> >
|
||||
</I>><i>
|
||||
</I>><i> Some more benefits for using a real database over an own implementation:
|
||||
</I>><i>
|
||||
</I>><i> - It's reliable. Atomic transactions, threading - all solved.
|
||||
</I>
|
||||
Transactions and threading are not a problem for the parser database, so
|
||||
that's not a real benefit.
|
||||
|
||||
><i> - It's easy to look into the data using a command line client and SQL
|
||||
</I>><i> statements
|
||||
</I>
|
||||
This is cool, but it has never been a requirement.
|
||||
|
||||
><i>
|
||||
</I>><i> Its not just pure performance. Using a database will allow us for
|
||||
</I>><i> example to switch the database software to a new implementation. And
|
||||
</I>><i> databases and SQL are very easy to understood and to change.
|
||||
</I>><i>
|
||||
</I>><i> I had to think about it too (I implemented the #develop database some
|
||||
</I>><i> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>
|
||||
That's not correct, MD's parser database was written from scratch. The
|
||||
inherited implementation would load everything in memory and would
|
||||
collapse the system trying to open the MD solution.
|
||||
|
||||
><i> after thinking about it the decision was easy - A database makes it
|
||||
</I>><i> easier to change the model and to make complicated querys more
|
||||
</I>><i> efficient.
|
||||
</I>
|
||||
But curiously they are especially bad at querying hierarchies of objects
|
||||
(such as namespace hierarchies or subclass hierarchies), unless you
|
||||
denormalize the tables.
|
||||
|
||||
Yes, databases are powerful. They can do amazing things with little
|
||||
effort. But generic databases don't fit everywhere. A well designed
|
||||
ad-hoc database may be better than a generic RDBMS, even if less
|
||||
powerful. Everything depends on the requirements and constraints of the
|
||||
application. For the specific case of the parser database, here are some
|
||||
requirements:
|
||||
|
||||
* Type and namespace lookup must be lightning fast. Type and
|
||||
namespace queries are used by the parser when resolving types,
|
||||
and by code completion when showing completion entries. I don't
|
||||
think we can afford hitting the disk for that kind of queries.
|
||||
* Most of operations are read operations, so the database must be
|
||||
optimized for reading. Write operations are much less common
|
||||
than reads.
|
||||
* The data is the database is discardable. It is always possible
|
||||
to regenerate a database by re-parsing a project or an assembly.
|
||||
* Memory usage must be contained. Project and assembly databases
|
||||
may contain a huge amount of information.
|
||||
* The set of queries that it has to support is known and limited.
|
||||
Those are basically:
|
||||
* Get all types.
|
||||
* Get all types implemented in a file, given the file
|
||||
name.
|
||||
* Get all subclasses of a class, given class name.
|
||||
* Get a type, given the type name.
|
||||
* Get all types and sub-namespaces of a namespace.
|
||||
* Get all sub-namespaces of a namespace.
|
||||
|
||||
A designer has to find the solution that better fulfills the constraints
|
||||
and requirements of an application. In the parser case, given the
|
||||
constraints we have, I think an ad-hoc database may perform better. Of
|
||||
course I might be wrong, since I haven't done any tests with SQLite, but
|
||||
I yet have to see a proof of the contrary.
|
||||
|
||||
><i>
|
||||
</I>><i> There are many more reasons using database software instead of own data
|
||||
</I>><i> storage solutions - otherwise the whole database software would be
|
||||
</I>><i> obsolete.
|
||||
</I>
|
||||
There are also many more reasons for not using databases, otherwise all
|
||||
applications would be using them.
|
||||
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#21">[ date ]</a>
|
||||
<a href="thread.html#21">[ thread ]</a>
|
||||
<a href="subject.html#21">[ subject ]</a>
|
||||
<a href="author.html#21">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,191 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217295366.3843.230.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000021.html">
|
||||
<LINK REL="Next" HREF="000025.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217295366.3843.230.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Jul 28 23:40:21 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#22">[ date ]</a>
|
||||
<a href="thread.html#22">[ thread ]</a>
|
||||
<a href="subject.html#22">[ subject ]</a>
|
||||
<a href="author.html#22">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Mon, Jul 28, 2008 at 9:36 PM, Lluis Sanchez Gual <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lluis at novell.com</A>> wrote:
|
||||
><i> El dl 28 de 07 de 2008 a les 23:44 +0200, en/na Mike Krüger va escriure:
|
||||
</I>>><i> Hi
|
||||
</I>>><i>
|
||||
</I>>><i> > This discussion should have been done before committing anything to
|
||||
</I>>><i> > trunk, but here it is anyway.
|
||||
</I>>><i> >
|
||||
</I>>><i> > Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>>><i> > improvements in performance and memory use. Guessing that it will be
|
||||
</I>>><i> > better is not enough. We need real numbers before taking the decision
|
||||
</I>>><i> > to
|
||||
</I>>><i> > switch, and only do it if the numbers are so much better that pay off
|
||||
</I>>><i> > the burden of having a dependency on SQLite.
|
||||
</I>>><i> >
|
||||
</I>>><i> > I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>>><i> > the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>>><i> > tuning
|
||||
</I>>><i> > up the parser database, and I'm quite happy about how is it
|
||||
</I>>><i> > performing.
|
||||
</I>>><i> >
|
||||
</I>>><i>
|
||||
</I>>><i> Some more benefits for using a real database over an own implementation:
|
||||
</I>>><i>
|
||||
</I>>><i> - It's reliable. Atomic transactions, threading - all solved.
|
||||
</I>><i>
|
||||
</I>><i> Transactions and threading are not a problem for the parser database, so
|
||||
</I>><i> that's not a real benefit.
|
||||
</I>
|
||||
Multithreaded *writes* could be useful if we're parsing on multiple
|
||||
cores, but those aren't going to happen with SQLite just yet anyway...
|
||||
|
||||
>><i> - It's easy to look into the data using a command line client and SQL
|
||||
</I>>><i> statements
|
||||
</I>><i>
|
||||
</I>><i> This is cool, but it has never been a requirement.
|
||||
</I>
|
||||
I found this appealing :-)
|
||||
|
||||
>><i> Its not just pure performance. Using a database will allow us for
|
||||
</I>>><i> example to switch the database software to a new implementation. And
|
||||
</I>>><i> databases and SQL are very easy to understood and to change.
|
||||
</I>>><i>
|
||||
</I>>><i> I had to think about it too (I implemented the #develop database some
|
||||
</I>>><i> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>><i>
|
||||
</I>><i> That's not correct, MD's parser database was written from scratch. The
|
||||
</I>><i> inherited implementation would load everything in memory and would
|
||||
</I>><i> collapse the system trying to open the MD solution.
|
||||
</I>><i>
|
||||
</I>>><i> after thinking about it the decision was easy - A database makes it
|
||||
</I>>><i> easier to change the model and to make complicated querys more
|
||||
</I>>><i> efficient.
|
||||
</I>><i>
|
||||
</I>><i> But curiously they are especially bad at querying hierarchies of objects
|
||||
</I>><i> (such as namespace hierarchies or subclass hierarchies), unless you
|
||||
</I>><i> denormalize the tables.
|
||||
</I>
|
||||
Isn't that true of an ad-hoc DB too?
|
||||
|
||||
><i> Yes, databases are powerful. They can do amazing things with little
|
||||
</I>><i> effort. But generic databases don't fit everywhere. A well designed
|
||||
</I>><i> ad-hoc database may be better than a generic RDBMS, even if less
|
||||
</I>><i> powerful. Everything depends on the requirements and constraints of the
|
||||
</I>><i> application. For the specific case of the parser database, here are some
|
||||
</I>><i> requirements:
|
||||
</I>><i>
|
||||
</I>><i> * Type and namespace lookup must be lightning fast. Type and
|
||||
</I>><i> namespace queries are used by the parser when resolving types,
|
||||
</I>><i> and by code completion when showing completion entries. I don't
|
||||
</I>><i> think we can afford hitting the disk for that kind of queries.
|
||||
</I>
|
||||
AFAIK, SQLite maintains an in-memory cache of configurable size, so as
|
||||
long as the databases are properly indexed, this shouldn't be an
|
||||
issue.
|
||||
|
||||
><i> * Most of operations are read operations, so the database must be
|
||||
</I>><i> optimized for reading. Write operations are much less common
|
||||
</I>><i> than reads.
|
||||
</I>
|
||||
This is true of SQLite.
|
||||
|
||||
><i> * The data is the database is discardable. It is always possible
|
||||
</I>><i> to regenerate a database by re-parsing a project or an assembly.
|
||||
</I>><i> * Memory usage must be contained. Project and assembly databases
|
||||
</I>><i> may contain a huge amount of information.
|
||||
</I>><i> * The set of queries that it has to support is known and limited.
|
||||
</I>><i> Those are basically:
|
||||
</I>><i> * Get all types.
|
||||
</I>><i> * Get all types implemented in a file, given the file
|
||||
</I>><i> name.
|
||||
</I>><i> * Get all subclasses of a class, given class name.
|
||||
</I>><i> * Get a type, given the type name.
|
||||
</I>><i> * Get all types and sub-namespaces of a namespace.
|
||||
</I>><i> * Get all sub-namespaces of a namespace.
|
||||
</I>
|
||||
I would also like to be able to extend the parser DB to store the
|
||||
C/C++ symbols. This should be relatively easy with SQLite.
|
||||
|
||||
It would also be nice to store the amount of times a particular item
|
||||
has been selected from the code completion list, so that if there are
|
||||
a number of completion entries that match the currently typed prefix,
|
||||
the completion window can select the most likely one. Visual Studio
|
||||
does this and it's *very* useful. Things like this would be pretty
|
||||
easy to implement with SQLite. We could also maintain various other
|
||||
tables and indices to accelerate things like "find references", which
|
||||
would help with speeding up renaming and other such refactorings.
|
||||
|
||||
><i> A designer has to find the solution that better fulfills the constraints
|
||||
</I>><i> and requirements of an application. In the parser case, given the
|
||||
</I>><i> constraints we have, I think an ad-hoc database may perform better. Of
|
||||
</I>><i> course I might be wrong, since I haven't done any tests with SQLite, but
|
||||
</I>><i> I yet have to see a proof of the contrary.
|
||||
</I>
|
||||
This is a fair point, and we should definitely perform benchmarks
|
||||
before coming to a conclusion.
|
||||
|
||||
>><i> There are many more reasons using database software instead of own data
|
||||
</I>>><i> storage solutions - otherwise the whole database software would be
|
||||
</I>>><i> obsolete.
|
||||
</I>><i>
|
||||
</I>><i> There are also many more reasons for not using databases, otherwise all
|
||||
</I>><i> applications would be using them.
|
||||
</I>
|
||||
The main reason I prefer SQLite would be maintainability; I found the
|
||||
old parser database to be somewhat hard to understand when I was
|
||||
trying to fix problems.
|
||||
|
||||
However, I fully agree that if the performance tests show that the
|
||||
ad-hoc database is significantly faster and/or less memory hungry,
|
||||
it's probably worth the effort of maintaining it.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#22">[ date ]</a>
|
||||
<a href="thread.html#22">[ thread ]</a>
|
||||
<a href="subject.html#22">[ subject ]</a>
|
||||
<a href="author.html#22">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,132 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000025.html">
|
||||
<LINK REL="Next" HREF="000024.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>"Andrés G. Aragoneses"</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=1217281493.8555.13.camel%40Shattrath.site"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">aaragoneses at novell.com
|
||||
</A><BR>
|
||||
<I>Tue Jul 29 04:09:58 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#23">[ date ]</a>
|
||||
<a href="thread.html#23">[ thread ]</a>
|
||||
<a href="subject.html#23">[ subject ]</a>
|
||||
<a href="author.html#23">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi. Just my 2 cents on this.
|
||||
|
||||
Mike Krüger wrote:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>>><i> This discussion should have been done before committing anything to
|
||||
</I>>><i> trunk, but here it is anyway.
|
||||
</I>>><i>
|
||||
</I>>><i> Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>>><i> improvements in performance and memory use. Guessing that it will be
|
||||
</I>>><i> better is not enough. We need real numbers before taking the decision
|
||||
</I>>><i> to
|
||||
</I>>><i> switch, and only do it if the numbers are so much better that pay off
|
||||
</I>>><i> the burden of having a dependency on SQLite.
|
||||
</I>>><i>
|
||||
</I>>><i> I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>>><i> the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>>><i> tuning
|
||||
</I>>><i> up the parser database, and I'm quite happy about how is it
|
||||
</I>>><i> performing.
|
||||
</I>>><i>
|
||||
</I>>><i>
|
||||
</I>><i>
|
||||
</I>><i> Some more benefits for using a real database over an own implementation:
|
||||
</I>><i>
|
||||
</I>><i> - It's reliable. Atomic transactions, threading - all solved.
|
||||
</I>><i> - It's easy to look into the data using a command line client and SQL
|
||||
</I>><i> statements
|
||||
</I>><i>
|
||||
</I>><i> Its not just pure performance. Using a database will allow us for
|
||||
</I>><i> example to switch the database software to a new implementation. And
|
||||
</I>><i> databases and SQL are very easy to understood and to change.
|
||||
</I>><i>
|
||||
</I>><i> I had to think about it too (I implemented the #develop database some
|
||||
</I>><i> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>><i> after thinking about it the decision was easy - A database makes it
|
||||
</I>><i> easier to change the model and to make complicated querys more
|
||||
</I>><i> efficient.
|
||||
</I>><i>
|
||||
</I>><i> There are many more reasons using database software instead of own data
|
||||
</I>><i> storage solutions - otherwise the whole database software would be
|
||||
</I>><i> obsolete.
|
||||
</I>><i>
|
||||
</I>
|
||||
There are a lot of reasons too why programs don't use SQL database
|
||||
software. Maintainability gets hurt also by adopting such a solution in
|
||||
a OOP world; I guess you have heard about the Impedance mismatch [1],
|
||||
hence the existance of complicated ORM [2] frameworks or OOP databases
|
||||
like DB4O [3] (which in particular could be a better bet, but I guess
|
||||
the license is not adequate for MD).
|
||||
|
||||
I'm also worried about the fact that your opinion about SQLite may be
|
||||
biased because I guess you only used Win32 OS when you were working in
|
||||
SharpDevelop, right? There has been huge performance problems (locking
|
||||
problems) with SQLite in Linux, which recently caused a lot of
|
||||
discussions due to its usage in Firefox (which BTW is performing for me
|
||||
a lot worse than other browsers in Linux). I can't give you the exact
|
||||
reference of where I read (but I can give you some first google hits
|
||||
like [4] and [5]) it but AFAIK this is yet a problem to be solved
|
||||
upstream (don't remember if it's in the kernel or in the extX filesystem).
|
||||
|
||||
Regards,
|
||||
|
||||
Andrés
|
||||
|
||||
[1] <A HREF="http://en.wikipedia.org/wiki/Object-Relational_impedance_mismatch">http://en.wikipedia.org/wiki/Object-Relational_impedance_mismatch</A>
|
||||
[2] <A HREF="http://en.wikipedia.org/wiki/Object-relational_mapping">http://en.wikipedia.org/wiki/Object-relational_mapping</A>
|
||||
[3] <A HREF="http://www.db4o.com/">http://www.db4o.com/</A>
|
||||
[4]
|
||||
<A HREF="http://digg.com/linux_unix/Firefox_3_has_system_killing_performance_problem_for_Linux">http://digg.com/linux_unix/Firefox_3_has_system_killing_performance_problem_for_Linux</A>
|
||||
[5]
|
||||
<A HREF="http://news.softpedia.com/news/Who-Freezes-The-System-Firefox-or-ext3-86242.shtml">http://news.softpedia.com/news/Who-Freezes-The-System-Firefox-or-ext3-86242.shtml</A>
|
||||
--
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#23">[ date ]</a>
|
||||
<a href="thread.html#23">[ thread ]</a>
|
||||
<a href="subject.html#23">[ subject ]</a>
|
||||
<a href="author.html#23">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,154 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=488ED056.8040208%40novell.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000023.html">
|
||||
<LINK REL="Next" HREF="000026.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=488ED056.8040208%40novell.com"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Tue Jul 29 04:34:23 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#24">[ date ]</a>
|
||||
<a href="thread.html#24">[ thread ]</a>
|
||||
<a href="subject.html#24">[ subject ]</a>
|
||||
<a href="author.html#24">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Tue, Jul 29, 2008 at 1:09 AM, "Andrés G. Aragoneses"
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">aaragoneses at novell.com</A>> wrote:
|
||||
><i> Hi. Just my 2 cents on this.
|
||||
</I>><i>
|
||||
</I>><i> Mike Krüger wrote:
|
||||
</I>>><i> Hi
|
||||
</I>>><i>
|
||||
</I>>><i>
|
||||
</I>>>><i> This discussion should have been done before committing anything to
|
||||
</I>>>><i> trunk, but here it is anyway.
|
||||
</I>>>><i>
|
||||
</I>>>><i> Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>>>><i> improvements in performance and memory use. Guessing that it will be
|
||||
</I>>>><i> better is not enough. We need real numbers before taking the decision
|
||||
</I>>>><i> to
|
||||
</I>>>><i> switch, and only do it if the numbers are so much better that pay off
|
||||
</I>>>><i> the burden of having a dependency on SQLite.
|
||||
</I>>>><i>
|
||||
</I>>>><i> I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>>>><i> the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>>>><i> tuning
|
||||
</I>>>><i> up the parser database, and I'm quite happy about how is it
|
||||
</I>>>><i> performing.
|
||||
</I>>>><i>
|
||||
</I>>>><i>
|
||||
</I>>><i>
|
||||
</I>>><i> Some more benefits for using a real database over an own implementation:
|
||||
</I>>><i>
|
||||
</I>>><i> - It's reliable. Atomic transactions, threading - all solved.
|
||||
</I>>><i> - It's easy to look into the data using a command line client and SQL
|
||||
</I>>><i> statements
|
||||
</I>>><i>
|
||||
</I>>><i> Its not just pure performance. Using a database will allow us for
|
||||
</I>>><i> example to switch the database software to a new implementation. And
|
||||
</I>>><i> databases and SQL are very easy to understood and to change.
|
||||
</I>>><i>
|
||||
</I>>><i> I had to think about it too (I implemented the #develop database some
|
||||
</I>>><i> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>>><i> after thinking about it the decision was easy - A database makes it
|
||||
</I>>><i> easier to change the model and to make complicated querys more
|
||||
</I>>><i> efficient.
|
||||
</I>>><i>
|
||||
</I>>><i> There are many more reasons using database software instead of own data
|
||||
</I>>><i> storage solutions - otherwise the whole database software would be
|
||||
</I>>><i> obsolete.
|
||||
</I>>><i>
|
||||
</I>><i>
|
||||
</I>><i> There are a lot of reasons too why programs don't use SQL database
|
||||
</I>><i> software. Maintainability gets hurt also by adopting such a solution in
|
||||
</I>><i> a OOP world; I guess you have heard about the Impedance mismatch [1],
|
||||
</I>><i> hence the existance of complicated ORM [2] frameworks or OOP databases
|
||||
</I>><i> like DB4O [3] (which in particular could be a better bet, but I guess
|
||||
</I>><i> the license is not adequate for MD).
|
||||
</I>><i>
|
||||
</I>><i> I'm also worried about the fact that your opinion about SQLite may be
|
||||
</I>><i> biased because I guess you only used Win32 OS when you were working in
|
||||
</I>><i> SharpDevelop, right? There has been huge performance problems (locking
|
||||
</I>><i> problems) with SQLite in Linux, which recently caused a lot of
|
||||
</I>><i> discussions due to its usage in Firefox (which BTW is performing for me
|
||||
</I>><i> a lot worse than other browsers in Linux). I can't give you the exact
|
||||
</I>><i> reference of where I read (but I can give you some first google hits
|
||||
</I>><i> like [4] and [5]) it but AFAIK this is yet a problem to be solved
|
||||
</I>><i> upstream (don't remember if it's in the kernel or in the extX filesystem).
|
||||
</I>
|
||||
Again, I'm completely non-biased to our outcome. I do like the
|
||||
completion prediction idea however. Not that its necessarily tied to
|
||||
Sqlite though.
|
||||
|
||||
However, note that Sqlite queries would most likely be delegated to a
|
||||
single thread for thread-safety (hopefully not the gui thread), the
|
||||
fsync() issue you notice in firefox would be a non-issue. It would
|
||||
just mean some async callbacks from the sqlite query would take a
|
||||
little longer if that level of atomic commit support is desired (which
|
||||
i doubt is the case). Sqlite prides itself on being able to safely
|
||||
abort a transaction at any cpu-cycle up to the last block write (which
|
||||
is atomic on all the platforms it runs on).
|
||||
|
||||
><i> Regards,
|
||||
</I>><i>
|
||||
</I>><i> Andrés
|
||||
</I>><i>
|
||||
</I>><i> [1] <A HREF="http://en.wikipedia.org/wiki/Object-Relational_impedance_mismatch">http://en.wikipedia.org/wiki/Object-Relational_impedance_mismatch</A>
|
||||
</I>><i> [2] <A HREF="http://en.wikipedia.org/wiki/Object-relational_mapping">http://en.wikipedia.org/wiki/Object-relational_mapping</A>
|
||||
</I>><i> [3] <A HREF="http://www.db4o.com/">http://www.db4o.com/</A>
|
||||
</I>><i> [4]
|
||||
</I>><i> <A HREF="http://digg.com/linux_unix/Firefox_3_has_system_killing_performance_problem_for_Linux">http://digg.com/linux_unix/Firefox_3_has_system_killing_performance_problem_for_Linux</A>
|
||||
</I>><i> [5]
|
||||
</I>><i> <A HREF="http://news.softpedia.com/news/Who-Freezes-The-System-Firefox-or-ext3-86242.shtml">http://news.softpedia.com/news/Who-Freezes-The-System-Firefox-or-ext3-86242.shtml</A>
|
||||
</I>><i> --
|
||||
</I>><i>
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>><i>
|
||||
</I>
|
||||
-- Christian
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#24">[ date ]</a>
|
||||
<a href="thread.html#24">[ thread ]</a>
|
||||
<a href="subject.html#24">[ subject ]</a>
|
||||
<a href="author.html#24">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,226 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=aec34c770807282040l1db47011yab3dc628a46004cb%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000022.html">
|
||||
<LINK REL="Next" HREF="000023.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=aec34c770807282040l1db47011yab3dc628a46004cb%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Tue Jul 29 05:31:57 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#25">[ date ]</a>
|
||||
<a href="thread.html#25">[ thread ]</a>
|
||||
<a href="subject.html#25">[ subject ]</a>
|
||||
<a href="author.html#25">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dl 28 de 07 de 2008 a les 23:40 -0400, en/na Michael Hutchinson va escriure:
|
||||
><i> On Mon, Jul 28, 2008 at 9:36 PM, Lluis Sanchez Gual <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lluis at novell.com</A>> wrote:
|
||||
</I>><i> > El dl 28 de 07 de 2008 a les 23:44 +0200, en/na Mike Krüger va escriure:
|
||||
</I>><i> >> Hi
|
||||
</I>><i> >>
|
||||
</I>><i> >> > This discussion should have been done before committing anything to
|
||||
</I>><i> >> > trunk, but here it is anyway.
|
||||
</I>><i> >> >
|
||||
</I>><i> >> > Migrating to SQLite only makes sense if it provides noticeable
|
||||
</I>><i> >> > improvements in performance and memory use. Guessing that it will be
|
||||
</I>><i> >> > better is not enough. We need real numbers before taking the decision
|
||||
</I>><i> >> > to
|
||||
</I>><i> >> > switch, and only do it if the numbers are so much better that pay off
|
||||
</I>><i> >> > the burden of having a dependency on SQLite.
|
||||
</I>><i> >> >
|
||||
</I>><i> >> > I might be wrong, but I don't believe that SQLite will be better than
|
||||
</I>><i> >> > the ad-hoc database we are using in MD 1.0. I spent a lot of time
|
||||
</I>><i> >> > tuning
|
||||
</I>><i> >> > up the parser database, and I'm quite happy about how is it
|
||||
</I>><i> >> > performing.
|
||||
</I>><i> >> >
|
||||
</I>><i> >>
|
||||
</I>><i> >> Some more benefits for using a real database over an own implementation:
|
||||
</I>><i> >>
|
||||
</I>><i> >> - It's reliable. Atomic transactions, threading - all solved.
|
||||
</I>><i> >
|
||||
</I>><i> > Transactions and threading are not a problem for the parser database, so
|
||||
</I>><i> > that's not a real benefit.
|
||||
</I>><i>
|
||||
</I>><i> Multithreaded *writes* could be useful if we're parsing on multiple
|
||||
</I>><i> cores, but those aren't going to happen with SQLite just yet anyway...
|
||||
</I>
|
||||
It isn't a real benefit, given the low rate of writes we require.
|
||||
|
||||
><i>
|
||||
</I>><i> >> - It's easy to look into the data using a command line client and SQL
|
||||
</I>><i> >> statements
|
||||
</I>><i> >
|
||||
</I>><i> > This is cool, but it has never been a requirement.
|
||||
</I>><i>
|
||||
</I>><i> I found this appealing :-)
|
||||
</I>
|
||||
Me too, but software design can't be driven by appealingness.
|
||||
|
||||
><i>
|
||||
</I>><i> >> Its not just pure performance. Using a database will allow us for
|
||||
</I>><i> >> example to switch the database software to a new implementation. And
|
||||
</I>><i> >> databases and SQL are very easy to understood and to change.
|
||||
</I>><i> >>
|
||||
</I>><i> >> I had to think about it too (I implemented the #develop database some
|
||||
</I>><i> >> years ago which monodevelop inherited (but optimized I admit ^^)) -
|
||||
</I>><i> >
|
||||
</I>><i> > That's not correct, MD's parser database was written from scratch. The
|
||||
</I>><i> > inherited implementation would load everything in memory and would
|
||||
</I>><i> > collapse the system trying to open the MD solution.
|
||||
</I>><i> >
|
||||
</I>><i> >> after thinking about it the decision was easy - A database makes it
|
||||
</I>><i> >> easier to change the model and to make complicated querys more
|
||||
</I>><i> >> efficient.
|
||||
</I>><i> >
|
||||
</I>><i> > But curiously they are especially bad at querying hierarchies of objects
|
||||
</I>><i> > (such as namespace hierarchies or subclass hierarchies), unless you
|
||||
</I>><i> > denormalize the tables.
|
||||
</I>><i>
|
||||
</I>><i> Isn't that true of an ad-hoc DB too?
|
||||
</I>
|
||||
Not always. A hierarchy of objects can be efficiently scanned in memory
|
||||
without 'denormalizing' it.
|
||||
|
||||
><i>
|
||||
</I>><i> > Yes, databases are powerful. They can do amazing things with little
|
||||
</I>><i> > effort. But generic databases don't fit everywhere. A well designed
|
||||
</I>><i> > ad-hoc database may be better than a generic RDBMS, even if less
|
||||
</I>><i> > powerful. Everything depends on the requirements and constraints of the
|
||||
</I>><i> > application. For the specific case of the parser database, here are some
|
||||
</I>><i> > requirements:
|
||||
</I>><i> >
|
||||
</I>><i> > * Type and namespace lookup must be lightning fast. Type and
|
||||
</I>><i> > namespace queries are used by the parser when resolving types,
|
||||
</I>><i> > and by code completion when showing completion entries. I don't
|
||||
</I>><i> > think we can afford hitting the disk for that kind of queries.
|
||||
</I>><i>
|
||||
</I>><i> AFAIK, SQLite maintains an in-memory cache of configurable size, so as
|
||||
</I>><i> long as the databases are properly indexed, this shouldn't be an
|
||||
</I>><i> issue.
|
||||
</I>
|
||||
Shouldn't, but we don't know.
|
||||
|
||||
><i>
|
||||
</I>><i> > * Most of operations are read operations, so the database must be
|
||||
</I>><i> > optimized for reading. Write operations are much less common
|
||||
</I>><i> > than reads.
|
||||
</I>><i>
|
||||
</I>><i> This is true of SQLite.
|
||||
</I>
|
||||
This is a design constraint to take into account to choose the right
|
||||
solution. I'm not saying that this is a problem in SQLite.
|
||||
|
||||
><i>
|
||||
</I>><i> > * The data is the database is discardable. It is always possible
|
||||
</I>><i> > to regenerate a database by re-parsing a project or an assembly.
|
||||
</I>><i> > * Memory usage must be contained. Project and assembly databases
|
||||
</I>><i> > may contain a huge amount of information.
|
||||
</I>><i> > * The set of queries that it has to support is known and limited.
|
||||
</I>><i> > Those are basically:
|
||||
</I>><i> > * Get all types.
|
||||
</I>><i> > * Get all types implemented in a file, given the file
|
||||
</I>><i> > name.
|
||||
</I>><i> > * Get all subclasses of a class, given class name.
|
||||
</I>><i> > * Get a type, given the type name.
|
||||
</I>><i> > * Get all types and sub-namespaces of a namespace.
|
||||
</I>><i> > * Get all sub-namespaces of a namespace.
|
||||
</I>><i>
|
||||
</I>><i> I would also like to be able to extend the parser DB to store the
|
||||
</I>><i> C/C++ symbols. This should be relatively easy with SQLite.
|
||||
</I>><i>
|
||||
</I>><i> It would also be nice to store the amount of times a particular item
|
||||
</I>><i> has been selected from the code completion list, so that if there are
|
||||
</I>><i> a number of completion entries that match the currently typed prefix,
|
||||
</I>><i> the completion window can select the most likely one. Visual Studio
|
||||
</I>><i> does this and it's *very* useful. Things like this would be pretty
|
||||
</I>><i> easy to implement with SQLite.
|
||||
</I>
|
||||
And with an ad-hoc database even easier. I don't think VS needs a
|
||||
relational database to implement this.
|
||||
|
||||
><i> We could also maintain various other
|
||||
</I>><i> tables and indices to accelerate things like "find references", which
|
||||
</I>><i> would help with speeding up renaming and other such refactorings.
|
||||
</I>
|
||||
Again, you don't have to convince me about how cool having all that info
|
||||
in a database is. I already know it.
|
||||
|
||||
><i>
|
||||
</I>><i> > A designer has to find the solution that better fulfills the constraints
|
||||
</I>><i> > and requirements of an application. In the parser case, given the
|
||||
</I>><i> > constraints we have, I think an ad-hoc database may perform better. Of
|
||||
</I>><i> > course I might be wrong, since I haven't done any tests with SQLite, but
|
||||
</I>><i> > I yet have to see a proof of the contrary.
|
||||
</I>><i>
|
||||
</I>><i> This is a fair point, and we should definitely perform benchmarks
|
||||
</I>><i> before coming to a conclusion.
|
||||
</I>><i>
|
||||
</I>><i> >> There are many more reasons using database software instead of own data
|
||||
</I>><i> >> storage solutions - otherwise the whole database software would be
|
||||
</I>><i> >> obsolete.
|
||||
</I>><i> >
|
||||
</I>><i> > There are also many more reasons for not using databases, otherwise all
|
||||
</I>><i> > applications would be using them.
|
||||
</I>><i>
|
||||
</I>><i> The main reason I prefer SQLite would be maintainability; I found the
|
||||
</I>><i> old parser database to be somewhat hard to understand when I was
|
||||
</I>><i> trying to fix problems.
|
||||
</I>
|
||||
Yes, it is hard to understand because it is complex, and it is complex
|
||||
because it is solving a complex problem. We should refrain the urge of
|
||||
rewriting all complex software we find, since there may be a good reason
|
||||
for it being complex.
|
||||
|
||||
><i>
|
||||
</I>><i> However, I fully agree that if the performance tests show that the
|
||||
</I>><i> ad-hoc database is significantly faster and/or less memory hungry,
|
||||
</I>><i> it's probably worth the effort of maintaining it.
|
||||
</I>
|
||||
And if tests show that SQLite is better than the ad-hoc database, I also
|
||||
agree on using it.
|
||||
|
||||
Lluis.
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#25">[ date ]</a>
|
||||
<a href="thread.html#25">[ thread ]</a>
|
||||
<a href="subject.html#25">[ subject ]</a>
|
||||
<a href="author.html#25">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,86 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Using SQLite as parser database
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=488ED056.8040208%40novell.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000024.html">
|
||||
<LINK REL="Next" HREF="000018.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Using SQLite as parser database</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Using%20SQLite%20as%20parser%20database&In-Reply-To=488ED056.8040208%40novell.com"
|
||||
TITLE="[Monodevelop-devel] Using SQLite as parser database">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Tue Jul 29 11:02:29 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#26">[ date ]</a>
|
||||
<a href="thread.html#26">[ thread ]</a>
|
||||
<a href="subject.html#26">[ subject ]</a>
|
||||
<a href="author.html#26">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Tue, Jul 29, 2008 at 4:09 AM, "Andrés G. Aragoneses"
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">aaragoneses at novell.com</A>> wrote:
|
||||
><i> I'm also worried about the fact that your opinion about SQLite may be
|
||||
</I>><i> biased because I guess you only used Win32 OS when you were working in
|
||||
</I>><i> SharpDevelop, right? There has been huge performance problems (locking
|
||||
</I>><i> problems) with SQLite in Linux, which recently caused a lot of
|
||||
</I>><i> discussions due to its usage in Firefox (which BTW is performing for me
|
||||
</I>><i> a lot worse than other browsers in Linux). I can't give you the exact
|
||||
</I>><i> reference of where I read (but I can give you some first google hits
|
||||
</I>><i> like [4] and [5]) it but AFAIK this is yet a problem to be solved
|
||||
</I>><i> upstream (don't remember if it's in the kernel or in the extX filesystem).
|
||||
</I>
|
||||
That's because Firefox uses SQLite in synchronous mode, which flushes
|
||||
to disk (and ext3 causes ALL files on the disk to be flushed). We
|
||||
wouldn't need that mode. Firefix also seems to write a huge amount of
|
||||
daya to disk compared to what it needs, probably for the same reason
|
||||
(excessive flushing of indices, etc)
|
||||
|
||||
It'd be fairer to compare Banshee, which opens its database with:
|
||||
Execute ("PRAGMA cache_size = ?", cache_size);
|
||||
Execute ("PRAGMA synchronous = OFF");
|
||||
Execute ("PRAGMA temp_store = MEMORY");
|
||||
Execute ("PRAGMA count_changes = OFF");
|
||||
|
||||
(see banshee/src/Core/Banshee.Services/Banshee.Database/BansheeDbConnection.cs)
|
||||
|
||||
Banshee's database has not caused any substantial problems.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#26">[ date ]</a>
|
||||
<a href="thread.html#26">[ thread ]</a>
|
||||
<a href="subject.html#26">[ subject ]</a>
|
||||
<a href="author.html#26">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,172 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list July 2008 Archive by author</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>July 2008 Archives by author</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Sat Jul 12 10:43:11 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Messages:</b> 25<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A><A NAME="11"> </A>
|
||||
<I>C.J. Adams-Collier
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A><A NAME="7"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A><A NAME="12"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="23"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="17"> </A>
|
||||
<I>Federico Di Gregorio
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="14"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="19"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="20"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="21"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="25"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="16"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="24"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="4"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="6"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="8"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="10"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="13"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="22"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="26"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="15"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="18"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="2"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="3"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="5"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="9"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Tue Jul 29 11:02:33 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,172 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list July 2008 Archive by date</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>July 2008 Archives by date</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Sat Jul 12 10:43:11 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Messages:</b> 25<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="2"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="3"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="4"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="5"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="6"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A><A NAME="7"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="8"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="9"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="10"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A><A NAME="11"> </A>
|
||||
<I>C.J. Adams-Collier
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A><A NAME="12"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="13"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="14"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="15"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="17"> </A>
|
||||
<I>Federico Di Gregorio
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="16"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="18"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="19"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="20"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="21"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="22"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="23"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="24"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="25"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="26"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Tue Jul 29 11:02:33 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,221 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list July 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>July 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Sat Jul 12 10:43:11 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Messages:</b> 25<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01215873791- -->
|
||||
<LI><A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="2"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01215873791-01216419378- -->
|
||||
<LI><A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="8"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01215873791-01216419378-01216460781- -->
|
||||
<LI><A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="9"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01215873791-01216419378-01216460781-01216471740- -->
|
||||
<LI><A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="10"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01215878753- -->
|
||||
<LI><A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="3"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01215878753-01216042865- -->
|
||||
<LI><A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="4"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01215878753-01216042865-01216053382- -->
|
||||
<LI><A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="5"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01215878753-01216042865-01216053382-01216087823- -->
|
||||
<LI><A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="6"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01216303169- -->
|
||||
<LI><A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A><A NAME="7"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<!--0 01217201571- -->
|
||||
<LI><A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A><A NAME="11"> </A>
|
||||
<I>C.J. Adams-Collier
|
||||
</I>
|
||||
|
||||
<!--0 01217243495- -->
|
||||
<LI><A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A><A NAME="12"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<!--0 01217269857- -->
|
||||
<LI><A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="13"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01217269857-01217286900- -->
|
||||
<LI><A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="19"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01217278748- -->
|
||||
<LI><A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="14"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01217278748-01217281493- -->
|
||||
<LI><A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="15"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01217278748-01217281493-01217282798- -->
|
||||
<LI><A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="17"> </A>
|
||||
<I>Federico Di Gregorio
|
||||
</I>
|
||||
|
||||
<!--2 01217278748-01217281493-01217282916- -->
|
||||
<LI><A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="16"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<!--2 01217278748-01217281493-01217295366- -->
|
||||
<LI><A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="21"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01217278748-01217281493-01217295366-01217302821- -->
|
||||
<LI><A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="22"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<!--3 01217278748-01217281493-01217295366-01217302821-01217323917- -->
|
||||
<LI><A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="25"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--2 01217278748-01217281493-01217318998- -->
|
||||
<LI><A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="23"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01217278748-01217281493-01217318998-01217320463- -->
|
||||
<LI><A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="24"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<!--3 01217278748-01217281493-01217318998-01217343749- -->
|
||||
<LI><A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="26"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01217283796- -->
|
||||
<LI><A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="18"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01217283796-01217289271- -->
|
||||
<LI><A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="20"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Tue Jul 29 11:02:33 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,172 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list July 2008 Archive by subject</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>July 2008 Archives by subject</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Sat Jul 12 10:43:11 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Messages:</b> 25<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A><A NAME="7"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="19"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="13"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="3"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="4"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="5"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="6"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A><A NAME="12"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="2"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="8"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="9"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="10"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="18"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="20"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A><A NAME="11"> </A>
|
||||
<I>C.J. Adams-Collier
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="14"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="15"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="17"> </A>
|
||||
<I>Federico Di Gregorio
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="16"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="21"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="22"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="23"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="24"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="25"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="26"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Tue Jul 29 11:02:33 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,221 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list July 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>July 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Sat Jul 12 10:43:11 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Messages:</b> 25<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01215873791- -->
|
||||
<LI><A HREF="000002.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="2"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01215873791-01216419378- -->
|
||||
<LI><A HREF="000008.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="8"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01215873791-01216419378-01216460781- -->
|
||||
<LI><A HREF="000009.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="9"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01215873791-01216419378-01216460781-01216471740- -->
|
||||
<LI><A HREF="000010.html">[Monodevelop-devel] Insufficient Requirement Checks
|
||||
</A><A NAME="10"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01215878753- -->
|
||||
<LI><A HREF="000003.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="3"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01215878753-01216042865- -->
|
||||
<LI><A HREF="000004.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="4"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01215878753-01216042865-01216053382- -->
|
||||
<LI><A HREF="000005.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="5"> </A>
|
||||
<I>Valentin Sawadski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01215878753-01216042865-01216053382-01216087823- -->
|
||||
<LI><A HREF="000006.html">[Monodevelop-devel] [Path] Updated ASP.NET Templates
|
||||
</A><A NAME="6"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01216303169- -->
|
||||
<LI><A HREF="000007.html">[Monodevelop-devel] [Fwd: Monodevevelop 1.9 Error when opening old Gtk# Project]
|
||||
</A><A NAME="7"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<!--0 01217201571- -->
|
||||
<LI><A HREF="000011.html">[Monodevelop-devel] the future of Prebuild and xbuild
|
||||
</A><A NAME="11"> </A>
|
||||
<I>C.J. Adams-Collier
|
||||
</I>
|
||||
|
||||
<!--0 01217243495- -->
|
||||
<LI><A HREF="000012.html">[Monodevelop-devel] gmcs bug affecting MD from SVN (was: Re: HEADS UP: Linear IR branch merge)
|
||||
</A><A NAME="12"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<!--0 01217269857- -->
|
||||
<LI><A HREF="000013.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="13"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01217269857-01217286900- -->
|
||||
<LI><A HREF="000019.html">[Monodevelop-devel] [MonoDevelop] Current SVN version may be buggy/dom changes
|
||||
</A><A NAME="19"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01217278748- -->
|
||||
<LI><A HREF="000014.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="14"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01217278748-01217281493- -->
|
||||
<LI><A HREF="000015.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="15"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01217278748-01217281493-01217282798- -->
|
||||
<LI><A HREF="000017.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="17"> </A>
|
||||
<I>Federico Di Gregorio
|
||||
</I>
|
||||
|
||||
<!--2 01217278748-01217281493-01217282916- -->
|
||||
<LI><A HREF="000016.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="16"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<!--2 01217278748-01217281493-01217295366- -->
|
||||
<LI><A HREF="000021.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="21"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01217278748-01217281493-01217295366-01217302821- -->
|
||||
<LI><A HREF="000022.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="22"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<!--3 01217278748-01217281493-01217295366-01217302821-01217323917- -->
|
||||
<LI><A HREF="000025.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="25"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--2 01217278748-01217281493-01217318998- -->
|
||||
<LI><A HREF="000023.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="23"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01217278748-01217281493-01217318998-01217320463- -->
|
||||
<LI><A HREF="000024.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="24"> </A>
|
||||
<I>Christian Hergert
|
||||
</I>
|
||||
|
||||
<!--3 01217278748-01217281493-01217318998-01217343749- -->
|
||||
<LI><A HREF="000026.html">[Monodevelop-devel] Using SQLite as parser database
|
||||
</A><A NAME="26"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01217283796- -->
|
||||
<LI><A HREF="000018.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="18"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01217283796-01217289271- -->
|
||||
<LI><A HREF="000020.html">[Monodevelop-devel] Some new DOM guidance
|
||||
</A><A NAME="20"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Tue Jul 29 11:02:29 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Tue Jul 29 11:02:33 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,71 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20New%20monodevelop-devel%20mailing%20list&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
|
||||
<LINK REL="Next" HREF="000001.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] New monodevelop-devel mailing list</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20New%20monodevelop-devel%20mailing%20list&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] New monodevelop-devel mailing list">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Jun 16 16:58:18 EDT 2008</I>
|
||||
<P><UL>
|
||||
|
||||
<LI>Next message: <A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#0">[ date ]</a>
|
||||
<a href="thread.html#0">[ thread ]</a>
|
||||
<a href="subject.html#0">[ subject ]</a>
|
||||
<a href="author.html#0">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi!
|
||||
|
||||
A new mailing list for the MonoDevelop project has been created:
|
||||
|
||||
<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
|
||||
This list will be used to discuss about the development of MonoDevelop,
|
||||
so if you are a project contributor you should subscribe it. Questions
|
||||
about the internals of MonoDevelop or development of add-ins should be
|
||||
directed to that list.
|
||||
|
||||
The old monodevelop list will be used from now on only for general
|
||||
discussion about using MonoDevelop.
|
||||
|
||||
Enjoy!
|
||||
Lluis.
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
|
||||
<LI>Next message: <A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#0">[ date ]</a>
|
||||
<a href="thread.html#0">[ thread ]</a>
|
||||
<a href="subject.html#0">[ subject ]</a>
|
||||
<a href="author.html#0">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,63 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Backport a fix?
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Backport%20a%20fix%3F&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000000.html">
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Backport a fix?</H1>
|
||||
<B>"Andrés G. Aragoneses"</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Backport%20a%20fix%3F&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Backport a fix?">aaragoneses at novell.com
|
||||
</A><BR>
|
||||
<I>Sat Jun 21 07:32:16 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#1">[ date ]</a>
|
||||
<a href="thread.html#1">[ thread ]</a>
|
||||
<a href="subject.html#1">[ subject ]</a>
|
||||
<a href="author.html#1">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>I committed a patch to trunk, provided in
|
||||
<A HREF="https://bugzilla.novell.com/show_bug.cgi?id=398789">https://bugzilla.novell.com/show_bug.cgi?id=398789</A> . Shall I backport
|
||||
the fix to the 1.9 branch?
|
||||
|
||||
Regards,
|
||||
|
||||
Andrés
|
||||
|
||||
--
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#1">[ date ]</a>
|
||||
<a href="thread.html#1">[ thread ]</a>
|
||||
<a href="subject.html#1">[ subject ]</a>
|
||||
<a href="author.html#1">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,57 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list June 2008 Archive by author</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>June 2008 Archives by author</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Mon Jun 16 16:58:18 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Messages:</b> 2<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A><A NAME="1"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A><A NAME="0"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Sat Jun 21 07:30:14 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,57 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list June 2008 Archive by date</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>June 2008 Archives by date</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Mon Jun 16 16:58:18 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Messages:</b> 2<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A><A NAME="0"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A><A NAME="1"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Sat Jun 21 07:30:14 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,59 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list June 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>June 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Mon Jun 16 16:58:18 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Messages:</b> 2<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01213649898- -->
|
||||
<LI><A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A><A NAME="0"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--0 01214047936- -->
|
||||
<LI><A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A><A NAME="1"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Sat Jun 21 07:30:14 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,57 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list June 2008 Archive by subject</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>June 2008 Archives by subject</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Mon Jun 16 16:58:18 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Messages:</b> 2<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A><A NAME="1"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A><A NAME="0"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Sat Jun 21 07:30:14 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,59 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list June 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>June 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Mon Jun 16 16:58:18 EDT 2008</i><br>
|
||||
<b>Ending:</b> <i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Messages:</b> 2<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01213649898- -->
|
||||
<LI><A HREF="000000.html">[Monodevelop-devel] New monodevelop-devel mailing list
|
||||
</A><A NAME="0"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--0 01214047936- -->
|
||||
<LI><A HREF="000001.html">[Monodevelop-devel] Backport a fix?
|
||||
</A><A NAME="1"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Sat Jun 21 07:32:16 EDT 2008</i><br>
|
||||
<b>Archived on:</b> <i>Sat Jun 21 07:30:14 EDT 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,75 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
|
||||
<LINK REL="Next" HREF="000058.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 05:11:08 EST 2008</I>
|
||||
<P><UL>
|
||||
|
||||
<LI>Next message: <A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#57">[ date ]</a>
|
||||
<a href="thread.html#57">[ thread ]</a>
|
||||
<a href="subject.html#57">[ subject ]</a>
|
||||
<a href="author.html#57">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
After the next release I want to improve refactoring.
|
||||
Currently we only have rename as refactoring operation. Generally I want
|
||||
to do refactoring a bit different than it is now.
|
||||
|
||||
I want a refactoring infrastructure that allows the user to preview all
|
||||
changes that are done in the refactoring step (see eclipse for an
|
||||
example).
|
||||
|
||||
I'll need to extend/change the current refactoring infrastructure for
|
||||
this. And one of the goals for the new one is: unit test support. The
|
||||
new code completion infrastructure is tested with unit tests and I think
|
||||
that this has improved the code completion correctness greatly.
|
||||
|
||||
Any thoughts/inputs here ?
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
|
||||
<LI>Next message: <A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#57">[ date ]</a>
|
||||
<a href="thread.html#57">[ thread ]</a>
|
||||
<a href="subject.html#57">[ subject ]</a>
|
||||
<a href="author.html#57">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,121 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000057.html">
|
||||
<LINK REL="Next" HREF="000066.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Rafael Teixeira</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">monoman at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 07:49:26 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#58">[ date ]</a>
|
||||
<a href="thread.html#58">[ thread ]</a>
|
||||
<a href="subject.html#58">[ subject ]</a>
|
||||
<a href="author.html#58">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>+1. Test-driven design is the way to go with such a complex subsystem.
|
||||
|
||||
I foresee some hard spots:
|
||||
1) UI-decoupling on preview/user-decision
|
||||
2) Memory-consumption to keep track of all pending changes, and before/after
|
||||
scenarios
|
||||
3) Undoability
|
||||
|
||||
Also it should be decided if all would be affected files should be loaded in
|
||||
editor windows, or changes could occur behind-the-scener after user
|
||||
previewing/deciding, this may bring in some synchronization issues with
|
||||
other subsystems/addins like the version control one.
|
||||
|
||||
About version control integration, it is not common on open source projects,
|
||||
but where I work currently SVN is configured to demand locking files to be
|
||||
able to commit changes on them, meaning that eclipse/vs.net keep asking me
|
||||
if I want to overwrite the locally marked-as-readonly files in the middle of
|
||||
refactorings, as I never try to guess and lock files prior to working on
|
||||
them, and I think we should support that too.
|
||||
|
||||
Just some thoughts
|
||||
|
||||
Regards,
|
||||
|
||||
On Wed, Nov 5, 2008 at 7:11 AM, Mike Krüger <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkrueger at novell.com</A>> wrote:
|
||||
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> After the next release I want to improve refactoring.
|
||||
</I>><i> Currently we only have rename as refactoring operation. Generally I want
|
||||
</I>><i> to do refactoring a bit different than it is now.
|
||||
</I>><i>
|
||||
</I>><i> I want a refactoring infrastructure that allows the user to preview all
|
||||
</I>><i> changes that are done in the refactoring step (see eclipse for an
|
||||
</I>><i> example).
|
||||
</I>><i>
|
||||
</I>><i> I'll need to extend/change the current refactoring infrastructure for
|
||||
</I>><i> this. And one of the goals for the new one is: unit test support. The
|
||||
</I>><i> new code completion infrastructure is tested with unit tests and I think
|
||||
</I>><i> that this has improved the code completion correctness greatly.
|
||||
</I>><i>
|
||||
</I>><i> Any thoughts/inputs here ?
|
||||
</I>><i>
|
||||
</I>><i> Regards
|
||||
</I>><i> Mike
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>><i>
|
||||
</I>
|
||||
|
||||
|
||||
--
|
||||
Rafael "Monoman" Teixeira
|
||||
---------------------------------------
|
||||
"I myself am made entirely of flaws, stitched together with good
|
||||
intentions."
|
||||
Augusten Burroughs
|
||||
-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081105/879d79a1/attachment.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081105/879d79a1/attachment.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#58">[ date ]</a>
|
||||
<a href="thread.html#58">[ thread ]</a>
|
||||
<a href="subject.html#58">[ subject ]</a>
|
||||
<a href="author.html#58">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,91 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000066.html">
|
||||
<LINK REL="Next" HREF="000064.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>"Andrés G. Aragoneses"</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">aaragoneses at novell.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 10:12:41 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#59">[ date ]</a>
|
||||
<a href="thread.html#59">[ thread ]</a>
|
||||
<a href="subject.html#59">[ subject ]</a>
|
||||
<a href="author.html#59">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Mike Krüger wrote:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> After the next release I want to improve refactoring.
|
||||
</I>><i> Currently we only have rename as refactoring operation. Generally I want
|
||||
</I>><i> to do refactoring a bit different than it is now.
|
||||
</I>><i>
|
||||
</I>><i> I want a refactoring infrastructure that allows the user to preview all
|
||||
</I>><i> changes that are done in the refactoring step (see eclipse for an
|
||||
</I>><i> example).
|
||||
</I>><i>
|
||||
</I>><i> I'll need to extend/change the current refactoring infrastructure for
|
||||
</I>><i> this. And one of the goals for the new one is: unit test support. The
|
||||
</I>><i> new code completion infrastructure is tested with unit tests and I think
|
||||
</I>><i> that this has improved the code completion correctness greatly.
|
||||
</I>><i>
|
||||
</I>><i> Any thoughts/inputs here ?
|
||||
</I>><i>
|
||||
</I>
|
||||
When you say next release, are talking about a 2.0 Alpha or 2.0 final?
|
||||
If you mean final, perfect. If not, IMHO I would dedicate more time to
|
||||
fix more basic use cases for refactoring features. I don't know if there
|
||||
are still bugs open on bugzilla, but with a brief look I see many
|
||||
regressions: go to declaration not shown in many cases, looking for
|
||||
references takes a lot of time, etc..
|
||||
I will see if I can report some of those, although it's difficult to
|
||||
isolate them.
|
||||
|
||||
Andrés
|
||||
|
||||
--
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#59">[ date ]</a>
|
||||
<a href="thread.html#59">[ thread ]</a>
|
||||
<a href="subject.html#59">[ subject ]</a>
|
||||
<a href="author.html#59">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,111 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000064.html">
|
||||
<LINK REL="Next" HREF="000065.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 16:32:31 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#60">[ date ]</a>
|
||||
<a href="thread.html#60">[ thread ]</a>
|
||||
<a href="subject.html#60">[ subject ]</a>
|
||||
<a href="author.html#60">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Wed, Nov 5, 2008 at 5:11 AM, Mike Krüger <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkrueger at novell.com</A>> wrote:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> After the next release I want to improve refactoring.
|
||||
</I>><i> Currently we only have rename as refactoring operation. Generally I want
|
||||
</I>><i> to do refactoring a bit different than it is now.
|
||||
</I>><i>
|
||||
</I>><i> I want a refactoring infrastructure that allows the user to preview all
|
||||
</I>><i> changes that are done in the refactoring step (see eclipse for an
|
||||
</I>><i> example).
|
||||
</I>
|
||||
DevExpress Refactor Pro has some nice previews within the editor, with
|
||||
arrows and highlighting and stuff.
|
||||
|
||||
><i> I'll need to extend/change the current refactoring infrastructure for
|
||||
</I>><i> this. And one of the goals for the new one is: unit test support. The
|
||||
</I>><i> new code completion infrastructure is tested with unit tests and I think
|
||||
</I>><i> that this has improved the code completion correctness greatly.
|
||||
</I>><i>
|
||||
</I>><i> Any thoughts/inputs here ?
|
||||
</I>
|
||||
I'm interested in a few different things:
|
||||
|
||||
* Cross-project/language aspects of refactoring. For example, if an
|
||||
identifier is renamed in a C# project, it may need to be renamed in a
|
||||
dependent VB project or in ASP.NET or XAML files. Unit testing of
|
||||
these will be an interesting challenge...
|
||||
|
||||
* Non-.NET refactoring hooks -- it should be possible to use some of
|
||||
the infrastructure (at least) for C/C++ or Python refactoring, for
|
||||
example.
|
||||
|
||||
* Extensibility -- how easy will it be to build more "complex"
|
||||
refactorings? It would be interesting to catalogue all the
|
||||
refactorings provided by popular IDEs and Addins (VS, Eclipse,
|
||||
Resharper, DevExpress Refactor Pro etc) and try to break them up into
|
||||
more primitive operations, so that languages can get the high-level
|
||||
operations for free by implementing only the low-level operations. I
|
||||
know we have something like this already, but I think it'd be good to
|
||||
re-evaluate the primitives in light of all of the high-level
|
||||
operations we might want to implement.
|
||||
|
||||
* Indexing -- for renaming operations (and "find all references") our
|
||||
performance is currently dire. It might be worth having an index to
|
||||
make these faster.
|
||||
|
||||
I don't have any ideas right now on how these should be done, but I
|
||||
think it's important to take them into consideration :-)
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#60">[ date ]</a>
|
||||
<a href="thread.html#60">[ thread ]</a>
|
||||
<a href="subject.html#60">[ subject ]</a>
|
||||
<a href="author.html#60">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,89 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Can%27t%20get%20monodevelop%20to%20show%20GTK%23%202.00%0A%09under%20C%23%20heading&In-Reply-To=1225069218822-1380670.post%40n2.nabble.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000073.html">
|
||||
<LINK REL="Next" HREF="000062.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Can%27t%20get%20monodevelop%20to%20show%20GTK%23%202.00%0A%09under%20C%23%20heading&In-Reply-To=1225069218822-1380670.post%40n2.nabble.com"
|
||||
TITLE="[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 20:08:01 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#61">[ date ]</a>
|
||||
<a href="thread.html#61">[ thread ]</a>
|
||||
<a href="subject.html#61">[ subject ]</a>
|
||||
<a href="author.html#61">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Sun, Oct 26, 2008 at 8:00 PM, Justin Weber <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">embed68k at dejazzd.com</A>> wrote:
|
||||
><i>
|
||||
</I>><i> I've been trying like hell to get GTK# 2.0 to show under the C# heading under
|
||||
</I>><i> new solution. I downloaded and installed Xcode from apple.com. I go into the
|
||||
</I>><i> add-in manager in monodevelop and it complains about not being able to find
|
||||
</I>><i> gtkcore 1.9.0 in the go-mono repository. I've tried every thing I could
|
||||
</I>><i> think of and searched forever to do this, but still I can't succeed. I've
|
||||
</I>><i> also tried getting a c# heading to appear in Xcode and followed the
|
||||
</I>><i> tutorials for moving the csharp plugin file, that doesn't work either. This
|
||||
</I>><i> is apple, it's not supposed to be this hard. Is it??
|
||||
</I>
|
||||
The GTK# addin isn't included in the Mac builds, because drag-n-drop
|
||||
issues in the Mac GTK prevent our GTK# designer from working on Mac.
|
||||
Unfortunately the GTK# templates are in the same addin as the
|
||||
designer. However, handwritten GTK# code should still work -- MD
|
||||
itself uses GTK#.
|
||||
|
||||
BTW, monodevelop-devel-list is for discussing the code/development of
|
||||
MonoDevelop. For other discussions, including bugs and support, please
|
||||
use monodevelop-list.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#61">[ date ]</a>
|
||||
<a href="thread.html#61">[ thread ]</a>
|
||||
<a href="subject.html#61">[ subject ]</a>
|
||||
<a href="author.html#61">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,99 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Automagic%20settings%20upgrade%20dilemma&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000061.html">
|
||||
<LINK REL="Next" HREF="000063.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Automagic settings upgrade dilemma</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Automagic%20settings%20upgrade%20dilemma&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Automagic settings upgrade dilemma">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 21:20:42 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#62">[ date ]</a>
|
||||
<a href="thread.html#62">[ thread ]</a>
|
||||
<a href="subject.html#62">[ subject ]</a>
|
||||
<a href="author.html#62">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi all,
|
||||
|
||||
Background: Until a few days ago, the ASP.NET project type in MD
|
||||
assumed that ASP.NET projects always had a CompileTarget value of
|
||||
"Library". This has led to all ASP.NET projects files being created
|
||||
with the default "Executable" target, since MD essentially ignored
|
||||
this properly, so I did not think to set it correctly. Unfortunately
|
||||
Visual Studio (MSBuild) *does* respect this properly from the project
|
||||
file, even though it gives the user no UI with which to change it.
|
||||
Building MD projects with VS (or MSBuild) hence hits a compile error
|
||||
when it can't find the Main entry point method. If this method's
|
||||
added, the build succeeds, but the project doesn't fun, since ASP.NET
|
||||
apparently ignores exe files.
|
||||
|
||||
Here's the dilemma: MD needs to fix the incorrect value it's been
|
||||
using in order to make existing projects compatible with VS and
|
||||
MSBuild. However, I'm not comfortable doing automagic, unavoidable and
|
||||
potentially unwanted changes (even if right now I can't think of any
|
||||
ready why anyone would want to build an exe). Which of the following
|
||||
should I do?
|
||||
|
||||
1) Make the change automatically
|
||||
2) Ask the user if they want to make the change (if they don't, it'll
|
||||
ask every time they open the project)
|
||||
3) Add a warning to the build process, and
|
||||
a) Don't do anything, let users fix it themselves in the project file
|
||||
b) Re-enable the CompileTarget-changing UI when the CompileTarget
|
||||
is incorrect
|
||||
|
||||
My preference is 3b.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#62">[ date ]</a>
|
||||
<a href="thread.html#62">[ thread ]</a>
|
||||
<a href="subject.html#62">[ subject ]</a>
|
||||
<a href="author.html#62">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,92 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Automagic%20settings%20upgrade%20dilemma&In-Reply-To=aec34c770811051820t75511d1bwb0f86404eea820b%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000062.html">
|
||||
<LINK REL="Next" HREF="000067.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Automagic settings upgrade dilemma</H1>
|
||||
<B>Mike Kestner</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Automagic%20settings%20upgrade%20dilemma&In-Reply-To=aec34c770811051820t75511d1bwb0f86404eea820b%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Automagic settings upgrade dilemma">mkestner at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 22:11:27 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#63">[ date ]</a>
|
||||
<a href="thread.html#63">[ thread ]</a>
|
||||
<a href="subject.html#63">[ subject ]</a>
|
||||
<a href="author.html#63">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Wed, Nov 5, 2008 at 8:20 PM, Michael Hutchinson <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">m.j.hutchinson at gmail.com</A>
|
||||
><i> wrote:
|
||||
</I>
|
||||
><i>
|
||||
</I>><i> 1) Make the change automatically
|
||||
</I>><i> 2) Ask the user if they want to make the change (if they don't, it'll
|
||||
</I>><i> ask every time they open the project)
|
||||
</I>><i> 3) Add a warning to the build process, and
|
||||
</I>><i> a) Don't do anything, let users fix it themselves in the project file
|
||||
</I>><i> b) Re-enable the CompileTarget-changing UI when the CompileTarget
|
||||
</I>><i> is incorrect
|
||||
</I>
|
||||
|
||||
Or
|
||||
|
||||
4) Don't worry about it.
|
||||
|
||||
I think #1 is probably right. Since there's no point in building an
|
||||
asp.netexe with a Main method, just do the update.
|
||||
|
||||
I suppose you could refine the logic and only update if its an exe AND a
|
||||
Main has not been specified. That's the only other defensible
|
||||
configuration, right, even though it sounds like it's an exercise in
|
||||
silliness from an asp.net standpoint.
|
||||
-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081105/2b60d686/attachment.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081105/2b60d686/attachment.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#63">[ date ]</a>
|
||||
<a href="thread.html#63">[ thread ]</a>
|
||||
<a href="subject.html#63">[ subject ]</a>
|
||||
<a href="author.html#63">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,69 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=4911B7E9.4070804%40novell.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000059.html">
|
||||
<LINK REL="Next" HREF="000060.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=4911B7E9.4070804%40novell.com"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Nov 6 02:11:50 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#64">[ date ]</a>
|
||||
<a href="thread.html#64">[ thread ]</a>
|
||||
<a href="subject.html#64">[ subject ]</a>
|
||||
<a href="author.html#64">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> When you say next release, are talking about a 2.0 Alpha or 2.0 final?
|
||||
</I>
|
||||
We're not going to integrate something brand new before 2.0 final - only
|
||||
bugfixes and "minor" enhancements. I have even delayed some small
|
||||
features (like auto saving) for after 2.0 release.
|
||||
|
||||
I've broken enough during the 1.0 -> 2.0 development :)
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#64">[ date ]</a>
|
||||
<a href="thread.html#64">[ thread ]</a>
|
||||
<a href="subject.html#64">[ subject ]</a>
|
||||
<a href="author.html#64">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,102 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=aec34c770811051332x52f4f988mbdf79c3db8d5eecd%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000060.html">
|
||||
<LINK REL="Next" HREF="000068.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=aec34c770811051332x52f4f988mbdf79c3db8d5eecd%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Nov 6 02:20:26 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#65">[ date ]</a>
|
||||
<a href="thread.html#65">[ thread ]</a>
|
||||
<a href="subject.html#65">[ subject ]</a>
|
||||
<a href="author.html#65">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> * Cross-project/language aspects of refactoring. For example, if an
|
||||
</I>><i> identifier is renamed in a C# project, it may need to be renamed in a
|
||||
</I>><i> dependent VB project or in ASP.NET or XAML files. Unit testing of
|
||||
</I>><i> these will be an interesting challenge...
|
||||
</I>><i>
|
||||
</I>
|
||||
Simple solution: If the project has no parser for all files in a project
|
||||
either warn the user or don't allow it. Currently we destroy code -
|
||||
that's not a good solution. Btw. for this I wan't previews - then the
|
||||
developer can have a clear picture on what's going on with the source
|
||||
code.
|
||||
|
||||
><i> * Extensibility -- how easy will it be to build more "complex"
|
||||
</I>><i> refactorings? It would be interesting to catalogue all the
|
||||
</I>><i> refactorings provided by popular IDEs and Addins (VS, Eclipse,
|
||||
</I>><i> Resharper, DevExpress Refactor Pro etc) and try to break them up into
|
||||
</I>><i> more primitive operations, so that languages can get the high-level
|
||||
</I>><i> operations for free by implementing only the low-level operations. I
|
||||
</I>><i> know we have something like this already, but I think it'd be good to
|
||||
</I>><i> re-evaluate the primitives in light of all of the high-level
|
||||
</I>><i> operations we might want to implement.
|
||||
</I>
|
||||
Just get a copy of "Refactoring: Improving the Design of Existing Code"
|
||||
from Martin Fowler :). I'm still sleeping with it under my pillow.
|
||||
|
||||
><i> * Indexing -- for renaming operations (and "find all references") our
|
||||
</I>><i> performance is currently dire. It might be worth having an index to
|
||||
</I>><i> make these faster.
|
||||
</I>><i>
|
||||
</I>
|
||||
Yes the performance is worse, but currently it's mostly because of
|
||||
something I would call "issue with the infrastructure" - we can do it
|
||||
much more faster. But currently I don't want extensive changes here.
|
||||
|
||||
><i> I don't have any ideas right now on how these should be done, but I
|
||||
</I>><i> think it's important to take them into consideration :-)
|
||||
</I>><i>
|
||||
</I>I'm pretty sure I would've missed Cross project/language aspects :-).
|
||||
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#65">[ date ]</a>
|
||||
<a href="thread.html#65">[ thread ]</a>
|
||||
<a href="subject.html#65">[ subject ]</a>
|
||||
<a href="author.html#65">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,96 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=dd99b8c80811050449s2a29a4fcha4a616cb4b242f31%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000058.html">
|
||||
<LINK REL="Next" HREF="000059.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=dd99b8c80811050449s2a29a4fcha4a616cb4b242f31%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Nov 6 02:32:53 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#66">[ date ]</a>
|
||||
<a href="thread.html#66">[ thread ]</a>
|
||||
<a href="subject.html#66">[ subject ]</a>
|
||||
<a href="author.html#66">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> 1) UI-decoupling on preview/user-decision
|
||||
</I>
|
||||
Modal dialog for refactorings ?
|
||||
|
||||
><i> 2) Memory-consumption to keep track of all pending changes, and
|
||||
</I>><i> before/after scenarios
|
||||
</I>
|
||||
If we only keep the deltas I don't see a problem. When we keep the parse
|
||||
tree of the whole solution we may have one. (At least we would waste
|
||||
some memory)
|
||||
|
||||
><i> 3) Undoability
|
||||
</I>><i>
|
||||
</I>Ok. This one is really hard especially the undo handling is not done ide
|
||||
wide instead it's coupled with the views to handle undo/redo. We may
|
||||
need to change if we want undoable refactorings.
|
||||
|
||||
><i> Also it should be decided if all would be affected files should be
|
||||
</I>><i> loaded in editor windows, or changes could occur behind-the-scener
|
||||
</I>><i> after user previewing/deciding, this may bring in some synchronization
|
||||
</I>><i> issues with other subsystems/addins like the version control one.
|
||||
</I>><i>
|
||||
</I>No I don't want editor windows there. I want a refactoring dialog that
|
||||
shows the refactorings in an understandable way - but I wan't to use an
|
||||
"editor window" to show the refactoring changes.
|
||||
|
||||
><i> About version control integration, it is not common on open source
|
||||
</I>><i> projects, but where I work currently SVN is configured to demand
|
||||
</I>><i> locking files to be able to commit changes on them, meaning that
|
||||
</I>><i> eclipse/vs.net keep asking me if I want to overwrite the locally
|
||||
</I>><i> marked-as-readonly files in the middle of refactorings, as I never try
|
||||
</I>><i> to guess and lock files prior to working on them, and I think we
|
||||
</I>><i> should support that too.
|
||||
</I>
|
||||
That's a good feature. I noted it.
|
||||
|
||||
Thanks
|
||||
Mike
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#66">[ date ]</a>
|
||||
<a href="thread.html#66">[ thread ]</a>
|
||||
<a href="subject.html#66">[ subject ]</a>
|
||||
<a href="author.html#66">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,97 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Automagic%20settings%20upgrade%20dilemma&In-Reply-To=aa2b03a40811051911l660b680eoee5b1f92c54d5829%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000063.html">
|
||||
<LINK REL="Next" HREF="000074.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Automagic settings upgrade dilemma</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Automagic%20settings%20upgrade%20dilemma&In-Reply-To=aa2b03a40811051911l660b680eoee5b1f92c54d5829%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Automagic settings upgrade dilemma">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 5 23:16:32 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#67">[ date ]</a>
|
||||
<a href="thread.html#67">[ thread ]</a>
|
||||
<a href="subject.html#67">[ subject ]</a>
|
||||
<a href="author.html#67">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dc 05 de 11 de 2008 a les 21:11 -0600, en/na Mike Kestner va
|
||||
escriure:
|
||||
><i>
|
||||
</I>><i> On Wed, Nov 5, 2008 at 8:20 PM, Michael Hutchinson
|
||||
</I>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">m.j.hutchinson at gmail.com</A>> wrote:
|
||||
</I>><i>
|
||||
</I>><i> 1) Make the change automatically
|
||||
</I>><i> 2) Ask the user if they want to make the change (if they
|
||||
</I>><i> don't, it'll
|
||||
</I>><i> ask every time they open the project)
|
||||
</I>><i> 3) Add a warning to the build process, and
|
||||
</I>><i> a) Don't do anything, let users fix it themselves in the
|
||||
</I>><i> project file
|
||||
</I>><i> b) Re-enable the CompileTarget-changing UI when the
|
||||
</I>><i> CompileTarget
|
||||
</I>><i> is incorrect
|
||||
</I>><i>
|
||||
</I>><i> Or
|
||||
</I>><i>
|
||||
</I>><i> 4) Don't worry about it.
|
||||
</I>><i>
|
||||
</I>><i> I think #1 is probably right. Since there's no point in building an
|
||||
</I>><i> asp.net exe with a Main method, just do the update.
|
||||
</I>><i>
|
||||
</I>><i> I suppose you could refine the logic and only update if its an exe AND
|
||||
</I>><i> a Main has not been specified. That's the only other defensible
|
||||
</I>><i> configuration, right, even though it sounds like it's an exercise in
|
||||
</I>><i> silliness from an asp.net standpoint.
|
||||
</I>
|
||||
I pretty much agree. I think #1 is ok.
|
||||
|
||||
Lluis.
|
||||
|
||||
><i>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#67">[ date ]</a>
|
||||
<a href="thread.html#67">[ thread ]</a>
|
||||
<a href="subject.html#67">[ subject ]</a>
|
||||
<a href="author.html#67">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,87 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000065.html">
|
||||
<LINK REL="Next" HREF="000069.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225879868.4924.17.camel%40linux-yd7m.site"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Thu Nov 6 11:09:20 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#68">[ date ]</a>
|
||||
<a href="thread.html#68">[ thread ]</a>
|
||||
<a href="subject.html#68">[ subject ]</a>
|
||||
<a href="author.html#68">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dc 05 de 11 de 2008 a les 11:11 +0100, en/na Mike Krüger va escriure:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> After the next release I want to improve refactoring.
|
||||
</I>><i> Currently we only have rename as refactoring operation. Generally I want
|
||||
</I>><i> to do refactoring a bit different than it is now.
|
||||
</I>><i>
|
||||
</I>><i> I want a refactoring infrastructure that allows the user to preview all
|
||||
</I>><i> changes that are done in the refactoring step (see eclipse for an
|
||||
</I>><i> example).
|
||||
</I>
|
||||
Notice that change previewing for the rename operation can be done with
|
||||
the current infrastructure. It's a matter of finding the references,
|
||||
displaying them and do the replace when the user clicks on OK. The API
|
||||
supports that, although we haven't implemented the GUI.
|
||||
|
||||
><i>
|
||||
</I>><i> I'll need to extend/change the current refactoring infrastructure for
|
||||
</I>><i> this. And one of the goals for the new one is: unit test support. The
|
||||
</I>><i> new code completion infrastructure is tested with unit tests and I think
|
||||
</I>><i> that this has improved the code completion correctness greatly.
|
||||
</I>><i>
|
||||
</I>><i> Any thoughts/inputs here ?
|
||||
</I>
|
||||
I'd like to see a high level design of the API to get an idea of how you
|
||||
plan to improve the refactoring infrastructure.
|
||||
|
||||
Thanks!
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#68">[ date ]</a>
|
||||
<a href="thread.html#68">[ thread ]</a>
|
||||
<a href="subject.html#68">[ subject ]</a>
|
||||
<a href="author.html#68">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,91 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225987760.7463.24.camel%40164-99-120-118.boston.ximian.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000068.html">
|
||||
<LINK REL="Next" HREF="000070.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225987760.7463.24.camel%40164-99-120-118.boston.ximian.com"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Fri Nov 7 02:41:47 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#69">[ date ]</a>
|
||||
<a href="thread.html#69">[ thread ]</a>
|
||||
<a href="subject.html#69">[ subject ]</a>
|
||||
<a href="author.html#69">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> Notice that change previewing for the rename operation can be done with
|
||||
</I>><i> the current infrastructure. It's a matter of finding the references,
|
||||
</I>><i> displaying them and do the replace when the user clicks on OK. The API
|
||||
</I>><i> supports that, although we haven't implemented the GUI.
|
||||
</I>><i>
|
||||
</I>
|
||||
No not really. It's a hack. There is an operation called:
|
||||
|
||||
IMember RenameMember (RefactorerContext ctx,
|
||||
IType cls,
|
||||
IMember member,
|
||||
string newName);
|
||||
|
||||
And that's it. Ok you've:
|
||||
MemberReferenceCollection FindMemberReferences (RefactorerContext ctx,
|
||||
string fileName, IType cls, IMember member);
|
||||
|
||||
><i> >
|
||||
</I>><i> > I'll need to extend/change the current refactoring infrastructure for
|
||||
</I>><i> > this. And one of the goals for the new one is: unit test support. The
|
||||
</I>><i> > new code completion infrastructure is tested with unit tests and I think
|
||||
</I>><i> > that this has improved the code completion correctness greatly.
|
||||
</I>><i> >
|
||||
</I>><i> > Any thoughts/inputs here ?
|
||||
</I>><i>
|
||||
</I>><i> I'd like to see a high level design of the API to get an idea of how you
|
||||
</I>><i> plan to improve the refactoring infrastructure.
|
||||
</I>><i>
|
||||
</I>><i> Thanks!
|
||||
</I>><i> Lluis.
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#69">[ date ]</a>
|
||||
<a href="thread.html#69">[ thread ]</a>
|
||||
<a href="subject.html#69">[ subject ]</a>
|
||||
<a href="author.html#69">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,207 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225987760.7463.24.camel%40164-99-120-118.boston.ximian.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000069.html">
|
||||
<LINK REL="Next" HREF="000071.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1225987760.7463.24.camel%40164-99-120-118.boston.ximian.com"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Fri Nov 7 03:31:07 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#70">[ date ]</a>
|
||||
<a href="thread.html#70">[ thread ]</a>
|
||||
<a href="subject.html#70">[ subject ]</a>
|
||||
<a href="author.html#70">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> Notice that change previewing for the rename operation can be done
|
||||
</I>with
|
||||
><i> the current infrastructure. It's a matter of finding the references,
|
||||
</I>><i> displaying them and do the replace when the user clicks on OK. The API
|
||||
</I>><i> supports that, although we haven't implemented the GUI.
|
||||
</I>><i>
|
||||
</I>
|
||||
No not really. It's a hack. There is an operation called:
|
||||
|
||||
IMember RenameMember (RefactorerContext ctx,
|
||||
IType cls,
|
||||
IMember member,
|
||||
string newName);
|
||||
|
||||
And that's it. Ok you've:
|
||||
|
||||
MemberReferenceCollection FindMemberReferences (RefactorerContext ctx,
|
||||
string fileName,
|
||||
IType cls,
|
||||
IMember member);
|
||||
MemberReferenceCollection FindVariableReferences (RefactorerContext ctx,
|
||||
string fileName, LocalVariable var);
|
||||
MemberReferenceCollection FindParameterReferences (RefactorerContext
|
||||
ctx, string fileName, IParameter param);
|
||||
|
||||
And with these three methods you can hack something together for this
|
||||
one refactoring case - but that's it. Thisis not really what I've in
|
||||
mind to do.
|
||||
|
||||
><i> >
|
||||
</I>><i> > I'll need to extend/change the current refactoring infrastructure
|
||||
</I>for
|
||||
><i> > this. And one of the goals for the new one is: unit test support.
|
||||
</I>The
|
||||
><i> > new code completion infrastructure is tested with unit tests and I
|
||||
</I>think
|
||||
><i> > that this has improved the code completion correctness greatly.
|
||||
</I>><i> >
|
||||
</I>><i> > Any thoughts/inputs here ?
|
||||
</I>><i>
|
||||
</I>><i> I'd like to see a high level design of the API to get an idea of how
|
||||
</I>you
|
||||
><i> plan to improve the refactoring infrastructure.
|
||||
</I>><i>
|
||||
</I>
|
||||
Currently:
|
||||
|
||||
Anything seems to be called "refactorer" (Even classes that don't
|
||||
implement IRefactorer) to make it more stangely we've a refactorer
|
||||
called CodeGenerator (inheriting from BaseRefactorer). It looks like
|
||||
thats currently anything is hacked together.
|
||||
It starts with clicking on something in the editor window there is a
|
||||
class that builds the context menu and this class controls which
|
||||
operations are valid.
|
||||
|
||||
I want:
|
||||
|
||||
Split up refactoring a bit to make it clear what each class does.
|
||||
|
||||
I intend to split up the "refactoring" feature. Each refactoring
|
||||
operation should be an own class that knows it's responsibilities (based
|
||||
on the resolve result) it knows when it's valid to display in the
|
||||
refactoring context menu.
|
||||
|
||||
Then we would've classes like:
|
||||
|
||||
Rename
|
||||
ImplicitImplementInterface
|
||||
ExplicitImplementInterface
|
||||
ExtractMethod
|
||||
|
||||
etc.
|
||||
|
||||
These refactorings should be placed in the addin tree.
|
||||
|
||||
We've a RefactorerContext - that's good these context should be
|
||||
containing the find functions and some helper functions that are
|
||||
currently splitted up between IRefactorer and CodeRefactorer).
|
||||
|
||||
Then we need a CodeGenerator - this is a class that actually builds
|
||||
code. Not by changing it, it should produce "diffs".
|
||||
|
||||
Then we need something like a result of the refactoring operations.
|
||||
That'll give us a list of files with diffs as well as a list of the
|
||||
class tree with changes. I intend to have a dialog that looks like:
|
||||
|
||||
-----------------
|
||||
|
||||
Positions
|
||||
|
||||
|
||||
-----------------
|
||||
|
||||
|
||||
Diffs
|
||||
|
||||
|
||||
-----------------
|
||||
|
||||
That's what I intend to:
|
||||
|
||||
class RefactoringResult {
|
||||
List<Change> Changes;
|
||||
}
|
||||
|
||||
class Change {
|
||||
string fileName;
|
||||
IMember memberLocation;
|
||||
|
||||
DomLocation position;
|
||||
|
||||
string old;
|
||||
string new;
|
||||
}
|
||||
|
||||
|
||||
Something like this an 'positions' should be switchable between class
|
||||
view and file view (like the pads).
|
||||
|
||||
The Refactoring should something look like:
|
||||
|
||||
IRefactoring {
|
||||
bool IsSupported (ResolveResult result);
|
||||
string GetDisplaySting (ResolveResult result);
|
||||
|
||||
void Run ();
|
||||
}
|
||||
|
||||
IResultRefactoring : IRefactoring {
|
||||
RefactoringResult DoOperation (RefactorerContext, ResolveResult
|
||||
result);
|
||||
}
|
||||
|
||||
I want to support maybe more than one type of refactoring, therefore
|
||||
just the "run" method. And there are more types than just the diff
|
||||
refactoring - implement/override members for example therefore not all
|
||||
refactorings require the position/diff dialogs.
|
||||
Another example could be renaming a local variable or parameter which
|
||||
could be displayed inline in the text editor instead of having pop up
|
||||
dialogs. (Ok I admit I've worked a bit with eclipse this week :) )
|
||||
|
||||
To decide: On which infrastructure we'll build. Currently it's a bit
|
||||
mixed up between CodeDOM and NRefactory. I would've chosen NRefactory
|
||||
because we're already building on this and an own AST gives more control
|
||||
than a pre defined one.
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#70">[ date ]</a>
|
||||
<a href="thread.html#70">[ thread ]</a>
|
||||
<a href="subject.html#70">[ subject ]</a>
|
||||
<a href="author.html#70">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,240 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1226046667.3624.105.camel%40linux-yd7m.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000070.html">
|
||||
<LINK REL="Next" HREF="000072.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1226046667.3624.105.camel%40linux-yd7m.site"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Fri Nov 7 11:17:22 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#71">[ date ]</a>
|
||||
<a href="thread.html#71">[ thread ]</a>
|
||||
<a href="subject.html#71">[ subject ]</a>
|
||||
<a href="author.html#71">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dv 07 de 11 de 2008 a les 09:31 +0100, en/na Mike Krüger va escriure:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> > Notice that change previewing for the rename operation can be done
|
||||
</I>><i> with
|
||||
</I>><i> > the current infrastructure. It's a matter of finding the references,
|
||||
</I>><i> > displaying them and do the replace when the user clicks on OK. The API
|
||||
</I>><i> > supports that, although we haven't implemented the GUI.
|
||||
</I>><i> >
|
||||
</I>><i>
|
||||
</I>><i> No not really. It's a hack. There is an operation called:
|
||||
</I>><i>
|
||||
</I>><i> IMember RenameMember (RefactorerContext ctx,
|
||||
</I>><i> IType cls,
|
||||
</I>><i> IMember member,
|
||||
</I>><i> string newName);
|
||||
</I>><i>
|
||||
</I>><i> And that's it. Ok you've:
|
||||
</I>><i>
|
||||
</I>><i> MemberReferenceCollection FindMemberReferences (RefactorerContext ctx,
|
||||
</I>><i> string fileName,
|
||||
</I>><i> IType cls,
|
||||
</I>><i> IMember member);
|
||||
</I>><i> MemberReferenceCollection FindVariableReferences (RefactorerContext ctx,
|
||||
</I>><i> string fileName, LocalVariable var);
|
||||
</I>><i> MemberReferenceCollection FindParameterReferences (RefactorerContext
|
||||
</I>><i> ctx, string fileName, IParameter param);
|
||||
</I>><i>
|
||||
</I>><i> And with these three methods you can hack something together for this
|
||||
</I>><i> one refactoring case - but that's it. Thisis not really what I've in
|
||||
</I>><i> mind to do.
|
||||
</I>><i>
|
||||
</I>><i> > >
|
||||
</I>><i> > > I'll need to extend/change the current refactoring infrastructure
|
||||
</I>><i> for
|
||||
</I>><i> > > this. And one of the goals for the new one is: unit test support.
|
||||
</I>><i> The
|
||||
</I>><i> > > new code completion infrastructure is tested with unit tests and I
|
||||
</I>><i> think
|
||||
</I>><i> > > that this has improved the code completion correctness greatly.
|
||||
</I>><i> > >
|
||||
</I>><i> > > Any thoughts/inputs here ?
|
||||
</I>><i> >
|
||||
</I>><i> > I'd like to see a high level design of the API to get an idea of how
|
||||
</I>><i> you
|
||||
</I>><i> > plan to improve the refactoring infrastructure.
|
||||
</I>><i> >
|
||||
</I>><i>
|
||||
</I>><i> Currently:
|
||||
</I>><i>
|
||||
</I>><i> Anything seems to be called "refactorer" (Even classes that don't
|
||||
</I>><i> implement IRefactorer) to make it more stangely we've a refactorer
|
||||
</I>><i> called CodeGenerator (inheriting from BaseRefactorer). It looks like
|
||||
</I>><i> thats currently anything is hacked together.
|
||||
</I>
|
||||
Before trying to rewrite any piece of code you should at least study the
|
||||
current code and try to understand how it works, what are the
|
||||
responsibilities of each class, and why it was designed in that way.
|
||||
Only then you'll be qualified to say what's wrong and propose a better
|
||||
solution. The use of words like "strangely", "hack" and "looks like"
|
||||
clearly show that you didn't follow this step.
|
||||
|
||||
I'm not saying that the current refactoring infrastructure is perfect.
|
||||
It is not. Much of it will probably have to be changed if we want to
|
||||
support more advanced refactoring operations. But you can't arbitrarily
|
||||
drop all current code, ignoring what has been done. We already had some
|
||||
bad experiences in MD because of this.
|
||||
|
||||
><i> It starts with clicking on something in the editor window there is a
|
||||
</I>><i> class that builds the context menu and this class controls which
|
||||
</I>><i> operations are valid.
|
||||
</I>><i>
|
||||
</I>><i> I want:
|
||||
</I>><i>
|
||||
</I>><i> Split up refactoring a bit to make it clear what each class does.
|
||||
</I>><i>
|
||||
</I>><i> I intend to split up the "refactoring" feature. Each refactoring
|
||||
</I>><i> operation should be an own class that knows it's responsibilities (based
|
||||
</I>><i> on the resolve result) it knows when it's valid to display in the
|
||||
</I>><i> refactoring context menu.
|
||||
</I>><i>
|
||||
</I>><i> Then we would've classes like:
|
||||
</I>><i>
|
||||
</I>><i> Rename
|
||||
</I>><i> ImplicitImplementInterface
|
||||
</I>><i> ExplicitImplementInterface
|
||||
</I>><i> ExtractMethod
|
||||
</I>><i>
|
||||
</I>><i> etc.
|
||||
</I>><i>
|
||||
</I>><i> These refactorings should be placed in the addin tree.
|
||||
</I>
|
||||
Will those refactoring classes be language-specific?
|
||||
For example, the Rename class, there will be a RenameCSharp and a
|
||||
RenameVisualBasic? if that's the case, will they share some code?
|
||||
|
||||
><i>
|
||||
</I>><i> We've a RefactorerContext - that's good these context should be
|
||||
</I>><i> containing the find functions and some helper functions that are
|
||||
</I>><i> currently splitted up between IRefactorer and CodeRefactorer).
|
||||
</I>><i>
|
||||
</I>><i> Then we need a CodeGenerator - this is a class that actually builds
|
||||
</I>><i> code. Not by changing it, it should produce "diffs".
|
||||
</I>
|
||||
Some add-ins need to perform basic code manipulation operation such as
|
||||
inserting a new method to a class or adding custom attributes to class
|
||||
declarations. Which class would provide those operations?
|
||||
|
||||
I'd like to see how the high level API will look like. That is, the API
|
||||
that will allow starting refactoring operations or manipulate code.
|
||||
|
||||
><i>
|
||||
</I>><i> Then we need something like a result of the refactoring operations.
|
||||
</I>><i> That'll give us a list of files with diffs as well as a list of the
|
||||
</I>><i> class tree with changes. I intend to have a dialog that looks like:
|
||||
</I>><i>
|
||||
</I>><i> -----------------
|
||||
</I>><i>
|
||||
</I>><i> Positions
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> -----------------
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> Diffs
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> -----------------
|
||||
</I>><i>
|
||||
</I>><i> That's what I intend to:
|
||||
</I>><i>
|
||||
</I>><i> class RefactoringResult {
|
||||
</I>><i> List<Change> Changes;
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i> class Change {
|
||||
</I>><i> string fileName;
|
||||
</I>><i> IMember memberLocation;
|
||||
</I>><i>
|
||||
</I>><i> DomLocation position;
|
||||
</I>><i>
|
||||
</I>><i> string old;
|
||||
</I>><i> string new;
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> Something like this an 'positions' should be switchable between class
|
||||
</I>><i> view and file view (like the pads).
|
||||
</I>><i>
|
||||
</I>><i> The Refactoring should something look like:
|
||||
</I>><i>
|
||||
</I>><i> IRefactoring {
|
||||
</I>><i> bool IsSupported (ResolveResult result);
|
||||
</I>><i> string GetDisplaySting (ResolveResult result);
|
||||
</I>><i>
|
||||
</I>><i> void Run ();
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i> IResultRefactoring : IRefactoring {
|
||||
</I>><i> RefactoringResult DoOperation (RefactorerContext, ResolveResult
|
||||
</I>><i> result);
|
||||
</I>><i> }
|
||||
</I>><i>
|
||||
</I>><i> I want to support maybe more than one type of refactoring, therefore
|
||||
</I>><i> just the "run" method. And there are more types than just the diff
|
||||
</I>><i> refactoring - implement/override members for example therefore not all
|
||||
</I>><i> refactorings require the position/diff dialogs.
|
||||
</I>
|
||||
Can you provide a list of all refactorings you plan to implement and
|
||||
what are the requirements of each of them?
|
||||
|
||||
><i> Another example could be renaming a local variable or parameter which
|
||||
</I>><i> could be displayed inline in the text editor instead of having pop up
|
||||
</I>><i> dialogs. (Ok I admit I've worked a bit with eclipse this week :) )
|
||||
</I>><i>
|
||||
</I>><i> To decide: On which infrastructure we'll build. Currently it's a bit
|
||||
</I>><i> mixed up between CodeDOM and NRefactory. I would've chosen NRefactory
|
||||
</I>><i> because we're already building on this and an own AST gives more control
|
||||
</I>><i> than a pre defined one.
|
||||
</I>><i>
|
||||
</I>><i> Regards
|
||||
</I>><i> Mike
|
||||
</I>><i>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#71">[ date ]</a>
|
||||
<a href="thread.html#71">[ thread ]</a>
|
||||
<a href="subject.html#71">[ subject ]</a>
|
||||
<a href="author.html#71">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,130 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1226074642.3779.27.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000071.html">
|
||||
<LINK REL="Next" HREF="000073.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Mike Krüger</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1226074642.3779.27.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">mkrueger at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Nov 10 02:53:29 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#72">[ date ]</a>
|
||||
<a href="thread.html#72">[ thread ]</a>
|
||||
<a href="subject.html#72">[ subject ]</a>
|
||||
<a href="author.html#72">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi
|
||||
|
||||
><i> I'm not saying that the current refactoring infrastructure is perfect.
|
||||
</I>><i> It is not. Much of it will probably have to be changed if we want to
|
||||
</I>><i> support more advanced refactoring operations. But you can't arbitrarily
|
||||
</I>><i> drop all current code, ignoring what has been done. We already had some
|
||||
</I>><i> bad experiences in MD because of this.
|
||||
</I>><i>
|
||||
</I>
|
||||
I don't want to drop code. In fact the current one is a good starting
|
||||
point. There is no need to 'drop' code - I only drop code when there is
|
||||
no other option. We can use refactoring methods move/rename some stuff -
|
||||
that's it. I would only drop code if it's GPL or really very different
|
||||
to refactor the code.
|
||||
The code we currently have is something I can work with.
|
||||
|
||||
Something different: But over time we must rewrite ALL GPL code. I think
|
||||
that's still on our todo list isn't it ?
|
||||
Refactoring is about improving the design of existing code, not to
|
||||
rewrite it. In this way it's possible to keep all "information" in the
|
||||
existing code. With a rewrite you'll loose all knowledge that lead to
|
||||
the existing code. If possible refactoring is always better.
|
||||
(But keep in mind that all GPL parts need to be rewritten, except we
|
||||
change our position here)
|
||||
|
||||
><i> > It starts with clicking on something in the editor window there is a
|
||||
</I>><i> > class that builds the context menu and this class controls which
|
||||
</I>><i> > operations are valid.
|
||||
</I>><i> >
|
||||
</I>><i> > I want:
|
||||
</I>><i> >
|
||||
</I>><i> > Split up refactoring a bit to make it clear what each class does.
|
||||
</I>><i> >
|
||||
</I>><i> > I intend to split up the "refactoring" feature. Each refactoring
|
||||
</I>><i> > operation should be an own class that knows it's responsibilities (based
|
||||
</I>><i> > on the resolve result) it knows when it's valid to display in the
|
||||
</I>><i> > refactoring context menu.
|
||||
</I>><i> >
|
||||
</I>><i> > Then we would've classes like:
|
||||
</I>><i> >
|
||||
</I>><i> > Rename
|
||||
</I>><i> > ImplicitImplementInterface
|
||||
</I>><i> > ExplicitImplementInterface
|
||||
</I>><i> > ExtractMethod
|
||||
</I>><i> >
|
||||
</I>><i> > etc.
|
||||
</I>><i> >
|
||||
</I>><i> > These refactorings should be placed in the addin tree.
|
||||
</I>><i>
|
||||
</I>><i> Will those refactoring classes be language-specific?
|
||||
</I>><i> For example, the Rename class, there will be a RenameCSharp and a
|
||||
</I>><i> RenameVisualBasic? if that's the case, will they share some code?
|
||||
</I>><i>
|
||||
</I>
|
||||
Thats in the responsibility of the classes they can support csharp and
|
||||
visualbasic, but I don't think that I'll support more than these two, I
|
||||
think I personally will stick to C#. Like with the code completion
|
||||
infrastructure in the csharp binding. It would be possible to use it for
|
||||
VB.NET and any other language that can produce NRefactory DOM.
|
||||
|
||||
When I'm really satisfied with refactoring and the capabilities of
|
||||
monodevelop (especially text editor and search features) I'll maybe
|
||||
improve visual basic support or bring any other language backend up to
|
||||
the C# level. But I don't know if we'll ever reach this point - there is
|
||||
always more stuff to do and I'm a C# fan :).
|
||||
|
||||
Cross language functionality for refactorings is something we need to
|
||||
factor in but my current 'plan' would be to disallow cross language
|
||||
refactorings until all refactoring commands are availble for any
|
||||
languages in the solution - not to allow partial refactorings.
|
||||
|
||||
Regards
|
||||
Mike
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#72">[ date ]</a>
|
||||
<a href="thread.html#72">[ thread ]</a>
|
||||
<a href="subject.html#72">[ subject ]</a>
|
||||
<a href="author.html#72">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,145 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Improving refactoring after 2.0
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1226303609.3613.134.camel%40linux-yd7m.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000072.html">
|
||||
<LINK REL="Next" HREF="000061.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Improving refactoring after 2.0</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Improving%20refactoring%20after%202.0&In-Reply-To=1226303609.3613.134.camel%40linux-yd7m.site"
|
||||
TITLE="[Monodevelop-devel] Improving refactoring after 2.0">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Tue Nov 11 11:03:49 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#73">[ date ]</a>
|
||||
<a href="thread.html#73">[ thread ]</a>
|
||||
<a href="subject.html#73">[ subject ]</a>
|
||||
<a href="author.html#73">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dl 10 de 11 de 2008 a les 08:53 +0100, en/na Mike Krüger va escriure:
|
||||
><i> Hi
|
||||
</I>><i>
|
||||
</I>><i> > I'm not saying that the current refactoring infrastructure is perfect.
|
||||
</I>><i> > It is not. Much of it will probably have to be changed if we want to
|
||||
</I>><i> > support more advanced refactoring operations. But you can't arbitrarily
|
||||
</I>><i> > drop all current code, ignoring what has been done. We already had some
|
||||
</I>><i> > bad experiences in MD because of this.
|
||||
</I>><i> >
|
||||
</I>><i>
|
||||
</I>><i> I don't want to drop code. In fact the current one is a good starting
|
||||
</I>><i> point. There is no need to 'drop' code - I only drop code when there is
|
||||
</I>><i> no other option. We can use refactoring methods move/rename some stuff -
|
||||
</I>><i> that's it. I would only drop code if it's GPL or really very different
|
||||
</I>><i> to refactor the code.
|
||||
</I>><i> The code we currently have is something I can work with.
|
||||
</I>><i>
|
||||
</I>><i> Something different: But over time we must rewrite ALL GPL code. I think
|
||||
</I>><i> that's still on our todo list isn't it ?
|
||||
</I>
|
||||
Yes, but it is not a priority right now.
|
||||
|
||||
><i> Refactoring is about improving the design of existing code, not to
|
||||
</I>><i> rewrite it. In this way it's possible to keep all "information" in the
|
||||
</I>><i> existing code. With a rewrite you'll loose all knowledge that lead to
|
||||
</I>><i> the existing code. If possible refactoring is always better.
|
||||
</I>><i> (But keep in mind that all GPL parts need to be rewritten, except we
|
||||
</I>><i> change our position here)
|
||||
</I>><i>
|
||||
</I>><i> > > It starts with clicking on something in the editor window there is a
|
||||
</I>><i> > > class that builds the context menu and this class controls which
|
||||
</I>><i> > > operations are valid.
|
||||
</I>><i> > >
|
||||
</I>><i> > > I want:
|
||||
</I>><i> > >
|
||||
</I>><i> > > Split up refactoring a bit to make it clear what each class does.
|
||||
</I>><i> > >
|
||||
</I>><i> > > I intend to split up the "refactoring" feature. Each refactoring
|
||||
</I>><i> > > operation should be an own class that knows it's responsibilities (based
|
||||
</I>><i> > > on the resolve result) it knows when it's valid to display in the
|
||||
</I>><i> > > refactoring context menu.
|
||||
</I>><i> > >
|
||||
</I>><i> > > Then we would've classes like:
|
||||
</I>><i> > >
|
||||
</I>><i> > > Rename
|
||||
</I>><i> > > ImplicitImplementInterface
|
||||
</I>><i> > > ExplicitImplementInterface
|
||||
</I>><i> > > ExtractMethod
|
||||
</I>><i> > >
|
||||
</I>><i> > > etc.
|
||||
</I>><i> > >
|
||||
</I>><i> > > These refactorings should be placed in the addin tree.
|
||||
</I>><i> >
|
||||
</I>><i> > Will those refactoring classes be language-specific?
|
||||
</I>><i> > For example, the Rename class, there will be a RenameCSharp and a
|
||||
</I>><i> > RenameVisualBasic? if that's the case, will they share some code?
|
||||
</I>><i> >
|
||||
</I>><i>
|
||||
</I>><i> Thats in the responsibility of the classes they can support csharp and
|
||||
</I>><i> visualbasic, but I don't think that I'll support more than these two, I
|
||||
</I>><i> think I personally will stick to C#. Like with the code completion
|
||||
</I>><i> infrastructure in the csharp binding. It would be possible to use it for
|
||||
</I>><i> VB.NET and any other language that can produce NRefactory DOM.
|
||||
</I>
|
||||
Maybe the core MD team won't be able to provide support for languages
|
||||
other than C#, but maybe somebody else wants to contribute it.
|
||||
|
||||
><i>
|
||||
</I>><i> When I'm really satisfied with refactoring and the capabilities of
|
||||
</I>><i> monodevelop (especially text editor and search features) I'll maybe
|
||||
</I>><i> improve visual basic support or bring any other language backend up to
|
||||
</I>><i> the C# level. But I don't know if we'll ever reach this point - there is
|
||||
</I>><i> always more stuff to do and I'm a C# fan :).
|
||||
</I>><i>
|
||||
</I>><i> Cross language functionality for refactorings is something we need to
|
||||
</I>><i> factor in but my current 'plan' would be to disallow cross language
|
||||
</I>><i> refactorings until all refactoring commands are availble for any
|
||||
</I>><i> languages in the solution - not to allow partial refactorings.
|
||||
</I>
|
||||
In some cases, a warning will be enough. For example, the user should be
|
||||
able to run Find References, but the results list could include a
|
||||
warning saying that project XXX could not be searched.
|
||||
|
||||
Even Rename Member should be allowed IMO. In the preview window it would
|
||||
show a warning about a projects whose languages does not support
|
||||
renaming, but it should allow renaming in those that support it.
|
||||
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#73">[ date ]</a>
|
||||
<a href="thread.html#73">[ thread ]</a>
|
||||
<a href="subject.html#73">[ subject ]</a>
|
||||
<a href="author.html#73">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,96 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Comipiling%20Monodevelop%20under%20Debian%20from%20trunk&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000067.html">
|
||||
<LINK REL="Next" HREF="000075.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk</H1>
|
||||
<B>Alexander M. Batishchev</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Comipiling%20Monodevelop%20under%20Debian%20from%20trunk&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk">abatishchev at godfather.net.ru
|
||||
</A><BR>
|
||||
<I>Mon Nov 17 09:50:09 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#74">[ date ]</a>
|
||||
<a href="thread.html#74">[ thread ]</a>
|
||||
<a href="subject.html#74">[ subject ]</a>
|
||||
<a href="author.html#74">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hello everybody,
|
||||
I'm trying to compile MD from trunk under Debian and got next trouble:
|
||||
|
||||
$ cd monodevelop
|
||||
$ ./configure --prefix=/usr/local
|
||||
checking for MONO_ADDINS... configure: error: Package requirements
|
||||
(mono-addins >= 0.3) were not met:
|
||||
No package 'mono-addins' found
|
||||
|
||||
$ svn co <A HREF="svn://anonsvn.mono-project.com/source/trunk/mono-addins">svn://anonsvn.mono-project.com/source/trunk/mono-addins</A>
|
||||
$ cd mono-addins
|
||||
$ ./autogen.sh --prefix=/usr/
|
||||
checking for GTK_SHARP_20... configure: error: Package requirements
|
||||
(gtk-sharp-2.0) were not met:
|
||||
No package 'gtk-sharp-2.0' found
|
||||
|
||||
$ svn co <A HREF="svn://anonsvn.mono-project.com/source/trunk/gtk-sharp">svn://anonsvn.mono-project.com/source/trunk/gtk-sharp</A>
|
||||
$ cd gtk-sharp
|
||||
$ ./autogen.sh --prefix=/usr/
|
||||
**Error**: autogen.sh has been replaced by bootstrap for the 2.5.x release.
|
||||
To bootstrap a 1.9.x build run bootstrap-2.4.
|
||||
$ ./bootstrap-2.12
|
||||
checking for PANGO... configure: error: Package requirements (pango) were
|
||||
not met:
|
||||
No package 'pango' found
|
||||
|
||||
Here is my trouble! Whare can I take the pango package?
|
||||
$ sudo apt-get install pango
|
||||
E: Couldn't find package pango
|
||||
|
||||
I have installed libpango1.0.-0 and libpango1.0-common but it doesn't helps.
|
||||
What I have to install more? Maybe libpango1.0-dev?
|
||||
Assist me please!
|
||||
|
||||
===
|
||||
Best regards,
|
||||
Alexander M. Batishchev
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#74">[ date ]</a>
|
||||
<a href="thread.html#74">[ thread ]</a>
|
||||
<a href="subject.html#74">[ subject ]</a>
|
||||
<a href="author.html#74">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,106 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Comipiling%20Monodevelop%20under%20Debian%0A%09from%09trunk&In-Reply-To=000401c948c3%24cf5f6d50%246e1e47f0%24%40net.ru">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000074.html">
|
||||
<LINK REL="Next" HREF="000076.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Comipiling%20Monodevelop%20under%20Debian%0A%09from%09trunk&In-Reply-To=000401c948c3%24cf5f6d50%246e1e47f0%24%40net.ru"
|
||||
TITLE="[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Nov 17 10:13:39 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#75">[ date ]</a>
|
||||
<a href="thread.html#75">[ thread ]</a>
|
||||
<a href="subject.html#75">[ subject ]</a>
|
||||
<a href="author.html#75">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dl 17 de 11 de 2008 a les 17:50 +0300, en/na Alexander M. Batishchev
|
||||
va escriure:
|
||||
><i> Hello everybody,
|
||||
</I>><i> I'm trying to compile MD from trunk under Debian and got next trouble:
|
||||
</I>><i>
|
||||
</I>><i> $ cd monodevelop
|
||||
</I>><i> $ ./configure --prefix=/usr/local
|
||||
</I>><i> checking for MONO_ADDINS... configure: error: Package requirements
|
||||
</I>><i> (mono-addins >= 0.3) were not met:
|
||||
</I>><i> No package 'mono-addins' found
|
||||
</I>><i>
|
||||
</I>><i> $ svn co <A HREF="svn://anonsvn.mono-project.com/source/trunk/mono-addins">svn://anonsvn.mono-project.com/source/trunk/mono-addins</A>
|
||||
</I>><i> $ cd mono-addins
|
||||
</I>><i> $ ./autogen.sh --prefix=/usr/
|
||||
</I>><i> checking for GTK_SHARP_20... configure: error: Package requirements
|
||||
</I>><i> (gtk-sharp-2.0) were not met:
|
||||
</I>><i> No package 'gtk-sharp-2.0' found
|
||||
</I>><i>
|
||||
</I>><i> $ svn co <A HREF="svn://anonsvn.mono-project.com/source/trunk/gtk-sharp">svn://anonsvn.mono-project.com/source/trunk/gtk-sharp</A>
|
||||
</I>><i> $ cd gtk-sharp
|
||||
</I>><i> $ ./autogen.sh --prefix=/usr/
|
||||
</I>><i> **Error**: autogen.sh has been replaced by bootstrap for the 2.5.x release.
|
||||
</I>><i> To bootstrap a 1.9.x build run bootstrap-2.4.
|
||||
</I>><i> $ ./bootstrap-2.12
|
||||
</I>><i> checking for PANGO... configure: error: Package requirements (pango) were
|
||||
</I>><i> not met:
|
||||
</I>><i> No package 'pango' found
|
||||
</I>><i>
|
||||
</I>><i> Here is my trouble! Whare can I take the pango package?
|
||||
</I>><i> $ sudo apt-get install pango
|
||||
</I>><i> E: Couldn't find package pango
|
||||
</I>><i>
|
||||
</I>><i> I have installed libpango1.0.-0 and libpango1.0-common but it doesn't helps.
|
||||
</I>><i> What I have to install more? Maybe libpango1.0-dev?
|
||||
</I>
|
||||
Yes, libpango1.0-dev.
|
||||
|
||||
><i> Assist me please!
|
||||
</I>><i>
|
||||
</I>><i> ===
|
||||
</I>><i> Best regards,
|
||||
</I>><i> Alexander M. Batishchev
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#75">[ date ]</a>
|
||||
<a href="thread.html#75">[ thread ]</a>
|
||||
<a href="subject.html#75">[ subject ]</a>
|
||||
<a href="author.html#75">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,121 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Comipiling%20Monodevelop%20under%20Debian%0A%09from%09trunk&In-Reply-To=1226934819.4215.5.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000075.html">
|
||||
<LINK REL="Next" HREF="000077.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk</H1>
|
||||
<B>Alexander M. Batishchev</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Comipiling%20Monodevelop%20under%20Debian%0A%09from%09trunk&In-Reply-To=1226934819.4215.5.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk">abatishchev at godfather.net.ru
|
||||
</A><BR>
|
||||
<I>Mon Nov 17 11:31:11 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#76">[ date ]</a>
|
||||
<a href="thread.html#76">[ thread ]</a>
|
||||
<a href="subject.html#76">[ subject ]</a>
|
||||
<a href="author.html#76">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi Lluis, thanks for answer your answer! Could you please me assist me a little bit more?
|
||||
MonoDevelop also requires glade-sharp witch compilation occurs an error:
|
||||
checking for GLADEUI... configure: error: Package requirements (libgladeui-1.0 >= 2.90.0) were not met:
|
||||
No package 'libgladeui-1.0' found
|
||||
My Debian package manager has only libgladeui-1.7 and libgladeui-1-dev (version 3.4.5-3 both). Both are installed.
|
||||
Why does it not met requirements?
|
||||
|
||||
-----Original Message-----
|
||||
From: Lluis Sanchez Gual [mailto:<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lluis at novell.com</A>]
|
||||
Sent: Monday, November 17, 2008 6:14 PM
|
||||
To: Alexander M. Batishchev
|
||||
Cc: <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">monodevelop-devel-list at lists.ximian.com</A>
|
||||
Subject: Re: [Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
|
||||
El dl 17 de 11 de 2008 a les 17:50 +0300, en/na Alexander M. Batishchev
|
||||
va escriure:
|
||||
><i> Hello everybody,
|
||||
</I>><i> I'm trying to compile MD from trunk under Debian and got next trouble:
|
||||
</I>><i>
|
||||
</I>><i> $ cd monodevelop
|
||||
</I>><i> $ ./configure --prefix=/usr/local
|
||||
</I>><i> checking for MONO_ADDINS... configure: error: Package requirements
|
||||
</I>><i> (mono-addins >= 0.3) were not met:
|
||||
</I>><i> No package 'mono-addins' found
|
||||
</I>><i>
|
||||
</I>><i> $ svn co <A HREF="svn://anonsvn.mono-project.com/source/trunk/mono-addins">svn://anonsvn.mono-project.com/source/trunk/mono-addins</A>
|
||||
</I>><i> $ cd mono-addins
|
||||
</I>><i> $ ./autogen.sh --prefix=/usr/
|
||||
</I>><i> checking for GTK_SHARP_20... configure: error: Package requirements
|
||||
</I>><i> (gtk-sharp-2.0) were not met:
|
||||
</I>><i> No package 'gtk-sharp-2.0' found
|
||||
</I>><i>
|
||||
</I>><i> $ svn co <A HREF="svn://anonsvn.mono-project.com/source/trunk/gtk-sharp">svn://anonsvn.mono-project.com/source/trunk/gtk-sharp</A>
|
||||
</I>><i> $ cd gtk-sharp
|
||||
</I>><i> $ ./autogen.sh --prefix=/usr/
|
||||
</I>><i> **Error**: autogen.sh has been replaced by bootstrap for the 2.5.x release.
|
||||
</I>><i> To bootstrap a 1.9.x build run bootstrap-2.4.
|
||||
</I>><i> $ ./bootstrap-2.12
|
||||
</I>><i> checking for PANGO... configure: error: Package requirements (pango) were
|
||||
</I>><i> not met:
|
||||
</I>><i> No package 'pango' found
|
||||
</I>><i>
|
||||
</I>><i> Here is my trouble! Whare can I take the pango package?
|
||||
</I>><i> $ sudo apt-get install pango
|
||||
</I>><i> E: Couldn't find package pango
|
||||
</I>><i>
|
||||
</I>><i> I have installed libpango1.0.-0 and libpango1.0-common but it doesn't helps.
|
||||
</I>><i> What I have to install more? Maybe libpango1.0-dev?
|
||||
</I>
|
||||
Yes, libpango1.0-dev.
|
||||
|
||||
><i> Assist me please!
|
||||
</I>><i>
|
||||
</I>><i> ===
|
||||
</I>><i> Best regards,
|
||||
</I>><i> Alexander M. Batishchev
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> _______________________________________________
|
||||
</I>><i> Monodevelop-devel-list mailing list
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">Monodevelop-devel-list at lists.ximian.com</A>
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list</A>
|
||||
</I>
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#76">[ date ]</a>
|
||||
<a href="thread.html#76">[ thread ]</a>
|
||||
<a href="subject.html#76">[ subject ]</a>
|
||||
<a href="author.html#76">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,79 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%20MD%27s%0A%09makefiles&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000076.html">
|
||||
<LINK REL="Next" HREF="000078.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%20MD%27s%0A%09makefiles&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Mon Nov 17 18:30:36 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#77">[ date ]</a>
|
||||
<a href="thread.html#77">[ thread ]</a>
|
||||
<a href="subject.html#77">[ subject ]</a>
|
||||
<a href="author.html#77">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi!
|
||||
|
||||
I've discussed with Mike (Kestner) a couple of times about the need for
|
||||
proper dependency checks between the MD makefiles. That is, a change in
|
||||
one of the MD projects would cause all dependent projects to be
|
||||
rebuilt.
|
||||
|
||||
I'm reluctant to do this change because any small change (even if not
|
||||
breaking change) in one of the core MD assemblies would cause the
|
||||
rebuild of all the 50 assemblies of MD, and that would be really
|
||||
annoying for those who work daily on those assemblies.
|
||||
|
||||
However Mike is right in that with proper dependency checking the
|
||||
makefiles would be more correct and would avoid weird build errors when
|
||||
there are changes in the api.
|
||||
|
||||
So I'd like to know what you think about this. I suggested making this
|
||||
project dependency optional, although I don't know how hard it would be.
|
||||
|
||||
Thoughts?
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#77">[ date ]</a>
|
||||
<a href="thread.html#77">[ thread ]</a>
|
||||
<a href="subject.html#77">[ subject ]</a>
|
||||
<a href="author.html#77">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,92 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%20MD%27s%0A%09makefiles&In-Reply-To=1226964636.4215.61.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000077.html">
|
||||
<LINK REL="Next" HREF="000079.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%20MD%27s%0A%09makefiles&In-Reply-To=1226964636.4215.61.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Nov 17 20:19:43 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#78">[ date ]</a>
|
||||
<a href="thread.html#78">[ thread ]</a>
|
||||
<a href="subject.html#78">[ subject ]</a>
|
||||
<a href="author.html#78">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Mon, Nov 17, 2008 at 6:30 PM, Lluis Sanchez Gual <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lluis at novell.com</A>> wrote:
|
||||
><i> Hi!
|
||||
</I>><i>
|
||||
</I>><i> I've discussed with Mike (Kestner) a couple of times about the need for
|
||||
</I>><i> proper dependency checks between the MD makefiles. That is, a change in
|
||||
</I>><i> one of the MD projects would cause all dependent projects to be
|
||||
</I>><i> rebuilt.
|
||||
</I>><i>
|
||||
</I>><i> I'm reluctant to do this change because any small change (even if not
|
||||
</I>><i> breaking change) in one of the core MD assemblies would cause the
|
||||
</I>><i> rebuild of all the 50 assemblies of MD, and that would be really
|
||||
</I>><i> annoying for those who work daily on those assemblies.
|
||||
</I>
|
||||
Actually, a full build is surprisingly fast these days. Also, you can
|
||||
work around this problem by cd'ing into the directory of the changed
|
||||
addin before issuing the "make" command.
|
||||
|
||||
><i> However Mike is right in that with proper dependency checking the
|
||||
</I>><i> makefiles would be more correct and would avoid weird build errors when
|
||||
</I>><i> there are changes in the api.
|
||||
</I>
|
||||
I think this would be a really good idea, as we've had a number of
|
||||
breakages resulting from the lack of proper dependencies. I've
|
||||
actually added dependencies to a couple of addins already.
|
||||
|
||||
><i> So I'd like to know what you think about this. I suggested making this
|
||||
</I>><i> project dependency optional, although I don't know how hard it would be.
|
||||
</I>
|
||||
I don't think it's necessary. Maybe we could make it more convenient
|
||||
by having make targets corresponding to the core areas e.g. make
|
||||
md-project-gui would execute make in
|
||||
main/src/core/MonoDevelop.Project.Gui.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#78">[ date ]</a>
|
||||
<a href="thread.html#78">[ thread ]</a>
|
||||
<a href="subject.html#78">[ subject ]</a>
|
||||
<a href="author.html#78">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,89 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=aec34c770811171719u2a3c4bafs93d5b93ce5b38850%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000078.html">
|
||||
<LINK REL="Next" HREF="000081.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Mike Kestner</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=aec34c770811171719u2a3c4bafs93d5b93ce5b38850%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">mkestner at gmail.com
|
||||
</A><BR>
|
||||
<I>Mon Nov 17 21:37:42 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#79">[ date ]</a>
|
||||
<a href="thread.html#79">[ thread ]</a>
|
||||
<a href="subject.html#79">[ subject ]</a>
|
||||
<a href="author.html#79">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Mon, 2008-11-17 at 20:19 -0500, Michael Hutchinson wrote:
|
||||
|
||||
><i> > However Mike is right in that with proper dependency checking the
|
||||
</I>><i> > makefiles would be more correct and would avoid weird build errors when
|
||||
</I>><i> > there are changes in the api.
|
||||
</I>><i>
|
||||
</I>><i> I think this would be a really good idea, as we've had a number of
|
||||
</I>><i> breakages resulting from the lack of proper dependencies. I've
|
||||
</I>><i> actually added dependencies to a couple of addins already.
|
||||
</I>
|
||||
There's potentially a larger issue, in that the MD makefiles are
|
||||
synchronized by MD itself, so the functionality which does this sync
|
||||
apparently does not currently support robust dependency checking for its
|
||||
output. Regardless of whether the MD project wants to have robust
|
||||
dependency checking for project references, I suspect many of our users
|
||||
will want it.
|
||||
|
||||
><i> > So I'd like to know what you think about this. I suggested making this
|
||||
</I>><i> > project dependency optional, although I don't know how hard it would be.
|
||||
</I>><i>
|
||||
</I>><i> I don't think it's necessary. Maybe we could make it more convenient
|
||||
</I>><i> by having make targets corresponding to the core areas e.g. make
|
||||
</I>><i> md-project-gui would execute make in
|
||||
</I>><i> main/src/core/MonoDevelop.Project.Gui.
|
||||
</I>
|
||||
If the feature is optional, I think it should probably be on by default,
|
||||
because most people will expect a change in a project to rebuild
|
||||
projects which depend on it.
|
||||
|
||||
--
|
||||
Mike Kestner <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkestner at gmail.com</A>>
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#79">[ date ]</a>
|
||||
<a href="thread.html#79">[ thread ]</a>
|
||||
<a href="subject.html#79">[ subject ]</a>
|
||||
<a href="author.html#79">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,78 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%20MD%27s%0A%09makefiles&In-Reply-To=1226964636.4215.61.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000083.html">
|
||||
<LINK REL="Next" HREF="000084.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Levi Bard</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%20MD%27s%0A%09makefiles&In-Reply-To=1226964636.4215.61.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">taktaktaktaktaktaktaktaktaktak at gmail.com
|
||||
</A><BR>
|
||||
<I>Tue Nov 18 09:00:04 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#80">[ date ]</a>
|
||||
<a href="thread.html#80">[ thread ]</a>
|
||||
<a href="subject.html#80">[ subject ]</a>
|
||||
<a href="author.html#80">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>><i> I've discussed with Mike (Kestner) a couple of times about the need for
|
||||
</I>><i> proper dependency checks between the MD makefiles. That is, a change in
|
||||
</I>><i> one of the MD projects would cause all dependent projects to be
|
||||
</I>><i> rebuilt.
|
||||
</I>
|
||||
This would be a Good Thing.
|
||||
|
||||
><i> I'm reluctant to do this change because any small change (even if not
|
||||
</I>><i> breaking change) in one of the core MD assemblies would cause the
|
||||
</I>><i> rebuild of all the 50 assemblies of MD, and that would be really
|
||||
</I>><i> annoying for those who work daily on those assemblies.
|
||||
</I>
|
||||
I agree with Michael H. that this isn't really a big deal.
|
||||
|
||||
|
||||
--
|
||||
<A HREF="http://homes.eff.org/~barlow/EconomyOfIdeas.html">http://homes.eff.org/~barlow/EconomyOfIdeas.html</A>
|
||||
<A HREF="http://www.dreamsongs.com/MobSoftware.html">http://www.dreamsongs.com/MobSoftware.html</A>
|
||||
<A HREF="http://www.gnu.org/philosophy/shouldbefree.html">http://www.gnu.org/philosophy/shouldbefree.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#80">[ date ]</a>
|
||||
<a href="thread.html#80">[ thread ]</a>
|
||||
<a href="subject.html#80">[ subject ]</a>
|
||||
<a href="author.html#80">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,97 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=1226975862.21959.45.camel%40linux-wpou.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000079.html">
|
||||
<LINK REL="Next" HREF="000082.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=1226975862.21959.45.camel%40linux-wpou.site"
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Tue Nov 18 09:54:09 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#81">[ date ]</a>
|
||||
<a href="thread.html#81">[ thread ]</a>
|
||||
<a href="subject.html#81">[ subject ]</a>
|
||||
<a href="author.html#81">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dl 17 de 11 de 2008 a les 20:37 -0600, en/na Mike Kestner va
|
||||
escriure:
|
||||
><i> On Mon, 2008-11-17 at 20:19 -0500, Michael Hutchinson wrote:
|
||||
</I>><i>
|
||||
</I>><i> > > However Mike is right in that with proper dependency checking the
|
||||
</I>><i> > > makefiles would be more correct and would avoid weird build errors when
|
||||
</I>><i> > > there are changes in the api.
|
||||
</I>><i> >
|
||||
</I>><i> > I think this would be a really good idea, as we've had a number of
|
||||
</I>><i> > breakages resulting from the lack of proper dependencies. I've
|
||||
</I>><i> > actually added dependencies to a couple of addins already.
|
||||
</I>><i>
|
||||
</I>><i> There's potentially a larger issue, in that the MD makefiles are
|
||||
</I>><i> synchronized by MD itself, so the functionality which does this sync
|
||||
</I>><i> apparently does not currently support robust dependency checking for its
|
||||
</I>><i> output. Regardless of whether the MD project wants to have robust
|
||||
</I>><i> dependency checking for project references, I suspect many of our users
|
||||
</I>><i> will want it.
|
||||
</I>
|
||||
No, that's unrelated. Makefile synchronization just keeps in sync lists
|
||||
of files and references, but it does not decide what to do with those.
|
||||
That's up to the makefile.
|
||||
|
||||
><i>
|
||||
</I>><i> > > So I'd like to know what you think about this. I suggested making this
|
||||
</I>><i> > > project dependency optional, although I don't know how hard it would be.
|
||||
</I>><i> >
|
||||
</I>><i> > I don't think it's necessary. Maybe we could make it more convenient
|
||||
</I>><i> > by having make targets corresponding to the core areas e.g. make
|
||||
</I>><i> > md-project-gui would execute make in
|
||||
</I>><i> > main/src/core/MonoDevelop.Project.Gui.
|
||||
</I>><i>
|
||||
</I>><i> If the feature is optional, I think it should probably be on by default,
|
||||
</I>><i> because most people will expect a change in a project to rebuild
|
||||
</I>><i> projects which depend on it.
|
||||
</I>
|
||||
That's ok to me, go ahead.
|
||||
|
||||
Lluis.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#81">[ date ]</a>
|
||||
<a href="thread.html#81">[ thread ]</a>
|
||||
<a href="subject.html#81">[ subject ]</a>
|
||||
<a href="author.html#81">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,79 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=1227020049.4215.77.camel%40portador.aticatac-centre">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000081.html">
|
||||
<LINK REL="Next" HREF="000083.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Mike Kestner</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=1227020049.4215.77.camel%40portador.aticatac-centre"
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">mkestner at gmail.com
|
||||
</A><BR>
|
||||
<I>Tue Nov 18 10:18:06 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#82">[ date ]</a>
|
||||
<a href="thread.html#82">[ thread ]</a>
|
||||
<a href="subject.html#82">[ subject ]</a>
|
||||
<a href="author.html#82">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Tue, 2008-11-18 at 09:54 -0500, Lluis Sanchez Gual wrote:
|
||||
><i>
|
||||
</I>><i> > There's potentially a larger issue, in that the MD makefiles are
|
||||
</I>><i> > synchronized by MD itself, so the functionality which does this sync
|
||||
</I>><i> > apparently does not currently support robust dependency checking for its
|
||||
</I>><i> > output. Regardless of whether the MD project wants to have robust
|
||||
</I>><i> > dependency checking for project references, I suspect many of our users
|
||||
</I>><i> > will want it.
|
||||
</I>><i>
|
||||
</I>><i> No, that's unrelated. Makefile synchronization just keeps in sync lists
|
||||
</I>><i> of files and references, but it does not decide what to do with those.
|
||||
</I>><i> That's up to the makefile.
|
||||
</I>
|
||||
So the sync code doesn't create make targets for project assemblies?
|
||||
And it doesn't update those targets at all after they are created?
|
||||
That's surprising to me. I thought we could create a valid Makefile for
|
||||
a project from scratch. I also thought we created distribution tarballs
|
||||
which had automake based build systems. All of the above scenarios
|
||||
would require make target dependency handling for project references.
|
||||
|
||||
--
|
||||
Mike Kestner <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">mkestner at gmail.com</A>>
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#82">[ date ]</a>
|
||||
<a href="thread.html#82">[ thread ]</a>
|
||||
<a href="subject.html#82">[ subject ]</a>
|
||||
<a href="author.html#82">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,114 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=1227021486.21959.50.camel%40linux-wpou.site">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000082.html">
|
||||
<LINK REL="Next" HREF="000080.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Adding project build dependencies in MD's makefiles</H1>
|
||||
<B>Lluis Sanchez Gual</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Adding%20project%20build%20dependencies%20in%0A%09MD%27s%09makefiles&In-Reply-To=1227021486.21959.50.camel%40linux-wpou.site"
|
||||
TITLE="[Monodevelop-devel] Adding project build dependencies in MD's makefiles">lluis at novell.com
|
||||
</A><BR>
|
||||
<I>Tue Nov 18 11:40:39 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#83">[ date ]</a>
|
||||
<a href="thread.html#83">[ thread ]</a>
|
||||
<a href="subject.html#83">[ subject ]</a>
|
||||
<a href="author.html#83">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>El dt 18 de 11 de 2008 a les 09:18 -0600, en/na Mike Kestner va
|
||||
escriure:
|
||||
><i> On Tue, 2008-11-18 at 09:54 -0500, Lluis Sanchez Gual wrote:
|
||||
</I>><i> >
|
||||
</I>><i> > > There's potentially a larger issue, in that the MD makefiles are
|
||||
</I>><i> > > synchronized by MD itself, so the functionality which does this sync
|
||||
</I>><i> > > apparently does not currently support robust dependency checking for its
|
||||
</I>><i> > > output. Regardless of whether the MD project wants to have robust
|
||||
</I>><i> > > dependency checking for project references, I suspect many of our users
|
||||
</I>><i> > > will want it.
|
||||
</I>><i> >
|
||||
</I>><i> > No, that's unrelated. Makefile synchronization just keeps in sync lists
|
||||
</I>><i> > of files and references, but it does not decide what to do with those.
|
||||
</I>><i> > That's up to the makefile.
|
||||
</I>><i>
|
||||
</I>><i> So the sync code doesn't create make targets for project assemblies?
|
||||
</I>><i> And it doesn't update those targets at all after they are created?
|
||||
</I>
|
||||
Nope.
|
||||
|
||||
><i> That's surprising to me. I thought we could create a valid Makefile for
|
||||
</I>><i> a project from scratch. I also thought we created distribution tarballs
|
||||
</I>><i> which had automake based build systems. All of the above scenarios
|
||||
</I>><i> would require make target dependency handling for project references.
|
||||
</I>><i>
|
||||
</I>
|
||||
We do support that, but it is a different feature.
|
||||
|
||||
On one hand, we have a Makefile Generator. This generator takes a
|
||||
solution and generates a set of makefiles and configuration files that
|
||||
can be used to build the project. The generated build system can
|
||||
optionally be based on Autotools. Notice that every time the makefiles
|
||||
are generated, the previous ones are overwritten. The makefiles it
|
||||
generates are good enough for the projects you can create with MD, but
|
||||
they can fall short for complex projects with more complex build system
|
||||
needs (but still, the generated makefiles can be a good starting point
|
||||
for those projects). The makefile generator is also used by the
|
||||
packaging add-in, when you create a Tarball package.
|
||||
|
||||
In MD, we have used the generator in the past to generate some of the
|
||||
makefiles in 'extras', which have later been modified and improved. We
|
||||
can certainly improve the generator to support project dependencies.
|
||||
|
||||
On the other hand there is the Makefile Synchronization feature. Using
|
||||
this feature, you can sync the file and references list of a project
|
||||
with a makefile. But it is just a matter of updating lists. What the
|
||||
makefile does with those lists is up to the makefile, and the
|
||||
synchronizer just doesn't care. So you can have arbitrarily complex
|
||||
makefiles, but still keep them synchronized with MD projects. You can of
|
||||
course generate makefiles with the Generator, and then enable
|
||||
synchronization.
|
||||
|
||||
In MD, we are using the makefile synchronizer to keep the makefiles up
|
||||
to date. However, if we want to support project dependencies we have to
|
||||
fix the makefiles, not the synchronizer.
|
||||
|
||||
I hope this clarifies things a bit.
|
||||
Lluis.
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#83">[ date ]</a>
|
||||
<a href="thread.html#83">[ thread ]</a>
|
||||
<a href="subject.html#83">[ subject ]</a>
|
||||
<a href="author.html#83">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,71 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20ViMode%20-%20patches%20in%20bugzilla&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000080.html">
|
||||
<LINK REL="Next" HREF="000085.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] ViMode - patches in bugzilla</H1>
|
||||
<B>Grzegorz Sobanski</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20ViMode%20-%20patches%20in%20bugzilla&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] ViMode - patches in bugzilla">grzegorz.sobanski at cs.put.poznan.pl
|
||||
</A><BR>
|
||||
<I>Wed Nov 26 08:43:15 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#84">[ date ]</a>
|
||||
<a href="thread.html#84">[ thread ]</a>
|
||||
<a href="subject.html#84">[ subject ]</a>
|
||||
<a href="author.html#84">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hi.
|
||||
|
||||
I put some patches to Vi mode in bugzilla, and will probably have some
|
||||
more in following days.
|
||||
|
||||
So I have a question - I have choosen the text editor component, so they
|
||||
are assigned to Mike Krueger, but afaik he is not responsible for vimode
|
||||
at all.
|
||||
Should I assign new patches to someone?
|
||||
Or maybe leave general monodevelop-bugs@?
|
||||
|
||||
|
||||
--
|
||||
silk
|
||||
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#84">[ date ]</a>
|
||||
<a href="thread.html#84">[ thread ]</a>
|
||||
<a href="subject.html#84">[ subject ]</a>
|
||||
<a href="author.html#84">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,74 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20ViMode%20-%20patches%20in%20bugzilla&In-Reply-To=492D5273.7020200%40cs.put.poznan.pl">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000084.html">
|
||||
<LINK REL="Next" HREF="000086.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] ViMode - patches in bugzilla</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20ViMode%20-%20patches%20in%20bugzilla&In-Reply-To=492D5273.7020200%40cs.put.poznan.pl"
|
||||
TITLE="[Monodevelop-devel] ViMode - patches in bugzilla">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 26 14:05:21 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#85">[ date ]</a>
|
||||
<a href="thread.html#85">[ thread ]</a>
|
||||
<a href="subject.html#85">[ subject ]</a>
|
||||
<a href="author.html#85">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Wed, Nov 26, 2008 at 8:43 AM, Grzegorz Sobanski
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">grzegorz.sobanski at cs.put.poznan.pl</A>> wrote:
|
||||
><i> Hi.
|
||||
</I>><i>
|
||||
</I>><i> I put some patches to Vi mode in bugzilla, and will probably have some
|
||||
</I>><i> more in following days.
|
||||
</I>><i>
|
||||
</I>><i> So I have a question - I have choosen the text editor component, so they
|
||||
</I>><i> are assigned to Mike Krueger, but afaik he is not responsible for vimode
|
||||
</I>><i> at all.
|
||||
</I>><i> Should I assign new patches to someone?
|
||||
</I>><i> Or maybe leave general monodevelop-bugs@?
|
||||
</I>
|
||||
Please assign them to me, mhutchinson at novell.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#85">[ date ]</a>
|
||||
<a href="thread.html#85">[ thread ]</a>
|
||||
<a href="subject.html#85">[ subject ]</a>
|
||||
<a href="author.html#85">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,85 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] MD Gendarme Addin
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20MD%20Gendarme%20Addin&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000085.html">
|
||||
<LINK REL="Next" HREF="000087.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] MD Gendarme Addin</H1>
|
||||
<B>Luciano _</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20MD%20Gendarme%20Addin&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] MD Gendarme Addin">lnc19 at hotmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 26 16:02:41 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#86">[ date ]</a>
|
||||
<a href="thread.html#86">[ thread ]</a>
|
||||
<a href="subject.html#86">[ subject ]</a>
|
||||
<a href="author.html#86">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>
|
||||
HI All:
|
||||
I was talking to Michael and i will try to start the MonoDevelop Gendarme addin.
|
||||
I have some affirmations/questions, Based on Michael post [*], that i need to clarify, any help will be helpfull.
|
||||
|
||||
1) I use Gendarme with System.Diagnostic.Process to not depend on it.
|
||||
2) I have to make a widget/dialog to setup Rules.xml file with all the futures: Rules sets, ignore rules, Severity levels, etc.
|
||||
3) User must jump to the offending code line/file and an explanation of the fault: This is the hard part, i will try to save log file, an parse it, any other way? (Parse html could be another way, but i think is harder than log file). I didn't see the log file, i didn't know if my approach is correct.
|
||||
4) I will use One rules.xml file per solution/target (Solution & Debug/Release/Test/etc)
|
||||
5) Allow to check the rules before checking to VCS.
|
||||
6) Use the MD Code DOM to find things not listed in MDB files. What is this?
|
||||
7) Add the Gendarme configuration file to the project.
|
||||
8) Warning message of gendarme result could it be shown in Construction Pad, as "Wanings".
|
||||
|
||||
|
||||
Thanks
|
||||
Lucian0
|
||||
|
||||
My english isn't my best skill :) So, sorry if i've some errors.
|
||||
|
||||
[*] <A HREF="http://groups.google.com/group/gendarme/browse_thread/thread/eba0f7b881926ab0/158fdf10b9d58998">http://groups.google.com/group/gendarme/browse_thread/thread/eba0f7b881926ab0/158fdf10b9d58998</A>
|
||||
|
||||
|
||||
_________________________________________________________________
|
||||
Stay up to date on your PC, the Web, and your mobile phone with Windows Live
|
||||
<A HREF="http://clk.atdmt.com/MRT/go/119462413/direct/01/">http://clk.atdmt.com/MRT/go/119462413/direct/01/</A>
|
||||
-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081126/9427f746/attachment.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081126/9427f746/attachment.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#86">[ date ]</a>
|
||||
<a href="thread.html#86">[ thread ]</a>
|
||||
<a href="subject.html#86">[ subject ]</a>
|
||||
<a href="author.html#86">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,109 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] MD Gendarme Addin
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20MD%20Gendarme%20Addin&In-Reply-To=BAY142-W11DD3BEECF3AE872350DCCA60A0%40phx.gbl">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000086.html">
|
||||
<LINK REL="Next" HREF="000088.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] MD Gendarme Addin</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20MD%20Gendarme%20Addin&In-Reply-To=BAY142-W11DD3BEECF3AE872350DCCA60A0%40phx.gbl"
|
||||
TITLE="[Monodevelop-devel] MD Gendarme Addin">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 26 18:17:03 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#87">[ date ]</a>
|
||||
<a href="thread.html#87">[ thread ]</a>
|
||||
<a href="subject.html#87">[ subject ]</a>
|
||||
<a href="author.html#87">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Wed, Nov 26, 2008 at 4:02 PM, Luciano _ <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lnc19 at hotmail.com</A>> wrote:
|
||||
><i> HI All:
|
||||
</I>><i> I was talking to Michael and i will try to start the MonoDevelop Gendarme
|
||||
</I>><i> addin.
|
||||
</I>><i> I have some affirmations/questions, Based on Michael post [*], that i need
|
||||
</I>><i> to clarify, any help will be helpfull.
|
||||
</I>><i>
|
||||
</I>><i> 1) I use Gendarme with System.Diagnostic.Process to not depend on it.
|
||||
</I>
|
||||
Yup, it'll need to run gendarme to produce an xml file in the output
|
||||
directory, then read in the XML. The Smokey code analysis addin
|
||||
already does this, so that code might be a good starting point.
|
||||
|
||||
This is the main priority IMO.
|
||||
|
||||
><i> 2) I have to make a widget/dialog to setup Rules.xml file with all the
|
||||
</I>><i> futures: Rules sets, ignore rules, Severity levels, etc.
|
||||
</I>
|
||||
See #4.
|
||||
|
||||
><i> 3) User must jump to the offending code line/file and an explanation of the
|
||||
</I>><i> fault: This is the hard part, i will try to save log file, an parse it, any
|
||||
</I>><i> other way? (Parse html could be another way, but i think is harder than log
|
||||
</I>><i> file). I didn't see the log file, i didn't know if my approach is correct.
|
||||
</I>
|
||||
There's the XML file, which should be very easy to load. The smokey
|
||||
addin does this.
|
||||
|
||||
><i> 4) I will use One rules.xml file per solution/target (Solution &
|
||||
</I>><i> Debug/Release/Test/etc)
|
||||
</I>
|
||||
I'm not sure how rule sets should apply to
|
||||
project/solutions/configurations, but this seems like a good model:
|
||||
<A HREF="http://blogs.msdn.com/fxcop/archive/2008/11/12/fun-with-code-analysis-rulesets.aspx">http://blogs.msdn.com/fxcop/archive/2008/11/12/fun-with-code-analysis-rulesets.aspx</A>
|
||||
|
||||
><i> 5) Allow to check the rules before checking to VCS.
|
||||
</I>><i> 6) Use the MD Code DOM to find things not listed in MDB files. What is this?
|
||||
</I>
|
||||
Some analyses might report an error in a member, without having a
|
||||
location. MD has an internal type database with lots of line/col/file
|
||||
information so this could be a good fallback. Very low priority
|
||||
anyway, so don't worry about it :)
|
||||
|
||||
><i> 7) Add the Gendarme configuration file to the project.
|
||||
</I>><i> 8) Warning message of gendarme result could it be shown in Construction Pad,
|
||||
</I>><i> as "Wanings".
|
||||
</I>
|
||||
It's debatable exactly how gendarme severity should map to
|
||||
error/warnings in the errors pad.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#87">[ date ]</a>
|
||||
<a href="thread.html#87">[ thread ]</a>
|
||||
<a href="subject.html#87">[ subject ]</a>
|
||||
<a href="author.html#87">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,209 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5Bgendarme%5D%20Re%3A%20%20MD%20Gendarme%20Addin&In-Reply-To=aec34c770811261517i6cdbe19aocd3e6b872d8452f1%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000087.html">
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin</H1>
|
||||
<B>Sebastien Pouliot</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20%5Bgendarme%5D%20Re%3A%20%20MD%20Gendarme%20Addin&In-Reply-To=aec34c770811261517i6cdbe19aocd3e6b872d8452f1%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin">sebastien at ximian.com
|
||||
</A><BR>
|
||||
<I>Wed Nov 26 21:02:33 EST 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#88">[ date ]</a>
|
||||
<a href="thread.html#88">[ thread ]</a>
|
||||
<a href="subject.html#88">[ subject ]</a>
|
||||
<a href="author.html#88">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Hello Luciano,
|
||||
|
||||
If you're not already I suggest you subscribe to
|
||||
<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">gendarme at googlegroups.com</A>
|
||||
|
||||
On Wed, 2008-11-26 at 18:17 -0500, Michael Hutchinson wrote:
|
||||
><i> On Wed, Nov 26, 2008 at 4:02 PM, Luciano _ <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">lnc19 at hotmail.com</A>> wrote:
|
||||
</I>><i> > HI All:
|
||||
</I>><i> > I was talking to Michael and i will try to start the MonoDevelop Gendarme
|
||||
</I>><i> > addin.
|
||||
</I>><i> > I have some affirmations/questions, Based on Michael post [*], that i need
|
||||
</I>><i> > to clarify, any help will be helpfull.
|
||||
</I>><i> >
|
||||
</I>><i> > 1) I use Gendarme with System.Diagnostic.Process to not depend on it.
|
||||
</I>><i>
|
||||
</I>><i> Yup, it'll need to run gendarme to produce an xml file in the output
|
||||
</I>><i> directory, then read in the XML. The Smokey code analysis addin
|
||||
</I>><i> already does this, so that code might be a good starting point.
|
||||
</I>
|
||||
Basically you can have:
|
||||
* one input XML file (optional, but it's how to configure everything);
|
||||
* a few parameters, like the assemblies being analyzed;
|
||||
* an ignore-list file (optional, but so useful); and
|
||||
* one output XML file.
|
||||
|
||||
><i> This is the main priority IMO.
|
||||
</I>><i>
|
||||
</I>><i> > 2) I have to make a widget/dialog to setup
|
||||
</I>
|
||||
Before setting up you'll need to know what to setup. This means you must
|
||||
be able to discover what is available (rules as a minimum, potentially
|
||||
configurable options later) to present them to the user.
|
||||
|
||||
Today different runners have different strategy. E.g. the console runner
|
||||
base itself on a file (the rules.xml file shipped w/Gendarme) while the
|
||||
wizard GUI runner inspects the rules assemblies to find the rules
|
||||
available. The addin needs is kind of in-between. In any case there's no
|
||||
need to link with the Gendarme binaries to get the information.
|
||||
|
||||
The other important feature IMO is to handle the "ignore-list", i.e.
|
||||
stuff you don't want to be warned about the next time you ask for your
|
||||
code to be analyzed. There should be a way to add to this list and a way
|
||||
to remove ignored stuff from it.
|
||||
|
||||
><i> Rules.xml file with all the
|
||||
</I>><i> > futures: Rules sets, ignore rules, Severity levels, etc.
|
||||
</I>
|
||||
Using an XML file you can*
|
||||
|
||||
(a) specify which rules are used (or not) during analysis;
|
||||
|
||||
(b) define different rule sets (inside the same XML file);
|
||||
|
||||
(c) set options on rules [1];
|
||||
|
||||
(d) set the applicability of each rule on:
|
||||
everything (the default on the console runner);
|
||||
code visible outside the assembly;
|
||||
code only visible inside the assembly;
|
||||
|
||||
* but you don't need to support all possible options in order to
|
||||
have a useful addin ;-)
|
||||
|
||||
What you cannot set in the XML file are filters on Severity and
|
||||
Confidence (i.e. filters on the defects) but you can specify them on the
|
||||
command-line (since Gendarme 2.2).
|
||||
|
||||
However it may be easier to filter defects later, i.e. not at analysis
|
||||
time, when you load the XML results (and that would work on Gendarme 2.0
|
||||
too). This would let users change filtering without re-analyzing the
|
||||
solution (or projects) which would be faster (since you would need to
|
||||
reload the results anyway).
|
||||
|
||||
><i> See #4.
|
||||
</I>><i>
|
||||
</I>><i> > 3) User must jump to the offending code line/file and an explanation of the
|
||||
</I>><i> > fault: This is the hard part, i will try to save log file, an parse it, any
|
||||
</I>><i> > other way? (Parse html could be another way, but i think is harder than log
|
||||
</I>><i> > file). I didn't see the log file, i didn't know if my approach is correct.
|
||||
</I>><i>
|
||||
</I>><i> There's the XML file, which should be very easy to load. The smokey
|
||||
</I>><i> addin does this.
|
||||
</I>
|
||||
You can use "--xml results.xml" to get the defects inside an XML file.
|
||||
The text and HTML formats would not only be harder to parse but also
|
||||
more likely to change too in future releases.
|
||||
|
||||
><i> > 4) I will use One rules.xml file per solution/target (Solution &
|
||||
</I>><i> > Debug/Release/Test/etc)
|
||||
</I>><i>
|
||||
</I>><i> I'm not sure how rule sets should apply to
|
||||
</I>><i> project/solutions/configurations, but this seems like a good model:
|
||||
</I>><i> <A HREF="http://blogs.msdn.com/fxcop/archive/2008/11/12/fun-with-code-analysis-rulesets.aspx">http://blogs.msdn.com/fxcop/archive/2008/11/12/fun-with-code-analysis-rulesets.aspx</A>
|
||||
</I>
|
||||
In VS.NET people generally defines a target for code analysis - i.e.
|
||||
where CODE_ANALYSIS is defined (you can see it inside the above link).
|
||||
This lets attributes, like [SuppressMessage], be compiled into the
|
||||
assemblies [2]. In the future it's likely people will want contracts to
|
||||
be part of the analysis (since it gives more clues about the code and
|
||||
rules are always hungry for clues).
|
||||
|
||||
I think people expects to be able to run analysis on both the solution
|
||||
and on specific projects. It's important to note that running the
|
||||
analysis on each projects will be a bit different (result wise) than
|
||||
running it on the solution. This is because some rules works on the set
|
||||
of assemblies being analyzed (so more assemblies, more complete the
|
||||
analysis can be and more potential defects can be found). IMO both
|
||||
options are valid (even if the solution-level analysis is more
|
||||
complete).
|
||||
|
||||
><i> > 5) Allow to check the rules before checking to VCS.
|
||||
</I>
|
||||
That's (quite) an advanced option - but something that you should keep
|
||||
in mind.
|
||||
|
||||
><i> > 6) Use the MD Code DOM to find things not listed in MDB files. What is this?
|
||||
</I>><i>
|
||||
</I>><i> Some analyses might report an error in a member, without having a
|
||||
</I>><i> location. MD has an internal type database with lots of line/col/file
|
||||
</I>><i> information so this could be a good fallback. Very low priority
|
||||
</I>><i> anyway, so don't worry about it :)
|
||||
</I>
|
||||
Yes, MDB has some limitations (e.g. fields, attributes) where no line
|
||||
information is available. Having a fallback, eventually, would be a nice
|
||||
addition.
|
||||
|
||||
><i> > 7) Add the Gendarme configuration file to the project.
|
||||
</I>><i> > 8) Warning message of gendarme result could it be shown in Construction Pad,
|
||||
</I>><i> > as "Wanings".
|
||||
</I>><i>
|
||||
</I>><i> It's debatable exactly how gendarme severity should map to
|
||||
</I>><i> error/warnings in the errors pad.
|
||||
</I>
|
||||
It's unlikely that people will want all of them mixed with compiler
|
||||
errors and warnings. You would be best to start with a separate view
|
||||
where filtering and sorting is possible.
|
||||
|
||||
Later you might want to give the options, for each rule, to act as an
|
||||
error, a warning or simply be shown in the code analysis view. That
|
||||
could be a great place to ask if some defects are "commit
|
||||
breakers" (point #5).
|
||||
|
||||
Don't hesitate to ask any questions (by email or on IRC).
|
||||
Sebastien
|
||||
|
||||
|
||||
[1] Right now the console runner use reflection to set options. Future
|
||||
versionS of Gendarme (planned for 2.4) will start using System.Component
|
||||
attributes to advertise rules options in a way that makes it easy to
|
||||
build an UI on top of it.
|
||||
|
||||
[2] The [SuppressMessage] attribute is not supported in current version
|
||||
of Gendarme - but the infrastructure is already in place (i.e. matching
|
||||
Gendarme and FxCop rules) to make this possible in the future.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A></li>
|
||||
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#88">[ date ]</a>
|
||||
<a href="thread.html#88">[ thread ]</a>
|
||||
<a href="subject.html#88">[ subject ]</a>
|
||||
<a href="author.html#88">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,207 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list November 2008 Archive by author</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>November 2008 Archives by author</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Wed Nov 5 05:11:08 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Messages:</b> 32<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="59"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="80"> </A>
|
||||
<I>Levi Bard
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="74"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="76"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="67"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="68"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="71"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="73"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="75"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="77"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="81"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="83"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="60"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A><A NAME="61"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="62"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="78"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="85"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="87"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="63"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="79"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="82"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="57"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="64"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="65"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="66"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="69"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="70"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="72"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A><A NAME="88"> </A>
|
||||
<I>Sebastien Pouliot
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="84"> </A>
|
||||
<I>Grzegorz Sobanski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="58"> </A>
|
||||
<I>Rafael Teixeira
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="86"> </A>
|
||||
<I>Luciano _
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Wed Nov 26 21:11:34 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,207 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list November 2008 Archive by date</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>November 2008 Archives by date</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Wed Nov 5 05:11:08 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Messages:</b> 32<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="57"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="58"> </A>
|
||||
<I>Rafael Teixeira
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="59"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="60"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A><A NAME="61"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="62"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="63"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="67"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="64"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="65"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="66"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="68"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="69"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="70"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="71"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="72"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="73"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="74"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="75"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="76"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="77"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="78"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="79"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="80"> </A>
|
||||
<I>Levi Bard
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="81"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="82"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="83"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="84"> </A>
|
||||
<I>Grzegorz Sobanski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="85"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="86"> </A>
|
||||
<I>Luciano _
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="87"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A><A NAME="88"> </A>
|
||||
<I>Sebastien Pouliot
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Wed Nov 26 21:11:34 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,271 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list November 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>November 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Wed Nov 5 05:11:08 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Messages:</b> 32<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01225879868- -->
|
||||
<LI><A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="57"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01225879868-01225889366- -->
|
||||
<LI><A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="58"> </A>
|
||||
<I>Rafael Teixeira
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225889366-01225956773- -->
|
||||
<LI><A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="66"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--1 01225879868-01225897961- -->
|
||||
<LI><A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="59"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225897961-01225955510- -->
|
||||
<LI><A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="64"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--1 01225879868-01225920751- -->
|
||||
<LI><A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="60"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225920751-01225956026- -->
|
||||
<LI><A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="65"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--1 01225879868-01225987760- -->
|
||||
<LI><A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="68"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225987760-01226043707- -->
|
||||
<LI><A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="69"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<!--2 01225879868-01225987760-01226046667- -->
|
||||
<LI><A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="70"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01225879868-01225987760-01226046667-01226074642- -->
|
||||
<LI><A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="71"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--3 01225879868-01225987760-01226046667-01226074642-01226303609- -->
|
||||
<LI><A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="72"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<!--3 01225879868-01225987760-01226046667-01226074642-01226303609-01226419429- -->
|
||||
<LI><A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="73"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01225933681- -->
|
||||
<LI><A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A><A NAME="61"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<!--0 01225938042- -->
|
||||
<LI><A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="62"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01225938042-01225941087- -->
|
||||
<LI><A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="63"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225938042-01225941087-01225944992- -->
|
||||
<LI><A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="67"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01226933409- -->
|
||||
<LI><A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="74"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01226933409-01226934819- -->
|
||||
<LI><A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="75"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01226933409-01226934819-01226939471- -->
|
||||
<LI><A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="76"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01226964636- -->
|
||||
<LI><A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="77"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01226964636-01226971183- -->
|
||||
<LI><A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="78"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01226964636-01226971183-01226975862- -->
|
||||
<LI><A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="79"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01226964636-01226971183-01226975862-01227020049- -->
|
||||
<LI><A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="81"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--3 01226964636-01226971183-01226975862-01227020049-01227021486- -->
|
||||
<LI><A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="82"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<!--3 01226964636-01226971183-01226975862-01227020049-01227021486-01227026439- -->
|
||||
<LI><A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="83"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
<!--1 01226964636-01227016804- -->
|
||||
<LI><A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="80"> </A>
|
||||
<I>Levi Bard
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01227706995- -->
|
||||
<LI><A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="84"> </A>
|
||||
<I>Grzegorz Sobanski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01227706995-01227726321- -->
|
||||
<LI><A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="85"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01227733361- -->
|
||||
<LI><A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="86"> </A>
|
||||
<I>Luciano _
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01227733361-01227741423- -->
|
||||
<LI><A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="87"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01227733361-01227741423-01227751353- -->
|
||||
<LI><A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A><A NAME="88"> </A>
|
||||
<I>Sebastien Pouliot
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Wed Nov 26 21:11:34 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,207 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list November 2008 Archive by subject</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>November 2008 Archives by subject</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Wed Nov 5 05:11:08 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Messages:</b> 32<p>
|
||||
<ul>
|
||||
|
||||
<LI><A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A><A NAME="88"> </A>
|
||||
<I>Sebastien Pouliot
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="79"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="81"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="82"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="83"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="77"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="78"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="80"> </A>
|
||||
<I>Levi Bard
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="62"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="63"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="67"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A><A NAME="61"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="75"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="76"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="74"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="57"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="58"> </A>
|
||||
<I>Rafael Teixeira
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="59"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="60"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="64"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="65"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="66"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="68"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="69"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="70"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="71"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="72"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="73"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="86"> </A>
|
||||
<I>Luciano _
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="87"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="84"> </A>
|
||||
<I>Grzegorz Sobanski
|
||||
</I>
|
||||
|
||||
<LI><A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="85"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Wed Nov 26 21:11:34 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
<a href="thread.html#start">[ thread ]</a>
|
||||
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,271 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<title>The Monodevelop-devel-list November 2008 Archive by thread</title>
|
||||
<META NAME="robots" CONTENT="noindex,follow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<a name="start"></A>
|
||||
<h1>November 2008 Archives by thread</h1>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p><b>Starting:</b> <i>Wed Nov 5 05:11:08 EST 2008</i><br>
|
||||
<b>Ending:</b> <i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Messages:</b> 32<p>
|
||||
<ul>
|
||||
|
||||
<!--0 01225879868- -->
|
||||
<LI><A HREF="000057.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="57"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01225879868-01225889366- -->
|
||||
<LI><A HREF="000058.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="58"> </A>
|
||||
<I>Rafael Teixeira
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225889366-01225956773- -->
|
||||
<LI><A HREF="000066.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="66"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--1 01225879868-01225897961- -->
|
||||
<LI><A HREF="000059.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="59"> </A>
|
||||
<I>"Andrés G. Aragoneses"
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225897961-01225955510- -->
|
||||
<LI><A HREF="000064.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="64"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--1 01225879868-01225920751- -->
|
||||
<LI><A HREF="000060.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="60"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225920751-01225956026- -->
|
||||
<LI><A HREF="000065.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="65"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--1 01225879868-01225987760- -->
|
||||
<LI><A HREF="000068.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="68"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225879868-01225987760-01226043707- -->
|
||||
<LI><A HREF="000069.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="69"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<!--2 01225879868-01225987760-01226046667- -->
|
||||
<LI><A HREF="000070.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="70"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01225879868-01225987760-01226046667-01226074642- -->
|
||||
<LI><A HREF="000071.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="71"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--3 01225879868-01225987760-01226046667-01226074642-01226303609- -->
|
||||
<LI><A HREF="000072.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="72"> </A>
|
||||
<I>Mike Krüger
|
||||
</I>
|
||||
|
||||
<!--3 01225879868-01225987760-01226046667-01226074642-01226303609-01226419429- -->
|
||||
<LI><A HREF="000073.html">[Monodevelop-devel] Improving refactoring after 2.0
|
||||
</A><A NAME="73"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01225933681- -->
|
||||
<LI><A HREF="000061.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A><A NAME="61"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<!--0 01225938042- -->
|
||||
<LI><A HREF="000062.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="62"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01225938042-01225941087- -->
|
||||
<LI><A HREF="000063.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="63"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01225938042-01225941087-01225944992- -->
|
||||
<LI><A HREF="000067.html">[Monodevelop-devel] Automagic settings upgrade dilemma
|
||||
</A><A NAME="67"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01226933409- -->
|
||||
<LI><A HREF="000074.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="74"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01226933409-01226934819- -->
|
||||
<LI><A HREF="000075.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="75"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01226933409-01226934819-01226939471- -->
|
||||
<LI><A HREF="000076.html">[Monodevelop-devel] Comipiling Monodevelop under Debian from trunk
|
||||
</A><A NAME="76"> </A>
|
||||
<I>Alexander M. Batishchev
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
<!--0 01226964636- -->
|
||||
<LI><A HREF="000077.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="77"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01226964636-01226971183- -->
|
||||
<LI><A HREF="000078.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="78"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01226964636-01226971183-01226975862- -->
|
||||
<LI><A HREF="000079.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="79"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--3 01226964636-01226971183-01226975862-01227020049- -->
|
||||
<LI><A HREF="000081.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="81"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
<!--3 01226964636-01226971183-01226975862-01227020049-01227021486- -->
|
||||
<LI><A HREF="000082.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="82"> </A>
|
||||
<I>Mike Kestner
|
||||
</I>
|
||||
|
||||
<!--3 01226964636-01226971183-01226975862-01227020049-01227021486-01227026439- -->
|
||||
<LI><A HREF="000083.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="83"> </A>
|
||||
<I>Lluis Sanchez Gual
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
<!--1 01226964636-01227016804- -->
|
||||
<LI><A HREF="000080.html">[Monodevelop-devel] Adding project build dependencies in MD's makefiles
|
||||
</A><A NAME="80"> </A>
|
||||
<I>Levi Bard
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01227706995- -->
|
||||
<LI><A HREF="000084.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="84"> </A>
|
||||
<I>Grzegorz Sobanski
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01227706995-01227726321- -->
|
||||
<LI><A HREF="000085.html">[Monodevelop-devel] ViMode - patches in bugzilla
|
||||
</A><A NAME="85"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
<!--0 01227733361- -->
|
||||
<LI><A HREF="000086.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="86"> </A>
|
||||
<I>Luciano _
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--1 01227733361-01227741423- -->
|
||||
<LI><A HREF="000087.html">[Monodevelop-devel] MD Gendarme Addin
|
||||
</A><A NAME="87"> </A>
|
||||
<I>Michael Hutchinson
|
||||
</I>
|
||||
|
||||
<UL>
|
||||
<!--2 01227733361-01227741423-01227751353- -->
|
||||
<LI><A HREF="000088.html">[Monodevelop-devel] [gendarme] Re: MD Gendarme Addin
|
||||
</A><A NAME="88"> </A>
|
||||
<I>Sebastien Pouliot
|
||||
</I>
|
||||
|
||||
</UL>
|
||||
</UL>
|
||||
</ul>
|
||||
<p>
|
||||
<a name="end"><b>Last message date:</b></a>
|
||||
<i>Wed Nov 26 21:02:33 EST 2008</i><br>
|
||||
<b>Archived on:</b> <i>Wed Nov 26 21:11:34 EST 2008</i>
|
||||
<p>
|
||||
<ul>
|
||||
<li> <b>Messages sorted by:</b>
|
||||
|
||||
<a href="subject.html#start">[ subject ]</a>
|
||||
<a href="author.html#start">[ author ]</a>
|
||||
<a href="date.html#start">[ date ]</a>
|
||||
<li><b><a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More info on this list...
|
||||
</a></b></li>
|
||||
</ul>
|
||||
<p>
|
||||
<hr>
|
||||
<i>This archive was generated by
|
||||
Pipermail 0.09 (Mailman edition).</i>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -0,0 +1,147 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Parser Overview
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=6d4a25b10809301159w52dfd680v3db2a3501a542a39%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
|
||||
<LINK REL="Next" HREF="000048.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Parser Overview</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=6d4a25b10809301159w52dfd680v3db2a3501a542a39%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Parser Overview">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Oct 1 03:18:47 EDT 2008</I>
|
||||
<P><UL>
|
||||
|
||||
<LI>Next message: <A HREF="000048.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#47">[ date ]</a>
|
||||
<a href="thread.html#47">[ thread ]</a>
|
||||
<a href="subject.html#47">[ subject ]</a>
|
||||
<a href="author.html#47">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>With your help, I was able to get this moving somewhat.
|
||||
|
||||
As an addin, this needs a lot of work. But it currently supports:
|
||||
|
||||
- Python project type
|
||||
- Project and file template
|
||||
- Pluggable python runtimes (cPython2.5 only currently. this will change
|
||||
after i get the ui components added)
|
||||
- Precompiling of python modules (either .pyc or .pyo for optimized)
|
||||
- Code folding for functions/comments/classes
|
||||
- Really basic completion that I will be adding to over the next few
|
||||
nights (basically until its usable for myself daily)
|
||||
- Parsing of python code is done via a subprocess to a long running
|
||||
python process. This allows for building a real AST using the "compiler"
|
||||
module.
|
||||
|
||||
and the obligatory screenshot
|
||||
|
||||
<A HREF="http://audidude.com/dropbox/monodevelop-python.png">http://audidude.com/dropbox/monodevelop-python.png</A>
|
||||
|
||||
Cheers!
|
||||
|
||||
-- Christian
|
||||
|
||||
On Tue, Sep 30, 2008 at 11:59 AM, Christian Hergert <
|
||||
<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
|
||||
><i> While I think its a worthy idea to remove the tight coupling to .NET logic,
|
||||
</I>><i> I'm not going to volunteer to do it. I'll work around it for the time being
|
||||
</I>><i> and it seems like a notable post-2.0 feature.
|
||||
</I>><i>
|
||||
</I>><i> -- Christian
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> On Mon, Sep 29, 2008 at 9:59 PM, Michael Hutchinson <
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">m.j.hutchinson at gmail.com</A>> wrote:
|
||||
</I>><i>
|
||||
</I>>><i> Hi,
|
||||
</I>>><i>
|
||||
</I>>><i> > On Mon, Sep 29, 2008 at 3:38 PM, Christian Hergert
|
||||
</I>>><i> > <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>>><i> >>
|
||||
</I>>><i> >> I have a class that extends ParsedDocument. Do references inside that
|
||||
</I>>><i> >> class get persisted to the parser database? Or is this perhaps
|
||||
</I>>><i> something
|
||||
</I>>><i> >> that i should have encapsulated in an ICompilationUnit.
|
||||
</I>>><i>
|
||||
</I>>><i> I /think/ any fields of objects that are [Serializable] will get
|
||||
</I>>><i> persisted, which includes all the collections that the base
|
||||
</I>>><i> ParsedDocument has.
|
||||
</I>>><i>
|
||||
</I>>><i> On Mon, Sep 29, 2008 at 7:29 PM, Christian Hergert
|
||||
</I>>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>>><i> > Ok, so after some further exploration, I think I understand the
|
||||
</I>>><i> > ICompilationUnit stuff. I was really hoping that the interface would
|
||||
</I>>><i> expose
|
||||
</I>>><i> > information via IEnumerable's so that I could maintain data in my own
|
||||
</I>>><i> format
|
||||
</I>>><i> > and yield requested data at will. It also seems that the
|
||||
</I>>><i> ICompilationUnit
|
||||
</I>>><i> > is very much geared towards c#/.net. I'll just map things the best I
|
||||
</I>>><i> can.
|
||||
</I>>><i>
|
||||
</I>>><i> ParsedDocument is designed to be language-agnostic. ICompilationUnit
|
||||
</I>>><i> is very much .NET-specific, so if you don't want to use it, you don't
|
||||
</I>>><i> have to. Have the field here is not ideal IMO, but my suggestion for a
|
||||
</I>>><i> .NET parse unit interface was not taken up. There's a thread of
|
||||
</I>>><i> discussion about this that you might be able to contribute to.
|
||||
</I>>><i>
|
||||
</I>>><i> The design so far has been pretty much driven by C#, so if you have
|
||||
</I>>><i> any suggestions to improve it, now would be the time to voice them,
|
||||
</I>>><i> before we start heading into the 2.0 betas.
|
||||
</I>>><i>
|
||||
</I>>><i> >>
|
||||
</I>>><i> >> As an example ..
|
||||
</I>>><i> >>
|
||||
</I>>><i> >> PythonParsedDocument : ParsedDocument {
|
||||
</I>>><i> >> PythonModule module; // hoping this gets persisted
|
||||
</I>>><i>
|
||||
</I>>><i> If what I suspect is correct, PythonModule would have to be
|
||||
</I>>><i> serializable. However, the DB is optimised/indexed for type lookup and
|
||||
</I>>><i> stuff, and this would obviously not work easily with custom
|
||||
</I>>><i> serializable classes. This may be something that we could improve.
|
||||
</I>>><i>
|
||||
</I>>><i> --
|
||||
</I>>><i> Michael Hutchinson
|
||||
</I>>><i> <A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</I>>><i>
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/93151f73/attachment-0001.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/93151f73/attachment-0001.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
|
||||
<LI>Next message: <A HREF="000048.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#47">[ date ]</a>
|
||||
<a href="thread.html#47">[ thread ]</a>
|
||||
<a href="subject.html#47">[ subject ]</a>
|
||||
<a href="author.html#47">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,160 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Parser Overview
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=6d4a25b10810010018ie33cf5dn25833fba366d362b%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000047.html">
|
||||
<LINK REL="Next" HREF="000049.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Parser Overview</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=6d4a25b10810010018ie33cf5dn25833fba366d362b%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Parser Overview">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Oct 1 04:57:00 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000047.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000049.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#48">[ date ]</a>
|
||||
<a href="thread.html#48">[ thread ]</a>
|
||||
<a href="subject.html#48">[ subject ]</a>
|
||||
<a href="author.html#48">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>I've added error highlighting as well.
|
||||
|
||||
<A HREF="http://audidude.com/dropbox/monodevelop-python-errors.png">http://audidude.com/dropbox/monodevelop-python-errors.png</A>
|
||||
|
||||
-- Christian
|
||||
|
||||
On Wed, Oct 1, 2008 at 12:18 AM, Christian Hergert <
|
||||
<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
|
||||
><i> With your help, I was able to get this moving somewhat.
|
||||
</I>><i>
|
||||
</I>><i> As an addin, this needs a lot of work. But it currently supports:
|
||||
</I>><i>
|
||||
</I>><i> - Python project type
|
||||
</I>><i> - Project and file template
|
||||
</I>><i> - Pluggable python runtimes (cPython2.5 only currently. this will
|
||||
</I>><i> change after i get the ui components added)
|
||||
</I>><i> - Precompiling of python modules (either .pyc or .pyo for optimized)
|
||||
</I>><i> - Code folding for functions/comments/classes
|
||||
</I>><i> - Really basic completion that I will be adding to over the next few
|
||||
</I>><i> nights (basically until its usable for myself daily)
|
||||
</I>><i> - Parsing of python code is done via a subprocess to a long running
|
||||
</I>><i> python process. This allows for building a real AST using the "compiler"
|
||||
</I>><i> module.
|
||||
</I>><i>
|
||||
</I>><i> and the obligatory screenshot
|
||||
</I>><i>
|
||||
</I>><i> <A HREF="http://audidude.com/dropbox/monodevelop-python.png">http://audidude.com/dropbox/monodevelop-python.png</A>
|
||||
</I>><i>
|
||||
</I>><i> Cheers!
|
||||
</I>><i>
|
||||
</I>><i> -- Christian
|
||||
</I>><i>
|
||||
</I>><i>
|
||||
</I>><i> On Tue, Sep 30, 2008 at 11:59 AM, Christian Hergert <
|
||||
</I>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>><i>
|
||||
</I>>><i> While I think its a worthy idea to remove the tight coupling to .NET
|
||||
</I>>><i> logic, I'm not going to volunteer to do it. I'll work around it for the
|
||||
</I>>><i> time being and it seems like a notable post-2.0 feature.
|
||||
</I>>><i>
|
||||
</I>>><i> -- Christian
|
||||
</I>>><i>
|
||||
</I>>><i>
|
||||
</I>>><i> On Mon, Sep 29, 2008 at 9:59 PM, Michael Hutchinson <
|
||||
</I>>><i> <A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">m.j.hutchinson at gmail.com</A>> wrote:
|
||||
</I>>><i>
|
||||
</I>>>><i> Hi,
|
||||
</I>>>><i>
|
||||
</I>>>><i> > On Mon, Sep 29, 2008 at 3:38 PM, Christian Hergert
|
||||
</I>>>><i> > <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>>>><i> >>
|
||||
</I>>>><i> >> I have a class that extends ParsedDocument. Do references inside that
|
||||
</I>>>><i> >> class get persisted to the parser database? Or is this perhaps
|
||||
</I>>>><i> something
|
||||
</I>>>><i> >> that i should have encapsulated in an ICompilationUnit.
|
||||
</I>>>><i>
|
||||
</I>>>><i> I /think/ any fields of objects that are [Serializable] will get
|
||||
</I>>>><i> persisted, which includes all the collections that the base
|
||||
</I>>>><i> ParsedDocument has.
|
||||
</I>>>><i>
|
||||
</I>>>><i> On Mon, Sep 29, 2008 at 7:29 PM, Christian Hergert
|
||||
</I>>>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>>>><i> > Ok, so after some further exploration, I think I understand the
|
||||
</I>>>><i> > ICompilationUnit stuff. I was really hoping that the interface would
|
||||
</I>>>><i> expose
|
||||
</I>>>><i> > information via IEnumerable's so that I could maintain data in my own
|
||||
</I>>>><i> format
|
||||
</I>>>><i> > and yield requested data at will. It also seems that the
|
||||
</I>>>><i> ICompilationUnit
|
||||
</I>>>><i> > is very much geared towards c#/.net. I'll just map things the best I
|
||||
</I>>>><i> can.
|
||||
</I>>>><i>
|
||||
</I>>>><i> ParsedDocument is designed to be language-agnostic. ICompilationUnit
|
||||
</I>>>><i> is very much .NET-specific, so if you don't want to use it, you don't
|
||||
</I>>>><i> have to. Have the field here is not ideal IMO, but my suggestion for a
|
||||
</I>>>><i> .NET parse unit interface was not taken up. There's a thread of
|
||||
</I>>>><i> discussion about this that you might be able to contribute to.
|
||||
</I>>>><i>
|
||||
</I>>>><i> The design so far has been pretty much driven by C#, so if you have
|
||||
</I>>>><i> any suggestions to improve it, now would be the time to voice them,
|
||||
</I>>>><i> before we start heading into the 2.0 betas.
|
||||
</I>>>><i>
|
||||
</I>>>><i> >>
|
||||
</I>>>><i> >> As an example ..
|
||||
</I>>>><i> >>
|
||||
</I>>>><i> >> PythonParsedDocument : ParsedDocument {
|
||||
</I>>>><i> >> PythonModule module; // hoping this gets persisted
|
||||
</I>>>><i>
|
||||
</I>>>><i> If what I suspect is correct, PythonModule would have to be
|
||||
</I>>>><i> serializable. However, the DB is optimised/indexed for type lookup and
|
||||
</I>>>><i> stuff, and this would obviously not work easily with custom
|
||||
</I>>>><i> serializable classes. This may be something that we could improve.
|
||||
</I>>>><i>
|
||||
</I>>>><i> --
|
||||
</I>>>><i> Michael Hutchinson
|
||||
</I>>>><i> <A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</I>>>><i>
|
||||
</I>>><i>
|
||||
</I>>><i>
|
||||
</I>><i>
|
||||
</I>-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/a207c424/attachment.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/a207c424/attachment.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000047.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000049.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#48">[ date ]</a>
|
||||
<a href="thread.html#48">[ thread ]</a>
|
||||
<a href="subject.html#48">[ subject ]</a>
|
||||
<a href="author.html#48">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,93 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Parser Overview
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=6d4a25b10810010157q6030d9ava976ff383c5bfd7%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000048.html">
|
||||
<LINK REL="Next" HREF="000050.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Parser Overview</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=6d4a25b10810010157q6030d9ava976ff383c5bfd7%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Parser Overview">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Oct 1 11:47:50 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000048.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000050.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#49">[ date ]</a>
|
||||
<a href="thread.html#49">[ thread ]</a>
|
||||
<a href="subject.html#49">[ subject ]</a>
|
||||
<a href="author.html#49">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Wed, Oct 1, 2008 at 4:57 AM, Christian Hergert
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
><i> I've added error highlighting as well.
|
||||
</I>><i>
|
||||
</I>><i> <A HREF="http://audidude.com/dropbox/monodevelop-python-errors.png">http://audidude.com/dropbox/monodevelop-python-errors.png</A>
|
||||
</I>><i>
|
||||
</I>><i> -- Christian
|
||||
</I>><i>
|
||||
</I>><i> On Wed, Oct 1, 2008 at 12:18 AM, Christian Hergert
|
||||
</I>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>>><i>
|
||||
</I>>><i> With your help, I was able to get this moving somewhat.
|
||||
</I>>><i>
|
||||
</I>>><i> As an addin, this needs a lot of work. But it currently supports:
|
||||
</I>>><i>
|
||||
</I>>><i> Python project type
|
||||
</I>>><i> Project and file template
|
||||
</I>>><i> Pluggable python runtimes (cPython2.5 only currently. this will change
|
||||
</I>>><i> after i get the ui components added)
|
||||
</I>>><i> Precompiling of python modules (either .pyc or .pyo for optimized)
|
||||
</I>>><i> Code folding for functions/comments/classes
|
||||
</I>>><i> Really basic completion that I will be adding to over the next few nights
|
||||
</I>>><i> (basically until its usable for myself daily)
|
||||
</I>>><i> Parsing of python code is done via a subprocess to a long running python
|
||||
</I>>><i> process. This allows for building a real AST using the "compiler" module.
|
||||
</I>>><i>
|
||||
</I>>><i> and the obligatory screenshot
|
||||
</I>>><i>
|
||||
</I>>><i> <A HREF="http://audidude.com/dropbox/monodevelop-python.png">http://audidude.com/dropbox/monodevelop-python.png</A>
|
||||
</I>
|
||||
Nice work!
|
||||
|
||||
Would you like to add this to extras?
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000048.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000050.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#49">[ date ]</a>
|
||||
<a href="thread.html#49">[ thread ]</a>
|
||||
<a href="subject.html#49">[ subject ]</a>
|
||||
<a href="author.html#49">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,112 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] Parser Overview
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=aec34c770810010847i439cf1ceh3fb903b041ecc50%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000049.html">
|
||||
<LINK REL="Next" HREF="000051.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] Parser Overview</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20Parser%20Overview&In-Reply-To=aec34c770810010847i439cf1ceh3fb903b041ecc50%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] Parser Overview">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Wed Oct 1 12:10:45 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000049.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000051.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#50">[ date ]</a>
|
||||
<a href="thread.html#50">[ thread ]</a>
|
||||
<a href="subject.html#50">[ subject ]</a>
|
||||
<a href="author.html#50">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>I would love to!
|
||||
|
||||
The code can currently be found at:
|
||||
|
||||
<A HREF="git://git.dronelabs.com/git/users/chris/monodevelop-pybinding.git">git://git.dronelabs.com/git/users/chris/monodevelop-pybinding.git</A>
|
||||
If you place that folder as a sibling to monodevelop/, you can run
|
||||
"./tester-tool" which will copy the lib over and run "make run" for you.
|
||||
|
||||
-- Christian
|
||||
|
||||
On Wed, Oct 1, 2008 at 8:47 AM, Michael Hutchinson <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">m.j.hutchinson at gmail.com</A>
|
||||
><i> wrote:
|
||||
</I>
|
||||
><i> On Wed, Oct 1, 2008 at 4:57 AM, Christian Hergert
|
||||
</I>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>><i> > I've added error highlighting as well.
|
||||
</I>><i> >
|
||||
</I>><i> > <A HREF="http://audidude.com/dropbox/monodevelop-python-errors.png">http://audidude.com/dropbox/monodevelop-python-errors.png</A>
|
||||
</I>><i> >
|
||||
</I>><i> > -- Christian
|
||||
</I>><i> >
|
||||
</I>><i> > On Wed, Oct 1, 2008 at 12:18 AM, Christian Hergert
|
||||
</I>><i> > <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>><i> >>
|
||||
</I>><i> >> With your help, I was able to get this moving somewhat.
|
||||
</I>><i> >>
|
||||
</I>><i> >> As an addin, this needs a lot of work. But it currently supports:
|
||||
</I>><i> >>
|
||||
</I>><i> >> Python project type
|
||||
</I>><i> >> Project and file template
|
||||
</I>><i> >> Pluggable python runtimes (cPython2.5 only currently. this will change
|
||||
</I>><i> >> after i get the ui components added)
|
||||
</I>><i> >> Precompiling of python modules (either .pyc or .pyo for optimized)
|
||||
</I>><i> >> Code folding for functions/comments/classes
|
||||
</I>><i> >> Really basic completion that I will be adding to over the next few
|
||||
</I>><i> nights
|
||||
</I>><i> >> (basically until its usable for myself daily)
|
||||
</I>><i> >> Parsing of python code is done via a subprocess to a long running python
|
||||
</I>><i> >> process. This allows for building a real AST using the "compiler"
|
||||
</I>><i> module.
|
||||
</I>><i> >>
|
||||
</I>><i> >> and the obligatory screenshot
|
||||
</I>><i> >>
|
||||
</I>><i> >> <A HREF="http://audidude.com/dropbox/monodevelop-python.png">http://audidude.com/dropbox/monodevelop-python.png</A>
|
||||
</I>><i>
|
||||
</I>><i> Nice work!
|
||||
</I>><i>
|
||||
</I>><i> Would you like to add this to extras?
|
||||
</I>><i>
|
||||
</I>><i> --
|
||||
</I>><i> Michael Hutchinson
|
||||
</I>><i> <A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</I>><i>
|
||||
</I>-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/555a9331/attachment.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/555a9331/attachment.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000049.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000051.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#50">[ date ]</a>
|
||||
<a href="thread.html#50">[ thread ]</a>
|
||||
<a href="subject.html#50">[ subject ]</a>
|
||||
<a href="author.html#50">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,67 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] warning highlighting
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20warning%20highlighting&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000050.html">
|
||||
<LINK REL="Next" HREF="000052.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] warning highlighting</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20warning%20highlighting&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] warning highlighting">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Thu Oct 2 02:07:12 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000050.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000052.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#51">[ date ]</a>
|
||||
<a href="thread.html#51">[ thread ]</a>
|
||||
<a href="subject.html#51">[ subject ]</a>
|
||||
<a href="author.html#51">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Currently, errors matching ErrorType.Warning are highlighted in red along
|
||||
with ErrorType.Error. Does it make sense to change this to a yellow'ish
|
||||
color? Do we want that configurable per text editor scheme?
|
||||
|
||||
I just added pyflakes support to the python parser to catch warnings. I
|
||||
would like these to not turn up red :-)
|
||||
|
||||
-- Christian / vwduder
|
||||
-------------- next part --------------
|
||||
An HTML attachment was scrubbed...
|
||||
URL: <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/4d708c01/attachment.html">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081001/4d708c01/attachment.html</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000050.html">[Monodevelop-devel] Parser Overview
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000052.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#51">[ date ]</a>
|
||||
<a href="thread.html#51">[ thread ]</a>
|
||||
<a href="subject.html#51">[ subject ]</a>
|
||||
<a href="author.html#51">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,78 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] warning highlighting
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20warning%20highlighting&In-Reply-To=6d4a25b10810012307t6d8a0816yeae8102608d6d472%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000051.html">
|
||||
<LINK REL="Next" HREF="000053.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] warning highlighting</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20warning%20highlighting&In-Reply-To=6d4a25b10810012307t6d8a0816yeae8102608d6d472%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] warning highlighting">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Thu Oct 2 03:06:47 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000051.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000053.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#52">[ date ]</a>
|
||||
<a href="thread.html#52">[ thread ]</a>
|
||||
<a href="subject.html#52">[ subject ]</a>
|
||||
<a href="author.html#52">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Thu, Oct 2, 2008 at 2:07 AM, Christian Hergert
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
><i> Currently, errors matching ErrorType.Warning are highlighted in red along
|
||||
</I>><i> with ErrorType.Error. Does it make sense to change this to a yellow'ish
|
||||
</I>><i> color? Do we want that configurable per text editor scheme?
|
||||
</I>><i>
|
||||
</I>><i> I just added pyflakes support to the python parser to catch warnings. I
|
||||
</I>><i> would like these to not turn up red :-)
|
||||
</I>
|
||||
I think we could maybe have as many as 5 underline colours:
|
||||
ParserError, ParserWarning, CompilerError, CompilerWarning, Spelling.
|
||||
Perhaps the Compiler/Parser distinction isn't necessary, though there
|
||||
are differences in their dynamicity that might warrant it, so we
|
||||
probably need to think this over.
|
||||
|
||||
These should of course be defined in the colour scheme so that they
|
||||
fit in with the other highlighting colours. The named colours should
|
||||
have fallbacks in case the schemes don't define all the colours.
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000051.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000053.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#52">[ date ]</a>
|
||||
<a href="thread.html#52">[ thread ]</a>
|
||||
<a href="subject.html#52">[ subject ]</a>
|
||||
<a href="author.html#52">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,90 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] warning highlighting
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20warning%20highlighting&In-Reply-To=aec34c770810020006j74414dcen66cc59a6b7dd3f4d%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000052.html">
|
||||
<LINK REL="Next" HREF="000054.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] warning highlighting</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20warning%20highlighting&In-Reply-To=aec34c770810020006j74414dcen66cc59a6b7dd3f4d%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] warning highlighting">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Thu Oct 2 03:58:04 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000052.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000054.html">[Monodevelop-devel] couple syntaxmode updates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#53">[ date ]</a>
|
||||
<a href="thread.html#53">[ thread ]</a>
|
||||
<a href="subject.html#53">[ subject ]</a>
|
||||
<a href="author.html#53">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>I think for the moment we should add a check in SourceEditorWidget.cs
|
||||
for warnings.
|
||||
|
||||
if (info.ErrorType == ErrorType.Warning)
|
||||
(marker as UnderlineMarker).Color = new Gdk.Color (232, 192, 52);
|
||||
|
||||
But you are right, abstracting this is a good idea.
|
||||
|
||||
-- Christian
|
||||
|
||||
On 10/2/08, Michael Hutchinson <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">m.j.hutchinson at gmail.com</A>> wrote:
|
||||
><i> On Thu, Oct 2, 2008 at 2:07 AM, Christian Hergert
|
||||
</I>><i> <<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
</I>>><i> Currently, errors matching ErrorType.Warning are highlighted in red along
|
||||
</I>>><i> with ErrorType.Error. Does it make sense to change this to a yellow'ish
|
||||
</I>>><i> color? Do we want that configurable per text editor scheme?
|
||||
</I>>><i>
|
||||
</I>>><i> I just added pyflakes support to the python parser to catch warnings. I
|
||||
</I>>><i> would like these to not turn up red :-)
|
||||
</I>><i>
|
||||
</I>><i> I think we could maybe have as many as 5 underline colours:
|
||||
</I>><i> ParserError, ParserWarning, CompilerError, CompilerWarning, Spelling.
|
||||
</I>><i> Perhaps the Compiler/Parser distinction isn't necessary, though there
|
||||
</I>><i> are differences in their dynamicity that might warrant it, so we
|
||||
</I>><i> probably need to think this over.
|
||||
</I>><i>
|
||||
</I>><i> These should of course be defined in the colour scheme so that they
|
||||
</I>><i> fit in with the other highlighting colours. The named colours should
|
||||
</I>><i> have fallbacks in case the schemes don't define all the colours.
|
||||
</I>><i>
|
||||
</I>><i> --
|
||||
</I>><i> Michael Hutchinson
|
||||
</I>><i> <A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</I>><i>
|
||||
</I></PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000052.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000054.html">[Monodevelop-devel] couple syntaxmode updates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#53">[ date ]</a>
|
||||
<a href="thread.html#53">[ thread ]</a>
|
||||
<a href="subject.html#53">[ subject ]</a>
|
||||
<a href="author.html#53">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,66 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] couple syntaxmode updates
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20couple%20syntaxmode%20updates&In-Reply-To=">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000053.html">
|
||||
<LINK REL="Next" HREF="000055.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] couple syntaxmode updates</H1>
|
||||
<B>Christian Hergert</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20couple%20syntaxmode%20updates&In-Reply-To="
|
||||
TITLE="[Monodevelop-devel] couple syntaxmode updates">christian.hergert at gmail.com
|
||||
</A><BR>
|
||||
<I>Fri Oct 10 03:25:29 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000053.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000055.html">[Monodevelop-devel] couple syntaxmode updates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#54">[ date ]</a>
|
||||
<a href="thread.html#54">[ thread ]</a>
|
||||
<a href="subject.html#54">[ subject ]</a>
|
||||
<a href="author.html#54">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>Are attached, ok to commit?
|
||||
|
||||
-- Christian
|
||||
-------------- next part --------------
|
||||
A non-text attachment was scrubbed...
|
||||
Name: syntax-updates.patch
|
||||
Type: text/x-patch
|
||||
Size: 1027 bytes
|
||||
Desc: not available
|
||||
Url : <A HREF="http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081010/1e5209a2/attachment.bin">http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20081010/1e5209a2/attachment.bin</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000053.html">[Monodevelop-devel] warning highlighting
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000055.html">[Monodevelop-devel] couple syntaxmode updates
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#54">[ date ]</a>
|
||||
<a href="thread.html#54">[ thread ]</a>
|
||||
<a href="subject.html#54">[ subject ]</a>
|
||||
<a href="author.html#54">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
|
|
@ -0,0 +1,65 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE> [Monodevelop-devel] couple syntaxmode updates
|
||||
</TITLE>
|
||||
<LINK REL="Index" HREF="index.html" >
|
||||
<LINK REL="made" HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20couple%20syntaxmode%20updates&In-Reply-To=6d4a25b10810100025i13aaa3e7h9989a68faa859f57%40mail.gmail.com">
|
||||
<META NAME="robots" CONTENT="index,nofollow">
|
||||
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
||||
<LINK REL="Previous" HREF="000054.html">
|
||||
<LINK REL="Next" HREF="000056.html">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#ffffff">
|
||||
<H1>[Monodevelop-devel] couple syntaxmode updates</H1>
|
||||
<B>Michael Hutchinson</B>
|
||||
<A HREF="mailto:monodevelop-devel-list%40lists.ximian.com?Subject=%5BMonodevelop-devel%5D%20couple%20syntaxmode%20updates&In-Reply-To=6d4a25b10810100025i13aaa3e7h9989a68faa859f57%40mail.gmail.com"
|
||||
TITLE="[Monodevelop-devel] couple syntaxmode updates">m.j.hutchinson at gmail.com
|
||||
</A><BR>
|
||||
<I>Fri Oct 10 14:23:37 EDT 2008</I>
|
||||
<P><UL>
|
||||
<LI>Previous message: <A HREF="000054.html">[Monodevelop-devel] couple syntaxmode updates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000056.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#55">[ date ]</a>
|
||||
<a href="thread.html#55">[ thread ]</a>
|
||||
<a href="subject.html#55">[ subject ]</a>
|
||||
<a href="author.html#55">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
<HR>
|
||||
<!--beginarticle-->
|
||||
<PRE>On Fri, Oct 10, 2008 at 3:25 AM, Christian Hergert
|
||||
<<A HREF="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">christian.hergert at gmail.com</A>> wrote:
|
||||
><i> Are attached, ok to commit?
|
||||
</I>
|
||||
Looks good. Thanks!
|
||||
|
||||
--
|
||||
Michael Hutchinson
|
||||
<A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
||||
</PRE>
|
||||
|
||||
|
||||
<!--endarticle-->
|
||||
<HR>
|
||||
<P><UL>
|
||||
<!--threads-->
|
||||
<LI>Previous message: <A HREF="000054.html">[Monodevelop-devel] couple syntaxmode updates
|
||||
</A></li>
|
||||
<LI>Next message: <A HREF="000056.html">[Monodevelop-devel] Can't get monodevelop to show GTK# 2.00 under C# heading
|
||||
</A></li>
|
||||
<LI> <B>Messages sorted by:</B>
|
||||
<a href="date.html#55">[ date ]</a>
|
||||
<a href="thread.html#55">[ thread ]</a>
|
||||
<a href="subject.html#55">[ subject ]</a>
|
||||
<a href="author.html#55">[ author ]</a>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
<hr>
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list">More information about the Monodevelop-devel-list
|
||||
mailing list</a><br>
|
||||
</body></html>
|
||||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче