Glad it worked for you!
On Mon, Sep 17, 2012 at 7:03 AM, Florin Jurcovici
wrote:
>> I would throw your initializer in a constructor if pointing to a
>> static. Define your props like this:
>
> I was suspecting something like this, but didn't dig deep enough into
> properties. I did the change
> I would throw your initializer in a constructor if pointing to a
> static. Define your props like this:
I was suspecting something like this, but didn't dig deep enough into
properties. I did the changes you suggested (deferred initialization
of non-nullable properties), and now node loads the
I would throw your initializer in a constructor if pointing to a
static. Define your props like this:
properties: {
someProp: {
nullable: false,
deferredInit: true,
check: [test.ClassWithStatics.constant1, test.ClassWithStatics.constant2]
}
}
And then inside of your constructor
I'm developing an app using appjs+nodejs+qooxdoo.
The main problem is SCOPE.
Hard to say what's your problem, but warning about binding and scope ...
I'm using lot's of qx.lang.Function.bind and var self = this; in my code.
Don't know exactly what's your problem but just take care of binding/sc
On 09/17/2012 02:42 PM, Florin Jurcovici wrote:
> I have something like:
>
> qx.Class.define("test.ClassWithStatics",
> {
> statics:
> {
> constant1: "john",
> constant2: "doe"
> },
>
> properties:
> {
> someProp:
>
I have something like:
qx.Class.define("test.ClassWithStatics",
{
statics:
{
constant1: "john",
constant2: "doe"
},
properties:
{
someProp:
{
init: test.ClassWithStatics
Hi Christian,
if you take the newest download version, you will have the
qx = require('./qx-oo')
syntax. Thats what I prefer. :)
Regards,
Martin
Am 09.08.2010 um 20:46 schrieb panyasan:
>
> Hi Martin,
>
>
> MartinWittemann wrote:
>>
>>> be solved differently. How did you import qx-oo a
Hi Martin,
MartinWittemann wrote:
>
>> be solved differently. How did you import qx-oo as a module in node.js?
>
> I just used the require statement and did not assign the return value of
> it to qx. As the qx-oo script defines a global qx variable, it is not
> necessary to assign it. But the
Hello Burak,
> what's going to be the license of qxoo, lgpl? it'd be wonderful if you
> could release qxoo under bsd license.
As its part of qooxdoo and contains only a part of the whole qooxdoo code, I
guess we don't change the license of it. Additionally, I don't think we are
going to "release
On 08/09/10 09:12, Martin Wittemann wrote:
> Hello Christian,
>
>> much more readable now!
> Totally agree! Thats really looking good, but still I have to get used to see
> qooxdoo code run on a server. :)
>
>> What I had to do to make this work is to add "exports.qx = qx;" at
>> the end of the q
Hello Christian,
> much more readable now!
Totally agree! Thats really looking good, but still I have to get used to see
qooxdoo code run on a server. :)
> What I had to do to make this work is to add "exports.qx = qx;" at
> the end of the qx-oo.js file. Is that something that could be added to
Another update:
Using Martin's qx-oo.js package, I have turned the server script into a real
qooxdoo class (rev. 20611). Goodbye, coding by closure (It is really a pain
to code javascript the old way once you have started qooxdoo development)!
compare
http://qooxdoo-contrib.svn.sourceforge.net/
Thanks Christian! I'll probably take a look at it this we :)
Regards,
Benoît.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5379944.html
Sent from the qooxdoo mailing list archive at Nabble.com.
---
Further update:
I just checked in the NodeSocket Contribution into qooxdoo-contrib:
http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/NodeSocket/trunk/
Here's a screenshot:
http://qooxdoo.678.n2.nabble.com/file/n5379905/Bild_1.png
If you look at the serve
MartinWittemann wrote:
>
> But anyway, I have good news! I took two hours yesterday right after the
> release to play a bit with building a file containing only the qooxdoo OO
> layer which can be used in webworkers, on servers (Rihno and node.js) and
> so on. I managed to get it done and will i
Hey,
sorry guys, I didn't have the time to read all your mails so I'm not sure whats
going on. But anyway, I have good news! I took two hours yesterday right after
the release to play a bit with building a file containing only the qooxdoo OO
layer which can be used in webworkers, on servers (Rih
panyasan wrote:
>
> leverage a technology (qooxdoo/javascript) and there is a way to extend it
> to the client in a simple and
"extend it to the SERVER", that is...
C.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5367495.html
Sent from the
Hello,
this has become an interesting discussion. But in the end: everyone starts
with different experiences and investments into technologies that need to be
most efficiently applied to the problem at hand. If I can leverage a
technology (qooxdoo/javascript) and there is a way to extend it to th
Hi.
> Threads are a debugging and maintenance nightmare. (...)
> I recommend against using them for nearly all applications.
You can't resonably expect an app server talking to several databases
simultaneously and serving up thousands of clients could do without threads.
You also can't reasona
Ok, we're now marching straight into a religious war about languages -
if I would be heeding what my grandmother used to say - never ever
discuss sex, religion and programming languages - I would remain silent.
But tongue in cheek away, let's expand a little bit on a specific part
of that discu
Hi.
Javascript has its advantages. Neither C# nor Java provide the same level of
flexibility. And it's definitely not the worst language I ever worked with. In
fact, it's one of the better ones.
A Javascript version with optional static typing plus mechanisms for aspects,
generics, operator ov
Hi.
> no one
> running a high-traffic site is choosing apache these days at the front
> line.
I wouldn't say so. A quick googling says something else:
http://durak.org/sean/pubs/bss/
http://www.e-gineer.com/v1/articles/web-servers-used-at-the-top-sites.htm
For me, node.js is
Hi Derrell,
On Mon, Aug 2, 2010 at 9:28 PM, Derrell Lipman <
derrell.lip...@unwireduniverse.com> wrote:
> On Mon, Aug 2, 2010 at 14:58, Petr Kobalíček wrote:
>
>> Hi,
>>
>> do you think that javascript is a good language to use it on server-side?
>> For me it's worst language I ever worked with,
Well said, as usual.
T.
> On Mon, Aug 2, 2010 at 14:58, Petr KobalÃÄ�ek
> wrote:
>
>> Hi,
>>
>> do you think that javascript is a good language to use it on
>> server-side?
>> For me it's worst language I ever worked with, but there is no other I
>> can
>> use to write multibrowser web-pages / w
On Mon, Aug 2, 2010 at 14:58, Petr Kobalíček wrote:
> Hi,
>
> do you think that javascript is a good language to use it on server-side?
> For me it's worst language I ever worked with, but there is no other I can
> use to write multibrowser web-pages / web-apps.
>
Different strokes for different
Hi,
do you think that javascript is a good language to use it on server-side?
For me it's worst language I ever worked with, but there is no other I can
use to write multibrowser web-pages / web-apps.
Using java on server side and java applets/javafx on client is the same
(same language for both
On 8/2/10, thron7 wrote:
> twisted is certainly a proven platform. but as apache, it is rather for
> complex applications, and it's a huge and unwieldy beast. nothing
> compared to the ultra-light node.js. and performance-wise i think there
> is no way current python implementations can beat v8 an
Qooxdoo is a huge beast too. Means it something;-)?
On Mon, Aug 2, 2010 at 7:16 PM, thron7 wrote:
> twisted is certainly a proven platform. but as apache, it is rather for
> complex applications, and it's a huge and unwieldy beast. nothing
> compared to the ultra-light node.js. and performance-wi
twisted is certainly a proven platform. but as apache, it is rather for
complex applications, and it's a huge and unwieldy beast. nothing
compared to the ultra-light node.js. and performance-wise i think there
is no way current python implementations can beat v8 and the likes, even
if run through s
> apache has years of experience dealing with dos attacks, broken clients,
> malicious input etc. it's also the swiss army knife of web servers. you
> can't throw all that away that easily.
OTOH, apache has more and more evolved into an application platform, and
is much too big and too heavy for s
Can't resist to point out that what you're aiming at exists with
twisted/nevow on the server side in python and athena/qooxdoo on the
client side.
- proven standalone webserver, http/https
- probably the oldest and widest protocol support for TCP/IP in Python
- completely asynchronous framework
On 08/02/10 17:36, b a wrote:
> On 8/2/10, benco wrote:
>> All Right. Yep indeed, in theory, node.js doesn't need another http server.
>>
>> But I heard that, according to the creator, nodejs isn’t really ready for
>> replacing http server yet - however, I don't know if it still the case
>> nowad
On 8/2/10, benco wrote:
> All Right. Yep indeed, in theory, node.js doesn't need another http server.
>
> But I heard that, according to the creator, nodejs isn’t really ready for
> replacing http server yet - however, I don't know if it still the case
> nowadays.
I'm pretty sure it can succesfu
Hi,
panyasan wrote:
>
> actually, what I have in mind is to replace Apache altogether for the
> node.js part
>
All Right. Yep indeed, in theory, node.js doesn't need another http server.
But I heard that, according to the creator, nodejs isn’t really ready for
replacing http server yet - ho
the_sheriff wrote:
>
> lines 185-216 serve static qooxdoo files
> http://github.com/wsdookadr/Q-Chess/blob/master/server/serv.js
>
Cool, thanks! Learning by example is the fastest way forward :-)
C.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp53
On 08/02/2010 12:02 PM, panyasan wrote:
>
> Hi Benoît,
>
> actually, what I have in mind is to replace Apache altogether for the
> node.js part. I have the feeling that small qooxdoo apps could do without
> Apache if a server script based on node.js can supply all the files that are
> needed fo
lines 185-216 serve static qooxdoo files
http://github.com/wsdookadr/Q-Chess/blob/master/server/serv.js
cheers
On 8/2/10, panyasan wrote:
>
> Hi,
>
> this weekend I started experimenting with node.js and Socket.IO, in order to
> implement a solution that will hook into the qx.event.message syste
Hi Benoît,
actually, what I have in mind is to replace Apache altogether for the
node.js part. I have the feeling that small qooxdoo apps could do without
Apache if a server script based on node.js can supply all the files that are
needed for the initial loading of the client application, and the
Hi Christian,
Thanks for the report.
I don't know if it is your case but I've heard that using Apache as http
server for node.js applications is not recommended/adapted. Nginx seems to
be a better candidate. Maybe you could give it a try ?
Best,
Benoît.
--
View this message in context:
http
Hi,
this weekend I started experimenting with node.js and Socket.IO, in order to
implement a solution that will hook into the qx.event.message system
(replacing the cometd contribution which I will no longer maintain). It
didn't go as fast as I originally thought -- for example, when mixing the
s
Hi Dietrich,
I've been using the mongodb and they are pretty solid. I had no luck
with any of the mysql drivers. Our current project uses redis (a
really database) and it works like a charm.
Best Fabian
On Thu, Jul 29, 2010 at 9:43 AM, Dietrich Streifert
wrote:
>
> Hi Fabian,
>
> sorry for nip
started writing a chess game server in node.js and qooxdoo on front-end
http://github.com/wsdookadr/Q-Chess
On 7/28/10, panyasan wrote:
>
> Hi,
>
> I am currently looking into node.js (http://nodejs.org/) and am pretty
> fascinated, actually thinking to creating some of my backend logic with
>
Hi Fabian,
sorry for nipping into this thread:
Are you using any DB modules/drivers with nodejs?
Are there reliable implementations? Or is there something like odbc/jdbc
(nodejsdbc?)
Thank you for your answer.
Best regards..
Am 29.07.2010 00:56, schrieb Fabian Jakobs:
> Hi Christian,
>
>
Hello Christian,
as far as i can say, it's currently not a topic here in the office. All my
interests are based on a some nerdy thought. ;)
But opening a bug is still a good idea even if i don't expect us to take care
of it in the future, at least not this year for sure. Maybe someone has too
mu
Fabian Jakobs wrote:
>
> Hi Christian,
>
> I am still on the mailing list by i read only topics which catch my
> interest - like yours does :)
>
> my qxoo should still work and provides all OO features and most of
> qx.core and qx.lang. The qooxdoo version used is from January but this
> shoul
Hi Christian,
I am still on the mailing list by i read only topics which catch my
interest - like yours does :)
my qxoo should still work and provides all OO features and most of
qx.core and qx.lang. The qooxdoo version used is from January but this
shouldn't matter much as this code usually does
Cool. I KNEW that the smart qooxdoo devs/community must have already noticed.
;-)
MartinWittemann wrote:
>
> Hello Christian,
> sure I have thought about such scenarios. I have tested node.js also and
> was impressed by its elegance. I once wrote a full JSON RPC layer for
> node.js which is on
Hello Christian,
sure I have thought about such scenarios. I have tested node.js also and was
impressed by its elegance. I once wrote a full JSON RPC layer for node.js
which is on my github account [1]. But i'm sure it's not working anymore
because ryan (node JS guru) removed the promises one day.
Hi Christian,
Personally, I am also planning to migrate my PHP works to node.js - it looks
really great! - but I'm not yet well familiar with it... so, all I can give
to you for the moment is some links.
Here is a list of (interesting) modules for/based on node.js :
http://wiki.github.com/ry/n
Hi Christian,
Please check it out:
http://github.com/wittemann/JSON-RPC-for-Node.js
http://github.com/fjakobs/qxoo
But Martin and Fabian know better than me (it's their personal
repositories). :)
Cheers,
Siarhei
On Jul 28, 2010, at 6:38 PM, panyasan wrote:
>
> Hi,
>
> I am currently looking
Hi,
I am currently looking into node.js (http://nodejs.org/) and am pretty
fascinated, actually thinking to creating some of my backend logic with
node.js rather than with my usual PHP.
Obviously, node.js cries out for a qx module providing all of the fine
OO-stuff that qooxdoo excels in.
Also
51 matches
Mail list logo
