Re:qooxdoo: javascript framework for desktop-like web apps
by gojomo on Thursday February 14, 2008 @01:10PM
(#115963)
Nice job of aping the Windows look... but often, web apps should look like web apps, since they are stuck in the browser pane, and suffer some network lags. I've seen a lot of projects shoot for a 'desktop-like' look & feel, spend a lot of time chasing it, but always miss by at least enough that the app lands in an 'uncanny valley', neither webby nor desktoppy.
Re:qooxdoo: javascript framework for desktop-like web apps
by edu on Thursday February 14, 2008 @02:34PM
(#116021)
I've spend the last 9 months building a web-application that had to look like a desktop one. I never liked the idea, but my bosses and our customers were not reasonable.
Now we have an application that runs on a web browser, looks neither like a web pager nor a desktop application, the back button does not work neither the bookmarks. Also, it feels reaaally slow, and there are some big hacks to ensure it works on both IE and FF (on safari and opera you get a message recommending to use IE/FF).
Moreover, we did not use the standard backend for the framework, and we had big problems to make them work well together.
Re:qooxdoo: javascript framework for desktop-like web apps
by jamongkad on Thursday February 14, 2008 @10:52PM
(#116273)
Dayum that sucks! But I agree that web apps should look like web apps and desktop apps should look like a desktop. Not that there is anything wrong with the latter. So how did the project go?
Re:qooxdoo: javascript framework for desktop-like web apps
by chwolfe on Thursday February 14, 2008 @06:25PM
(#116150)
Considering the pointy haired boss ignored your advice and let the customer run wild in the design phase, you have no reason to feel ashamed for that abomination.
Re:qooxdoo: javascript framework for desktop-like web apps
by bdfh42 on Thursday February 14, 2008 @11:42AM
(#115896)
I always get nervous when I see statements like "No HTML, CSS nor DOM knowledge is needed" but this does seem an interesting set of tools - I am looking forward to having a few more minutes to spend reviewing this properly.
Re:qooxdoo: javascript framework for desktop-like web apps
by jksmith on Thursday February 14, 2008 @09:59PM
(#116237)
Response seemed a little slow to me, but I don't know what the quality of the staging was by the time it got to my browser so I'll reserve judgement.
I hope this framework does not make the mistake of that other Windows-look framework has done, is overly model everything down to a setter/getter for the minutest datapoint -- end result is an uncompressed codebase that drags during creation and freeing.
Cut some corners, leave a few nodes out of those object hierarchies, and put more code on a single line - won't bother me any.
Re:qooxdoo: javascript framework for desktop-like web apps
by wallflower on Thursday February 14, 2008 @11:26AM
(#115880)
Wow. makes me feel old. I used to curse Netscape (if I wasn
't cursing IE) and curse IE (if I wasn't cursing Netscape) about DOM support. I used to write Javascript to programatically manipulate DHTML layers by hand and use Dan Steinman's DHTML library. It's so much easier now using Prototype et al.
Re:qooxdoo: javascript framework for desktop-like web apps
by edw519 on Thursday February 14, 2008 @11:32AM
(#115887)
Thanks for the Dan Steinman reference. I remember learning some pretty cool javascript hacks from his site years ago. Anyone who hasn't seen it oughta take a look.
Re:qooxdoo: javascript framework for desktop-like web apps
by wallflower on Thursday February 14, 2008 @01:36PM
(#115982)
Wow. All this walk down Internet memory lane. Made me remember GaboCorp.
Remember GaboCorp >?> - the kick-ass Flash website done by a teenager/young adult? Well, get this, he has a blog http://pixelbreath.gabocorp.com/... he's all grown up - and just resigned as UX Lead for Comcast Interactive...
Now we have an application that runs on a web browser, looks neither like a web pager nor a desktop application, the back button does not work neither the bookmarks. Also, it feels reaaally slow, and there are some big hacks to ensure it works on both IE and FF (on safari and opera you get a message recommending to use IE/FF).
Moreover, we did not use the standard backend for the framework, and we had big problems to make them work well together.
I'm ashamed of myself :(
You could spend weeks evaluating everything out there looking for the "right"/"best" one for your needs.
I hope this framework does not make the mistake of that other Windows-look framework has done, is overly model everything down to a setter/getter for the minutest datapoint -- end result is an uncompressed codebase that drags during creation and freeing.
Cut some corners, leave a few nodes out of those object hierarchies, and put more code on a single line - won't bother me any.
http://www.jalix.org/ressources/internet/dhtml/_dynduo/dyndu...
Remember GaboCorp >?> - the kick-ass Flash website done by a teenager/young adult? Well, get this, he has a blog http://pixelbreath.gabocorp.com/... he's all grown up - and just resigned as UX Lead for Comcast Interactive...
Cleary it is from years ago.