أرشيف لـديسمبر, 2008

كل سنة وانتم طيبين اولا سنة سعيدة عليكم 🙂

كل ماقرا فى سى بكون ممتن جدا ان مش بضطر استخدمها فى معظم الوقت

الكتاب The Definitive Guide to Linux Programming كتاب فوق الممتاز اضافلى كتير جدا و بيحققلك رسوخ كبير لاغنى عنه لأى مبرمج شبكات بيناقش جزئيات نظرية الأول عن المصطلحات الهامة وهيكلية الخادم/العميل وتصميم بروتوكولات خاصة واهم القرارات اللتى يجب عليك اخذها فى التطبيق ..كطريقة الإتصال ، الهيكيلية 2-tier او 3-tier ،بالنسبة للعميل monolithic , modular ، وسيناريوهات خاصة بالخادم هل سيتم تحويله ل daemon وافضل طريقة لمعالجة اكثر من عميل وكيفية التعامل مع اللوج وغيرها وجزئية عن البرمجة الدفاعية وايضا دراسة لتطبيق شبكات برنامج دردشة مشابه ل digichat بس كdesktop application

وجزئية خاصة بتأمين الإتصال و الauthentication وتوقيع الداتا وبعض المشكلات الأمنية الشائعة (هجومات معتادة ، BOF، .. الخ)

تطبيق آمن (لم انهيه)

ملحق عن IPv6 (لم انهيه)

ازاى لسه ؟

Posted: ديسمبر 27, 2008 in General

حاجات مستغربها جدا مثلا ناس لسه للآن مش فاهمة يعنى ايه .NET وايه اللى وفرته

http://www.arabteam2000-forum.com/index.php?showtopic=181747

ولسه فى ناس فاكره انها لو عملت سوفتوير باللغة العربية او موجة للعرب فقط دا كفيل بنقل العرب للصدارة و هيجذب الأجانب للعروبة والإسلام ووو (على سبيل المثال المتحمسين للغة ج )

لسه فى ناس متعودة على وجود مصمم الواجهات فى ال IDE وبتشتكى من كدا(كنت وربنا عافانا)

فصل الكود عن الواجهة (بصورة عامة) مفهوم مهم للمبرمجين وحتى لو توافر المصمم فمش المفروض انه يتخطى حدوده داخل الكود

ازى لسه فى مليون ويب فريمورك للجافا وكلهم فى اتجاهات مختلفة ؟ امتة هيتعلمو من Rails, Merb ؟

انهيت pyhappymapper كبورت ل HappyMapper لتحويل ملف XML لpython objects

http://programming-fr34ks.net/smf/articles-12/happymapper-(xml-to-python)/

احمد مصطفى هيرجع قريب بعد مافجر الجهاز

نختم بسؤال هل جافا هى الكوبول التالية ؟

Merb gets merged into Rails 3!

Posted: ديسمبر 25, 2008 in General, Scripting
الوسوم:, , , , , ,

مفاجأة غير متوقعة تماما ولكن حركة استراتيجية ممتازة


It’s christmas, baby, and do we have a present for you. We’re ending the bickering between Merb and Rails with a this bombshell: Merb is being merged into Rails 3!

We all realized that working together for a common good would be much more productive than duplicating things on each side of the fence. Merb and Rails already share so much in terms of design and sensibility that joining forces seemed like the obvious way to go. All we needed was to sit down for a chat and hash it out, so we did just that.

What this will mean in practice is that the Merb team is putting their efforts into bringing all of the key Merb ideas into Rails 3. Yehuda Katz will outright join the Rails core team, Matt Aimonetti will work on a new evangelism team, and Carl Lerche and Daniel Neighman (hassox) will be co-starring the effort to bring all this over. We’ve immortalized the merge with plaque page at rubyonrails.org/merb.

What’s being brought over? Some of the key ideas that they’ll be taking with them from Merb into Rails 3 are:

  • Rails core: Yes, Rails is a full-stack framework and will remain so, but there’s no reason we shouldn’t also make it possible to run with less than the full monty. Rails 3 will make it easy to run just a bare minimum and then allow you to opt in just the stuff you want, if that’s necessary for your particular situation. Think “rails myapp—core” (and “rails myapp—flat”).
  • Performance optimizations: Merb has a lot of Rails pieces rewritten to be faster. We’ll be bringing all that good stuff over. We’ll also bend the architecture in the places where that’s necessary for a big yield. In short, Rails 3 will get all the performance attention that the Merb guys are known for.
  • Framework agnosticism: Rails will always have a default answer to every question within the stack. If you don’t care about testing frameworks, you’ll get test/unit. If you don’t care about which ORM, you’ll get Active Record. But some people do care and want something else. Some people want RSpec for testing, others want to use Sequel or Data Mapper for ORM, others again prefer Haml for templating, and some might prefer jQuery for Ajax. All these people should feel like Rails is welcoming them with open arms. Yes, we’ll have a default, but we shouldn’t have any form of discrimination against alternatives.
  • Rigorous API: Too many plugins break when Rails is updated because it’s not clear where they can safely hook into the internals and when they’re monkeypatching and should expect things to break. The Merb guys committed to a public API with tests to ensure that it wouldn’t break. They’ll bring over that line of thinking and give Rails 3 a tested and documented API for extensions that won’t break willy-nilly with upgrades.

This is not a big bang rewrite It’s important to understand, however, that this is not a “big bang” rewrite of Rails. We’re far beyond the time when we could just throw out everything and start over. This is going to be a progressive improvement of Rails that’ll carefully judge new initiatives on their impact on backwards compatibility as well as their general utility.

I’m sure there’ll be some parts of Rails 3 that are incompatible, but we’ll try to keep them to a minimum and make it really easy to convert a Rails 2.x application to Rails 3. The Merb guys will also be working hard on giving existing Merb users a manageable upgrade path to Rails 3. We’re working with lots of ideas including allowing existing Merb controllers to be mounted alongside new Rails 3 ones. We’ll see how it all plays out, but play out it will.

Also, the Merb guys aren’t just abandoning the existing Merb user base and their applications. They’ll still be doing bug fixes, security fixes, and work on easing the upgrade path to Rails 3. This will all progress in a nice, orderly fashion.

The timeline Rails 2.3 is just around the corner. We hope to wrap up and release in January. It’s a blockbuster release packed with goodies to the tilt. But as soon as that’s done, all eyes will be on Rails 3.

The probably-overly-optimistic goal is to have at least a beta version ready for RailsConf 2009 in Las Vegas. Who knows if we’ll make it, but we’ll certainly have made tons of progress on it by then.

So all of these changes are pretty much effective immediately. We’ve already started the collaboration and we’ll be rolling out a bunch of public initiatives announcing the concrete elements of the work under the Rails 3 milestone very shortly.

No hard feelings, just kumbaja This is quite a dramatic turn of events. We went from testy relations to coming together in not very long at all. But I’ve been incredibly positively surprised at how well everyone on both sides have been gelling behind the scenes. The more we talk, the more we realize that we want the same things. And in the few cases were we do care about something different, it’s usually complimentary.

I really hope that everyone within both communities will deal with this news as gracefully as the key contributors from both camps. Let’s just wipe the slate clean on anything that has gone before and cherish that we can now move forward in unity instead of as fractions of the same ideas.

Rails 3 is going to kick ass.

http://weblog.rubyonrails.org/2008/12/23/merb-gets-merged-into-rails-3

http://rubyonrails.org/merb

http://yehudakatz.com/2008/12/23/rails-and-merb-merge/

الجديد فى كتاب البايثون

Posted: ديسمبر 20, 2008 in General
الوسوم:, ,

اخيرا رسينا على الفهرس

تم الغاء فصل wxPython ربما فى التحديثات او كجزء منفصل وبكدا هيكون الرئيسى هو استخدام PyGTK ومعاها دراسة Gqamoos (هتغطى على حاجات زى ال treeview اللتى لم يتم ذكرها)

بالنسبة PyQt (سيتم اضافة الtutorial المترجمة مع الكتاب)

تم اضافة جزئية عن tKinter (كيفية انشاء واجهة بسيطة مثل Gladizer وبعض المفاهيم العامة الخاصة بها)

تم انهاء فصل الشبكات (انشاء سرفر وكلاينت بسيط ، سرفر لمعالجة اكثر من عميل ، تطبيق دردشة ، تطبيق مشاركة الملفات)

تم حذف مقدمة Zope واستبدالها بجزئيات عن pylons, webpy,Grok

تم حذف فصل Postgres ودا بسبب وجود شرح كامل على ال DB API فى جزئية MySQL (ربما يتم اضافة Storm مكانها)

اضافت جزئية عن twisted, soup

تطبيق عن ال screen scraping

تم اضافة فصل ال Modules/Packages

وبعض الإضافات الأخرى

Qamoos#

Posted: ديسمبر 18, 2008 in General
الوسوم:, , , ,

وصلنى ايميل بيطلب عمل المثال الخاص بالقاموس GQamoos بإستخدام C#, GTK

تم استخدام Monodevelop و stetic لإنشاء المثال

للتحميل اضغط هنا

الحمد لله بعد نجاح الإصدار الأول قررت ان يكون فى إصدار تانى مع تحسينات للتصفح اونلين

فى الإصدار التانى هيتم اضافة برمجة الواجهات الرسومية وتم انهاء ال 3 اجزاء Gnome, Qt, wx
وإضافة دراسة rSQLiteGUI (معتمدة على ال gtk وال active records كتطبيق)

ازاى اقدر اساعد؟
لسه فى مكان لأساسيات threading, networking وكتابة ال extensions وبعض الإضافات على rails
اذا تقدر تنهى التنسيق ومراجعة اللغة ياريت تراسلنى

عيد سعيد

Posted: ديسمبر 8, 2008 in General
الوسوم:,

كل سنة وانتم طيبين والى الله اقرب