[Mono-list] GTK bindings
Mike Krueger
mike@icsharpcode.net
Mon, 15 Oct 2001 08:12:36 +0200
This is a multi-part message in MIME format.
------=_NextPart_000_0036_01C15551.2655BE70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi
> What kind of limitations are you running into Windows.Forms, I want to
> know what kind of deficiencies it has.
- Controls have a size limit of 32768 pixels (SharpDevelop can "only" =
view
files with 2200 lines ... I don't want a 16bit int limit 2001)
- Building a forms designer is quite difficult ... MS hides much
functionalaty
- Docking Windows/Tab Controls are really no fun to implement, to get
something
VS.NET like you have to build it from ground up and use dllimport. =
I'm
not sure
that it can be done without the "old" windows apis
- There are only few controls that can be used with windows.forms
- The Windows.Forms do have a "bad" design.
- You don't get events for every case (ex. you get no event when you
move a window ...
VS.NET style docking is only possible with this in my opinion. =
The
don't use Drag&Drop
they use windows moving)
- It sux that Microsoft uses neat controls for their stuff which =
can't
be used for own programs
- The helpsystem
- Menu Items with Icons (you have to build your own)
- Tab Controls
- Docking ...
- Startup performance is horrible when you use Windows.Forms
- I'm not a big java fan, but the Swing classes do have an overall
better design than the
Windows.Forms.
I don't know if I will use a GTK+/GNOME wrapper, because I don't know =
the
GTK+/GNOME
limits, but I'm pretty sure that this library don't "hide" all important
information.
I think that I just "try" GTK+/GNOME, maybe it will suite my needs much
better than Windows.Forms.
My "plan" it is to write a little GUI designer for this library and if I
suceed I could transform
sharpdevelop to the other library. (Windows.Forms causes too many =
headaches
... I hope really
that GTK+ is better, but I don't have GTK+ experience ... under linux I =
was
too lazy to learn a
GUI api ... there are way to many ... gtk, qt, wxwindows, motif (old but
still used) ...)
Maybe it would be better to build a GUI library from ground up in C#, =
but if
the GTK+/GNOME
wrapper is good and don't have too many design flaws it should be ok to =
use.
cya
------=_NextPart_000_0036_01C15551.2655BE70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi<BR><BR>> What kind of limitations =
are you=20
running into Windows.Forms, I want to<BR>> know what kind of =
deficiencies it=20
has.<BR><BR>- Controls have a size limit of 32768 pixels (SharpDevelop =
can=20
"only" view<BR> files with 2200 lines ... I don't want a =
16bit int=20
limit 2001)<BR>- Building a forms designer is quite difficult ... MS =
hides=20
much<BR>functionalaty<BR>- Docking Windows/Tab Controls are really no =
fun to=20
implement, to get<BR>something<BR> VS.NET like you have to =
build it=20
from ground up and use dllimport. I'm<BR>not sure<BR> that =
it can be=20
done without the "old" windows apis<BR>- There are only few controls =
that can be=20
used with windows.forms<BR>- The Windows.Forms do have a "bad"=20
design.<BR> - You don't get events for every case (ex. =
you get=20
no event when you<BR>move a window =
...<BR> =20
VS.NET style docking is only possible with this in my opinion. =
The<BR>don't use=20
Drag&Drop<BR> they use windows=20
moving)<BR> - It sux that Microsoft uses neat controls =
for=20
their stuff which can't<BR>be used for own=20
programs<BR> - The=20
helpsystem<BR> - Menu Items =
with Icons=20
(you have to build your =
own)<BR> - Tab=20
Controls<BR> - Docking=20
...<BR> - Startup performance is horrible when you use =
Windows.Forms<BR> - I'm not a big java fan, but =
the=20
Swing classes do have an overall<BR>better design than=20
the<BR> =
Windows.Forms.<BR><BR>I don't=20
know if I will use a GTK+/GNOME wrapper, because I don't know=20
the<BR>GTK+/GNOME<BR>limits, but I'm pretty sure that this library don't =
"hide"=20
all important<BR>information.<BR>I think that I just "try" GTK+/GNOME, =
maybe it=20
will suite my needs much<BR>better than Windows.Forms.<BR>My "plan" it =
is to=20
write a little GUI designer for this library and if I<BR>suceed I could=20
transform<BR>sharpdevelop to the other library. (Windows.Forms causes =
too many=20
headaches<BR>... I hope really<BR>that GTK+ is better, but I don't have =
GTK+=20
experience ... under linux I was<BR>too lazy to learn a<BR>GUI api ... =
there are=20
way to many ... gtk, qt, wxwindows, motif (old but<BR>still used)=20
...)<BR><BR>Maybe it would be better to build a GUI library from ground =
up in=20
C#, but if<BR>the GTK+/GNOME<BR>wrapper is good and don't have too many =
design=20
flaws it should be ok to use.<BR><BR>cya<BR></FONT></DIV></BODY></HTML>
------=_NextPart_000_0036_01C15551.2655BE70--