The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Mostly he's been screaming abuse on twitter @leppie
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DDEthel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
I have restarted work on a game development studio I started some time ago. I have decided to make it completely WinForms based, (as WPF is very confusing and has a very steep learning curve, and I don't have the time to really learn it right now) and it will use MonoGame as the backend engine.
Here are some of the features I have in mind:
* MonoGame backend engine * WiX, NSIS, and InnoSetup bindings * WYSIWYG Designers (2D/Tile Based designer will be based on code from tIDE[^], 3D designer will (hopefully) be in a release after v1.0) * Code autocompletion (obviously) * Integration with Git, Subversion, and Mercurial * Extensible (ICSharpCode.Core) * MSBuild based project file format. * Possible integration with PyGame * Macro IDE * NuGet integration * Run on a USB Flash Drive (like SharpDevelop) * Debugger
I am open to any other ideas for AddIns, backend engines, designers, etc. I may eventually port this to WPF if I get enough time, but that will likely be in the future.
I will post a link here when I get a repository created, unless you guys don't want me to.
UPDATE: Due to popular demand, I have decided to bite the bullet and learn WPF. Wish me luck in getting VS to cooperate.
WPF is easy!! I just gave a tutorial to colleague! :P
What you should try to learn (in this order)
1. Basic controls: - ContentControl (ex: Button, RadioButton, CheckBox, ...), ItemsControl (ex: ComboBox, TabControl, ListBox) 2. Basic UI Brushes, margin, Padding, 3. panels (Grid, StackPanel, DockPanel (klike WinForm anchro) Canvas (like WinForm XY position) so far just like winform, but cuter (and easier!! :P)
Why WPF Rocks: 4. Basic Data binding: make a business object, bind it to a view, behold, learn minimal styling and templatingg, behold! 5. Bind a list of business data to a business view, behold! Validation
6. Advanced data template
you could almost do that of your own, I'm sure you could find 5' video on each topic. When you mast all those 6 point (each easy on its own) you are good enough with WPF!!!
My programming get away... The Blog... Taking over the world since 1371!
there's nothign that WPF can do that Winform can't. So can't really justify "learning curve" (Very steep)
This said, I code WPF everyday now and like it's syntax - Microsoft however did not make much advancement other than everything that's syntactic nicety (like WPF ability to define UI in Xaml or XML tags like you do in ASP.NET)
same can be said for WCF, with socket, you can code up everything in a few days from encryption/compression to serialization of object graphs to load balancing - and you can debug all on debugger. With WCF, you need Memorize config settings and COMPLY to "Best Practice" set forth by M$
M$ didn't really have us developers in mind last couple years.
as WPF is very confusing and has a very steep learning curve
I had the same feeling before I learned WPF, but if you wrestle through a book, you'll be up and running in less then a week. (Ok, if you can afford the time, if you only work on it after office hours it's of course longer) .
My advise is not be afraid of WPF, I found it confusing at first too, but then I figured it was not that different from designing a webpage and of I went.
I likely will. Thanks for the offer for help. Right now I am just getting the layout of the project set up (e.g. creating the projects/creating the files/stubbing out the methods/etc.) I will actually start writing the code when all of that is finished. Makes it easier to write the code without having to switch between three or four files while coding.
I must admit, my thought was actually that if you aren't comfortable writing in WPF, then there's no reason you shouldn't use Windows Forms. There are a lot of theme engines for WinForms that would allow you to redesign how your application looks, and it removes one of the barriers to entry for you.
I was brought up to respect my elders. I don't respect many people nowadays.
No other social or 3rd party actions similar to Follow, Reply, Retweet and Favorite may be attached to a Tweet.
I guess that means that if you made a "retweet" button that posted to Twitter AND other social networks (e.g., Facebook, App.net), you'd be in violation of the API requirements and your account could be disabled. That seems pretty anti-competitive to me; I really hope somebody sues Twitter for their ridiculous requirements.
May be attached to a Tweet? What does that even mean? I guess they don't want someone to basically start hijacking tweets? You think you're tweeting but they are only going to "twinter" my new knockoff.
Well, the requirements are geared toward developers like me who are displaying tweets from their company inline on their company's website (imagine a feature on a homepage that displays the most recent tweets).
They want very strict control over exactly what that inline display looks like, and what can be done with it (e.g., you must have a button to allow a user to reply to the tweet, but that button can't also allow the user to post that reply to some other site).
Say you are a member of both Twitter and Facebook, and my company posts an interesting video (say, Mr. Rogers fighting Chuck Norris) in its Twitter feed, and we then display that Twitter feed on the company website (say, NorrisVsRogers.com). Why shouldn't we create a button that will allow you to simultaneously post that video to your account on Twitter and Facebook (maybe when it posts to Facebook it automatically links back to the Twitter post too), if you so choose? And how would that compromise the tweet?