Shaggar posted:

if you throw away all the unix stuff the unix philosophy isn't bad.

Shaggar posted:

y'all need to go back and read some wpf tutorials and stay away from stack overflow until you get the tutorials to work.

BONGHITZ posted:

just make a command line program, all the best programs are command line programs

Bloody posted:

i still use winforms for my half hour long bespoke serial port bangers

Careful Drums posted:

hey is wpf like the same thing for metro/wp8 apps? because i tried that once and it looked a lot like that xaml there.

Shaggar posted:

the whole thing you're doing with the static instance is really weird, dude.

if you're gonna use a static instance (idk why you would) then set it as the data context of your view

in MainWindow.xaml.cs:

C# code:

public MainWindow()
{
	InitializeComponent();
	this.DataContext = BlackjackViewModel.Instance;

}

Then in MainWindow.xaml

XML code:

<Window x:Class="BlackjackGame.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:classes="clr-namespace:BlackjackGame"
        Title="MainWindow" Height="480" Width="640">
    <Grid>
        <Label x:Name="lblPlayerTotal" Content="{Binding PlayerTotal}" HorizontalAlignment="Left" Margin="10,264,0,0" VerticalAlignment="Top" Width="38"/>
        <Label x:Name="lblDealerTotal" Content="{Binding DealerTotal}" HorizontalAlignment="Left" Margin="10,160,0,0" VerticalAlignment="Top"/>
    </Grid>
</Window>

{Binding PropertyName} causes the binder to look for that PropertyName as a path on the local data context. Since we set the local data context to an object of type BlackjackViewModel, those paths should be readily available. UpdateSourceTrigger=PropertyChanged is redundant since its the default.

Also, since .net 4, the compiler will automatically add the INPC cruft to basic properties so your viewmodel can be simplified to this:

C# code:

class BlackjackViewModel
{
	private static BlackjackViewModel __instance = null;

	static BlackjackViewModel()
	{
		__instance = new BlackjackViewModel();
	}

	public int CardsRemaining { get; set; }
	public int PlayerTotal { get; set; }
	public int DealerTotal { get; set; }

	public static BlackjackViewModel Instance
	{
		get { return __instance; }
	}

}

also, to make INPC a little easier, create an abstract class like this:

C# code:

public abstract class NotifyPropertyChanged : INotifyPropertyChanged
{
	public event PropertyChangedEventHandler PropertyChanged;

	protected virtual void OnPropertyChanged(string propertyName)
	{
		if (this.PropertyChanged != null)
		{
			this.PropertyChanged(this, new PropertyChangedEventArgs(propertyName));
		}
	}
}

and then if you want to do notifications, have your viewmodel extend NotifyPropertyChanged instead of implementing INotifyPropertyChanged. You can then call the OnPropertyChanged method like you're doing currently, but you don't need to write it over and over in each viewmodel.

coffeetable posted:

i didnt think much of code complete & the pragmatic programmer. lotta pages that say very little

ones i have been impressed by so far

• The Practice of Programming. its everything that prag prog and code complete covers, but in <300 pages. tef's standard recommendation.
  
• Working Effectively with Legacy Code. its claimed subject is fixing other people's fuckups, but in doing so it has a lot to say about how to design & structure yr programs. think suspicious dish recommended me this one
  
• The Algorithm Design Manual. best algorithms book around. fuuuuuuuck CLRS.
  
• Learn You A Haskell. not to actually learn haskell (though its v cool), but just so's you properly understand there are alternatives to OO
  

but more generally, just cultivate an interest in some pet topic and practice.

tef posted:

any book spine wider than your thumb is probably a reference manual, or reads like one. or worse, somewhere between a manual and a textbook and suitable for neither.

if you have some specific goal in mind of where you want to practice programming, we can probably give you better recommendations. "How do i make faster software" "how do i make maintable software"

but a lot of technical problems often boil down to social problems, so learning to work in a team and communicating well are probably the skills you want to hone the most to set you apart.

coffeetable posted:

reactiveui's documentation is non-existent, but off the top of my head
- use ObservableForProperty to get an observable for listview.SelectedItem
- subscribe your command to the shiny new observable

e: oh cool you don't need ObservableForProperty any more, the .WhenAny extension method will now construct it implicitly when you call it on an object

Luigi Thirty posted:

NOPE THEY'RE ALL STILL 0

i swear to god i'll paypal 5 dollars to whoever can make these loving labels update i am absolutely furious and i'm never touching wpf again without a 1500 page loving reference book that i bought off the loving internet

Careful Drums posted:

hey is wpf like the same thing for metro/wp8 apps? because i tried that once and it looked a lot like that xaml there.

Blinkz0rz posted:

Bloody posted:

sounds like a pain in the rear end how is it any better than the old pain in the rear end way of doing it

Malcolm XML posted:

winforms suffers from being totally loving horrible for anything complex

coffeetable posted:

this bit

code:

var observable = this.WhenAny(x => x.List, m => m.Value)
    .Throttle(TimeSpan.FromMilliseconds(500), RxApp.MainThreadScheduler)

creates an IObservable, which is a posh way of saying "a sequence of objects in time". what you want is for UpdateNewList to be called every time a new object arrives. to do that, you want to subscribe to the observable, which you do by writing

code:

observable.Subscribe(x => UpdateNewList(x))

or at least, i think so. it's hard to tell w/o seeing the whole program.

as an aside, Introduction to Rx is $1.32 on Amazon and both a good read and a light read. well worth it if you're gonna be mucking about with Rx a lot.

Luigi Thirty posted:

i have only ever done this and web things which is why uis are stupid and confusing

Luigi Thirty posted:

NOPE THEY'RE ALL STILL 0

i swear to god i'll paypal 5 dollars to whoever can make these loving labels update i am absolutely furious and i'm never touching wpf again without a 1500 page loving reference book that i bought off the loving internet

coffeetable posted:

i didnt think much of code complete & the pragmatic programmer. lotta pages that say very little

ones i have been impressed by so far

• The Practice of Programming. its everything that prag prog and code complete covers, but in <300 pages. tef's standard recommendation.
  
• Working Effectively with Legacy Code. its claimed subject is fixing other people's fuckups, but in doing so it has a lot to say about how to design & structure yr programs. think suspicious dish recommended me this one
  
• The Algorithm Design Manual. best algorithms book around. fuuuuuuuck CLRS.
  
• Learn You A Haskell. not to actually learn haskell (though its v cool), but just so's you properly understand there are alternatives to OO
  

but more generally, just cultivate an interest in some pet topic and practice.

tef posted:

(yep, there's a lot of crud there but it advocates building systems out of a component architecture, but a radically simpler one based around binary streams between chunks)

Symbolic Butt posted:

seconding The Algorithm Design Manual. it's very straight to the point, the stories are fun to read and the second chapter is the best reference on algorithms in general that I've seen.

I faintly recall that someone recommended it to Pollyanna and she didn't like it

Luigi Thirty posted:

okay i rewrote it to get rid of the dumb event processing, the half-rear end singleton, and made the viewmodel non-static among other things. now i can see my totals and they update when i set them in the viewmodel!

Luigi Thirty posted:

okay i rewrote it to get rid of the dumb event processing, the half-rear end singleton, and made the viewmodel non-static among other things. now i can see my totals and they update when i set them in the viewmodel!

Luigi Thirty posted:

okay i rewrote it to get rid of the dumb event processing, the half-rear end singleton, and made the viewmodel non-static among other things. now i can see my totals and they update when i set them in the viewmodel!

Malcolm XML posted:

wow its like if u buy into the mvvm pattern wpf is great!!!!

Shaggar posted:

the only javascripts you should use are jquery and knockout. and even knockout is only for weird edge cases where you don't have a web application server to write your pages for you.

Shaggar posted:

the only javascripts you should use are jquery and knockout. and even knockout is only for weird edge cases where you don't have a web application server to write your pages for you.