michab66
|
Posted: December 23, 2009 18:02 by michab66
|
|
Hi, could someone explain the general strategy of BSAF? To be more concrete: I was in an evaluation phase checking whether we can use SAF in a commercial application. In our next UI refactorings we expected to be able to remove a lot of our code, replacing it with the concepts from SAF. I just migrated our in-house test-application from the Sun SAF reference implementation to BSAF. My experience was a bit mixed: BSAF did a some of restructurings that we had to follow. But to make a long story short: Most of the problems could be solved. That brings me to the key question: Is there a clear strategy in the evolution of BSAF? Does it make sense to use BSAF in a commercial application or is it not yet mature enough? The problem is that it is actually hard to understand what parts of SAF or BSAF are 'official' and can be relieably used and which are not. For example the TopLevelFactory class from the RI was removed, so it seems not to be part of the strategy. Then we were not able to automatically keep the position and size of the main window with BSAF. In this latter case it is even hard to understand whether this has been removed because it is not part of the BSAF vision, if it is simply a coding error on our side or if it is a defect in BSAF. So what to do? Better stay with the RI for a while? Best wishes, Michael. |
BSAF general strategy
3 posts
Replies: 2 - Last Post: June 04, 2011 10:46
by: jhirzel
by: jhirzel
showing 1 - 3 of 3
etf
|
Posted: December 27, 2009 17:55 by etf
|
|
General strategy of the project is preserving of key principals made by Hans Muller: - as small and simple as possible; - explain it all in one hour; - work very well for small and medium applications. Thus no revolutionary changes are planned. The top priorities are fixing bugs, code clean up, unit testing coverage. Nevertheless new features and API improvements are also considered but without braking backward compatibility. SAF is unsupported project and I see no sense in staying with it. BSAF is based on the last public stable release of SAF (1.03). Version 1.03 was the last release made by Hans Muller. All the following releases are inconsistent, unstable and have broken API. BSAF is an open-source project developed by the community. We have no resources to provide the proper level of testing. That is why we are greatly interested in users feedback. Stability and quality of the project depends on your contributions: - bug reports; - patches with fixes and improvements; - suggestions on architecture and API improvements. We are looking forward to further cooperation with you. |
Replies: 2 - Last Post: June 04, 2011 10:46
by: jhirzel
by: jhirzel
