Hello, I also worry about smslib :)
My main reason is that JavaComm / RxTx, i.e. the main interfaces for talking to serial devices are either dropped or left in their fate. Without a serial library, smslib is nothing. I know there are some other serial libraries as well, but I've yet to test them (has anyone?) I've even thought of converting it completely to .NET, but this is easier said than done - the PDU library is the most painful stuff. 1) I cannot give an answer on this. As a general info, I can say that my goal was to make smslib more streamlined, compact and easier to extend. V4 will *only* support gsm modems and maybe bulk operators (HTTP interfaces). Also, no smsserver at the beginning... V4 works for the most part, but it's not complete and lucks documentation. 2) V4 does. V3 does not. 3) This was the initial design for V4, but I am not sure it's optimal - SMSLib is a small project. Don't really know... 4) Word taken :) I know and that was one of the reasons I've decided to rewrite everything almost from scratch and review parts, write automated tests etc etc, Thank you for your thoughts. On 8 August 2013 22:55, Andrew-L via SMSLib Discussion Group < smslib+noreply-apn2wqcpc0kwghqoy7gmrh38xpei2as0mbz4fwym4rh3pz...@googlegroups.com > wrote: > Hello SMSLib developers and maintainers. > > I just worry about project future. > > 1. Github shows two branches v3 and v4. But v4 wasn't announced. When it > happens and which main changes we will see? > > 2. Why you don't use maven or something like that for automate building > and resolve dependencies? Also publishing in maven repository would help > distribute your lib and updates very and very much. Store jars and other > binaries in git is not good idea and shows bad quality. When it happens? > > 3. I was surprised very much when I took some test classes, SMS sender > using hardware and SMPP on one module. I think it shall be splinted into > separated modules and examples. It became from #2. If you have troubles > with it - I can help. > > 4. Code quality. When I started use smslib I made a lot of changes for > taking working and understandable version. I had a bug: after a few hours > native smslib stopped to take any sms from modem. I fixed it using > refactoring. And I can say that thread model was wrote by school boy with > basic java knowledge and have a lot of weak places (nullpointer for example > unhanded and could kill both AsyncNotifier and AsyncMessageProcessor as > result it could stop processing events at all). It is not usable for > serious projects. PDUUtils and other classes with parsing text was wrote by > someone who does not knows regular expressions. The code could be smaller > and understandable and looks more professional and work more stable > (without unexpected nullpointers) with professional tools like regular > expressions and patterns. When smslib will show best quality from box? > > Thank you for interesting. > > Andrew. > > -- > You received this message because you are subscribed to the Google Groups > "SMSLib Discussion Group" group. > To view this discussion on the web visit > https://groups.google.com/d/msgid/smslib/c6e8220d-cfbd-40ab-a897-fe0a8a675c01%40googlegroups.com > . > > > -- You received this message because you are subscribed to the Google Groups "SMSLib Discussion Group" group. To view this discussion on the web visit https://groups.google.com/d/msgid/smslib/CABkOnhNS8kB35XGhp2AA9kceSuHoBbj1zRyzquZ%3DA-cZ7W%3Dg9A%40mail.gmail.com.
