Re: [Vala] gtk widget bindings complete



I copied this to vala-list, I hope you don't mind.

* gege2061 wrote, On 25/06/08 16:43:
Good work!

After analyzing the generated code, I have some proposals :
  * Use abstract class,
  
you're probably right. It's just sugar, but sugar is important.
  * Create abstrat method for signal,
  
I considered this. I'm not certain of the benefits.
There are lots of signals, most of which exist of exist for each widget.

Often there is a different signal handler for the same signal for different widgets.

So what would these abstract methods be? Dispatchers? Based on what info?

Only the developer knows what signals he wants to catch and how, so I left these to be done in the subclass, but at least the developer only has to get the name right and the rest happens automatically.

  * Use verbatim string for XML (see my example).
  
I don't like this because the xml may actually contain """ and there is no way to escape it.
I did have it set to close the string on \n and start a new line and open the string again, but vala doesn't support const string concatenation yet. so I had to comment that out in the xml.
I'll put it back when vala adds support.

Do you use anjuta?

Sam

	
What you think?

2008/6/25 Sam Liddicott <sam liddicott com>:
  
Thanks to Nicolas who helped convert these to use gtkbuilder.

New files and a sample project are uploaded to:
http://www.liddicott.com/~sam/?p=98

All .glade files can be converted to .ui files
All .ui files can be converted to .vala files
and, as normal, .vala files are converted to .c and .h files and compiled.

The conversions only occur if they are needed according to makefile
inferences, which means if you add demo.glade to the
project_GLADESOURCES you probably also want to add demo.vala (the file
won't exist yet) to project_VALASOURCES

I use stamp files for .glade and .ui files even though I don't need to,
because thats what anjuta uses to group source files, otherwise I had to
search through OTHER to edit my glade files.

Sam

    



  



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]