Le 2015-10-26 13:09, Sebastian Kuzminsky a écrit : > Hello Nick and Fernand, I'm a developer on the LinuxCNC project and > we've been talking about getting linuxcnc-features into the next > stable release of linuxcnc. > > Is this something you'd be interested in, willing to help with? > > We noticed that there are two linuxcnc-features repos on github, what > is the relationship between them? > >
Hello Sebastian, I must admit you took me by surprise when you wrote you wanted to include features in next stable release. I knew it would be interesting but I though that it needed some more refinements before. I have a tight schedule currently and cannot spend much time to rush the project. It seems that you deleted bringing_features and I do not blame you. I hope you still think that it is a very good add-on to linuxcnc, nothing else comes close. Since I wrote more than 90% of the code I am the one that knows it best and I will help you. But you should not work with version 2.0 it is outdated, having been released about 4 months ago. Version 2.01 released last month is much better. They both have much code and files to delete. Those releases were the first I made and it was some kind of market test to find the interest. I believe version 2.02 will be ready to include in stable linuxcnc and I am proposing you what I know will work. Please correct me on what does not fit your view. Features depend on a good directory structure and links to those directories. APP_PATH : /usr/features files in this dir : features.py features.glade features.ui CHANGES README.md sub-dirs : catalogs lathe mill examples graphics images ini lathe mill lib support Working dir : $HOME/linuxcnc/features link to APP_PATH/features.ui links to APP_PATH/... catalogs examples graphics ini lib support USER_DATA : $HOME/linuxcnc/features/user (not $USER, full access) (preferences file will be saved there, no need to create) sub-dirs : catalogs lathe (files that will be saved here : default template and history) mill (user will save his modified menu.xml) graphics ini lib scripts (or the name you think is best, this is where resulting file 'features.ngc' will be saved) xml No files need to be created. This is where the user puts his modified files. Features will first search files in USER_DATA and use it if found, else it uses APP_PATH Links needed : /usr/local/bin/features to APP_PATH/features.py (stand alone from anywhere, no need for args, everything from defaults or preferences file) /usr/share/pyshared/gladevcp/features.glade -> APP_PATH/features.glade /usr/lib/pymodules/python2.7/gladevcp/features.glade -> APP_PATH/features.glade /usr/share/pyshared/gladevcp/features.py -> APP_PATH/features.py /usr/lib/pymodules/python2.7/gladevcp/features.py -> APP_PATH/features.py optional : /usr/share/pyshared/gladevcp/features_user -> USER_DATA Files to edit : /usr/share/pyshared/gladevcp/hal_pythonplugin.py /usr/share/glade3/catalogs/hal_python.xml Linuxcnc ini files axis-features.ini, axis_mm-features.ini and axis_lathe-features.ini could be added in sim.axis without any other files OR sim.axis.features dir could be created with the needed files Similar option for gmoccapy This is what I am preparing for release 2.02 I hope to have it ready in less than one month. Some new features I am adding are very difficult to implement, gcode is terrible IMHO. Regards Fernand ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers