Recently, Saurabh Sood suggested me to blog more often, and this an attempt yet again to write more often. Off course, what I may write may or may not be appealing to others, but then its my area 🙂
Anyway, the past few weeks, I have written a bit of code, a bit actually means a teeny weeny bit, but hey, the good news is SaX3 is completely localized / internationalized now and this will be shown in the next openSUSE release.
Offcourse, if you are a translator, you can help me out by translating the files at https://github.com/openSUSE/sax3/tree/master/src/translation and by sending an email with translated files, I will include it in the upcoming repos, I will also try to get it to the openSUSE translation repository, so that lives become easier for all of us.
Other than that, we have a new contributor at openSUSE and who is already writing great articles for the news team, thanks a lot Nenad 🙂
There are plenty of things down the line and I hope I will update the same in the coming weeks, till then cya people..
The changes I have made in SaX3 in the following week
1. Fixed a few nasty bugs.
2. The monitor module does not work which works now ( I need to be more careful the future)
3. Tried porting to openSUSE 11.3 ( Testers Required)
4. Pushed to factory, but it is hghly recommended to add X11:sax as your project repository for sax until 12.1
Please test it thoroughly,and let me know if common troubleshooting use cases for a single monitor is supported. If there is anything missing let me know. Xinerama is not supported
For both factory and 11.4.
Next up is touchpad, which I will finish by this thursday. And will begin pencil downs the following week onwards.
Its been a long time I posted anything, but things look promising now, SaX3 is moving forward and 2 of its module have been completed, the keyboard module and the mouse module, so please test it and give me your feedbacks and if there are any bugs. BUGS will certainly be squashed, I dont know about UI changes. Suggestions are welcome. I plan to work on touchpads next.
This is my 2nd report, this week not to show much for the users, but we did a quite interesteing things. SaX is now module oriented.So, if anyone wants to write a module for SaX3 it is possible now. Besides the important things which I did was
Learn the augeas C api
Submitted a .desktop lens for augeas
It is module oriented
Tried out Doxygen
SaX3 is now localised.
The launcher is now complete 🙂 Again, the source code is here http://github.com./manugupt1/sax3 Regarding modules, If anyone wants to check out how modules work, they work using .desktop files in /usr/share/sax3/modules.d. If you will remove it we can remove it from the launcher.
This week I worked on SaX3 internal UI architecture, offcourse we will be using libyui but we wanted to make it as flexible as possible so that the UI Library can be replaced by anybody and still keep SaX usable, for that we implemented the factory pattern and most of the code was working. Finally, we have something working and the screenshots below show that SaX3 is working in graphical mode and ncurses mode.
I am adding screenshots of the launcher that will launch various configuration modules such as keyboard, mouse, graphic card etc etc . Also this is just a start and by the time I present my next report I week, this will be much cleaner and you can play around more with it. Right now it does not do anything so dont get surprised.
Well, SaX off course needs no introduction for old time openSUSE and SUSE Users and certainly lots of people want it to be back on openSUSE. My proposal for Google Summer Of Code for SaX3 was selected and my mentor will be Michal Hrušecký. Now I will tell about the little interesting things on which I will be working on and some of the more interesting things later on at the end of the blog post.
SaX as most of on planet SUSE knows stands for SUSE Advanced X Configuration Tool, but for others lets say we want to have a Graphical Front End for Xorg.conf.d, so that we can easily configure our hardware too. The specific bits on which I will be focusing would be keyboard, mouse, touchpad and offcourse whats SaX without a good screen configuration tool like monitor, yes we will support that. One of the interesting features that SaX3 will support that it will have a graphical UI for ncurses mode even, so even if your X is not functioning, you dont need to remember a lot of command line commands.
Offcourse, a SaX without a proper monitor configuration is worthless and here is where I will need a lot of inputs from people at forums and other places. I am greatful for all those have offered to help me from forums and everywhere else. I would take an oppurtunity to as to what platform will suit them, the forum itself, a Mailing list or through private channels or on IRC even where I can bug them a bit and make the best use of their experience SaX can work as expected.
Please post your views on your comment and I will get back to you soon.