Make A Tech Deck Onlines

AIR (formerly Apollo) / Gears: All!

I am not one of those that draw a red line between what some have called RDA (Rich Desktop Application for running outside the browser) and RIA (Rich Internet Application that run in a browser).

markets, technologies, content and capabilities of these two families are too close to them as truly separate ... I will continue here to discuss platforms RIA for techno as different as WPF, AIR, Ajax, Flash, Silverlight, XUL, Java or the platform of widgets: I exclude by or Flex OpenLazlo cons of this terminology to the extent that they are only technologies server (for RIA platform, of course) and not the runtimes.

This proximity between technologies at first glance seems rather different from elsewhere each day a little more clear. The latest example is with some testing on Google Gears one hand and AIR on the other.

These two tech start from the same principle: the inertia of habits web development is such competition between tech news so fierce that it is better to impose complete a soft revolution. And what is the kind of revolutionary discourse?

- Continue to use your tech web development: Ajax, Flash ... what are good techno, and you still have a lot of customers to satisfy with.
- Continue to develop sites / applications that can be visited with a simple browser is a major web should not lose.
- Go farther on some features with customers / users want with our technologies: offline mode, access to resources systems.
- Rest assured, our technologies are converging: Javascript, XML, SQLite ...

And you know what? It's true! He does not just commercial speech as we have heard a lot in recent years. The few tests we have made my colleagues and I showed that for the same application implementations AIR and Gears are very close ... and that's very good news, you can not find?

Pinnaclegameprofiler Mac

Translation of "What is Web 2.0": new release

With the help of Chris, an associate of way, I was able to complete the few missing pieces to the French version to "What is Web 2.0" presentation of the brilliant vision by Dale Dougherty and Tim O'Reilly. All this has been the site of the young and friendly company your servant. The links of the original have also been added and corrected a few blunders.

The new dip in this seminal article was in fact an opportunity for me to note that nearly 2 years later, he still retains its freshness and relevance as if his principles were timeless ...

For connoisseurs, some shortcuts to the new translated parts (these are the side blocks):
Platform wins against an application every time
The architecture of participation
A thesis of the investment in Web 2.0
design models of Web 2.0

Nightmare Campus Free Online

other

I was recently shocked to see the Canadian Union of Public Employees (CUPE) go to an offensive against the private sector! In fact, billboards along the highway, it says: "PPP, stop that! Municipal employees are there for you. The personal is there for that? .

So here, CUPE on a crusade against the private sector. What surprises me first is to see that these people do not engage in arguments, they deliver a slogan. Indeed, to say that municipal employees are there for you, seeing how many are overpaid nothing to do some blue collar or bus drivers, such an assertion has a funny taste. But to imply that the private sector, contrary to the public, is not there for us, there is truly something fall off his chair.

It's true that any private company is, in itself, there to make money. In fact, it is a truism that a company makes no money going to close. But where is the harm in that? You knew that, according to statistics, the majority of Quebecers work in a private company (which includes self-employed)? Besides, for sector unions Privately, they are more likely to make money in a profitable business in a bankrupt company. Otherwise, why harp to go to Wal Mart or McDonald's? Anyway, I am among those who believe there are too many employees in the public sector in Quebec. Consider the case of the Ministry of Education. In Quebec, there are over 3000 to work as servants. In Denmark, for a similar population and similar needs, they are 300 ... There is something to think about, it seems! But the distance from the subject.

short, to see CUPE use a slogan as meaningless, it is essential to deliver the record straight. Municipalities are not wealthy, and have limited budgets. A municipality, like any private company has every reason to return to its budgets, it is a minimum which we can legitimately expect. If it can reduce its costs, everyone is a winner (we're talking about taxpayers' money, anyway!). If the municipality has employees that do not matter and expensive (it often is!), Nothing should prevent him from correcting the situation and offer a quality of service (but in saying this, I just cause anger among union movements). In summary, if a municipality may entrust part of its services to a company, it costs him less and that quality standards are met, then why not? Otherwise, if the company is not the case, we do not renew the contract and is entrusted to another company. Nothing complicated there! It's like when you go to a restaurant, if you're expensive, the service was rotten and your meal was bad, you go eat somewhere else next time! So it's the advantage of a private company that offer quality services at affordable prices. No company is to bankruptcy. In either case, if public employees are fine and do not cost too much, the municipality will keep them, no doubt. So why such a campaign of fear? As for me, the only ones who should fear are the incompetent employees.

But what strikes me most is that this beautiful propaganda campaign is paid for by taxpayers' money. CUPE is a union of public employees, employees are paid from your taxes, and by A + B, union dues are paid through your taxes and your taxes. Thus, the union made a propaganda at taxpayer expense to encourage municipalities to spend more public money?? There is an obvious nonsense!

As stated Réjean Breton, the "union" should stop thinking that everything they are owed! No, we're not beholden to the unions, quite the contrary! Their abuses have been bankrupt companies have indebted Quebec, have established trade union practices questionable, made the promotion of incompetence, but they still have the mentality of 1870 when private enterprise is seen as the big bad wolf. Unions public sector are not there for "us", they are merely parasites of taxpayers' money to benefit its members and the quality of service is the least of their worries.

Quadriderm Nf En Houston

Ajax Development: some keys to a modern architecture javascript



a time when Ajax is spreading to invade many jobs from and some specialized sites where more and more code returns the client side, it becomes necessary to ask some questions about the architecture developments Javascript.

These questions are these:
1 - use-t-on (or not) frameworks integrating server and client (Backbase, GWT, webdev)?
2 - The javascript is located there only or client-side then he will also be generated by the server?
3 - What js libraries use client side? how to articulate them?
4 - Use-t-on (or not) as a true JavaScript object language with " namespaces" and " classes" inherit from each other?
5 - What layers distinguished in the development JavaScript and how to articulate them both and with the layers server?
6 - What architectural practice generally followed in js?

I give you faster MY answers to these questions ... I quite frankly slice give rise to better the debate!

1 - A server-side Ajax framework?
No, delegate the Responsibilities of the client server technology is a bad idea. It may allow you time to be more productive, but certainly not over time. To address problems on the client side, it is of course much more efficient to use a client technology ... although it may seem painful to some (re) making Javascript, XHTML and CSS.

2 - JS client-side only?
Yes, as much as possible ... The advantages are many: clear separation of application layers, performance, productivity development in the long term.

3 - what JS libraries?
A good bookstore and a single "core" (prototype or jQuery is my first choice, but it is not forbidden to look elsewhere ... being very careful!) To be used in background: no question, for example used only for prototype Ajax.Request! The core library is intended to event handling, DOM manipulation and AJAX calls throughout your code.
If you have chosen the core library, elements that come to hang up (especially the advanced graphical effects) you should not miss.

4 - classes and namespaces?
Yes, of course! Although Javascript does not natively these possibilities, it is quite possible to simulate and to reap the benefits that it has long server-side to these practices. Prototype is an excellent example.

5 - which layers side JS?
At a time when local storage becomes a reality in Ajax applications, establish a real data access layer seems increasingly inevitable: read about the very good brief team of Google Gears.
Generally, the layers will look like side JS increasingly to those commonly known "server side" data / data access / business logic / interface. The challenge will be to link this with the responsibilities assigned to the server: the task is feasible in reality.

6 - Good architectural practices JS?
This is obviously not quite the same as on a server technology: JavaScript is a language very specific (but not a sub-language!) And the rich client poses very specific problems. However, it does not, rather, to use design patterns to properly address and resolve most problems: a ride on Ajax Patterns be useful to anyone who asks good questions on the subject.

Go ahead, react, you indignant, run me flowers, insult me! These issues are crucial, then it is better to talk ...

Acid Reflux Prostatitis

Google Gears: Any interest in a demo WorkerPool

I will return very soon in more detail about what might change Gears for users, developers and web entrepreneurs ... but I can not resist waiting to pleasure to share with you a little demo that shows the interest of a party that has Gears, it seems, not been assessed at fair value through many readers: WorkerPool .

While the strengths of a server and a database available in JS on the client seem fairly obvious, the concept of workerpool is less so. Remember it. The workerpool can do music by javascript function in a process different from others. This is not really a "thread ", but it tastes the same: the process created do not block each other and are treated effectively by the operating system.

Not convinced? After you install Gears , try the following demo with workerpool and without workerpool ... Then we'll talk performance limitations of javascript !

Secondary Cancer Of The Spine

Google Gears ... a revolution? The main tech

I could not decently miss out on the project Google Gears after all my items on the Web offline. Lack of time, it will still need me to do (very) short on the subject yet. Google Gears

arrives in 3 pieces: workerpool (a solution to turn the JS outside runtime usual browser), localserver (a mini-server web page stored for cached) and Database (a database SQLite provided with a Javascript API).

This has little to do with the approach of Dojo Offline Toolkit , but it is still very exciting, this solution is even technically so attractive it could eventually be included in operating systems and / or browsers. Want to bet?