Re: GSOC Code Completion in Basic IDE
Hi, If i have: dim aMediaProperties(1) as new com.sun.star.beans.PropertyValue and then write: aMediaProperties(0). - code completion changes this to aMeaMediaProperties. Also if I have dim oGraphics as Object and then write oGr.. I thought code completion complete it - is this not supported? Great work otherwise. Regards, Tomaž On Mon, Sep 2, 2013 at 7:05 PM, Gergő Mocsi gmocs...@gmail.com wrote: Hi all, I've managed to push my feature into master. A few words about it: Interface definitions use its fully qualified name, like dim something as foo.bar.ServiceName (not XServiceName, here I'll introduce some namspace magic soon). Functions implemented: - code completion - autoclose parenthesis - autoclose procedures - autoclose double quotes(strings) - autoclose defined variables (all kind of them). Extended types: here I mean UNO types (and I'm not sure if we really need this option, please give me feedback about this). About the listbox: It is quite simple, it displays the type's fields+methods (here, I'll make it to appear with more colums, like Type (field/method), Name and also parameters can be inserted ). Listbox appearance: It is moved right/up when it can exceed the visible area. Tab key cycles in the matching entries, ESC, leaving the actual context dismisses the window. Any ideas, opinions are accepted. Regards, Gergő ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: GSOC Code Completion in Basic IDE
Hi, So firstly it's great to see this finally land in master, congratulations!!. But... I fear that you really don't do the feature justice, there is little explanation or context in the information below, I understand what you mean ( but.. I have been following what you have been doing ) I doubt others have the back story. A screen shot, an explanation of how to enable to feature, or what the various elements of the feature do or what options you need to enable or even guidance of where to find those options would be very very useful. I think it is going to be hard for someone to quickly understand what now is available and how to use it and that is a shame. On 02/09/13 18:05, Gergő Mocsi wrote: Hi all, I've managed to push my feature into master. A few words about it: Interface definitions use its fully qualified name, like dim something as foo.bar.ServiceName (not XServiceName, here I'll introduce some namspace magic soon). It sounds like this is how it works currently but that isn't correct, you can't actually define a variable based on a service name, this is aspirational. I think you need to give people a little more context/information in order for them to understand e.g. a) Point out that right now there is experimental support for defining ( e.g. Dim ) a variable as an UNO type in basic ( this is a BIG language change ) that this language change is crucial for ( any useful ) codecompletion on a variable to work. b) Explain what works now and what you would like to get working in the next step. c) Encourage people ( by teasing them with some example(s), screenshot(s) or screencast(s) ) to try out this new feature and hopefully find that it is really useful d) Outline the consequences of such a change ( if it were to be enabled default ) on backward compatibility, comparability with other Office versions etc. e) Hopefully generate some useful discussion and maybe gather support for making a change like this default in the future Functions implemented: - code completion - autoclose parenthesis - autoclose procedures - autoclose double quotes(strings) - autoclose defined variables (all kind of them). Extended types: here I mean UNO types (and I'm not sure if we really need this option, please give me feedback about this). actually here even I don't know what you mean :-/ perhaps you mean that use of experimental UNO types ( which you need to explain to the reader more about ) isn't required for most of the other functions mentioned ( which again could do with some explanation, screen shots etc. ) HTH Noel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
GSOC Code Completion in Basic IDE
Hi all, I've managed to push my feature into master. A few words about it: Interface definitions use its fully qualified name, like dim something as foo.bar.ServiceName (not XServiceName, here I'll introduce some namspace magic soon). Functions implemented: - code completion - autoclose parenthesis - autoclose procedures - autoclose double quotes(strings) - autoclose defined variables (all kind of them). Extended types: here I mean UNO types (and I'm not sure if we really need this option, please give me feedback about this). About the listbox: It is quite simple, it displays the type's fields+methods (here, I'll make it to appear with more colums, like Type (field/method), Name and also parameters can be inserted ). Listbox appearance: It is moved right/up when it can exceed the visible area. Tab key cycles in the matching entries, ESC, leaving the actual context dismisses the window. Any ideas, opinions are accepted. Regards, Gergő ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[GSOC] Code completion in Basic IDE - weekly report
Hi all, this is my weekly report. UI: Menu and ModalDialog was replaced by a tab in Tools/Options, and it's called Basic IDE Option. ListBox: left arrow dismisses the dialog when the cursor goes beyond the dot, right arrow dismissed when cursor reaches the next line. Function Autocorrect Keywords was renamed to Autocorrection, because it autocorrects not just keywords but the UNO variables also (now, I'm working on to autocomplete procedures, other types, like String, Boolean, etc. ). Autoclose procedures: cursor is places inside the completed sub/function. Code: CodeCompleteWindow::ResizeListBox: Function was simplified, I've introduced some constants, and the position+size calculation is completely done by this( the initial text selection is passed in as a parameter). Variables according to autocorrection were renamed to keep the consistence. Regards, Gergő ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
