Hi Ralf, thanks for the feedback. See my comments below:
Am 17.08.2008 um 15:54 schrieb Ralf Nieuwenhuijsen: > 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. Have you seen the new documentation? http://qooxdoo.org/documentation/0.8/helloworld There is a new script to easily start a new application using the skeleton. > > > 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 First it does not help me a lot what you are writing here. The dependency resolver works flawlessy here with a lot of people. Maybe there is something wrong with your checkout or your harddrive. Normally a "./generate.py source" is all your need. Touching all files, fixing all files etc. is completely nonesense. I see no reason something like this is required. It would be helpful do delete the whole cache folder and try it again. If then any errors occour please send us the output of the generator. It should present you how many classes etc. it includes. > > > 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. This is nowhere related to Apache etc normally, but try to load up your application locally (just using file://) when possible to exclude all issues with some type of caching your apache may do. > > > 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... Mhh, you can use a Canvas or Basic layout. Tell me please what exactly you are trying to do. These issues are always more helpful with some type of contextual information. > 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. That is exactly what it should do. This is like all these layout types behave. They stack up on each edge. The Stack layout in XAML behaves the same. Would be interesting where you have seen such a layout you are thinking of the Dock layout should be and what the name of such a layout is. > 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. A screenshot of the end result you would like to produce would be helpful. I am quite confused by your explanation :) > > > 5. THe table widget is still a developer's usability nightmare. Worse, You can be sure that the table will be improved in future versions. We also see the need for such improvements. But this was never planned to be done in the 0.8 time frame. > > 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. This is mainly for keeping the real demo code small. This helper mainly creates the window were the table is displayed in. This is nice to show the resizability of the table when the window is modified for example. > > 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.. > I am completely agree with this. The table has feature for power users but is far to complex for most simple cases. This is known and will be improved after 0.8 is out. > 6. This is likely a bug, but when using SVN groupboxes legends' are > cut off and end with dots.. Interesting. When you shrink the GroupBox this is indented though. Can you send us a more detailed description with a screenshot or even better directly but this issue in a bug report at bugzilla.qooxdoo.org? Thanks. > > > 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.. We are working hard to get it cleaned up and polished for the release. During some refactorings it might be that the version in SVN is unstable. The themes could be changed in the config.json file in your application folder. Documentation on this topic follows in a few days. > > > 8. When using [someobj].tr('bla') .. i get run-time errors .. how does > language support work now? What is the error you got. Please put this is a bug report with all details. The feedreader do have full localization support enabled and it seems to work pretty well. > > > 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. It is a contribution but not yet converted to 0.8 as far as I know. This is nothing the core team can currently offer as well. We need the community to help us in this regard. For being included into the core framework we need a maintainer who is able to continue the support for the following qooxdoo versions as well and being into schedule with the normal qooxdoo releases. Details on the procedure are currently prepared by Andreas as far as I am informed. > > > 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. Normally pooling and reusing is better than disposing etc. Short answer: Use destroy() on qooxdoo widgets, at least when you just want to remove this widget and all it's children. For all other qooxdoo objects use dispose() instead. > > > 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. Seems you have overseen the whole 0.8 section: http://qooxdoo.org/documentation/0.8 Also a interesting and helpful introductary read should be: http://qooxdoo.org/documentation/0.8/ui_overview > > > 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... Mhh, I hope this would finally not be the case. In fact no release before had such a good and complete API documentation for example. Just have yourself a look at: http://api.qooxdoo.org/devel Still there will be follow some more detailed documentation after the release is out. I think this is quite normal for such a big release. Greetings, Sebastian > > > 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 ------------------------------------------------------------------------- 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
