[RPM (6.0)] [DIST generic] smc-6.0.1-3.jpp6
Will Tatam <[email protected]> Thu, 1 Nov 2012 04:06:16 +0100
| Newsgroups | gmane.linux.jpackage.announce |
|---|---|
| Message-ID | <[email protected]> |
Name : smc Relocations: (not relocatable) Version : 6.0.1 Vendor: JPackage Project Release : 3.jpp6 Build Date: Thu 01 Nov 2012 04:04:57 AM CET Install Date: (not installed) Build Host: flat.netmindz.net Group : Development/Java Source RPM: (none) Size : 3620668 License: Mozilla Public License 1.1 Signature : (none) Packager : Will Tatam <[email protected]> URL : http://smc.sourceforge.net/ Summary : State Machine Compiler Description : Your application lives in a world of asynchronous, unordered events: mouse clicks, timeouts, messages, and OS signals. And you're ready for them. You've carefully designed your objects. You're using robust patterns that facilitate reuse and anticipates future product direction. Your dynamic models allow your objects to recover from all but the most catestrophic events. Your application is ready for anything. But there's a hitch. Your detailed state diagrams are only pictures. How are you going to translate your drawings into code? A transition matrix is cryptic while switch statements means your state machine logic is scattered all over your code. The state pattern looks like a great solution but that means writing and maintaining a class for each state - too much work. Enter SMC - The State Machine Compiler. Now you put your state diagram in one file using an easy-to-understand language. SMC generates the state pattern classes for you. No more hand-maintained transition matrices. No more widely scattered switch statements. Instead, the state diagram is in one place, coded directly from the picture to the SMC language and is easily maintained. SMC uses the state pattern to its fullest extent. In the real world, events don't always happen when they should. Dealing with unexpected events is a must for a robust application. By combining virtual methods with the state pattern, SMC allows you to define "Default" transitions - transitions which allow your objects to handle unexpected events, recover and continue providing service (rather than crashing, burning and getting you into trouble). SMC is a Java application. That means SMC will work on any platform where Java 1.5.0 or better is supported. --------------- Will Tatam <[email protected]> 6.0.1-3 - Auto rebuild for JPackage 6 in centos5 mock --------------- smc.src: W: source-or-patch-not-bzipped smc-6.0.1.tgz smc.src: W: non-standard-group Development/Java smc.src: W: no-signature smc.src:192: W: libdir-macro-in-noarch-package (main package) %dir %attr(-,root,root) %{_libdir}/gcj/%{name} smc.src:193: W: libdir-macro-in-noarch-package (main package) %attr(-,root,root) %{_libdir}/gcj/%{name}/%{name}-%{version}.jar.* smc.src: W: invalid-license Mozilla Public License 1.1 1 packages and 0 specfiles checked; 0 errors, 6 warnings. --------------- Index: smc.spec =================================================================== RCS file: /home/projects/jpackage/cvs/rpms/free/smc/smc.spec,v retrieving revision 1.4 diff -u -r1.4 smc.spec --- smc.spec 14 Jun 2012 06:28:36 -0000 1.4 +++ smc.spec 1 Nov 2012 03:06:14 -0000 @@ -38,7 +38,7 @@ Name: smc Version: 6.0.1 -Release: 2%{?dist} +Release: 3%{?dist} Epoch: 0 Summary: State Machine Compiler License: Mozilla Public License 1.1 @@ -203,6 +203,9 @@ %doc %{_docdir}/%{name}-%{version} %changelog +* Thu Nov 01 2012 Will Tatam <[email protected]> 6.0.1-3 +- Auto rebuild for JPackage 6 in centos5 mock + * Thu Jun 14 2012 Ralph Apel <[email protected]> - 0:6.0.1-2 - Avoid FileDigest and PayloadIsXz problems on EL5