I'm involved in two HTML/JS project. One is a Win8 game:
http://apps.microsoft.com/webpdp/app/game-dev-tycoon/1159e78f-b270-4839-bef7-3146bcfd3f99 The game uses a bunch of libraries, most importantly CreateJS and jQuery. Here is a list: - CreateJS <http://createjs.com/> - jQuery <http://jquery.com/> - jQuery Timeago <http://timeago.yarp.com/> - jQuery SimpleModal <http://simplemodal.com/> - LINQ for JavaScript <http://linqjs.codeplex.com/> - Mersenne Twister<http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html> The other app is our new NovaMind Win8 app: http://apps.microsoft.com/webpdp/app/novamind/d1c809ab-90ab-4ae8-8d6e-a159ae90f8d8 For NovaMind we created our own canvas library and animation library. The only other libs we use are: - zip.js <http://gildas-lormeau.github.com/zip.js/> - Json2Xml <http://goessner.net/download/prj/jsonxml/> The rest is custom code. I blog a little about our experiences here <http://www.patrickklug.com/>if you are interested. Overall, once I got over some preconceived ideas about JavaScript I found it extremely easy to move to HTML/JS and with tons of examples available online it's generally rather easy to implement something you have envisioned. CSS can be tricky for sure and some seemingly ordinary things like centering content horizontally and vertically can be a real headache but apart from that it's pretty good. Good latest example is our new radial menu<http://www.youtube.com/watch?v=ygbFq-oIEjk#t=1m12s>. I'm convinced that it would have taken us way longer to implement anything like that in WPF and the performance would probably be much worse. With companies like Teleric pushing HTML5 controls <http://www.kendoui.com/>heavily it's even becoming more viable for LOB apps to move to HTML in my opinion. Anyway, I couldn't be happier with the move to HTML/JS. On Wed, Aug 29, 2012 at 11:02 AM, Greg Keogh <[email protected]> wrote: > Thanks chaps, sorry for the late reply. It turns out I didn’t need to > “pass” the command on from the dialog to the main window for this > particular case, but I’m sure I will at some time in the near future and > this issue will return and I’ll have to find an elegant way of doing it.** > ** > > ** ** > > Context menus are general problem in WPF due to their quirks in binding > and commands. I haven’t looked into it, but they don’t live in the control > tree in the usual way. Same with DataGrid columns and some other bits and > pieces.**** > > ** ** > > Carl, I ran some experiments and removed PlacementTaget from dozens of my > menus and they all continued to work, except some attached to a ToolBarTray > which required this element:**** > > ** ** > > CommandTarget="{Binding Path=PlacementTarget, RelativeSource={ > RelativeSource FindAncestor, AncestorType={x:Type ContextMenu}}}"**** > > ** ** > > So for years now I have assumed that I needed that line on my menus, > probably due to early problems like the one with ToolbarTray, but it turns > out most of them aren’t needed. I have globally removed the unnecessary > elements and it’s nice to remove XAML clutter. So thanks for the reminder > to look into that issue.**** > > ** ** > > Patrick, what tools/kits are you using to write HTML/JS?**** > > ** ** > > Greg **** > > ** ** > > _______________________________________________ > ozwpf mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > >
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
