On Sat, May 23, 2015 at 4:42 PM, Chris Morley <chrisinnana...@hotmail.com> wrote: > > >> Date: Sun, 24 May 2015 00:16:53 +0530 >> From: gswithba...@gmail.com >> To: emc-developers@lists.sourceforge.net >> Subject: Re: [Emc-developers] StepConf > >> >> Thanks. I got overall idea what to do. But is there any tutorial or >> some documentation of >> these file so that I can understood properly. As I found it difficult >> to understand that what each function is for. >> >> Is there any other task like making GUI new or make it attractive :P. >> >> >> -- >> >> Gurwinder Singh Bains >> http://gurwindersinghbains93.wordpress.com > > stepconf.py > -main program, initializes data, loads and saves data, > has most of the functions to calculate data, and the tests that use HAL. > > pages.py > - This is used to manipulate the pages of stepconf. > Stepconf is based on a GTK2 notebook widget. > It actually tabs through the pages based on the next and back buttons. > We have hidden the tabs so it doesn't look like a notebook. > > often it actually calls functions in stepconf.py to do calculations > > it sets the widgets from the data: PAGENAME_prepare(self) > and sets the data from the widgets : PAGENAME_finish(self) > it has the callback functions from the widgets of the pages. > callbacks are the mechanism to cause action to users selection of the GUI. > > self.d is a reference to data (data is in stepconf.py) > self.w is a reference to widgets (widgets is in stepconf.py but comes from > GLADE) > > stepconf.py and pages.py are used to build the data base from user inputs. > > build_HAL.py > -This builds the HAL files from the collected data > self.d is a reference to data (data is in stepconf.py) > self.a is a reference to stepconf.py's functions > SIG is a reference to steconf.py's private data which is mostly signal names. > > build_INI.py > -This builds the INI file from the collected data > self.d is a reference to data (data is in stepconf.py) > self.a is a reference to stepconf.py's functions > SIG is a reference to steconf.py's private data which is mostly signal names. > > all the GLADE files. > main_page.glade has a top-level window with the notebook widget. > all the other glade files are later added as tabs to the notebook. > If a widget needs to be referenced in the python code it must have a unique > name. If you start stepconf in a terminal it will show warnings for basic > name clash. ( stepconf -d will give more debugging info ) > all pages (besides main_page.glade) must NOT have a top-level window. > This can be done by right clicking an widget in the editor > and forcing it to be a top-level object.
Thanks, its helpful for me. You know that GSoC starts and I am working on povray export task. I have to complete my this weeks task before end of this week so that I can work on and will decide what tasks I will do for LinuxCNC. I want to decide tasks early so that I will concentrate on those parts only. I have create my git repository for linuxCNC below is link for it. https://github.com/GurwinderSinghBains/Linuxcnc -- Gurwinder Singh Bains http://gurwindersinghbains93.wordpress.com ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
