Undolog.com

After acquiring Macromedia, Adobe creates its Labs , development labs! Building on the success of Microsoft with its Internet Explorer 7 Blog - that has (and has) saved a lot of services pack - Adobe also adopted the technique of the beta version. In fact, he was now, instead of waiting for the now very long time to develop a software (be it tradition, is a Web Application) why do not propose to you the version still in development? In this way there is a real-time feedback on the actual quality of the software you are developing.

However, in all honesty, the software should haouse down a little 'prices for their software, since the beta - you pay or are paid - we do users!

With Adobe Soundbooth beta overwrites the known SoundEdit. Adobe Photoshop Lightroom is a new product aimed at professional photographers, with lots of video demos online. Flash 9 with ActioneScript 3 appears also in the alpha version to download! Although it is indicated preview! To find the mobile Flash Lite 2.1 Authoring Update , but it seems that a final release rather than anticipation. Apart from this small miscellany of beta, alpha and upgrade believe that the initiative is good, if not excellent.
So for the curious who want ahead and not wait to try a new version of software, Adobe Labs is a place of safe fun! I stress again the tendency to involve end users to the stages of development, a trend that owes its spread to the Web 2.0 generation. Most likely it will be a mode in the near future it will spread like wildfire wherever possible. You could try un'appartamente un'autombile or before it is released, for example ...

More ...

Version 7 of Microsoft's browser was (finalemente) released in English (it was released almost simultaneously with the release of FireFox 2). In short - through the Windows Automatic Update service - will be installed on millions of machines, such as system patches. Someone has already criticized this move by Microsoft umpteenth shouting misconduct. Web developers, however, more interested in knowing what will Internet Explorer 6 (IE6) and how will comportarso in developing Web sites

The release through Windows Update is scheduled for early November! It follows that within a week will be nice that IE6 buried. Web developers will have to upgrade your PC of course, found herself without a version 6 of which make the canonical test of compatibility.

It is clear that those who - like us - is absolutely manic updates and must have the latest release of software, is between a rock and a hard place. Also - obviously - IE6 is dead! And about time too! A candidate browser to be sure - if there ever is one - in the near future (next day) is definitely IE7, since the latter will undergo patches (service packs) security.

From developers understand that IE6 is abandoned! Additionally, Microsoft has explicitly advised to move urgently to version 7, if there was any need to repeat it. Web developers must adopt a machine with IE6 for testing? By not update it? It would have suffered attacks from all sides and avoid going on the net?

The obvious solution - and beneficial to Microsoft - is that developers and end users to pass immediately to IE7, whether they like it or not!

More ...

There is a very important reason for preferring the inclusion of content via PHP - server side - on a Web page with respect to the use of JavaScript - client side. In the development of tools outing services used on the CMS getmePage applick.com was possible to use Ajax engine as HTTP server data recovery. The problem, in this case, was that you had to do with the content of a site, content being indexed by search crawlers like googlebot! The crawlers do not execute JavaScript, making it a blank page in the eyes of googlebot. Today I am content to make a difference in indexing in search engines, so you have to be careful how they are generated content on a page. The one who sees the 'enduser is not the view of a tool such as googlebot. This is one of the reasons that determined the choice of PHP nell'engine data recovery dell'applick getmePage. PHP, in fact, is executed by the Web server before sending the page to the client. It follows, therefore, that what he sees is what a crawler sees the enduser.

More ...

As already touched on " JavaScript vs. PHP "(or ASP, CFM, ...), the question of whether or not to enter a kernel Web2.0 JavaScript in your scripts, instead of leaving it - in the majority of members - the server side, can cause confusion if not bewilderment. However there are good reasons to favor the server than the client, reasons that have nothing to do with Web2.0 that, in contrast, puts the spotlight on your JavaScript scripts.

More ...

For those who develop modules and FORM of contacts, a need exists to verify the immisione of an e-mail address. Today more than ever, ready to run with demons SPAM everywhere, it is good to guard against "crafty" ready to use HTML forms to send mail or perform illegal hack to SPAM and more.

More ...

nei fogli di stile. Here are some brief tips on how to use class and id in style sheets. Keep in mind that once the use of advanced JavaScript techniques, such as the use of Ajax engines, may come into conflict with the recommendations made here! And in the end we will see why.

More ...

Because of the incompatibility of style and perhaps output - yet - cross-browser, not everyone knows about the vast potential of style sheets. We want to show, therefore, some features of CSS syntax unknown to most and to remind us how little - often - we exploit fully the tools we have available.

Note: All sample were tested on Firefox 1.5.0.5

Select by attributes

This feature, often referred to cone advanced CSS2, allows strabiglianti things, if we reflect for a moment. The biggest advantage is the HTML ottinene side, where there is no need to distinguish between classes or id tag in the CSS. It is precisely the attributes - still present - in the TAG to indicate which style associated. Furthermore, any attribute of the tag can be taken as a selector: alt, title, accesskey, etc. ...

Selection for depth

This type of selection is nothing short of spectacular, if you consider that can be added to the previous one. It allows you to define the hierarchy of elements. Looking at the example below we will immediately realize the extraordinary importance of this type of selection, which keeps the HTML clean and free of unnecessary indicators.

e – fantastico – first-letter ! Indeed, just to conclude this overflight, as well as last-child exists first-child , and - amazing - first-letter ! Try it.
We obviously have touched the subject, very comprehensive to say the truth, who sees CSS as advanced instrument for the definition of layput pages. There are other selectors and behaviors, and great news for the specification of the CSS file for future generation.

More ...

Developing web applications with technologies like Ajax has revealed all the limitations of the Internet protocol HTTP. Sooner or any programmer trardi collides with the need - for example - to have a permanent connection with the client. The sending to the clients of a broadcast message is still impossible without resorting to some contrivance risky!

In the Internet scenario, however, the use of special components such as ActiveX Object, Flash or Java Applet, allowing to circumvent the problem well. Often, in fact, one wonders if the HTTPRequest object (brick base for Ajax experience) can not be substituted by an ActiveX component or using an invisible Flash movie just in case!

This is one of the most poignant part of the development of next-generation web application. To prove it, in fact, there are a whole series of "beta" web application using mixed technologies to solve the various problems that arise - and that the HTTPRequest is unable to perform. The same FlickR , one of the most successful photo-blog, makes use of Flash movies in some sections of the site. There are actually even more complex where there are Java applets or ActiveX controls to get them where no one - Ajax - was gone before!

What should be done in the short term, is a new standard for the HTTPRequest, even calling him in another way. Able to obtain an object, present in all browsers, capable of making connections permaneti and able to manipulate multiple protocols. However, this would be a pipe dream for developers but ragionandoci well, it could lead to death of the Internet as we know it.

When HTTP was designed as a global network we know today had very different speeds and users. The important points of HTTP are:

• Connecting to the Web Server
• Request a file
• Disconnecting

The HTTP is born with the basic idea of not burdening the network transmission; minimal support handshake! Even now, when the browser requests a page to a Web Server, place just the three steps listed above. It 'important to note that Google has developed a software like Google Earth in order to overcome obstacles, and connection to other stuff. Internet connection is ready to bear permaneti? We think it's premature. Most of the hosting service would collapse in a few seconds. Banda and CPU should be much more able to withstand the amount of traffic that is produced today.

The fact that support connections permaneti are well circumscribed and are increasingly using sophisticated technology and components and specifications.

More ...

There is a rumor that is currently an ongoing discussion on the use of Javascript as a manufacturer of HTML content. In particular, the dilemma haunts the universe Ajax. Under this acronym hides a method to contact the Web Server using JavaScript script, without the browser has to reload the entire page with the result - and annoying - "fliker" video.

The fact that this technique allows to communicate with the Web Server means, in practice, you can send - and receive - information from the Web server without the user - in fact - if you know it! On this last statement would be appropriate to open a separate discussion.

Returning to our question, the main question is: once it receives the response from the Web Server who has to build the scaffolding HTML that you can put the answer in the current page? The Web server must make at the time the answer or a task is delegated to the client side Javascript?

In practice, some say the best way is to pack the complete answer directly on the server side, so that the client JavaScript and should only take place (get & insert). Others, however, argue that the best thing is receiving spurious data, raw, perhaps in an XML structure and process all the client side, using JavaScript, and always with JavaScript to create the scaffolding needed to insert the HTML page.

It appears immediately evident, however, that it is not possible - a priori - supporting a model relative to each other. Both, obviously, must be contextualized. E 'possible that in some cases to pack everything to the Web Server it is actually the best choice, both during development and in speed of transmission.

It must be said at once that the idea to load large quantities of Javscript code on the client is not a beautiful solution. I say this in remembrance of scalability. A system that has already heavy in its early stages, has little chance to progress in peace in the future. Moreover, even among the widespread incomptibilità browser available, then the client side Javascript code make it too tiring to develop articulated. However some people it does! Undoubtedly.

The moral, to date, with browsers and operating systems we have, seems to be that everyone must choose his own way, tomorrow we'll see. Visit our website Applick.com , the code was written using both methods, as appropriate.

Tomorrow, perhaps, the browser will come pre-coded on board! You will definitely revised the component HTTPRequest. For now this technique has its re-birth (see use of IFRAME TAG) is the minimum standard HTTPRequest made ​​on the component, its presence and implementation of both the increase in the browser and banda-media available to Internet users. The HTTPRequest HTTP is still a sub-channel, nothing more nor less. Send XML instead of HTML does not make much difference, by sniffing the network there realize now. Perhaps these are moaning about something else that goes beyond the question of Ajax. It 'true that a certain part of the Internet community calls for a change, structural changes. There has been talk - rightly - pemanenti connections, which certainly have nothing to do with the current policy (and original) of the HTTP protocol.

The reality, in the end, it may be to admit that the current technology of the Internet is outdated. His protocols, designed for other network speed and other conditions, are obsolete.

More ...