Hi RCB, Sorry I don't understand Spanish but I understood your point with Google translate. I hope you are OK with English...
You are right. SambaPOS source code is hard to work with. I tried organizing source code better for V3 version (
https://github.com/emreeren/SambaPOS-3) and naming things better but I know it is not enough. The worst part is I won't have enough time soon for creating a documentation for source code. On the other hand I'm still improving myself and making big architectural changes that can break documentation.
Yes my intention by making it open source was having support from developer community but I couldn't attract enough attention and as new features developed things changed.
But still we can do something.
1. You can create issues on Github. I normally relate issues with code changes and by tracking change you can understand how it implemented.
2. It is hard to create long answers to questions such as "tell me the architecture" but you can try implementing a feature and ask questions about how it can be done.
3. I'm planning to implement support for altering SambaPOS behavior with extensions. You can tell me what you want to create and I'll try creating a customization point for that area.
4. While trying to implement extensions we can document what we learned so a development documentation can born.
In fact I'm not an experienced OSS developer. This is my first try and I'm open to all suggestions about improving things.
Thanks.
PS: Is it true Cuban girls does not rolls cigars? How disappointing
