Ankarada Android geliştirici günleri düzenlecek. Bu güzel etkinliği kaçırmamanızı tavsiye ederim. Etkinlikte konuşmacı olmak ve bildiri göndermek isteyenler için etkin katılım çağrısını aşağıda bulabilirsiniz.
21 / 22 Mayıs tarihlerinde ODTÜ Kültür ve Kongre Merkezinde gerçekleşecek olan Android Geliştirici Günleri‘nde geliştiriciler açısından mobil dünya ve Android teknolojileri üzerine sunumlar, eğitimler ve çalıştaylar yer alacaktır.
Android Geliştirici Günleri ile ülkemizde Android’e daha çok dikkat çekmek ve Android Geliştirici Günlerinin bu küresel pazardan pay almak isteyecek geliştiriciler ve girişimler için bir kıvılcım ve ilham kaynağı olmasını amaçlıyoruz.
Android ve Mobil teknolojiler konusunda bilgi ve tecrübelerinizi paylaşmak isterseniz, sizi Android Geliştirici Günleri’ne aşağıdaki konular başta olmak üzere etkin katılımcı olarak davet ediyoruz. Bu konuların dışında yeni konu ve tekliflere açığız. Ayrıntılı bilgi organizasyonun web sitesinde yer almaktadır.
  • Mobil Dünya
    • Mobil Dünyanın Geleceği
    • Gelecek Mobil Teknolojiler
  • Android İşletim Sistemi
    • Ice Cream Sandwich
    • Gelecek Versiyonlar
    • Farklı Mimarilerde Çalışabilirlik
    • Farklı Alanlarda Kullanım (Endüstri, Savunma, Ev Elektroniği)
  • Android Uygulama Geliştirme
    • Uygulama Geliştirme Pratikleri
      • Farklı Ekranlarda Çalışabilme
      • Sistem kaynaklarını verimli kullanma
      • Kullanıcı Arayüzü Tasarımı, vb.
    • Android SDK
    • Tablet Uygulamaları
  • Tüm Mobil Platformlar için Uygulama Geliştirme Altyapıları
  • İletişim Çözümleri
  • Mobil Eğitim
  • Uygulamalardan Gelir Elde Etme
  • Mobil Ödeme
  • Güvenlik
  • NFC
  • Google TV
  • HTML5 (Mobil Web Uygulamaları)
  • Oyun Geliştirme
Android Geliştirici Günleri  - www.androidgelistiricigunleri.com
Android Developer Days - www.androiddeveloperdays.com

                               İOS PROGRAMLAM(objective C)

Ben bu programlamaya girerken inanın ne yapacağımı çok düşündüm ama C++ orta seviyede bildiğimden bunuda yaparım diye düşündüm.ve kodlabın objective C kitabını aldım ve okudum .. Gördüğüm kadarıyla kitabdaki C(objective C)  ile C++ kütürhaneleri olarak yakın diyer yönlerden gördellik olsun grafik veyahut diğer donanımlardan olsun  çok farklı kütüphaneler vardı.Bundada  kategoriler çoktur. Yarışmalar TÜRKİYEDE biraz kısıtlıdır yine Odtü de yapılmak tadır \/


                     https://www.facebook.com/events/151378298320798
                     http://obss.com.tr/2012/05/18/odtu-programlama-yarismasi-platin-sponsoruyuz/



               WİNDOWS PHONE PROGRAMLAMA (C #)-ENGLİSH


 1->Hello World


I was really excited to see the upcoming release of Windows Phone 7. This is truly a great answer from Microsoft to the rest of world. Apple iOS which is currently the most popular mobile platform, Google Android, BlackBerry, etc. were taking pace with the new technologies and Microsoft was still battling to find a space in the mobile world. Of course, Windows Mobile operating system was popular some time before but the smart phones were not really popular and on aging, the platform itself is being outdated in front of other new age platforms.
All programs for Windows Phone 7 can be written in .NET managed code. Currently C# is the only programming language supported. The tools for Windows Phone 7 can be downloaded freely from Windows Phone 7 website. It includes:
  • Visual Studio 2010 Express Edition
  • XNA Game Studio 4.0
  • On Screen Phone Emulator
Windows Phone 7 can be programmed mainly using XNA FrameWorks and the popular Silverlight platform. XNA is used for high performance games (usually 3D games) and Silverlight is usually used for the 2D graphical applications.
Windows Phone 7 contains the stripped down version of Silverlight 3. Microsoft has avoided the Silverlight features which are not really compatible with the Windows Phone 7 platform. The animations for the programs can be down using the Microsoft Expression Blend.
Ultimately, it is the programmer’s responsibility to choose which platform should be used for programming Windows Phone 7 application.
Windows Phone 7 contains the Azure services to access the cloud service. One of the examples is XBox Live (runs on cloud). Programs are location aware and can access data through Bing, social networking websites, etc.
Windows Phone 7 features Multi-Touch screen with 3 navigation buttons. Back (like the back button in the browser. This will terminate the application), Start button (to navigate to home screen), Search. Currently the native resolution of a Windows Phone hardware is 400×800. Also 320×480 resolution screen is expected. The hardware component features are:
  • Wi-Fi
  • Camera
  • Accelerometer – to detect the movement of the phone
  • GPS based Location
  • Vibration (programmable)
  • FM Radio
  • Push notifications
Once after downloading the tools, you can either start programming in the Visual Studio Express Edition or Visual Studio 2010 (if it’s already installed).
Here I’m demonstrating a basic Windows Phone 7 application in Silverlight. The code is only tested in Simulator not on any real hardware.
Create the new project using the Wizard:

The basic layouts will automatically be created using the XAML and the corresponding C# source will also be created. Notice that the standard controls available in the Windows phone 7 are not similar to the controls available in Windows. They’re transparent and designed for the phone. The entire theme is based on black. You can simply start debugging/execute the code using the emulator available. It’s better not to close the emulator Windows frequently as it may take time to start it up. The program will automatically be deployed and starts in the emulator.
The user actions like home screen, back button, search, etc. will end up the application by default. The application must manage itself to restore the previous state if necessary on quit. On startup, Windows phone 7 emulator will ask for the basic setup. It’s very easy to set it up and this is a one time process. The emulator can be used for changing the orientation between portrait and landscape. The buttons are available on the right top corner of the emulator window on hovering the mouse.
The demo application loads the posts from this blog and displays it, with tap on the post titles listed, the article will be loaded on webBrower.
The layout and controls are as follows:

Loading the Feed Items

The Silverlight application had put a lot of restrictions in accessing the APIs and resources of other websites. Loading news feed (RSS/Atom) is not really painful using the C# code. Silverlight supports asynchronous read operations for web requests. SyndicationFeed class is not supported by default. Basically, it’s safe to add this assembly to the project (System.ServiceModel.Syndication.dll). You can browse to Windows SDK folder, locate and add the same assembly in the “Client” folder.
private</span /> void</span /> buttonRefresh_Click(object</span /> sender, RoutedEventArgs e)
{
    //</span /> Load the feed items
</span />    LoadFeedItems();
}

private</span /> void</span /> LoadFeedItems()
{
    //</span /> Asynchronously load the feed content.
</span />    WebClient client = new</span /> WebClient();
    Uri address = new</span /> Uri(&quot;http://</span />feeds.feedburner.com/sharingmythoughts&quot;);
</span />    client.OpenReadCompleted += client_openReadComplete;
    //</span /> Add the callback on completion
</span />    client.OpenReadAsync(address);
    webBrowser.Visibility = Visibility.Collapsed;
    buttonBack.Visibility = Visibility.Collapsed;

}
private</span /> void</span /> client_openReadComplete(object</span /> sender, OpenReadCompletedEventArgs args)
{
    try</span />
    {
        listBoxPosts.Items.Clear();
        //</span /> try to load the result in the XML reader.
</span />        //</span /> Exception may occur if the request is failed
</span />        XmlReader reader = XmlReader.Create(args.Result);

        //</span /> Syndication Feed is not supported by default.
</span />        //</span /> It's safe to add this assembly.
</span />        SyndicationFeed feed = SyndicationFeed.Load(reader);
        Items = feed.Items.ToArray();
        foreach</span /> (SyndicationItem e in</span /> Items)
            listBoxPosts.Items.Add(e.Title.Text);
    }
    catch</span />
    {
        MessageBox.Show(&quot;Error downloading feed&quot;);
    }
}

Navigate to the Base URL on Tapping

private</span /> void</span /> OnTapItem(object</span /> sender, MouseButtonEventArgs e)
{
    if</span /> (listBoxPosts.SelectedIndex >= 0</span />)
    {
        buttonRefresh.Visibility = Visibility.Collapsed;
        buttonBack.Visibility = Visibility.Visible;
        webBrowser.Visibility = Visibility.Visible;
        Uri address = new</span /> Uri(Items[listBoxPosts.SelectedIndex].Id);
        webBrowser.Navigate(address);
    }
}
The mobile theme I’ve enabled for this blog is not really working well. The WPTouch theme I installed seems to not really identify Windows Phone 7 user agent string. (Amazingly, it works well when I load using Intenet Explorer App in the Phone 7.)

Adding Support for Orientation

By default, the wizard creates the application with Portrait Orientation. The page content will not be arranged according to the current orientation if we don’t add support for it. Change the orientation to Portrait/Landscape/PortraitOrLandscape in the XAML file:
SupportedOrientations="PortraitOrLandscape" Orientation="Portrait"

Handling Orientation Events

It’s possible to override OnOrientationChanged function do if we need to manage something else other than the default orientation change support implemented in the base class. For the simple applications using controls, we can use the standard alignment support provided by the grids and panels. The controls will be perfectly aligned according the vertical and horizontal settings of the controls.
<</span />Grid</span /> x:Name</span />="</span />ContentPanel"</span /> Grid.Row</span />="</span />1"</span /> Margin</span />="</span />12,0,12,0"</span />></span />
    <</span />ListBox</span /> Margin</span />="</span />0"</span /> x:Name</span />="</span />listBoxPosts"</span /> MouseLeftButtonUp</span />="</span />OnTapItem"</span /> /</span />></span />
    <</span />phone:WebBrowser</span /> Margin</span />="</span />0"</span /> x:Name</span />="</span />webBrowser"</span /> /</span />></span />
<</span />/</span />Grid</span />></span />
<</span />Button</span /> Content</span />="</span />Refresh"</span /> Height</span />="</span />71"</span /> HorizontalAlignment</span />="</span />Right"</span /> 
 Margin</span />="</span />320,145,0,0"</span /> x:Name</span />="</span />buttonRefresh"</span /> VerticalAlignment</span />="</span />Top"</span /> 
 Width</span />="</span />160"</span /> Click</span />="</span />buttonRefresh_Click"</span /> /</span />></span />
<</span />Button</span /> Content</span />="</span />Back"</span /> Height</span />="</span />71"</span /> HorizontalAlignment</span />="</span />Left"</span /> Margin</span />="</span />0,145,0,0"</span /> 
 x:Name</span />="</span />buttonBack"</span /> VerticalAlignment</span />="</span />Top"</span /> Width</span />="</span />160"</span /> 
 Click</span />="</span />buttonBack_Click"</span /> /</span />></span />
Override the OnOrientationChanged if more flexibility is necessary:
protected</span /> override</span /> void</span /> OnOrientationChanged(OrientationChangedEventArgs args)
{
    //</span /> do your code. If base is not called, then the orientation will not be changed
</span />    base</span />.OnOrientationChanged(args);
},
KAYNAK \/
 
http://www.codeproject.com/Articles/116805/Programming-Windows-Phone-7-Hello-World
 
 
 
2->Windows Phone 8 - A Restart
Written by Mike James   
Thursday, 21 June 2012 00:00
Microsoft has announced some of the details of the new Windows Phone 8 system - and if you have been following the plot there are few surprises. The main thing is that the upgrade to the new Windows Kernel, and essentially WinRT, means that this is a new start and WP7 is dead.
Windows Phone 7 provided a development environment designed around managed code and Silverlight in particular. Windows Phone 8 is supporting WinRT and aligning with the other Windows 8 systems - desktop and tablet. This really cannot be a surprise to anyone, as maintaining one environment for Windows Phone and another for the rest would have been the final sign that Microsoft had lost it grip on reality. In this case moving to WinRT is the only logical thing to do.

What all this means, however, is that for the consumer, and for supporters of Windows Phone, any loyalty or support has just been rewarded by a kick in the teeth. The new system needs hardware resources that just aren't present in current handsets. In other words, if you have a Windows Phone 7 it will remain a WP7 for the rest of time  - no upgrade is available. This applies even to brand new models such Nokia's Lumia. This must be a particularly bitter pill for Nokia to swallow. After betting the farm on WP7, it now has to tell customers that everything they bought is legacy. On the plus side, Nokia seems to have a WP8 prototype ready.

WP8event

This situation is made worse by the simple fact that, while a WP8 phone will run old WP7 Silverlight and XNA applications, any new WP8 apps won't run on a WP7 phone. So not only are WP7 phones not upgradable, they are essentially not even going to be able to get any new apps tailored for WP8.
The only concession is that when WP8 ships Microsoft will make available a final upgrade to WP7 - WP7.8  - which will bring the appearance of the new WP8 Metro- based interface and some of the new facilities. This might make some users feel better ... until the killer WP8 app becomes available and they discover they can't run it.
The new OS is based on Windows NT core rather than Windows Embedded Compact. This brings a unity with the  desktop and tablet operating environment - NTFS, network stack, DirectX and device drivers are all the same across all of them.
WP8 does have some interesting hardware requirements including multicore processors, up to 64, and built-in NFC. However, you can't help but wonder how much of this extra processing power is needed to enable the dual support of managed code and Silverlight and the new WinRT. The promise that WP7 apps would run on WP8 might just be a very expensive promise. The new screen resolutions are 1280x768, 128x720 and the old 480x800.
From a developer's point of view the situation still isn't' clear. It seems that the tools are the same but the APIs are identical to the desktop version. While XNA and Silverlight are supported, Microsoft is giving clear advice that new apps should be written for the new APIs which are compatible across WP8 and Windows 8.  Of course, such apps will not be backward compatible with WP7 which has now been essentially cut off from the future.
The advice is to use C#, VB, JavaScript, HTML and XAML if you want to create an app but C/C++ is you want to create a game. The reason is that C/C++ has easy access to DirectX. To quote the Windows Phone blog:
"Windows Phone 8 has full C and C++ support, making it easier to write apps for multiple platforms more quickly. It also means Windows Phone 8 supports popular gaming middleware such as Havok Vision Engine, Autodesk Scaleform, Audiokinetic Wwise, and Firelight FMOD, as well as native DirectX-based game development."
One interesting point is that Microsoft are claiming that they will use "cloud compilation" to re-compile existing WP7 apps so that they run faster. This will be done without the involvement of the developer. What is more the apps are compiled to machine code which is makes them load and run faster.  This hints that more is going on in the support of Silverlight and XNA apps than just providing the environment they need to run. This is all still very unclear. It could be that Silverlight/XNA support isn't provided by hosting these subsystems on WP8 but by recompiling the managed code to run under the new API. If so this not only means that you have to focus on Metro apps - it means Metro apps are the only possibility for new projects.
The unification of WP8 and Windows 8 desktop and tablet is logical - but it was avoidable. The existing WP7 software environment could have been changed to provide all of the features of WP8 without the need for a restart and without the need to dump so many existing technologies.
The situation is a mess from the point of view of  consumers and developers. What matters now is how quickly we all forget about the past and press on with the future.

WP8event

If you would like to see the WP8 video presenation then this is available at the Channel 9 site. The section targeting developers starts at 1:29.