[Mono-winforms-list] Porting Mono winforms to a new OS/Window Manager

2011-01-12 Thread Michael Mudge
We are working on getting Mono WinForms up and running on our device,
and I'd like to make sure that we're on the right track and have a
good understanding of what is ahead of us.  Through the project, most
of our issues have been unknown unknowns - so if you can anticipate
any obstacles, it would be very helpful.

We use a GUI manager called PegX - it is fairly primitive.  As I
understand it, there is some dependency between LibGDIPlus and the
GUI, and XPlatUIDriver is also meant to map to the GUI.  What is the
description of these relationships?

PegX does make use of some hardware acceleration, so we would like to
leverage that as much as possible.  Also, the current implementation
of LibGDIPlus has dependencies on many things - FontConfig, FreeType,
LibPNG, XLib, GLib, Cairo.  We only have FreeType and Cairo completely
ported.

Are there parts of LibGDIPlus that we can cut out and replace with
calls straight to PegX, and minimize all of the remaining
dependencies?  Is there someone who can help guide us?

The system is touchscreen-only.  How much do we need to be concerned
with the UI message pump?  The only touchscreen events are down, move
and up.  How might we detect that the cursor has clicked on a textbox
so that we can pop up our onscreen keyboard?  And most importantly,
what questions have I failed to ask?

Thanks,
- Michael Kipp Mudge
Welch Allyn
___
Mono-winforms-list maillist  -  Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list


Re: [Mono-winforms-list] Current Authenticated User

2011-01-12 Thread user65

Hi there Giuliano

A suggestion: You can put the authentication logic (Active Directory
Authentication) in the service layer (WCF/Web Service), 
on a IIS machine. eg, private bool AuthenticateUser(...

On your client side, you can store the authenticated user details, eg Full
name etc
in a Singleton object class or something.

Thus eliminating the need to use
System.Security.Principal.WindowsIdentity.GetCurrent(),
and call it like this SingletonClass.Username after the user has been
authenticated.

Regards,
user65
-- 
View this message in context: 
http://mono.1490590.n4.nabble.com/Current-Authenticated-User-tp3048473p3214773.html
Sent from the Mono - WinForms mailing list archive at Nabble.com.
___
Mono-winforms-list maillist  -  Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list