Just for the records: HP has revealed plans to acquire Tabblo
Vyomesh Joshi, EVP at HP said: "By acquiring Tabblo's technology and making it available to companies that host popular websites, HP will be firmly on the path to becoming the print engine of the web."
As Ned Batchelder wrote, acquiring technology was not the point. Instead it was the creative solution they made: "...HP was excited by what we created..."
It's interesting to hear that Django with it's background in traditional press industry will be part of a big effort for becoming the "print engine for the web".
We at Tabblo are of course very excited about the acquisition by HP. One of the things that HP valued in Tabblo was our ability to innovate quickly and deliver solid products in a short amount of time. We definitely feel like Django was one of the reasons we were able to do that, and to make such an impression on HP.
So thanks a bunch to the entire Django community. You were part of our success. We'll be continuing with Django inside HP. Here's to more successes in the future!
Mitja wrote: > Just for the records: HP has revealed plans to acquire Tabblo
> Vyomesh Joshi, EVP at HP said: "By acquiring Tabblo's technology and > making it available to companies that host popular websites, HP will > be firmly on the path to becoming the print engine of the web."
> As Ned Batchelder wrote, acquiring technology was not the point. > Instead it was the creative solution they made: "...HP was excited by > what we created..."
> It's interesting to hear that Django with it's background in > traditional press industry will be part of a big effort for becoming > the "print engine for the web".
On 3/23/07, Ned Batchelder <n...@nedbatchelder.com> wrote:
> We at Tabblo are of course very excited about the acquisition by HP. > One of the things that HP valued in Tabblo was our ability to innovate > quickly and deliver solid products in a short amount of time. We > definitely feel like Django was one of the reasons we were able to do > that, and to make such an impression on HP.
> So thanks a bunch to the entire Django community. You were part of our > success. We'll be continuing with Django inside HP. Here's to more > successes in the future!
> We atTabbloare of course very excited about the acquisition by HP. > One of the things that HP valued inTabblowas our ability to innovate > quickly and deliver solid products in a short amount of time. We > definitely feel like Django was one of the reasons we were able to do > that, and to make such an impression on HP.
> So thanks a bunch to the entire Django community. You were part of our > success. We'll be continuing with Django inside HP. Here's to more > successes in the future!
> --Ned.
> Mitja wrote: > > Just for the records: HP has revealed plans to acquireTabblo
> > Vyomesh Joshi, EVP at HP said: "By acquiringTabblo'stechnology and > > making it available to companies that host popular websites, HP will > > be firmly on the path to becoming the print engine of the web."
> > As Ned Batchelder wrote, acquiring technology was not the point. > > Instead it was the creative solution they made: "...HP was excited by > > what we created..."
> > It's interesting to hear that Django with it's background in > > traditional press industry will be part of a big effort for becoming > > the "print engine for the web".
On Apr 4, 6:18 am, "bedros" <2bed...@gmail.com> wrote:
> nice work; I've always been impressed by Django; and Tabblo website > gives a more convincing reason to use Django.
> But, I'm still not sure on javascript/ajax library to use with > Django... so my question which ajax kit did you use with Tabblo.
Go jquery... but really, any javascript framework will do... i still think that people who complain about lack of "ajax support in Django" haven't even tried doing anything with it and they're just complaining ;-)
Django is not getting of your way of doing anything.
Anyway, regarding your question, thir first page uses Prototype.
We use a number of libraries. We have prototype and scriptaculous, and have been making a lot of use of YUI as well. In terms of Django integration, we use the libraries less as an automatic remote object methodology and more as an ad-hoc protocol between the browser and the server, so we really haven't missed a tight integration into Django.
>> nice work; I've always been impressed by Django; and Tabblo website >> gives a more convincing reason to use Django.
>> But, I'm still not sure on javascript/ajax library to use with >> Django... so my question which ajax kit did you use with Tabblo.
> Go jquery... but really, any javascript framework will do... i still > think that people who complain about lack of "ajax support in Django" > haven't even tried doing anything with it and they're just > complaining ;-)
> Django is not getting of your way of doing anything.
> Anyway, regarding your question, thir first page uses Prototype.
> We use a number of libraries. We have prototype and scriptaculous, and > have been making a lot of use of YUI as well. In terms of Django > integration, we use the libraries less as an automatic remote object > methodology and more as an ad-hoc protocol between the browser and the > server, so we really haven't missed a tight integration into Django.
> >> nice work; I've always been impressed by Django; and Tabblo website > >> gives a more convincing reason to use Django.
> >> But, I'm still not sure on javascript/ajax library to use with > >> Django... so my question which ajax kit did you use with Tabblo.
> > Go jquery... but really, any javascript framework will do... i still > > think that people who complain about lack of "ajax support in Django" > > haven't even tried doing anything with it and they're just > > complaining ;-)
> > Django is not getting of your way of doing anything.
> > Anyway, regarding your question, thir first page uses Prototype.
