File size: 3,085 Bytes
4aa5fce
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
[02:59] <WilsonStudioWeb>  Anyone here familiar in working with the Ubuntu Software center API in JSOn format?
[06:31] <dpm> good morning everyone
[07:05] <dholbach> good morning
[09:55] <TheFred> hello
[09:56] <TheFred> I've been reading about using quickly to create ubuntu applications, and can see that 'quickly edit' opens the files, but which one should i place my python (2.7) code into?
[10:20] <dpm> hi TheFred. Your GUI code should be on the <yourapp>Window.py file
[10:20] <dpm> you can modify it to suit your needs
[10:20] <TheFred> aha - thanks,i was tinkering trying to work it out for myself
[10:20] <dpm> but that does not mean that the code needs to be confined there
[10:20] <dpm> you can add your own additional modules outside of that file
[10:21] <dpm> what that file provides is just a boilerplate to help you get started
[10:21] <TheFred> I was banging my head trying to modify the __init__.py
[10:21] <TheFred> dpm, thanks - thats appreciated
[10:22] <dpm> TheFred, no worries, glad to help. Feel free to ask here or on askubuntu if we can give a hand in any way
[10:22] <TheFred> I know this is newbish - but do i have to create my own class, or modify the ***Window class thats already there?
[10:23] <dpm> it all depends on what you want to do. If you are just starting, I'd recommend just modifying the window that's created for you
[10:23] <dpm> simply run 'quickly design', strip it of anything you don't need
[10:24] <dpm> add the widgets, that you need, etc
[10:24] <dpm> and modify the rest in the code (on <yourapp>Window.py)
[10:25] <dpm> you might also want to read the tutorial, it's quite helpful. You can run 'quickly tutorial' and the documentation viewer will pop up with the docs
[10:25] <TheFred> ok, i've got a python program that runs well, it reads ascii strings from a socket and would like to display this in either a text box or label
[10:26] <TheFred> aha - quickly tutorial, you say.... thats gold
[10:26] <dpm> :-)
[10:27] <dpm> if your program is contained in a module, perhaps you can just drop it as it in the 'yourapp' folder and integrate it with <yourapp>Window.py so that it reads the results and displays them
[10:27] <dpm> this way you get nice separation between logic and UI
[10:34] <TheFred> thats an area i really need to do more work on - classes and modules, this may just be the motivation i need
[10:52] <dpm> cool :)
[10:53] <dpm> a real project always helps with motivation
[14:26] <TheFred> hmm, now to try to get the strings from the socket into a textview.. but how to I go about connecting data = client_socket.recv(512) to a text view?
[14:26] <TheFred> The button events seem straight forward enough, but socket events?
=== gnufz is now known as gnufs
[21:45] <strycore> hey there
[21:46] <strycore> I don't know if anyone here uses vim to code PyGobject, but i'm having a lot of troubles with it
[21:47] <strycore> i've explained the problem in details here: https://plus.google.com/u/0/105054545451660940700/posts/YMd62nU17GP
[21:48] <strycore> but basically, vim crashes as soon as i enter PyGobject code