[Mono-list] Updating or Redoing go-mono.net
Richard Norman
Jazzynupe@sbcglobal.net
Sat, 10 Jan 2004 10:25:27 -0800
This is a multi-part message in MIME format.
------=_NextPart_000_01A8_01C3D764.1105F390
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
The other option is to use UserControls to create the framework and then
have standard server controls for the rest. That is what I use in my company
quite often. What that buys you is the ability to not only include the same
content in various pages, but you can create events and properties on the
controls so you can do things like highlight new or updated sections through
code. You can also take the concept of searching and filtering across pages.
I have implemented a search of data using a UserControl instead of creating
a Custom WebControl. Encapsulating functionality like the class tree would
not be too tough either, cause once you create the user control, you use a
property to pass the correct XML DOM and the control iterates through the
tree creating the nodes and links.
So a revision of the go-mono.com site can be done with everything that is
available, the question is how far do you want to take it.
Sincerely,
Richard Norman
Web/Application Developer
---------------------------------------------------------------------------
Message: 7
Subject: Re: [Mono-list] Updating or Redoing go-mono.net
From: Miguel de Icaza <miguel@ximian.com>
To: Ben Maurer <bmaurer@users.sourceforge.net>
Cc: Aaron Weber <aaron@ximian.com>, mono-list@lists.ximian.com
Date: Sat, 10 Jan 2004 01:14:39 -0500
Hello,
> One of the issues is that v1, asp.net does not have alot of the things
> we need (MasterPages is the biggest example). Once we get to v2 stuff,
> doing the site would be much easier.
>
> OTOH, by the time we 1.0, we *really* want to be dogfooding on the
> homepage.
Well, we can always use the ASP.NET include directive to get 99% of the
MasterPage features ;-)
Miguel.
------=_NextPart_000_01A8_01C3D764.1105F390
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P><SPAN class=3D268420718-10012004><FONT face=3DArial size=3D2>The =
other option is to=20
use UserControls to create the framework and then have standard server =
controls=20
for the rest. That is what I use in my company quite often. What that =
buys you=20
is the ability to not only include the same content in various pages, =
but you=20
can create events and properties on the controls so you can do things =
like=20
highlight new or updated sections through code. You can also take the =
concept of=20
searching and filtering across pages.</FONT></SPAN></P>
<P><SPAN class=3D268420718-10012004><FONT face=3DArial size=3D2>I have =
implemented a=20
search of data using a UserControl instead of creating a Custom =
WebControl.=20
Encapsulating functionality like the class tree would not be too tough =
either,=20
cause once you create the user control, you use a property to pass the =
correct=20
XML DOM and the control iterates through the tree creating the nodes and =
links.</FONT></SPAN></P>
<P><SPAN class=3D268420718-10012004><FONT face=3DArial size=3D2>So a =
revision of the=20
go-mono.com site can be done with everything that is available, the =
question is=20
how far do you want to take it.</FONT></SPAN></P><SPAN=20
class=3D268420718-10012004><FONT face=3DArial size=3D2>
<DIV align=3Dleft><FONT face=3DArial>Sincerely,</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial></FONT> </DIV>
<DIV align=3Dleft><FONT face=3DArial>Richard Norman</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial>Web/Application=20
Developer</FONT></DIV></FONT></SPAN>
<P><SPAN class=3D268420718-10012004><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
-----------</FONT></SPAN></P>
<P><FONT size=3D2>Message: 7</FONT></P>
<P><FONT size=3D2>Subject: Re: [Mono-list] Updating or Redoing=20
go-mono.net</FONT></P>
<P><FONT size=3D2>From: Miguel de Icaza =
<miguel@ximian.com></FONT></P>
<P><FONT size=3D2>To: Ben Maurer =
<bmaurer@users.sourceforge.net></FONT></P>
<P><FONT size=3D2>Cc: Aaron Weber <aaron@ximian.com>,=20
mono-list@lists.ximian.com</FONT></P>
<P><FONT size=3D2>Date: Sat, 10 Jan 2004 01:14:39 -0500</FONT></P>
<P><FONT size=3D2>Hello,</FONT></P>
<P><FONT size=3D2>> One of the issues is that v1, asp.net does not =
have alot of=20
the things </FONT></P>
<P><FONT size=3D2>> we need (MasterPages is the biggest example). =
Once we get=20
to v2 stuff, </FONT></P>
<P><FONT size=3D2>> doing the site would be much easier.</FONT></P>
<P><FONT size=3D2>> </FONT></P>
<P><FONT size=3D2>> OTOH, by the time we 1.0, we *really* want to be =
dogfooding=20
on the </FONT></P>
<P><FONT size=3D2>> homepage.</FONT></P>
<P><FONT size=3D2>Well, we can always use the ASP.NET include directive =
to get 99%=20
of the MasterPage features ;-)</FONT></P>
<P><FONT size=3D2>Miguel.</FONT></P></DIV></BODY></HTML>
------=_NextPart_000_01A8_01C3D764.1105F390--