Need advise about an application

azrael jura.grozni at gmail.com
Sun Apr 5 19:14:08 CEST 2009


On 5 tra, 14:48, 一首诗 <newpt... at gmail.com> wrote:
> Do you have to show these data on GUI?  If so, why not use the event
> pattern?
> As far as I know, it's the standard way wxPython works.

Yes, I have to show the signaled data, but also create some
statistical meassurement  datasets as also some graphical
represenatations  and graphs.
wyPython works this way and it supports custom made events. I thought
of something like that. But I am not sure how to combine the serial
port signal to the event to call the handler. Time to google for it :D
But I am still  not sure if to use one thread for signal receiving and
DB saving, and anotherone for statistics and other stuff because it is
very important to save the signal which comes every second. if the
statistics generation can use the rest of the time, then it should be
done.

I have absolutly no expirience with multi thread programing. I know
about them only from theory I got to learn at college. I wanted to ask
for an advice from something from someone with lots expirience, but
also to learn new stuff by example.






>
> BTW : If it's not complicated, I think maybe some wysiwyg solution is
> better.
> I use python for almost every thing, except these related to GUI.

How do you mean WYSIWYG. I know what you mean but Don't know egactly
what you mean.


>
> On Apr 5, 8:31 pm, azrael <jura.gro... at gmail.com> wrote:
>
> > I am currently working on an application and I need a advise.
>
> > I am supposed to read data from a device connected to a serial port. I
> > am reading data using pySerial. The devise is sending signals with a
> > time between two signals of one second.
>
> > The application is supposed  to collect the data and put it into a
> > sqlite DB. wxPython GUI.
> > I am worried about this asspect that I have two solutions how to do it
> > but as I never tried it I wanted to ask for advise which one should be
> > easier.
>
> > solution 1):
> > The GUI is set into a separate thread then the part of collecting and
> > saving data. Well one thread for getting signals and saving data and
> > the other for GUI and data presentation
>
> > solution 2):
> > create an event which is binded to pySerial read methon. Well when the
> > devise sends a signal the event function is triggered.
>
> > Or maybe combine the two?




More information about the Python-list mailing list