Re: [Vala] gda-sql-parser.h not being included when using libgda-5.0

2019-09-25 Thread Jonathan Moerman via vala-list
Hi,

If the code compiles all necessary files were included during compilation.
To me it doesn't seem likely that a missing include is to blame here. Also
keep in mind that it is often the case that a header file isn't included
directly, but pulled in by another header file from the same library.
Here libgda.h causes a large number of header files to be included (which
in turn included even more header files).

Should the vapi file still be invalid you can make a patched version of the
vapi file and pass this file to valac (how you can accomplish this depends
on your build system). If this fixes the issue for you it may indeed be a
good idea to open a bug report for this.
You can also edit the generated C files and compile the binary again. (Most
build systems are smart enough not to touch the intermediate C files when
these are newer than the Vala files.)

 Jonathan Moerman


Op di 24 sep. 2019 om 17:12 schreef Shem Pasamba via vala-list <
vala-list@gnome.org>:

> Hello,
>
> How do I make my vala code add a #include
>  in the c generated code?
>
> Spent some time debugging why my code was crashing at:
> Gda.Statement s = parser.parse_string(sql, out remain);
> which is at gda-sql-parser.c:451 (seen from gdb after installing *-dbgsyms
> in ubuntu), but finally figured out that the said include file was not
> being included.
>
> I looked at the vapi file at /usr/share/vala/vapi/libgda-5.0.vapi and that
> include for that file is not there. Should I file a bug report for this? If
> so, where? And if I can cook up a patch, should I patch the vapi file?
>
> Thanks for your help & answers.
>
> All the best,
>
> Shem Pasamba
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list


Re: [Vala] New Vala Language Server

2019-05-10 Thread Jonathan Moerman via vala-list
Thanks for sharing! Will have to check it out when I have some time
available.

Op vr 10 mei 2019 22:04 schreef :

> Hi,
> because there was a recent discussion about to implement another Vala
> Language Server. I just wanted to inform you that there is a new one [1]
> which looks really good and active. There is also a gedit plugin to test it
> [2] :). It is unfortunately not listed at the wiki. In my opinion it is
> more advanced then the other ones.
>
> Regards,
> Bernhard
>
> 1 https://gitlab.gnome.org/esodan/gvls
> 2 https://gitlab.gnome.org/esodan/gvls/tree/master/src/ui/gedit
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list


Re: [Vala] valaDevelop

2019-05-10 Thread Jonathan Moerman via vala-list
For me valaIDE didn't really solve any problems I had. What I would like is
a stable (so no Gnome Builder, that one is really crash prone with Vala
projects.) IDE with error checking, autocomplete and support for cmake
(preferably not tied to any build system). The closest I've gotten to a
good development environment is gedit + valencia (vala autocomplete)
(Though I consider the interface of modern gedit to be a bit of trainwreck).

For any previous IDE it was pretty much the same story, I lose more
functionality than I get by using the IDE, so I stop using the IDE
immediately. (And the previous IDEs were often quite buggy.)

I don't think it is a good idea to build a IDE specialized in Vala
development as the community is far too small and will likely stay that way.
It would probably be better to make a language server implementation for
Vala.

Because of all of this I don't really get excited when someone makes a new
IDE. And, yes, the IDE not being open source didn't help, but it certainly
wasn't the only reason.

With fright I had to realize that all these OPENSOURCE projects no
> longer work with modern systems.
> No one has enhanced or fixed something, even though it's open source!
>

Well if the IDE wasn't worth using why work on fixing them? Getting these
IDEs in what I consider a good shape would also have taken too much effort.
More effort than it would take me to just write/improve a plugin for a text
editor like gedit. (Not that I really have had the time to do that besides
some small fixes.)

 Jonathan Moerman


Op vr 10 mei 2019 om 17:33 schreef Wolfgang Mauer <
wolfgang.ma...@kabelmail.de>:

> Maybe a bit cynical:Idon't blame others 
>
> When I became aware of vala last year, I was looking for an IDE and
> found valaIDE and valama and others.
> With fright I had to realize that all these OPENSOURCE projects no
> longer work with modern systems.
> No one has enhanced or fixed something, even though it's open source!
>
>
> That's why I decided against opensource, so that's not the case with my
> IDE, which was first written in C# by the way.
>
>
> I did not expect that it comes to such a rejection.
> I had rather expected that I get applause for a working IDE.
> But, it always comes differently than you think...
>
>
>
> Am 10.05.19 um 16:07 schrieb rastersoft:
>
> > I'm afraid that I have to disagree with you: you didn't provide any
> > kind of source code. Yes, you published the generated .c files, but
> > those aren't the source code, I can't use that to fix a bug or add new
> > features (well, I can try, but doing that would be nearly as hard as
> > fixing a binary executable with a disassembler and an hexadecimal
> > editor). So those "source files" are completely useless.
> >
> > Also, I think that the problem IS that it wasn't open source, and your
> > depart shows precisely why: the only person with access to the source
> > code leaves the project and it dies, leaving all the current users
> > with just a binary that can't be enhanced or fixed, and that sooner or
> > later will stop working on modern systems. I lived this several times,
> > and that's why I decided to not use valadevelop. Yes, I tested it and
> > it was good, but I didn't want to be left again trapped with a dead
> > project.
> >
> > Of course, it is your code and you are the only one with the right to
> > decide what to do with it; but if you make a decision, don't blame
> > others.
> >
> > El 10/5/19 a las 15:35, Wolfgang Mauer escribió:
> >> I'm sorry, maybe it's because I work in a big software company and
> >> get paid for my development, so the "spirit" of open source
> >>
> >> If the source I provided is not enough, you'll probably have to
> >> continue hoping/waiting for better IDE.
> >>
> >>
> >> Am 10.05.19 um 15:18 schrieb Luca Dionisi via vala-list:
> >>> +1
> >>> I use Gnome Builder, but I am always in search of better free software
> >>> alternatives.
> >>>
> >>> On Fri, May 10, 2019 at 3:17 PM Dr. Michael Lauer
> >>>  wrote:
> >>>
>  Well, I can imagine that it would have generated more feedback if
>  it was
>  developed
>  in the open. Most (of the few) Vala developers have strong roots in
>  open
>  source and
>  – although not as comfortable as ValaDevelop – there are
>  „alternatives"
>  out there which
>  are completely open.
> 
>  That said, Wolfgang, if you no longer want to work on it, why not
>  free it
>  at last and upload
>  the source?
> 
>  Best regards for the future,
> 
>  :M:
> 
>  ___
>  vala-list mailing list
>  vala-list@gnome.org
>  https://mail.gnome.org/mailman/listinfo/vala-list
> 
> >>> ___
> >>> vala-list mailing list
> >>> vala-list@gnome.org
> >>> https://mail.gnome.org/mailman/listinfo/vala-list
> >>
> >> ___
> >> vala-list mailing 

Re: [Vala] valaDevelop

2019-03-27 Thread Jonathan Moerman via vala-list
Wolfgang was using the MIT license before the C code was uploaded so if the
MIT license certainly won't be any *less* valid/applicable.
The generated C source code also makes it at least doable to introduce
fixes and small improvements, should this be necessary. (And compiling the
software on other architectures is now also possible of course.)
I don't see why uploading the generated code over the Vala code is
preferred, but that isn't a choice for me to make.

 Jonathan Moerman


Op wo 27 mrt. 2019 om 13:12 schreef Wolfgang Mauer <
wolfgang.ma...@kabelmail.de>:

> Sounds like you're a lawyer ;-)
>
> I just want to offer an easy IDE for Vala developers and those coming
> from C#.
> If there any problems with the license or anything else i just stop
> publishing and keep private...
>
> /
> Wolfgang
>
>
> Am 27.03.19 um 12:59 schrieb Luca Dionisi:
> >> Yes, sure. I was wrong, no problem for the use of the LGPL-licensed
> >> libvala.
> >> I am not sure, instead, that this work could be defined as
> >> MIT-licensed. I mean, in the spirit of free-software (and MIT license
> >> is a free-software license) users should be able to study and modify
> >> the code. I don't think that can be done with generated C code.
> >>
> >>
> >> On Wed, Mar 27, 2019 at 12:51 PM Wolfgang Mauer
> >> mailto:wolfgang.ma...@kabelmail.de>>
> wrote:
> >>
> >> From my understanding, the user must be able to use a
> >> modified/fixed/own version of the static lib, and he can..
> >>
> >> In addition you do not have to link the libvala statically, you
> >> can build it now used as a shared one...
> >>
> >> Am 27.03.19 um 12:39 schrieb Luca Dionisi:
> >>> IANAL, but does providing generated C source code suffice to
> >>> meet the LGPL requirements?
> >>> I wouldn't say so. Just my 2 cents.
> >>>
> >>> On Wed, Mar 27, 2019 at 12:16 PM Wolfgang Mauer
> >>>  >>> > wrote:
> >>>
> >>> Now source is available at
> >>> https://github.com/wolfgangmauer/valaDevelop/tree/master/src
> >>>
> >>> The source is the same as used for building the binary, so
> >>> if you want
> >>> to build it yourself...
> >>>
> >>>
> >>> Wolfgang
> >>>
> >>>
> >>> Am 27.03.19 um 08:37 schrieb Wolfgang Mauer:
> >>> > In order not to violate the LGPL of libvala and static
> >>> linking, i
> >>> > decided to provide the source code in addition to the binary.
> >>> >
> >>> > If someone wants to build valaDevelop himself, he can do it.
> >>> > i will update the git soon...
> >>> >
> >>> > Greetings
> >>> > Wolfgang
> >>> >
> >>> > ___
> >>> > vala-list mailing list
> >>> > vala-list@gnome.org 
> >>> > https://mail.gnome.org/mailman/listinfo/vala-list
> >>>
> >>> ___
> >>> vala-list mailing list
> >>> vala-list@gnome.org 
> >>> https://mail.gnome.org/mailman/listinfo/vala-list
> >>>
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list