Primul gand pe care l-am avut cu totii in echipa a fost “in ce codam”. A fost usor sa trecem prin cei cativa termeni, care ne mai trecusera pe la ureche, si sa alegem Metoda aia *usoara* prin care tot ce era desenat pe hartie si gandit, sa devina realitate… web. La fel de usor a fost sa incercam sa scriem primele linii de cod mai complicate ca sa ne dam seama ca trebuie sa si gusti inainte sa mananci. Si ca sa trecem in planul concretului ne-am gandit la 3 metode de a face paginile sa fie dinamice (adica sa integram o comunitate, sa avem pagini context sensibile) : un framework, un cms sau php de la 0.

La capitolul framework, am constat ca este destul de popular codeigniter (http://www.codeigniter.com) si dupa vizionarea a exact doua tutoriale video cu tot cu incercat cod, am fost convinsi ca si noi putem sa dezvoltam un intreg website in 20 de minute (precum video-ul arata un blog gata in tot atatea minute). Problema cu un framework este dificultatea de a intelege cum lucreaza bibliotecile, ce trebuie sa incarci si ce module fac ceea ce zic ca fac. O problema cu care m-am  confruntat personal a fost o simpla logare. In primul rand nu exista modulul gata facut de autentificare ci trebuie supraincarcate anumite clase. In al doilea rand, voiam sa ma folosesc de cunostintele, de baza, de PHP, insa constatam ca pana si sesiunile sunt vazute altfel. Concluzia noastra este ca un framework se studiaza intai. Avantajul, totusi,  al unui astfel de framework este modelul MVC care personal mi s-a parut intuitiv si foarte aplicabil.

Frameworkul Zend a fost inca o propunere, laudat fiind si pentru ca php are module zend, insa nu am reusit sa trecem de configurarea acestuia.

Punctul doi in aceasta discutie, ar fi un Content Management System. Din pacate, tema aleasa nu se preteaza la o astfel de abordare. Sigur ca putem scrie module php pentru CMS, dar intervine si aici problema studierii sistemului. Am fi mers ori pe Joomla ori pe WordPress, care vin si cu un design gata facut si customizabil (mai putin la WordPress).

Solutia numarul 3 ne avantajaza cel mai mult, php de la 0.  Cateva minute pe w3schools si doua trei exemple de lucru cu baza de date face ca PHP sa nu para o necunoscuta. Exista mii de linii de sample code utilizabil si customizabil, apoi reutilizabil in cadrul aceluiasi proiect. Suntem obisnuiti sa codam in C, Java, Scheme, Haskel, Prolog, CLIPS chiar si Verilog, limbajul nu este o problema.  De asemenea partea de control (administratorul) nu trebuie sa fie extrem de complex, noi construim sistem, stim cum merge. Singurul dezavantaj este securitatea care s-ar putea sa ne dea batai de cap.

Cam atat pe partea de programare pe server.

În seara asta 5 manageri de echipe ne-am strâns pentru a discuta despre tehnologiile folosite de fiecare în cadrul proiectului.

Sesiunea a durat cam 2 ore și fiecare am abordat câte o tehnologie importanta în următoarea ordine:

1) Andrei – JavaScript

• a punctat foarte bine caracteristicile acestui limbaj de scripting client-side
• am discutat apoi despre utilitatea acestui limbaj
• am amintit de Firebug ca si aplicatie pentru debugging-ul codului
• Sergiu a amintit de framework-uri precum JQuery și YUI

2) Eu – PHP (bineînțeles)

• limbaj de scripting server-side
• foarte bine documentat, fiind baza pentru foarte multe site-uri din prezent
• weak typing
• PHP ca limbaj orientat obiect

3) Tibi – AJAX

• Asynchronous JavaScript and XML
• nu este un limbaj propriu-zis, folosind JavaScript pentru partea de codare și XML pentru formatul raspunsurilor. Raspunsurile pot fi și în format JSON sau plain text.
• ne-a dat un exemplu cu o apllicație cu chat și a subliniat importanta metodei asincrone de comunicare

4) Mircea – JavaFX

• RIA (Rich Internet Application)
• http://javafx.com/samples/ – pentru exemple
• un bun inlocuitor pentru Silverlight sau Flash
• foarte bun pentru dezvoltarea unui joc online, browser based

5) Sergiu – CMS-uri (WordPress)

• Content Management Systems
• ”CMS-urile sunt o serie de programe, scrise de obicei într-un limbaj server site(PHP de exemplu dar nu numai) care folosesc HTML, CSS, AJAX și altele pentru a facilita afisarea și editarea de continut într-un mod facil”
• am discutat și despre diferențele dintre CMS-uri și Framework-urile PHP și despre folosire CMS sau scriere cod de la zero.

Mai multe găsiți și pe pagina asociată transcript-ului asociat chat-ului nostru.

zAnimation is finally on codeplex. You can find it here: http://zanimation.codeplex.com/.

It’s all very basic for now, no samples or documentation yet. The code is somewhat documented. I believe experienced people will have no problem using it. It’s just a matter of selecting the right content processor, checking out my past blog entry to write a definitions file, and writing model.Play(“Walk”); I won’t be working on the documentation or samples the next 2 weeks, my exams are still more important.

There are only two master games; the experiential game and the status game.

The experiential game is the game of all beings. The status game is the game of human beings.

The experiential game, in itself, when played with others, is positive-sum; that is, everybody benefit.

The status game is zero-sum; for one to gain some other must lose.

In humanity, the experiential game is intrinsically linked with the status game.

The status game is inescapable.

Unfortunate.

I have one word for Microsoft on PDC 2009:

Awesomeness!

This years Product Developers Conference was much scaled back compared to last years but it had a great innovation in format that allowed people who didn’t attend the conference physically to still interact with it virtually.

And so the good folks at Channel 9 had built up a talkshow like studio at the PDC, with live streaming video through Silverlight, and the ability to viewers to ask questions live on air via Twitter.

This was immensely fun. I had the opportunity to ask questions to at least two technical fellows at Microsoft. Technical Fellow is the highest technical ranking at Microsoft besides of course Chief Technical Architect, a position which is currently held by Ray Ozzie.

I asked a question to Patrick Dussud, Technical Fellow and lead architect of the .Net Common Language Runtime (CLR), designer of the CLR GC and a member of the Windows Core Architechture team. The question was about how how parallel you could make the GC and what possible downsides this had.

I also asked a question to David Campbell, another Technical Fellow, from the Business Platform Division (BPD) where he manages Microsoft SQL Azure and .Net services in the cloud computing space. This question was about whether databases (e.g. SQL Server), programming runtimes (e.g. CLR) and … are merging. David mentiond that MSIL/CIL bytecode execution on SQL Server – “close to the data” – has improved performance of managed code accessing data greatly.

LINQ shows us where things are going: tighter and tighter integration. Erik Meijer, who is perhaps the lead architect of LINQ and whom I was also able to ask a question, also works for David Campbell on cloud programmability. The  new Reactive Extensions (Rx) for .Net is a pearl which we’ll see permeate .Net soon. It also builds smoothly on top of Parallel Extensions for .Net (Px), which is Microsoft’s near- to mid-term answer to the manycore challenge.

Parallel Extensions for .Net comes from the Parallel Computing Platform (PCP) team which is the team tasked with the strategic challenge posed by the massively parallel hardware of the future.

It gets better. I also asked a question to the director of NASA’s Mars programme as well as a NASA scientist.

I repeat: Awesomeness!

NASA had a marked pressence at this years PDC because they have offered up data on Microsoft’s new “Dallas” data marketplace. The attendees were apparently given 3D goggles and were viewing stereoscopic images of Mars. Pretty damned cool.

Supposedly recordings of the live Channel 9 stream will be available. I’d certainly like it.

This years PDC will be one tough PDC to outdo.

I am just loving the Tweening platform v11 by Jack Doyle. You keep on exploring the engine, it will keep on surprising you with its control, ease of use and flexibility. I used to be a big fan of Tweener before, but now its all TweenMax in my projects for the last 6-7 months or so. There a loads of features I can talk about right now which I absolutely love but may be I would explain them sometime later.

For now, I just want to say that I have now become a Shockingly Green Club GreenSock member and I would certainly encourage other developers to donate for all the effort Jack has been putting into making this platform so wonderful.

The European Commission presents a framework for encouraging the use of public private partnerships (PPPs) to meet existing and future needs for investment in public services, infrastructure and research in Europe.

The framework involves:

• increased funding for PPPs through working with the EIB, by re-focusing existing Community instruments and by developing guarantee instruments for PPP financing;
• in cases involving EU funding, better rules and procedures in order to ensure a level playing field between wholly publicly managed projects and those managed under PPPs;
• a more effective framework for innovation, including the possibility for the EU to participate in private law bodies and directly invest in specific projects;
• considering an EU legislative instrument on concessions, based on the ongoing Impact Assessment;
• improved information dissemination and exchange of best practice; including the creation of a new PPP group in which relevant stakeholders can share their concerns and further ideas with regard to PPPs.

Microsoft .NET Framework (dibaca Microsoft Dot Net Framework) adalah sebuah komponen yang dapat ditambahkan ke sistem operasi Microsoft Windows atau telah terintegrasi ke dalam Windows (mulai dari Windows Server 2003 dan versi-versi Windows terbaru). Kerangka kerja ini menyediakan sejumlah besar solusi-solusi program untuk memenuhi kebutuhan-kebutuhan umum suatu program baru, dan mengatur eksekusi program-program yang ditulis secara khusus untuk framework ini. .NET Framework adalah kunci penawaran utama dari Microsoft, dan dimaksudkan untuk digunakan oleh sebagian besar aplikasi-aplikasi baru yang dibuat untuk platform Windows.

Pada dasarnya, .NET Framework memiliki 2 komponen utama: CLR dan .NET Framework Class Library.

Program – program yang ditulis untuk .NET Framework dijalankan pada suatu lingkungan software yang mengatur persyaratan-persyaratan runtime program. Runtime environment ini, yang juga merupakan suatu bagian dari .NET Framework, dikenal sebagai Common Language Runtime (CLR). CLR menyediakan penampilan dari application virtual machine, sehingga para programmer tidak perlu mengetahui kemampuan CPU tertentu yang akan menjalankan program. CLR juga menyediakan layanan-layanan penting lainnya seperti jaminan keamanan, pengaturan memori, garbage collection dan exception handling / penanganan kesalahan pada saat runtime. Class library dan CLR ini merupakan komponen inti dari .NET Framework. Kerangka kerja itu pun dibuat sedemikian rupa agar para programmer dapat mengembangkan program komputer dengan jauh lebih mudah, dan juga untuk mengurangi kerawanan aplikasi dan juga komputer dari beberapa ancaman keamanan.

CLR adalah turunan dari CLI (Common Language Infrastructure) yang saat ini merupakan standar ECMA. Untuk keterangan lebih lanjut, silakan mengunjungi situs ECMA atau kunjungi sumber pranala di bawah artikel ini.

Solusi-solusi program pembentuk class library dari .NET Framework mengcover area yang luas dari kebutuhan program pada bidang user interface, pengaksesan data, koneksi basis data, kriptografi, pembuatan aplikasi berbasis web, algoritma numerik, dan komunikasi jaringan. Fungsi-fungsi yang ada dalam class library dapat digabungkan oleh programmer dengan kodenya sendiri untuk membuat suatu program aplikasi baru.

Pada berbagai literatur dan referensi di Internet, .NET Framework seringkali disingkat menjadi .NET saja.

.NET 2.0 saat ini juga memiliki pasangan kembar yang berjalan di Linux dan UNIX, yaitu Mono. Mono dikembangkan oleh Ximian, yang selanjutnya diakuisisi oleh Novell. Mono merupakan platform open source, berarti semua orang dapat berpartisipasi di dalam pengembangan Mono.

.NET Framework SP1 and Visual Studio 2008 SP1 on IIX
Visual Studio 2008 dan .NET Framework 3.5 Service Pack 1 tidak seperti Service Pack konvensional yang biasanya hanya terdiri dari perbaikan atas bugs atau improvement dari sisi performance. Namun Visual Studio 2008 dan .NET 3.5 SP1 memiliki beberapa tambahan fitur yang dirangkum dari hasil feedback customer. Kehadiran VS2008 SP1 juga memberikan kompatibilitas akses terhadap SQL Server 2008 RTM. SP1 memberikan fitur baru di ADO.NET Entity Framework dan dukungan untuk ASP.NET Dynamic Data (mungkin masih ingat Dynamic Data Library).

SP1 memberikan improvement di sisi Common Language Runtime (CLR), kemampuan untuk generate managed code yang memangkas waktu untuk startup & eksekusi aplikasi, kemampuan untuk memanfaatkan ASLR (Address Space Layout Randomization). ASLR adalah teknik security yang mengacak posisi dari data (executable), library, heap, atau stack dalam address space (memory). Pengacakan posisi data mengurangi potensi serangan virus/trojan yang memiliki kemampuan memprediksi data.

Beberapa pengembangan di .NET Framework SP1 antara lain:

Peningkatan performance 20-45% untuk pengembangan aplikasi yang menggunakan Windows Presentation Foundation (WPF).
Beberapa penambahan fitur dalam Windows Communication Foundation yang memberikan kemudahan bagi developer untuk akses data dan services.
Perbaikan di area data platform, seperti ADO.NET Entity Framework, ADO.NET Data Services, dan tentunya support untuk SQL Server 2008 RTM.

Sedangkan Visual Studio 2008 SP1 memberikan:

Peningkatan usabilitas bagi designer untuk membangun aplikasi yang berbasis WPF.
Dukungan penuh konektivitas dan fitur SQL Server 2008 RTM.
Komponen dan kakas (tools) Visual C++ dan Visual Basic termasuk dukungan Ribbon untuk pengembangan aplikasi MFC berbasis Office 2007.
Respon yang lebih baik terhadap Team Foundation Server (TFS) yang terkait dengan version control dan integrasi email dengan work item.
Penambahan fitur di AJAX, pengembangan website, dan dukungan penuh untuk memberikan lingkungan pengembangan yang kondusif bagi JavaScript.

Referensi: id.wikipedia.org, geeks.netindonesia.net

If your web site contain a huge number of pages and corresponding level of difficulty in keeping track of all of them, your organization rely on constant and regular web site changes, often with several people working on it and your web site contributors lack sufficient knowledge in HTML and also you need to editorially review each new page before publication. When you are using a CMS will save a lot of time, hassle and money in the long run.

A Content Management System, or CMS for short, is a collection of procedures used to manage work flow in a collaborative environment. These procedures can be manual or computer based. Or in other word, CMS is an administrative software system that allows its users, often unskilled in HTML and web development, to update, edit and create new pages on their website.

In a CMS data can be defined as almost anything – documents, movies, pictures, phone number, scientific data, etc. CMSs are frequently used for storing, controlling, revising, and publishing documentation. Content that is controlled is industry-specific. (Entertainment content differs from the design of a fighter jet). There are various terms for systems (related processes) that do this. Examples include: Web Content Management, Digital Asset Management, Digital Records Management, Electronic Content Management (and others). Synchronization of intermediate steps, and collation into a final product are common goals of each.
Basic of a CMS

A typical CMS works like these; a web design layout is designed and developed. Usually this entails a logo/banner at the top, standard navigation menus across the top, down the left side, and/or at the foot of the page, and a ‘blank’ area where content is inserted, this layout format is then converted into a master template for all subsequent pages. During the process of this conversion, the CMS admin backend is integrated and tested. Web content producers are given access and instructions on how to add text and images to web pages automatically. Most CMS are usually very intuitive and easy to operate. and each generated page is saved onto a database, for future editing or deletion. More elaborate CMS can perform unique functions (such as archiving, built-in search engines, and mod rewrites), but basic functionality is still related to easy creation and editing of web pages.

Types of CMS

• Proprietary CMS
  These systems are usually very expensive to purchase such as the $500,000 and up Vignette system. These high end systems however come loaded with full features and usually have excellent customer and technical support. Common uses of these systems involve very large organizations with departments that require unique functionality.
• Open source
  These systems are typically free and relatively easy to install. Some of the better known open source systems include Mambo and Drupal. Because of its open source nature however, you will find a dearth of customer and technical support, however there exists a huge following and forums dedicated to the popular systems. Customization capabilities vary from system to system. Be sure to do all the necessary research before deciding on one.
• Custom CMS
  These types of systems are usually preferred as they allow you to develop from scratch, your preferred functionality. Debugging is also less of an issue as your web developer, having written the codes, can easily isolate and fix problems. Bear in mind there are literally hundreds of CMS to choose from. Ranging in costs from free to over $500,000. What you do need to do, is firstly figuring out exactly what functionality your organization needs, your development budget and finally find a system that suits those needs best.The downside to installing a CMS is of course, the amount of web development needed initially. While you are able to obtain free open source CMS programs, you still need to hire someone experienced and capable enough to integrate it correctly. This initial expense however, is usually a necessary evil and is justified as you avoid the need of hiring or outsourcing your webmastering needs down the road.

Ultimately a CMS is meant to make life easier, not creating new rigid standards that require stop gap hacks or workaround solutions.

copas from Globaltor – About Content Management System And Relation With Your Business Needs

It looks like the long-awaited new International Standard, ISO 31000:2009, Risk management – Principles and guidelines is finally out and can be yours for only CHF 112, or about USD 110 or CAD 116.

Here’s the link to the press release http://www.iso.org/iso/pressrelease.htm?refid=Ref1266

I am fresh out of Swissees these days. If anyone has a copy and would like me to review it for readers of Riskczar.com, please email the pdf to me at riskczar@gmail.com.

Scurtă introducere

Dacă te întrebi la ce or fi bune plugin-urile astea jQuery, îți voi spune eu: îți permite extinderea întregii librării jQuery prin adăugarea de noi metode și funcții la aceasta. De exemplu, ai putea crea un plugin care, printr-un singur apel, va parcurge toate link-urile unei pagini, și la fiecare link către un fișier PDF va adăuga o iconiță descriptivă. Apelul va arăta ceva în genul:

$("a").adaugaIconitaPDF();

Idei pentru plugin-uri sunt multe, prea multe chiar, și ca să te convingi poți intra pe pagina de plugin-uri jQuery unde le vei găsi ordonate după categorie. La momentul actual, acolo sunt 3684 de plugin-uri! Deci idei sunt cu tonele, și tot apar plugin-uri zi de zi. Așa că, ori poți sta să cauți plugin-ul care-ți trebuie, ori poți învăța să creezi propriile plugin-uri, lucru despre care voi discuta în următoarele câteva articole.

Să intrăm în pâine!

Pentru început, e nevoie de puțină teorie interesantă. În caz că nu știai deja, jQuery e renumit pentru faptul că poate fi folosit cu ajutorul unui singur caracter: simbolul dolar ($). De puține ori, însă, vei da peste probleme folosind simbolul $, fiindcă nu este singurul framework care face uz de acest simbol. Așa că, pentru a evita conflicte, când este cazul, se poate folosi cuvântul “jQuery“. De exemplu:

jQuery("a").fadeIn();
jQuery.variabila = 2;

Acum să îți spun și care sunt acele puține cazuri când pot apărea conflicte cu simbolul $: când creezi plugin-uri, și când folosești încă un framework împreună cu jQuery, de exemplu ExtJS + jQuery. Știind acum aceste lucruri, să începem cu plugin-urile! Pentru a putea crea plugin-uri, e nevoie să știi jQuery, evident, și care sunt obiectele extensibile din jQuery:

1. jQuery
   • se ocupă cu procesarea internă
   • extinde metode (în alte limbaje de programare sunt cunoscute ca metode statice, sau metode de clasă)
2. jQuery.fn
   • se ocupă de elemente HTML și interacțiunile dintre ele
   • extinde funcții (în alte limbaje de programare sunt cunoscute ca metode de instanță)

Ca să fiu sigur că nu mă vei pierde, îți voi explica ce reprezintă metodele și funcțiile. Dacă ai deja experiență în programarea orientată pe obiecte, poți sări peste paragraful acesta. Deci, metodele pot fi apelate direct, fără a instanția o clasă. Funcțiile, pe de altă parte, pot fi apelate doar asupra unui obiect ce reprezintă o instanță a unei clase. Dacă nu știi nici ce reprezintă instanțierea, e cazul să te oprești aici și să iei un tutorial de POO în C++ sau orice alt limbaj vrei.

Știind acum ce obiecte jQuery pot fi extinse, voi crea un simplu plugin care afișează un mesaj la încărcarea unor elemente HTML. Apelul va fi simplu:

$.mesaj("mesaj la comanda");     //metodă
$("div").mesaj("m-am incarcat"); //funcție

Și acum iată codul, trivial de altfel:

//codul pentru metodă
jQuery.mesaj = function(msg) {
   alert(msg);
};

//codul pentru funcție
jQuery.fn.mesaj = function(msg) {
   alert(msg);
}

Ți se pare complicat ? Dacă da, e grav, fiindcă în următoarele articole se mai complică, fiindcă voi discuta despre:

• variabile locale și globale
• ascunderea variabilelor
• orientarea pe obiecte
• setările plugin-urilor
• funcții cu opțiuni și parametri
• template-urile cele mai utilizate pentru plugin-uri
• și în final, o listă de guidelines, adică un mic ghid

In our “fisking” of part A of the UNECE/METIS framework, we have arrived at the foreword, and the important question, what is a framework? A framework for what? For whom?

First of all, we are once again – incorrectly – told that this is a UNECE common metadata framework, as opposed to a UNECE/METIS common metadata framework:

“The United Nations Economic Commission for Europe (UNECE) is pleased to present this publication, Part A of the Common Metadata Framework”

Then, we learn that the initiative was taken in 2004 by METIS, which

“concluded that a framework was needed to provide links and context to previous and current international metadata standards initiatives together with comparisons of selected examples of current practices, to help national statistical organizations to develop their metadata systems”

This is a long sentence, so let us break it down into smaller pieces. A framework is, yes what?

1. “links … to previous and current international standards initiatives”. (How do they define a standards initiative? Why only the international initiatives?)

2. “comparisons of selected examples of current practices”. (How are the examples selected? Why only current examples?)

3. A “context” for, yes for what? Here, the long sentence, with its convoluted and double-stitched references, fails us. It is unclear. Is the context only for standards initiatives? For these initiatives and the comparisons? Or is it context, and links, and comparisons, that make up a framework for development of metadata systems? Whoever wrote this sentence has not cared about clarity of language.

4. The purpose of the framework is to “help statistical organisations develop their metadata systems”. (What is a “statistical organization”?)

Apparently, three things are being conflated here. As I have described in an earlier post, the background of the 2004 initiative was to:

1. create an infrastructure for better sharing of information between NSO:s

2. process available information so that it became more usefull to NSO:s

3. clarify and agree on what statistical metadata is all about. (It is this third ambition that is the framework).

Links and comparisons cover the first two points, not the framework. This leaves us with only one discernable definition of what the framework is: it is a “context”. That is not a definition, if anything, it is a synonyme!

Well, there it is! It has taken UNECE/METIS five years to define a common metadata framework as a context!

(True, there is more in the foreword. After the sentence, as above, the framework is given another definition. This time an operational one, when its four parts are listed and described briefly. I will return to that!)

Microsoft va a liberar una de las 3 versiones de su Framework para el entorno .net.

De a poco Microsoft va cambiando su política restrictiva de varios de sus productos y los esta adaptando a lo que ocurre hoy en dia con el software libre.  La versión .net se convertirá en Open Source pero será la menor de todas.

Como vemos en el blog de Muy Linux exiten 3 versiones del .net framework:

1. El .NET Framework que el proyecto Mono trata de replicar, que tiene todas las funcionalidades del proyecto de Microsoft y ocupa unos 200 Mbytes.
2. El .NET Compact Framwork, una versión algo más limitada de la anterior que elimina muchas cosas que no se utilizan en pequeños entornos, y que por ejemplo se usa en Windows Mobile o en la Xbox 360.
3. El .NET Micro Framework, la más pequeña de las tres y que está diseñada para dispositivos con recursos muy limitados.

Es la tercera opción que Microsoft liberara bajo Licencia Apache 2.0 y ofrece la posibilidad de que cualquier programador pudiera utilizar el entorno sin limitación alguna.

Aunque todavia no se liberará por completo ya que existen partes del código del framework que fueron desarrollado por terceros y también lo estas partes las utilizan para otros proyectos en donde todavia no se liberará su código.

Microsoft va cambiando el rumbo de sus políticas restrictivas, aunque todavia no es mucho ya se está llendo por el buen camino.

Visto en: Muy Linux

Estes dias, estava vendo uns projetos antigos e lembrei de um framework bem legal para Java chamado ZK. O problema do ZK é que você consegue aproveitar o máximo dele quando você programa usando Servlets, e não usando o modelo ZUL dele. Lembrei de alguns projetos que fiz, de algumas coisas interessantes que ele fazia e também lembrei que eu cheguei a programar com Servlet em Ruby, e aqui vai como eu fiz mais esse trabalho para evitar Java. NOTA: Isso funciona com qualquer framework Java, seja ele ZK ou Echo2 ou qualquer outro, porque na verdade o que você faz é escrever algumas linhas de código de “cola” e depois passa o controle para o JRuby

A primeira coisa que você precisa é do JRuby instalado, e de um compilador Java. Crie seu projeto normalmente, e provavelmente você terá uma classe que será responsável por instanciar a primeira classe (janela, página, seja lá o que for) do seu Servlet. Nesse ponto que a “mágica” acontece. Para simplificar as coisas, que vou criar uma classe (chamada Inicial) que instanciará uma JFrame. Toda a JFrame será definida em JRuby.

O processo: Basicamente, o que faremos é o seguinte: Criaremos uma classe abstrata (Janela), e nesta classe criaremos uma função, que será usada pelo JRuby. Na classe de “cola”, instanciaremos um interpretador JRuby, rodaremos um código para instanciar a classe do Ruby e faremos um “casting” desse objeto para a classe abstrata. Primeiro, a classe abstrata:

Arquivo Janela.java:
import javax.swing.*;

public abstract class Janela extends JFrame {
        public abstract void exibir();
}

Até aqui, nenhum segredo. A classe extende JFrame (quando você for usar seu Framework, ela deverá extender a “Window” do seu framework) e possui um método abstrato “exibir”. Agora, a classe em JRuby

Arquivo ruby/janela.rb
java_import 'javax.swing.JFrame'
java_import 'javax.swing.JButton'
java_import 'javax.swing.JOptionPane'

class Janela < Java::Janela
  def exibir
    set_size 300, 200

    self.default_close_operation = JFrame::EXIT_ON_CLOSE
    self.title = 'Uma janela qualquer'
    show

    puts "Exibi uma janela!!!"
  end
end

Caso você não esteja acostumado com JRuby usando Swing, ignore os detalhes da implementação. O que é importante é pensar que você está criando uma classe JRuby, que herda de Java::Janela (a janela que definimos no Java), e cria um método “exibir”. Agora, vem o código mais complicado, a classe Inicial que instanciará a classe Ruby:

Arquivo Inicial.java:
import java.util.*;
import org.jruby.*;
import org.jruby.javasupport.*;
import org.jruby.runtime.builtin.*;

public class Inicial {
    public static void main(String[] args) {
        Ruby rubyRuntime;

        //Inicia os "load paths", para indicar aonde o JRuby procurará os "require"s
        List<String> pathsLoad = new ArrayList<String>();
        pathsLoad.add("ruby/");
        pathsLoad.add("ruby/lib");

        //Instancia os serviços do JRuby
        rubyRuntime = JavaEmbedUtils.initialize(pathsLoad);
        //Carrega o arquivo "janela.rb"
        rubyRuntime.getLoadService().load("janela.rb", false);

        //Roda um comando JRuby, e captura o resultado
        Object janela_rb = rubyRuntime.evalScriptlet("Janela.new");
        //Transforma na classe abstrata
        Janela janela = (Janela)JavaEmbedUtils.rubyToJava(rubyRuntime,
                                 (IRubyObject) janela_rb, Janela.class);

        janela.exibir();
    }
}

Aqui, a mágica acontece: Cria-se um rubyRuntime, cria-se uma lista com os loadPaths (aonde o Ruby buscará os “require”s, que no meu caso eu destinei para a pasta “ruby” e “ruby/lib”. Então, instancia-se o rubyRuntime, pede-se para ele carregar o arquivo “janela.rb”, roda-se um comando bem simples (“Janela.new”) e captura o resultado, depois convertemos isso para uma classe Java. Como não temos uma definição de classe mesmo para Ruby, fazemos um “casting” para o Janela (classe abstrata no Java) e então finalmente rodamos o código “exibir”. Aparentemente, as novas versões do JRuby tornarão isso mais fácil porque permitirão que os códigos JRuby sejam compilados para Bytecode (e esses Bytecodes serão realmente classes Java válidas), mas até o momento essa é a solução mais elegante para o problema.

Nota: não será possível carregar Gems ou bibliotecas instaladas no seu sistema, a não ser que elas sejam descompactadas na pasta “ruby/lib”.

Mais informações:

• Página oficial do JRuby
• Wiki do JRuby
• Framework ZK

Nova versão do Flash deixa processador livre e AIR traz suporte a interface sensível ao toque e outras novidades.

A Adobe lançou hoje os betas que prometeu recentemente: AIR 2.0 e Flash 10.1.

A nova versão do Flash usará a placa de vídeo para poder executar vídeos em alta definição. Isso representa ganho no processador, já que o trabalho da renderização dos vídeos será feito pela placa de vídeo, e não mais pelo processador.

Download: Adobe Flash 10.1 beta

Já o AIR, framework da Adobe, cujas novidades já foram comentadas aqui no blog, traz suporte à interface sensível ao toque.

Download: Adobe AIR 2.0 beta
Saiba mais: Outras novidades do AIR 2.0 (em inglês)

Yes, there are problems already with the title of part A of the UNECE/METIS framework. According to this title, the document is part A of a “common metadata framework”. Common to whom? Which metadata?

It seems that there can be two different answers to these questions:

1. Taken literally, and as a stand-alone statement, a framework that covers all the metadata in all the systems in the world. As I have pointed out before, such a claim is ridiculous.

2. Given the name of the publishing organisation, a framework for all the metadata in all the activities of UNECE. But this is also too wide, since UNECE activities cover more than just statistics.

In other words, already the title is substandard in terms of precision of language. Either the title, or the name of the publishing organisation, has to be more specific:

1. A more correct title could be a (UNECE) “common framework for metadata in official statistics”

2. The complete name of the publishing body could be given, i.e. not just UNECE but UNECE/METIS.  If so, the title “common metadata framework” starts to make sense.

But, is this semantic analysis not just a case of nit-picking? Well, think about it! If you are in the business of international standardisation, one of your core competences is a clear and precise use of language.

What the title of part A of the UNECE/METIS framework suggests, is a lack of such competence, on the part of the author/authors of this document.

When I started “fisking” part A of the UNECE/METIS framework, I was chocked by how substandard the document is. I will therefore begin my review of it with three general observations:

1. It makes a range of claims about statistical metadata systems. But where are the real life examples that match these claims? It would seem that large parts of the document describe something that does not yet exist, a fiction.

2. It has a list of references at the end, but in the main text there are no concrete references to individual reports, and pages in those reports. This begs the question if the author has really read the listed references?

3. Both language and structure are so substandard, that they are far from satisfying basic editorial practices and requirements for a text of this kind. (Several examples of this will be given in the review that follows).

The Samurai Web Testing Framework is a live linux environment that has been pre-configured to function as a web pen-testing environment. The CD contains the best of the open source and free tools that focus on testing and attacking websites. In developing this environment, we have based our tool selection on the tools we use in our security practice. We have included the tools used in all four steps of a web pen-test.

Starting with reconnaissance, we have included tools such as the Fierce domain scanner and Maltego. For mapping, we have included tools such WebScarab and ratproxy. We then chose tools for discovery. These would include w3af and burp. For exploitation, the final stage, we included BeEF, AJAXShell and much more. This CD also includes a pre-configured wiki, set up to be the central information store during your pen-test.

The Samurai Web Testing Framework is a LiveCD focused on web application testing. We have collected the top testing tools and pre-installed them to build the perfect environment for testing applications.

http://samurai.inguardians.com/