Ali Özgür

(Turkish)

Son günlerin gündemde tutunamayan konusu Fatih Projesi ciddi vaadleri olan ve ülkemizin geleceğini yakından ilgilendiren bir proje. Bu proje kapsamında yapılması planlanan çalışmalar şu 5 ana başlık altında toplanmış

1. Donanım ve Yazılım Altyapısının İyileştirilmesi
2. e-İçeriğin Sağlanması ve Yönetilmesi
3. Öğretim programlarında Etkin BT Kullanımı
4. Derslerde BT Kullanımı İçin Öğretmenlere Hizmetiçi Eğitim
5. Ağ Altyapısı ve Geniş Bant İnternet Kullanımı ile Bilinçli ve Güvenli BT Kullanımının Sağlanması

Yesterday Yalla Apps contacted with me and asked for an interview. The interview was conducted to get more insight on the WP7 developer community and thier opinions about different platforms.

Here is a stackoverflow question which describes the issue very well

I have some code that needs to run after the a UIWebView finishes loading a document. For that I’ve set the UIWebView’s delegate to my controller, and implemented the webViewDidFinishLoading method.

This gets called multiple times, depending on the type of page to load. I’m not sure if it’s because of ajax requests, requests for images, or maybe even iframes.

Is there a way to tell that the main request has finished, meaning the HTML is completely loaded?

Or perhaps delay my code from firing until all of those events are done firing?

Some people say that “UIWebView must die”. Yes I actually agree with them. UIWebView loads slower than Safari, it is hard to use and it does not expose some core methods. For example you can not get source of the loaded HTML page or the document title with a regular method call. But it has its strenghts like thestringByEvaluatingJavaScriptFromString (MonoTouch equivalent is EvaluateJavascript) method. With this method you can perform some of the missing core functions.

This post is the winner of The CodeProject Android Development Competition

Oh well… It seems that we are making the same old mistake again. It is hard to articulate my feelings about the trending tablet business. It feels like we are traversing the same path again. To be more clear I guess we again do what we did in the past when the PC business was in its early days.

I’ve been recently working on a smart client (WinForms) application backed by Entitiy Framework 4 (EF4) on Visual Studio 2010. In this blog post I will try to give you some tips regarding some limitations and points to be careful about EF4.

Based on one of my articles Artem Smirnov posted a question about how to test a Repository(DAL) method in a project using Nhibernate as ORM. Here is his question

“I wanted to unit test a similar, but more common, problem: a Repository method. I.e., create a test Order for a particular date, and test that the FetchOrdersByDate method returns this order if the date matches. My guess was that I could just create an Order, attach it to the session without saving it to the database, then somehow stub the database and make NH fetch it from the cache. After doing a lot of search, I discovered that this is impossible, so I had to hit the database for every test. Given that NH looks extremely flexible, i.e., Interfaces everywhere, this is kind of strange..”

Here is my answer