Hi,

I have discovered QooxDoo recently and going by examples and doing some
tests across other frameworks, it looks like the best thing available.
Especially for someone coming in from Python (read OO) and getting into use
browser based UI for our next app.

I think QooxDoo is a Great framework...and it will thrive as long as those
who use it...keep using it in their projects.

Adding more and more different widgets and putting them up for
Demo...(something like what Dojo has on its website)..will definitely get
users to look more at QooxDoo.

The world is looking at big-data...and what do people do with
big-data...they graph it, map it, and put it on charts...so having, Graphs,
Charts, Map APIs will help.

Qnx (creator of the QNX RTOS), is now looking at HTML 5 to create
Automobile Dashboards (instrument clusters inside Cars that would run on
QNX)...so they need a lot of analog dials etc...adding such Widgets will
also help people come to QooxDoo.

my 2cents worth...

Best regards,
Vishal Sapre

============================================================

On Thu, Apr 18, 2013 at 3:11 PM, tedi tedi <tedi1...@yahoo.com> wrote:

> Yes, the name might make some people think it's not serious enough, cause
> it sounds funny and some don't know how to pronounce it.
>
> Anyway, I guess I'm measuring the popularity of a framework by how many
> applications are out there, created with that framework.
>
> I did see some writen in GWT ( not created by google ), and I understand
> that there are a lot of people knowing Java, but i think there is a good
> majority of people that use Apache as a webserver, and not Apache Tomcat,
> and GWT kind of requires servlets, i mean you could talk with a PHP server
> script, but you lose all the beauty of the framework. So I guess that's why
> I don't like GWT.
>
> I also saw a lot of applications or modules created with ExtJS, I also
> heard about people that were looking for ExtJS developers.
>
> I didn't find a qooxdoo application out there, that's still in use. I know
> about the list that's on the site (
> http://qooxdoo.org/community/real_life_examples ) but that's not enough
>
> I'm a bit worried about the fact that 1and1 does not use qooxdoo on their
> website, I mean their Control Panel, for thier hosting service. And i'm
> worried that qooxdoo is almost 7 years old now, and it still has such a
> small comunity. Maybe it's going to die at some time, or maybe 1&1 will
> stop investing in it
>
> I mean, when Adobe made Flex (or ActionScript) there were a lot of people
> that made a lot of small applications using their tool, but qooxdoo is used
> only by you guys, Why isn't there a company that relies on qooxdoo? SPAR's
> online store doesn't use qooxdoo anymore and lots of link from the
> real_live_examples are dead.
>
> Those are not good signs, as much as I really like qooxdoo.
>
> PS: Only one book writen about qx? :-\
>   ------------------------------
>  *De la:* thron7 <thomas.herchenroe...@1und1.de>
> *Către:* qooxdoo Development <qooxdoo-devel@lists.sourceforge.net>
> *Trimis:* Joi, 18 Aprilie 2013 12:04:24
> *Subiect:* Re: [qooxdoo-devel] Question
>
> On 04/17/2013 01:02 PM, tedi tedi wrote:
>
>  How come qooxdoo is not as popular as  GWT or ExtJS ?
>
> That's a tough question to answer. You don't get much feedback from people
> that decide against a technology ;-). It's also a question about how you
> measure being popular. You could say popularity for a JS framework is
> measured by the number of *developers* using it to create applications.
> Being a deverloper tool that would be a decent measure of popularity in my
> view. But you could also say it's the number of *users* using applications
> written with qooxdoo. Wouldn't an application with a million users speak
> towards the underlying framework?! And in the latter respect I think
> qooxdoo doesn't fare that badly.
>
> But even if you stick with the #developers measure - how do you assess
> it?! Number of downloads of the SDK?! Number of queries on Google?! If you
> e.g. look at Google Trends you will find that the number of queries related
> to Perl have significantly decreased over the years. Does that mean the
> number of developers has decreased, or fallen below all other scripting
> languages? Or just that it has become so easy and common-sense to go
> directly to the relevant information that fewer people need to search for
> it?! Python and Ruby on the other hand have relatively stable query counts
> over the last years. Does that mean their user bases have stalled?!
>
> Anyway, I would tend to think that there are fewer developers using
> qooxdoo than GWT or ExtJS. With GWT it's easy to explain as GWT is a strong
> web development platform for *Java* programmers. Alll shops with Java
> skills would naturally slant towards GWT. I'm not so sure about ExtJS. I
> don't think it is about technical merits (nor about marketing efforts as
> some people have it). Rather, my impression is far fewer people take a
> deeper look at qooxdoo. Maybe things like the name, the class and
> developement model or the intertwining with the tool chain alienate people
> on first sight, especially when they live west of the Atlantic. Which is a
> catalyst market for many things in IT.
>
> T.
>
-- 
Thanks and best regards,
Vishal Sapre
---
"Life is 10% how you make it, and 90% how you take it"
"बहुजन हिताय, बहुजन सुखाय (Benefit for most people, Happiness for most
people.)"
---
Please DONT print this email, unless you really need to. Save Energy &
Paper. Save the Earth.
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to