Friday, May 30, 2008
It is also an important step for the Dynamic Language Runtime as there are now two major languages (plus Managed JScript) that run on top of it.
As well as generating the 'xap' files for deployment, it will also package them dynamically running as a server - so you can test your dynamic apps from the filesystem without having to repackage them after every change.
The new update fixes the situation where Chiron wouldn't work with Firefox (when serving locally - and mainly on the Mac) because of an IPv4 / 6 binding issue.
Wednesday, May 28, 2008
Monday, May 26, 2008
Tuesday, May 20, 2008
Monday, May 19, 2008
Sunday, May 18, 2008
Friday, May 16, 2008
Thursday, May 15, 2008
Friday, May 09, 2008
standalone desktop Silverlight applications.
Thursday, May 08, 2008
Wednesday, May 07, 2008
OpenTK needs no setup. It runs on Linux and Windows and works with all .Net languages, like C#, VB.Net and IronPython. Best of all, it is - and will remain! - free for both commercial and non-commercial projects.
This is OpenGL like you've never seen it before.
Tuesday, May 06, 2008
In order to use a similar API, Harry has written a module called 'ipypulldom' that wraps .NET functionality:
Monday, May 05, 2008
- Amazon SimpleDB (AWS) with IronPython and Resolver One
- IronPython in Action Progress (with WMI Example)
- Resolver One 1.1.1 Features Announced
- Resolver One and the Python Magazine
The second screencast has also just been added to ShowMeDo:
Intro to the IronPython Flying Circus
A 200 level presentation by Sarah Dutkiewicz
Come see taunts with an outrageous French accent, knights who say Ni,
Vikings who like Spam, and lumberjacks who like to press wildflowers as we
explore some basics behind IronPython, the .NET implementation of the
Python programming language.
We’re pleased to announce the release of IronPython 2.0 Beta 2. In addition to the usual bug fixes (~25 reported on CodePlex and ~50 reported internally), this release has been partially focused on improving the performance of IronPython, in particular startup perf. Another focus of this release was improving upon our traceback support which had regressed quite a bit in 2.0B1 and had largely been broken in the 2.0 Alphas. Our traceback support should now be superior to that of IronPython 1.1!
We’ve also made a minor change to our packaging by adding a Microsoft.Scripting.Core.dll in addition to the Microsoft.Scripting.dll that’s been around since the start of 2.0. We are doing this purely as an architectural layering cleanup. Microsoft.Scripting.Core contains DLR features that are essential to building dynamic languages. Microsoft.Scripting will contain language implementation helpers that can either be re-used (e.g., BigInts) or copied (possibly e.g., the default binder). This process is all about our work to get the DLR architecture right and shouldn’t have any noticeable IronPython impact except that there’s now one more DLL to include in any package.
Jimmy Schementi has posted a very thorough (if slightly belated) explanation of why those changes were made, including explaining some of the details of packaging dynamic applications for Silverlight 2.0.
DIC is an interactive environment for working with SAP Business 1 through the COM API:
why he wrote DIC:
If you have been involved with SAP Business One implementation projects, I'm sure you have at some point faced a situation where you needed to quickly modify a large amount of records in the customer's database. Here are some real-world examples from my past projects:
- Change the default warehouse for 2,000 items in the database
- Remove 4,000 items that were imported with an incorrect item number
- Remove a few thousand items (from a total item count of 50,000) that have not been used in any transaction
- Copy the account settings from one itemgroup to all the rest of the item groups (about 200 of them)
Being familiar with relational databases, I've pretty often found myself mumbling something like this:
"Dude, if they just would allow me to run a simple SQL update query in the database. This task would be completed in a few seconds."
Well, this is prohibited by SAP for rather obvious reasons. We need to get by with somewhat less powerful tools. (! *cough*)
I chose Python as the language of DIC because Python has a very clear, human-readable syntax and it also lets you interact with live objects as you build your code.