Open ashleysommer opened 10 years ago
ghost
commented
10 years ago you can close tab of notebook by click on his cross :) Vala completion is unstable sorry, but developers work on. I keep your comments about file naming and file types ;)
Yannick
Lasall
commented
10 years ago Thank you for your detailed feedback!
- No Close button on the tabs. When opening files in tabs in the editor, there is no way to close a tab.
You can close a tab with the close button in the row below the tab row on the right side. And yes, a close button directly next to the tab name would be nice (and easy to implement). Right now the extra row is needed to move the tabs around (the complete tab window) to view files side by side for example. Goal is to include that functionality into the tab button of course (requires some gdl tweaks).
- No rename feature in the Project files browser. If I want to rename a file, I need to delete it and recreate it, or rename it in my file system and reload the project.
Good point, should be easy to implement. Right now the project browser is a very basic implementation, without any features.
- If I use the + button to create a new file in the vapi folder in my project, for example mynewfile.vapi, it will automatically append .vala onto the end like mynewfile.vapi.vala which is not what should happen.
That's clearly a bug, thx for reporting!
Is code completion considered usable?
Right now it's not working at least for recent Vala versions (0.24, 0.25+). This is going to be the next bug I'm going to fix after getting rid of some memory leaks... Auto-completion worked well before, I don't know the last working commit though (I think it's related to the Vala version).
Is debugging working? [...] Is debugging Vala code an intended feature?
It's only working (at least implemented) for plain build system. And yes basic debugging is an intended feature for the first release (for all supported build systems, so CMake, Autotools and plain).
The valama interface did not work out of the box at all.
That's an issue of the distribution not keeping the themes in sync with the gtk version. I'm using KDE on Debian Sid and even if the default theme looks very ugly (imho) all widgets are at least displayed.
All of those issues are in fact fairly easy to fix (except the autocompletion maybe) so it's mainly related to the lack of man-power. But reporting such issues will push it up in the priority queue ;) .
ashleysommer
commented
10 years ago Hi Lasall,
Thanks for your reply.
In regards to the close button on the pages, I believe I was experiencing some kind of layout bug. On my screen, the title-bar of each document page was blank (no icon or text) and had only a small button with a [<] arrow in the upper-right corner which allowed me to collapse the notebook. I did something to reset the layout of the IDE, and now the notebook pages behave correctly with the correct icon and text at the top and the close button for each page in the correct location.
I might potentially be able to help out with some simple coding and bug-fixing tasks if you like. I am just getting started with Vala, but I have about 10 years experience in Java and C#, and a good working knowledge of C. Are there any parts in particular that are higher priority to fix than others?
ghost
commented
10 years ago @flubba86 you can fix some memory leaks :|
Lasall
commented
10 years ago Great to hear that! Memory leaks have high priority for me at the moment but there are some easy to fix issues like a right click menu for the project browser (to rename files etc.) and the .vapi.vala bug. Look at src/ui/project_browser.vala and src/dialogs/create_file.vala. Also even if you use a "good" theme the look in general is a bit clunky imho, so just polishing the look of all different parts of Valama is very welcome. (Also I like to have the look managed by ui files (Glib ressources) but this requires quite some changes even if it shouldn't be too hard.)
Also feel free to drop any questions in #valama on freenode (even if I'm not there my bouncer should catch everything). General coding style should be clear according to (most parts of) existing code but you can also take a look at the the Wiki.
ghost
commented
10 years ago extension bug fixed : https://github.com/Valama/valama/pull/157
I've just started using Valama for a new Vala-based project I'm undertaking. So far Valama is by far the most capable modern Vala IDE I have come across, I am however noticing some basic features missing from the interface.
And some questions: Is code completion considered usable? For me it works (in a very limited capacity) for about 2 minutes after opening a project, then does not work at all. Is debugging working? I can add breakpoints, but the code does not stop on them. I understand it is very difficult to debug Vala code because it is running the compiled C code. Is debugging Vala code an intended feature?
And some comments: My system is Debian Sid with the XFCE4 window manager. The valama interface did not work out of the box at all. I have libgtk+ 3.12 and other required libraries, but none of my system themes have compatibility with the gtk 3.10+ interface and widgets. I had to download and install a gtk 3.12 compatible theme before I was able to get the interface widgets to display. I dont believe the modern interface design is very usable, and is not worth installing new libraries and themes just to display them.
Keep Up the good work.