Hi, there, here are some things that I keep bumping it with 0.8 SVN..
It's a mixture of questions and comments, I hope the devs don't mind:
1. I love the shorter names for everything. It makes a lot less code
wrap and therefor really helps readability.
2. Getting the build system to build was DIFFICULT. I used the
skeleton; but I had to change config.json and then hack generate.py.
Perhaps this info can stored in a file like ~/.qooxdoo ? If it would
be in a normal linux file structure, i could just throw it in
/usr/local and expect everything to work .. but it's not in a sane
structure for this kind of usage. This will lower the change of
qooxdoo getting packaged and put into distrobutions ... The worst
thing? There is not a file with 3 lines of text explaining what to do?
How does anything test this? Am I the only one trying it out? Or is
everybody else psycic? Please put a 'getting started' file in SVN
root. You don't have to dumb it down .. 6-10 lines of text explaining
how to create a project .. and how to compile it, would be great.
3. I am at WAR with the dependency resolver. I now have a script that
in 30% of the time, makes the resolver work ..
touch source/classes/project/*
./generate.py source
touch source/classes/project/*
./generate.py fix
rm ../cache -R
./generate.py source
killall firefox-bin
firefox
But I'm still clueless .. the worst thing, it isn't consistent. What
is going on here? Why is it not including classes I'm using? The above
script likely does a lot more than it needs to do, but it still only
works one in every three times. Often I just have to repeat the
script a couple of times. Opening/adding spaces and saving again,
until somehow mysteriously, the build system catches on.
But since, a lot of people are testing this, this has got to be my
fault. I just don't understand how. I'm using out-of-the-box apache
with a symlink to the project directory and qooxdoo directory.
4. How are we supposed to use the new layout system? It's confusing ..
it seems like we can't change the left/right/top after adding a
widget... The dock layout doesn't do what I expected as well. If I
add more than object to the left they are layout horizontally, rather
than vertically. The vertical spacing within the north-side is
ignored, the spacing argument seems to only apply to the regions... I
ended up using a custom layout, that sort of did the same thing I
intended to do.
5. THe table widget is still a developer's usability nightmare. Worse,
the demo's are using code we can't see from the demo browser. See
this:
qx.Class.define("demobrowser.demo.table.Table", {
extend : demobrowser.demo.table.TableDemo,
The trivial example of a table uses 150 lines of code (without
comments counted) and extends some other hidden class we can't see.
I can image the need for extensibility and being able to tweak every
little part of the table. But somebody needs to make SimpleTable() and
FormTable(). I'll try myself, but since it severly lacks
documentation, just figuring out how it works will take as much time
as it did for qooxdoo 0.7, about a week at the least.
SimpleTable would be something like: new SimpleTable ({ 'Name':
'String', 'Age':'Integer', 'Comment':'String'}, [ .. data .. ]);
At least include a extremely minimal example demo of a table, just
using all the defaults..
6. This is likely a bug, but when using SVN groupboxes legends' are
cut off and end with dots..
7. How do I change appeance? I like Modern .. but it seems to have
more bugs, and being able to easily change the layout, at least shows
me which bugs are layout-related..
8. When using [someobj].tr('bla') .. i get run-time errors .. how does
language support work now?
9. Still no file-upload class .. eventhough the code has been
available .. I think this should be a release target; it's just
imcomplete .. and without a file upload widget a lot of use-cases
dissapear.
10. I had this pet-peeve with 0.7 as well .. how are we suppose to
manage memory? Are we suppose to call dispose? When? It was never
documented. I just never bothered.
11. Documentation isn't considered a release target. This is an
organisational bug .. Why? because without documentation we can't
properly test your framework. There are zero words about setting up a
"hello, world" project. There are no words about how to use the
layout-system either. So even the trivial stuff is like searching for
a needle in a haystack. Trying out hundred different things...
seriously .. with documentation comes collaboration.
12. For a lot these things, I would love to submit bug reports, but i
don't know what the expected behavior is supposed to be, so I don't
know if it's a bug, or if things just work differently now...
Please note: All of this critism is meant with all the best
intentions, it's just that currently, trying to test the framework is
nearly impossible without more information. At this point it seems
that the 0.8 official release will be the tech demo and once (a couple
of months) when the build system and documentation matures, it will be
usuable by developers. Because that is one bridge that seems to have
been ignored...
Greetings & Love,
Ralf Nieuwenhuijsen
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
