Re: [dba-dev] Need i-team for specification [was [dba-dev] New Filter Dialog]
Am Montag, 9. März 2009 13:57 schrieb Frank Schönheit - Sun Microsystems Germany: In case you suggest the latter, how and where should this version of the spec be announced? Did you do this as Writer doc, or do you plan to do it in the Wiki? In the first case, you should find a place. I have used OpenOffice.org Software Specification Template and thus I have a Writer document. There is the specification wiki that says one should put the spec (even if preliminary) online on http://specs.openoffice.org... but how do I? On this page I cannot find any hint. -Karl - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Need i-team for specification [was [dba-dev] New Filter Dialog]
Am Montag, 9. März 2009 21:10 schrieb Frank Schönheit - Sun Microsystems Germany: Hi Karl, I have used OpenOffice.org Software Specification Template and thus I have a Writer document. There is the specification wiki that says one should put the spec (even if preliminary) online on http://specs.openoffice.org... but how do I? On this page I cannot find any hint. Sigh ... one reason I prefer the Wiki ... You need CVS access to the ¨specs¨ project. Since I cannot grant you this, and I am not even sure the project is still alive ... I could offer you CVS access to the DBA project, so you can commit your spec (still using CVS) to http://dba.openoffice.org/specifications/index.html. Well, I just wanted to apologise for the false alarm since I managed to upload the file to http://specs.openoffice.org/servlets/ProjectDocumentList The document should be visible to other users once the project owner (Christian Jansen) has approved the file. If the project is dead it cannot be for long since the last spec was approved on February 19, 2009. I guess it is better now to wait and see if it gets approved. If not, then I would have to try the CVS. I will announce the spec as soon as it is visible to the public. -Karl - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Need i-team for specification [was [dba-dev] New Filter Dialog]
Hi Frank, Am Donnerstag, 5. März 2009 15:42 schrieb Frank Schönheit - Sun Microsystems Germany: Hi Karl, So please read on, as I need a member of dev, ux and qa. I might not have all the necessary time, but if nobody else volunteers for the dev part, then count me in. (But be warned that I seldom can resist giving UX-related comments :) There does not seem to be much interest in ux and qa... :-( I have finished a first version of a specification. Lots of details are still missing. I didn't pay, for example, any attention to accessibility yet. However, the first version has enough content (23 pages) to see how I think the new filter dialogue could -- and should -- work. Before I continue, I would like to get some feedback. Maybe my ideas are in complete disagreement with the expectations of the community. So how should we proceed? Shall I stop and move the first version to /dev/null since I do not have a complete i-team, or should I upload it somewhere and wait for being bashed? ;-) In case you suggest the latter, how and where should this version of the spec be announced? Anyway, I think I should stop now and wait for feedback. -Karl - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] Fwd: [ux-request] Need i-team for specification [was [dba-dev] New Filter Dialog]
Hi, since I didn't get any responce yet, I resent this mail to disc...@ux as suggested. -Karl. -- Weitergeleitete Nachricht -- Subject: [ux-request] Need i-team for specification [was [dba-dev] New Filter Dialog] Date: Mittwoch, 4. März 2009 01:18 From: Karl Weber karl.webe...@gmx.net To: dev@dba.openoffice.org Cc: requ...@ux.openoffice.org, d...@qa.openoffice.org, d...@openoffice.org Hi, I offered and would like to write a specification concerning Base. As I understand the procedures this would only make sense if I had an i-team, which I currently lack. So please read on, as I need a member of dev, ux and qa. I hope, this is the proper approach to find these members. Anyway, I don't know any other way. Please excuse me if I did it wrong. In order to introduce the project I will write something about (1) What is the subject of the specification (2) What should be improved (3) What the specification should describe (4) What I think I can offer OOo Since the spec affects Base (dba), maybe answers to this mail should be addressed to d...@dba? (Ad 1) As far as I know, there is no issue, but only the description of a developer project in [1] [1] http://dba.openoffice.org/development/projects.html#new_filter (Ad 2) Currently Base has two filters: (a) The filter dialog, used to filter rows of a table or query shown in the data source browser. It is also used to add a filter in the properties dialog of a form (at design time). (b) The filter navigator used to filter rows displayed in a table controll of a form (at runtime). Both of these filters are quite different with respect to capability and user interface. At least to me this was quite confusing at the beginning. The specification should have the following objectives: (A) Unify the user interface, i.e. describe a user interface for a new filter dialog that can (and should) replace both, the old filter dialog and the filter navigator. (B) Enhance the functionality of the filter so that it will also meet the requirements of power users. It should be possible to define filters with more complex filter conditions. (C) Provide a dialog that is easier to use. (D) Provide a dialog that is more intuitive to use. Well, (D) may turn out to be problematic, since I don't know any way about how to measure intuitiveness. (Ad 3) The specification should... (a) Describe the logical structure of the filter without any regard to the user interface. This will precisely describe the functionality of the filter. This should support implementation and testing. (b) Describe the user dialog, i.e. the interaction of the user with the user interface. (c) Describe each dialog window in detail (layout, properties of the controls etc.) (Did I miss anything?) (Ad 4) I have more than ten years of experience with enterprise software. I am browsing tables almost on a daily basis. Thus, I think I have a good understanding of what a (power) user needs and wants. On the other hand, I don't know the source code of OOo and I do not plan to implement the new filter dialog. This is one reason why I also need a developer in the i-team (which need not be the person to actually implement the filter later). I am not familiar with the procedures with OOo projects. Thus, I need some support in this regard. Since writing this specification will require some effort on my side, I wouldn't like it to be in vain. So I hope to find the necessary support (i.e. an i-team) so that the new filter will likely be integrated into OOo in the not so distant future... -Karl Am Sonntag, 1. März 2009 23:02 schrieb Frank Schönheit - Sun Microsystems Germany: Hi Karl, So I _could_ start...? Definitely. Of course the more people you involve, especially from UX the more chances the specified changes will ever become reality :) (And of course, the more people you involve, the more difficult it will become due to the lot of different opinions :) I guess I have to use the specification template for Writer. Matter of taste. Personally, I find writing specifications in the Wiki more difficult with regard to the involved work in actually writing, on the other hand, the Wiki has its advantages (the online version is always up-to-date, corrections/additions can easily be made by other parties, etc.). The Wiki template can be found at http://wiki.services.openoffice.org/wiki/Specification_Template (unfortunately not linked from http://wiki.services.openoffice.org/wiki/Specification). On [2] I found some other things that need to be done/checked before I start: In general, do not impose too much meaning into those requirements (but don't cite me on that :). (-- denotes a quote) --Q1 [Feature/Enhancement] --Does an unambiguously clear feature or enhancement request exists? Well, does one exist? I hope the description in [1] is enough to fullfill this request. If not, what has to be done? For this item, like for the others
Re: [dba-dev] Need i-team for specification [was [dba-dev] New Filter Dialog]
Hi Frank, Am Donnerstag, 5. März 2009 15:42 schrieb Frank Schönheit - Sun Microsystems Germany: Hi Karl, So please read on, as I need a member of dev, ux and qa. I might not have all the necessary time, but if nobody else volunteers for the dev part, then count me in. (But be warned that I seldom can resist giving UX-related comments :) This will be welcome. I think ux is an important part and the one I am the least sure about. (But things may always turn out otherwise...) If ux doesn't answer until tomorrow I will resend the mail to discuss...@ux. They say one should do so if there is no answer from requ...@ux within a couple of days. Ts. Didn't I say don't cite me on that? :) Sorry! -Karl - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] Need i-team for specification [was [dba-dev] New Filter Dialog]
Hi, I offered and would like to write a specification concerning Base. As I understand the procedures this would only make sense if I had an i-team, which I currently lack. So please read on, as I need a member of dev, ux and qa. I hope, this is the proper approach to find these members. Anyway, I don't know any other way. Please excuse me if I did it wrong. In order to introduce the project I will write something about (1) What is the subject of the specification (2) What should be improved (3) What the specification should describe (4) What I think I can offer OOo Since the spec affects Base (dba), maybe answers to this mail should be addressed to d...@dba? (Ad 1) As far as I know, there is no issue, but only the description of a developer project in [1] [1] http://dba.openoffice.org/development/projects.html#new_filter (Ad 2) Currently Base has two filters: (a) The filter dialog, used to filter rows of a table or query shown in the data source browser. It is also used to add a filter in the properties dialog of a form (at design time). (b) The filter navigator used to filter rows displayed in a table controll of a form (at runtime). Both of these filters are quite different with respect to capability and user interface. At least to me this was quite confusing at the beginning. The specification should have the following objectives: (A) Unify the user interface, i.e. describe a user interface for a new filter dialog that can (and should) replace both, the old filter dialog and the filter navigator. (B) Enhance the functionality of the filter so that it will also meet the requirements of power users. It should be possible to define filters with more complex filter conditions. (C) Provide a dialog that is easier to use. (D) Provide a dialog that is more intuitive to use. Well, (D) may turn out to be problematic, since I don't know any way about how to measure intuitiveness. (Ad 3) The specification should... (a) Describe the logical structure of the filter without any regard to the user interface. This will precisely describe the functionality of the filter. This should support implementation and testing. (b) Describe the user dialog, i.e. the interaction of the user with the user interface. (c) Describe each dialog window in detail (layout, properties of the controls etc.) (Did I miss anything?) (Ad 4) I have more than ten years of experience with enterprise software. I am browsing tables almost on a daily basis. Thus, I think I have a good understanding of what a (power) user needs and wants. On the other hand, I don't know the source code of OOo and I do not plan to implement the new filter dialog. This is one reason why I also need a developer in the i-team (which need not be the person to actually implement the filter later). I am not familiar with the procedures with OOo projects. Thus, I need some support in this regard. Since writing this specification will require some effort on my side, I wouldn't like it to be in vain. So I hope to find the necessary support (i.e. an i-team) so that the new filter will likely be integrated into OOo in the not so distant future... -Karl Am Sonntag, 1. März 2009 23:02 schrieb Frank Schönheit - Sun Microsystems Germany: Hi Karl, So I _could_ start...? Definitely. Of course the more people you involve, especially from UX the more chances the specified changes will ever become reality :) (And of course, the more people you involve, the more difficult it will become due to the lot of different opinions :) I guess I have to use the specification template for Writer. Matter of taste. Personally, I find writing specifications in the Wiki more difficult with regard to the involved work in actually writing, on the other hand, the Wiki has its advantages (the online version is always up-to-date, corrections/additions can easily be made by other parties, etc.). The Wiki template can be found at http://wiki.services.openoffice.org/wiki/Specification_Template (unfortunately not linked from http://wiki.services.openoffice.org/wiki/Specification). On [2] I found some other things that need to be done/checked before I start: In general, do not impose too much meaning into those requirements (but don't cite me on that :). (-- denotes a quote) --Q1 [Feature/Enhancement] --Does an unambiguously clear feature or enhancement request exists? Well, does one exist? I hope the description in [1] is enough to fullfill this request. If not, what has to be done? For this item, like for the others, the following holds: It is *one* possible mean to ensure a certain pre-requisite. There are other means, and case-depending, you might choose one of the others. (That's my personal interpretation, but it worked well in the past :) What this requirement wants to ensure is that all involved parties have the same understanding of the goal. In fact, this requirement is *very*
Re: [dba-dev] New Filter Dialog
Hallo Ocke, Am Freitag, 27. Februar 2009 07:43 schrieb Ocke Janssen: On 26.02.09 22:25, Karl Weber wrote: Hi, I noticed that the OOo community is interested in a new filter dialog -- according to [1]. I would like to contribute a specification. Note, however, that I do not plan to do any coding. Someone else would have to implement the specification. May be someone on this list just want to do the coding but is afraid of the specification. ;-) I think, there should only be _one_ filter dialog that is used during design time, i.e. to add a filter to a query or table, and that is also used by the end user in a form. I agree with what is said in [1]: The design is an important part of the project. I think it is not an easy task to create a filter dialog that can represend any filter condition that is logically possible and that is intuitive for the designer and the end user. Is there still any interest, in particular in getting just a specification? Sure. That would bring us one step further. So I _could_ start...? I guess I have to use the specification template for Writer. On [2] I found some other things that need to be done/checked before I start: (-- denotes a quote) --Q1 [Feature/Enhancement] --Does an unambiguously clear feature or enhancement request exists? Well, does one exist? I hope the description in [1] is enough to fullfill this request. If not, what has to be done? --Q2 [Concept]: --For changes requiring modifications in more than one application: Is --there product concept available, which is understandable to the --intended readership? I guess, this is irrelevant, since only one application is concerned: Base. --Q3 [Project-Resources]: --Do you have a project team? An OpenOffice.org feature is always --being developed by an Implementation Team (i-Team). An i-Team consists --at least of two distinct persons: --* A developer (required) --* A QA representative (required) -- Ask for a QA representative in the d...@qa.openoffice.org mailing list. --* A User Experience member (required only if the feature or bug -- fix affects the user interface or the behavior of the application) This is my first problem. How do I get this i-team? I have to specify their names in the spec. I can ask for a QA representative as described, but where do I get a developer? And how do I get a User Experience member? --Q4 [i-Team Agreement]: --Do all i-Team members agree on Q1 - Q3? Well, first I need these three people... --What happens if I can't answer all questions mentioned above, with Yes? --The consequence could be that your valuable work won't be integrated --into OpenOffice.org. So, at the moment I should better not start or should I? Although it might not be necessary to meet all these requirements as long as only the spec is going to be written, it would be a good idea to involve at least a User Experience member. I hope these are the only requirements that may have to be fullfilled. It would be great if you could help me meet them! Thanks in advance, -Karl [1] http://dba.openoffice.org/development/projects.html#new_filter [2] http://wiki.services.openoffice.org/wiki/Specification - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] New Filter Dialog
Hi, I noticed that the OOo community is interested in a new filter dialog -- according to [1]. I would like to contribute a specification. Note, however, that I do not plan to do any coding. Someone else would have to implement the specification. I think, there should only be _one_ filter dialog that is used during design time, i.e. to add a filter to a query or table, and that is also used by the end user in a form. I agree with what is said in [1]: The design is an important part of the project. I think it is not an easy task to create a filter dialog that can represend any filter condition that is logically possible and that is intuitive for the designer and the end user. Is there still any interest, in particular in getting just a specification? -Karl [1] http://dba.openoffice.org/development/projects.html#new_filter - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] Form Tablecontrol event: how to obtain column, row and other information
Hi, I hope, this is the proper list. I have a tablecontrol in a form and I can assign macros/scripts to various events. I already noticed, that one can also assign macros to events of columns, but this doesn't seem to work. (OOo 3.0) There should be an open issue about this problem. So for the moment I have to live with events -- e.g. mouse pressed -- fired from the tablecontrol as a whole. When this event is fired, I need to know a couple of things I don't know how to find out. Maybe someone can help me: (1) Was the mouse pressed in a particular cell, and if so, which one? (2) Was the mouse pressed on a column header, and if so, which column? (3) Was the mouse pressed on a row marker, and if so, which row? (4) Was the mouse pressed outside of header, row markers and cells? (5) How can I find out, which rows are selected, if any? (6) When I press the right mouse button in a cell or on a column header, a pop-up menu appears. Can I add my own menu items to these menus, and if so, how? Lot's of questions, but any help is very wellcome! (Pointers to documentation may suffice, if there is any. I didn't find any help in the DevGuide. ) Thanks in advance, -Karl - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
