It's important to note that XAML was --> NOT MEANT TO BE CODED! BY HAND <--- but despite the constant hand waving we/they used to give developers over and over, we/they in turned bent over and upped the investment into cider team via VS2010 (which btw is two separate teams now doing "design" surface --gah!) ..DESPITE the original caution.
Blend had such promise... *sigh* :) Learn Blend, it's a forgiving tool if you give it a shot... and i'd go a pepsi challenge with a VS2010 coder (TAB + dot + Click, Ship) vs. Blend ...(Drag + Ship) :D --- Regards, Scott Barnes http://www.riagenic.com On Mon, Feb 28, 2011 at 7:15 PM, Peter Maddin <[email protected]>wrote: > Thanks I am trying to become more familiar with Expression Blend 4 to do > the > design side of things than hacking XAML. > I think that one will always need to do some final adjustments to the XAML > anyway. > > Regards Peter > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On > Behalf Of Winston Pang > Sent: Monday, 28 February 2011 4:56 PM > To: ozWPF > Subject: Re: WPF application to allow for different screen resolutions > > You'll realise over time that, you probably use the designer to > visualise the end result, and to assist in generating the more > chunkier XAML, but most of the time, you'll go into a habit of > cleaning it up yourself anyways, I try to ward away trying to do a > layout by dragging and dropping on a design surface. More hand coding > of the layout is what I prefer. > > > On Mon, Feb 28, 2011 at 7:48 PM, Peter Maddin <[email protected]> > wrote: > > Ok thanks > > > > Just have to be careful the designer doesn't add in fixed values for me. > > > > Regards Peter > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > On > > Behalf Of Winston Pang > > Sent: Monday, 28 February 2011 4:36 PM > > To: ozWPF > > Subject: Re: WPF application to allow for different screen resolutions > > > > Honestly, most of the time you don't have to do too much, it seems to > > function pretty well, whether it be resolutions and DPI (apart from > > manually positioning windows, you'll need to factor in DPI in the > > calculation). > > > > A rule of thumb that I have read before is, try to limit fix heights > > and widths unless that's the requirement or the design, otherwise, > > most say you should just let it all stretch out and take up all the > > room, and then depend on margins/padding to fix up layout and spacing. > > > > I think WPF does a pretty good job at handling most of it for you > anyways. > > > > On Mon, Feb 28, 2011 at 7:19 PM, Peter Maddin <[email protected]> > > wrote: > >> When I developed WinForms applications I did so at a certain screen > >> resolution. > >> > >> Clients use any number of screen resolutions. > >> > >> When they chose to use a screen resolution that was significantly > > different > >> from what I was using there were problems with the way controls were > >> rendered. > >> > >> My understanding was that WPF could address this sort of issue. > >> > >> What should one do to ensure that one’s WPF applications will look the > > same > >> (as much as it is possible) so that any controls resize appropriately > and > >> textblocks, textboxes scale their font size appropriately. > >> > >> > >> > >> My current focus has been getting my application to play nicely with > > thread > >> that consumes a wcf web service and a loadable COM dll. This is working > ok > >> and now I need to focus on the GUI side of things. > >> > >> > >> > >> I have seen a zoom control in WPFExtensions in CodePlex > >> (http://wpfextensions.codeplex.com/) > >> > >> > >> > >> Is this an approach I should use or is there a better way? I would like > > the > >> whole application to be resized not just a user control. > >> > >> > >> > >> Any feedback very much appreciated. > >> > >> > >> > >> Regards Peter Maddin > >> Applications Development Officer > >> PathWest Laboratory Medicine WA > >> Phone : +618 6396 4285 > >> Mobile: 0414 240 307 > >> E-Mail : [email protected]; [email protected] > >> The contents of this e-mail transmission outside of the WAGHS network > are > >> intended solely for the named recipient's), may be confidential, and may > > be > >> privileged or otherwise protected from disclosure in the public > interest. > >> The use, reproduction, disclosure or distribution of the contents of > this > >> e-mail transmission by any person other than the named recipient(s) is > >> prohibited. If you are not a named recipient please notify the sender > >> immediately. > >> > >> > >> > >> > >> > >> _______________________________________________ > >> ozwpf mailing list > >> [email protected] > >> http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > >> > >> > > _______________________________________________ > > ozwpf mailing list > > [email protected] > > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > > > > _______________________________________________ > > ozwpf mailing list > > [email protected] > > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > > > _______________________________________________ > ozwpf mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > > _______________________________________________ > ozwpf mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf >
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
