TRINIX

Even Cisco have noticed the importance of Webbassed tools like wiki’s, applications, …

Cisco CEO John Chamber talked at the Interop Conference in Las Vegas, about how the Web 2.0 (r)evolution is necessary for Business to increase their productivity and thus their profit. Web 2.0 has become an essential tool for Business to promote them selves and to enable better availability. He ’s a strong believer of the Web 2.0 possibilities.
Check out the video and read the complete article (see links below)

Video: http://www.youtube.com/watch?v=awkk4Xa9deQ

Article:

Cisco CEO John Chambers proclaims the future is Web 2.0 by ZDNet’s Dan Farber — Cisco CEO John Chambers ran on stage and then strolled throughout the crowd giving his vision of the networked future during his Network + Interop keynote presentation. As he walked and talked throughout the ballroom with the verbal passion and polish of a televangelist, Chambers proclaimed that Web 2.0, which he defined broadly as collaboration, [...]

You can now vote for your favorite Web Application of 2007.

You can choose from 250 nominees.
All the nominees are divided in Categories.

You can have a look at the whole list, perhaps you will find something new.
Because there are a lot of great Web Applicatios that get to little attention.
So check them out and vote to support them.

http://www.webware.com/html/ww/100.html 

Everybody who has ever used a Mac, have certainly liked the Dock menu with the nice Mouse-over effect.

This effect is called fish-eye, and the people at n-design-studio have made an nice looking HTML/CSS version of the Mac Dock menu. They used JQuery as Javascript library. JQuery has the Fish-eye effect build-in.
It really works and looks nice, so perhaps you can use this in a Web Application or website.

Example: http://www.ndesign-studio.com/demo/css-dock-menu/css-dock.html 

Ever wanted to re-create your own YouTube like clone.

Well read this article. It describes perfectly how you can achieve this.

http://www.onlamp.com/pub/a/php/2007/05/24/creating-mytube-with-flex-and-php.html

It explains how to set-up an PHP back end, with the FFmpeg video converter tool for converting the uploaded movies in a Flash Video (FLV) file and 2 version of a Flex GUI for the users.

Fabio Zendhi Nagao has taken the time to write out Javascript library for Validating and masking form input, called fValidator. This library is written in unobtrusive javascript and really easy to use.

He has put a whole range of validation and masking in this library. It’s definiately worth of checking this out.

More info at: http://zend.lojcomm.com.br/fValidator/

I recently wanted to add an item to my context (Right-mouse) menu for opening a JPEG file.

If you want to add an entry on a Context menu that appears on just one type of file or a few different types of files. I will show you how to easily to add (or remove) it using the context editor in Folder Options.

1. Open up My Computer.
2. Click on the Tools menu, select Folder Options, and click on the File Types tab.
3. Scroll though the list of file types and select the extension that you would like to modify.
4. Click the Advanced button to bring up the Edit File Type window. This is where you will see a list of all of the different entries that will show up in the context menu, shown here:
5. Just press the New button, give the menu item a description, then select the program you want to use and click OK.
6. Click OK and you are finished.

Ever wondering what’s the difference between Apollo, Silverlight, Flex and JavaFX.

Here you will find your answers.

http://ttlnews.blogspot.com/2007/05/test_22.html

I found more interesting notes on ‘Future of Web Apps SF 2006‘ conference.
Special thnx to Juixe for providing the Conference Notes (PDF).

This time it contains information on “Funding and Selling a Startup” from Evan Williams, the man behind Blogger (now part of google services) and Odeo.

Quota : “Evan was at the Future of Web Apps
conference in San Francisco to talk about his experience with web
entrepreneurship. Evan’s talk was titled Selling and Funding: Pros and Cons of
Bringing in a Third Party.

During his talk, Evan noted several rules for a web startup. These rules
included: be user-centric, be self-centered, be greedy, be tiny, and be
balanced. Having given out a few rules for a startup, Evan spent most of his
time talking about his five best Odeo screw-ups.

Evan’s first mistake when building Odeo was to try to build too much. He
talked that mentioned that they had written large number of verbose specs and
in the end they were not the first in the market.

Evan’s second screw up was building a service for people not like themselves.
In an essence, Evan stated that they did not ‘eat their own dog food.’ In general,
it is a good idea to use the freaking service you are building!

The third major screw up that Evan learned from his second entrepreneur endeavor was not adjusting fast enough. All these web 2.0 applications are all trying to keep up with the Joneses. Someone integrate with Google Maps, your web application needs to integrate with Google Maps. They start tagging your service start tagging. Evan
reminded the audience to try to be a purple cow, not a mee too application.

Another screw up mentioned by Evan of Odeo was raising too much money,
too early. Raising too much money almost seems counterintuitive. Raising too
much money was not heard in the web 1.0 era when champagne bottle was
served for breakfast and companies had a $10 million burn rate a month. Evan
said to “think of money as fuel.” If you have the fuel before the engine, you
start thinking about the fuel. He said, “What do you do with soo much fuel,
you drop some on the floor and light it on fire.” Kevin Rose and Michael
Arrington echoed Evan’s thought on raising cash, raising money is about
timing.

The last screw up mentioned by Evan of his experience from building Odeo was
not listening to his gut, his techie intuition, in hiring, raising moola, and building
the ‘right’ product. Evan quoted Markus Frind of Plenty of Fish who said, ‘The
enemy was thinking.’”

This is my conclusion of what Evan is saying:

• be unique, think out-side the box
• be up-to-date,watch the market and study trends
• grow step by step, take the time to evolve
• follow you instinct

I found this interesting notes on ‘Future of Web Apps SF 2006‘ conference.
Special thnx to Juixe for providing the Conference Notes.

Ryan Carson (organizer of Future of Web Applications and owner of Hey Amigo, Drop Send, and Think Vitamin) explains his personal DONT’S

Quote’s : “
Ryan Carson is the Future of Web Applications conference organizer and he
spoke about what he wish he had known before starting his online ventures,
Hey Amigo, Drop Send, and Think Vitamin. Ryan started his session by saying,
“We built three web applications, the first one we don’t talk about.” Here are
the 14 things Ryan wished he had known before he started his applications.
Hopefully they will help you, if you didn’t already now them. Before I begin I
should not that his advice sounds more appropriate from small teams, not
multinational conglomerates.

14. For the last piece of advice he wished he had known before building a web
application, Ryan quoted other speakers. Ryan said that the first, and maybe
even the second, version of an application are always throwaways. Marketing
and promotion can be a full time job; if you build it you need to promote it
before they will come. User’s can be trusted; you don’t have to validate an
email to have users start using your system “

Interesting point of view and I can totally find myself in this 14 points.

He forget to mention one important thing (according to me).

15. It’s important to keep track of version and notify users when the new version goes life and what changed since the previous versions. By doing this you prevent a ton of calls and emails from users about that their application changed without them knowing about it. Plus it creates a positive marketing vibe (new version, new functions, more people hear about this, RSS, blogs, …) Your application gets extra attention and perhaps attracts more potential users. So think commercial even with versions!

This comes in handy, when you want to use specific files.
I listed a couple of possibilities.

JavaScript Import:

<script
   type='text/javascript'
   src='directory/file.js'>
</script>

CSS:

<style type='text/css'  media='all'>
   @import 'directory/file.css';
</style>

Icon Import:

<link
   rel='Shortcut Icon'
   href='directory/file.ico'
   type='image/x-icon'>

PHP Import:

<?php @ require_once ('directory/file.html'); ?>

Adding an extra @ will prevent for possible errors to be shown.