Beginning GUI

[Lint Radley]

Hi Everyone,

I've done several C# console applications now, and feel comfortable with
the language. Can anyone recommend a web site, book, etc which has
information on starting to develop full GUI applications?

Many Thanks,

Lint

 

[Guest]

this one is pretty goo
http://www.amazon.co.uk/Windows-For...ef=sr_1_6/026-2705790-1462017?ie=UTF8&s=books

 

[Daniel]

I wouldn't even say you need a book but if you feel better that way.

Assuming visual studio:

You just make a win form application, and drop and place controls you want
for your gui on to the form and begin on your way. Best way to learn is
experiment. understand the basics too, drag a button on the form, and for
its click code, click the button on the designer and it takes oyu to where
you want to put your code for the button on click etc

v.easy nowadays

 

[Basil Abusamrah]

I disagree. If you're fairly new to programming and are just starting to
move into the Windows Forms world, you should definitely use a resource.

Chances are you are new to an event-based application and without the
proper resource(s) you would probably end out thinking it's 'magic.'

 

[Daniel]

Ok....

Event based, when you clcik a control or do anythign with it it triggers an
event

Vis studio does the catching of that event for you when you double click the
control for a button it does the onclick handler and you code there what you
want the button or control to do when clicked.

To see other events you clcik the lightneing bolt symbol and then choose the
event you want to handle from the list, and voila same thing.

To make your own events which is more advanced, look up on the net any
tutorial on this, LOADS of them.

So a quick explanation and online tutorials that are up to date because they
are always getting posted....total cost £0 .

or buy a book, that is one authors opinion of how to implement it and costs
£25 or so and goes out of date. But as i DID SAY if you feel better with a
book get one.

But from a console background are you going to think it's magic? lol. i am
sorry Basil, but your opinion is a tad ignorant and insulting to the
original posters intellect.

 

[Lint Radley]

Thanks for your replies. I am not new to programming, I am new to C#.

 

[Simon Tamman]

Dan,

I disagree with your sentiments completely.
Sure I was able to figure most things out myself when I started out but it
wasn't until I picked up a book (Simon Robinsons Professional C#) that I
even realised I could use:

textBox1.DataBindings.Add("Text", obj, "Name");

Previous to that I was constantly copying the values back and forth like a
retard.

Buying that kind of knowledge IS massively useful and helps developers
become better programmers.

Are you telling me that it doesn't make you a better programmer to read
things like the Framework Design Guidelines
(http://www.amazon.com/Framework-Design-Guidelines-Conventions-Development/d
p/0321246756/sr=1-1/qid=1161709609/ref=sr_1_1/104-1806346-1142323?ie=UTF8&s=
books)
or GOF
(http://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-Profes
sional/dp/0201633612)?

I will confess that I was shit before I started reading up on books, sure I
thought I was great at the time but that's only because I didn't realise
just how much I didn't know at that point.
I'm a contracter so I get to move from company to company and get to see a
lot of people's different work.
The amount of times i've seen all sorts of crazy ass implementations that
were devised just because someone never read up on simple standards is
astonishing.

I have not yet encountered a programmer that I admire that heavily uses the
VS designer gui without really understanding what goes on in the background.
This is made worse by VS 2005 that places the automagicality of the designer
in a completely seperate file.
I still prefer to see events hooked up in either the Ctor or a method that
is called from the Ctor, it makes the code more readable IMO.

Simon

 

[Basil Abusamrah]

Once again we're back to the point of understanding. Knowing what to do
and understanding are quite different, knowing how to double click a
control to get VS to register (and create) a method be called-back by
the event wont get you far at all.

Even you yourself mentioned using an online tutorial for actually
learning (not using) events, and if I recall I recommended a RESOURCE,
not a 'book.' Kind of odd how you call me ignorant yet support my view.

I wont be surprised if you lose a job at an interview because you
couldn't explain the actual wiring of an event and instead explain that
VS 'does the catching.'

Back to the point - Lint, if you understand delegates, events, and
callbacks then I'm sure you could definitely pick up Windows Form
programming with VS quite quickly without a resource.

 

[Daniel]

btw just to add to your ignorance as i put it, i never said getting a book
was totally bad nor did i say you were wrong to mention a resource.,i was
referring to your comment about if he doesn't get a book or some outside
teaching he will think its 'magic' lol It's like saying get a book on a car
or you'll think it is powered by magic potions and runs on magical dust! It
was a daft comment and insulting comment to the poster. Who himself has
since replied to let you know he is no newbie. Tho never met a newbie that
thought it was all magic, then read a book and went OHHH so its not magic
then, well i'll be! lol.....well maybe thats what you used to think?

No need to get so touchy Pretty sure i'd be ok in an interview tho, since
i'd be doing the interviewing....i own my own company and wrote the base
engine that supports it. You take care tho Basil lol

 

[PS]

Hi Everyone,

I've done several C# console applications now, and feel comfortable with
the language. Can anyone recommend a web site, book, etc which has
information on starting to develop full GUI applications?

One thing that no one mentioned is that you don't necessarily create all
your UI elements at design time. You may find it better to create and
populate your forms at run time programmatically if the controls will vary
based on software settings or authorizations. I find it a lot easy to deal
with adding only the needed controls rather than disabling or disposing of
un-needed controls.

Also you can consider using user controls if you are using tabs or a single
workspace model that will have it's content change (e.g. like Outlook). Then
you can switch the user controls in and out of the main work area rather
than deal with one big form with loads of panels (and loads of code behind).

PS

 

[Daniel]

No one mentioned it because he is just about to learn. Best to start basic
then, when you need, start making them programatically etc.

 

[PS]

No one mentioned it because he is just about to learn. Best to start basic
then, when you need, start making them programatically etc.

The OP is not new to programming and wants to develop a full GUI
application. So he should be informed that UIs can be created at both run
time and design time. I don't think there is any "best" way to design UIs.

PS