1. My web site has moved to a new domain.  I'll be adding some new stuff to it soon.
2. Existing client work and contracting still going on (with the managing that entails).
3. List & Label work continues.  Been in talks with Combit and it will appear the pricing will be similar as in the past.  This will be part of #1 above.  But this ABC compliant version will not be the first offering.  That will come later.
4. Other former Solace products will soon be available, for the moment with minor improvements and changes.
5. A new line of commercial software is about to make its debut.

The above takes attention and effort and budgeting of time is important.  More later.

1. Remove redundant code from the templates.  A lot of template code is now gone.  When you make ABC compliant templates, a lot of the code in past versions is rendered obsolete since ABC takes care of many issues (like when to export a class, thus you will not find any template code for this purpose).  In addition to this, many settings are gone as well as the template code to support it.  For example, the checkbox to indicate if this is a DLL or not.  ABC is smart enough to spot when you use DLLs, so you don't need to indicate it twice!
2. Consolidate code.  There are far too many routines, and worse, these are generated by the templates.  It clutters up your code.  These routines, where still needed are now in class code as methods. In addition to this, some of these methods cannot be named at design time, so they don't exist.  For example, when you wish to send a file to List and Label, it makes sense to name the method SendCustomerToLL.  Obviously, a class designer cannot possibly know a name of a method in such a context.  However, the templates do.  They now generate new method names based on the file(s) you wish List and Label to know about.  As well as the method code.  The only work you need to do is indicate which file(s) you want.  By default, the entire record layout is sent, you can override and exclude certain fields (like Salary, password, login ID, etc).  I think this is far easier if you spent your time and effort making exceptions (if any) to the defaults.
3. List & Label classes properly show up in the embed tree.  This is for overriding public methods as you see fit, just like other embeds.  They have a DATA and CODE section (with PARENT call), properly colored too.  Part of the ABC standard.
4. Ensure each template in the set generates proper working code.  This means out of the box as well as developer changes and overrides.  This is the part taking most of my time as each template does certain functions.  Included in this is the removal of the old RepLay files.  This added complexity to your projects, something a few emails complained about and I agree.  This means the removal of the two files from your dictionary (no longer needed nor required).  This means that you don't have to import TXAs into your application either.  It means removal of template code that supported this.  I've still more work to do on this part, but so far, so good.
5. Each template in the set generates compilable and working code.  This milestone will take some time as well since each template has redundant (and sloppy) code in it.  As well as the new features requested.
6. Release a limited beta.  I hope I can do this by the end of Feburary.  This is a big part of the modernization project.  I see this in separate phases, first the tests will be limited to Clarion 6 and ABC applications.  In this phase, only test projects should be used.  No 3rd party add-ons.  Version 13 should also work, but lets see what the testers say about that.  The next phase would be existing L&L applications.  Since this is a new set of templates, some confusion is expected here since you will see two distinct and different List and Label templates in your registry.  How does this affect existing List and Label developers?  I'm taking notes about this.  I'm sure conversion (or porting?) to the new templates will stir up some issues.  My job is to make this as smooth as possible.
7. After any and all issues are addressed during the beta, the first release!  If all goes well (and when does that ever happen?), I see a March release date.

Some have asked questions about the cost.  Yes, there will be a cost, but I PROMISE it won't break the bank!  This is mainly because I've yet to see any revenue from this project (my revenue derives from current clients) and yet I am gladly giving support to the old product and won't take fees for this.  The upgrade and exactly how much and how to order is the subject of a future blog.  I've got a plan for this that I think will be fair to all parties (and easy!).

So that is it in a rather large nutshell.  I hope this gives you a rough timeline as to when and what remains to be done.  I'm pretty sure you will like the new templates and the flatter interface so finding settings is easier.  They are certainly easier on the eyes.  My goal is to make List and Label appear like its a part of your application, ready to design and run saved reports with almost zero changes required of the developer.  That is a common request by existing L&L developers as well as those who tried to use it in the past and got confused and dumped it.

Existing developer's concentration is on embedding List and Label in their apps; new List and Label developers don't need to worry about how to do this, but instead concentrate on using List and Label to design and run their reports.

1. There are too many routines that make following the code difficult.  I agree.  These routines are now moved to private methods, the templates will generate the code in context for them.  That is, List  & Label needs to know about which files?  This also means the template interface needs some adjustments so its near automatic as to which files are needed.  Easy enough to do with the table schematic.  If a developers wants to change this, usually by witholding a file from L&L, then minimal effort is needed there.
2. Manual variables should be easy to define and use.  Why not use local data for that?  Global?
3. Why is there a need for importing procedures into your apps and declaring files not in your dictionary?  There should not be.
4. And why must one use an extra file to define which report goes where?  This is the LLRepLay file to be precise.  To be honest, I don't see why this is needed.  Seems to me the classes and templates should be clever enough to make some assumptions in context of the procedure you use it.  They are default values and the developer is free to change them as they see fit.  Also, all data once saved in L&L is available to L&L.  Unless you make a change, then its merely re-sent.

These conceptual ideas forced me to change my approach.  Yes, that is going to add some time, but not much.  I got this data early enough to do something about it.  Its a bit of a pain for me, but that is so you don't have some later.

The end result I'm after is with minimal action on the part of a Clarion developer connects your application to List & Label so it looks like your product all along.  Regardless of L&L standard (embed designed reports) or professional (the report designer is also part of your application) versions.  I'm thinking a few minutes of installing and you now have the best report tool out there fully function inside your application as if it belongs there.

I'm impressed with the feedback and suggestions.  Please keep them coming!

• The same deals with Combit's List and Label core remains the same.  You will get it cheaper through us than going direct to Combit.
• Older versions will remain; for a short while longer until I determine what the market for these older versions are.  The templates support versions all the way back to version 6.  I'm not sure the wisdom of carrying such old versions, but I won't drop these until I know no one is using older versions (version 11 and older).
• Despite my distaste for legacy code, the legacy side will continue as-is.  So for you legacy developers, breathe easy.

What is coming?

• Version 12 support.  Makes sense since this is the current version.
• Version 13 support.  This is not yet released into the English community, it is planned for next month.  I hope to get an advanced copy soon and start building the support.
• ABC compliance.  The Solace templates are not ABC compliant.  The next release will be.  Its just easier for me (and you).
• Lack of features.  I've got some feedback, but I need more.  I've got the impression that there are features and APIs that are not supported and should be.  Please don't be shy and let me know what they are.  Bug reports are welcome.  If you've submitted these before, please send them to me.  I don't have one single report from any customer.  Please include your version and serial number (I do have a list of customers).
• A place to order upgrades and new products.  Don't expect this for at least a month yet.  I can get this set up easily enough, but until there is a product ready to download and install (with new docs), it does not make sense to make this for sale yet.

All in all, a very busy time; so I do ask for some patience.  I still have to finish up some custom coding, send out contracts for pending projects, chase down some overdue projects, legal paper work, finances, etc.

Oh yeah, there is also a new Clarion book in the works.  More on that later.  I'm tired, me. ;-)

A common criticism of SV is that they do not disseminate in a timely manner.  They don't market, keep quiet, etc.  I agree that they don't regularly disseminate, but I don't think that is a valid criticism.  One has to step back a bit and look at the overall picture.

Bob Zaunere, the CEO of Softvelocity does not state anything that is not ready for mass consumption.  Lets look at the milestones (for lack of a better word) at the things he did publicly state.

Clarion 7 (and .NET) was first mentioned at the ETC IV developer's conference in East Tennessee.  He talked about the new Clarion.NET compiler and even gave a demo of it.  There were discussions about a new IDE being 32-bit or better.  Very little else was shown or discussed.  But the message was simple, there is a new version in the works and the work has just started on it.  Actually, I think it may have started even earlier, but this was the first public event something was shown.  In the grand scheme of things, there was not much shown.

Then there was the Orlando Devcon hosted by Softvelocity.  There was a discussion on the future, however only some screen shots were shown.  The focus was mostly on the current edition, Clarion 6.

The next milestone was the conference in Brazil.  It was more of a short movie and it showed a primitive IDE that lacked many features.  It was more advanced than the ETC IV and Devcon presentations, but the message was misunderstood.  Since there was no demo of the dictionary and application generator (still off in the future), it was mistakenly assumed that the dct and app concepts were being dropped despite the many corrections by Z to the contrary.  Those features were simply not in a state to be demonstrated.

April of 2006 and we had the Australian developer's conference.  Due to some technical glitches, there were no visuals of C7 at all.  Yet there was data about C7 and I passed along key points that Z and I had in a phone call before I left.  It was a bit more data than what was even shown in Brazil.

The next milestone was Cambridge, UK.  Bob Z and some of his developers traveled there and the main focus was Clarion.NET.  The IDE was not much to look at yet.  But when showing off some of the features of Clarion.NET the language, it went over quite a few heads.  This was very new stuff.  In hindsight, it may have been a little premature.

The last milestone was the wildly successful Aussie Devcon in May of 2007.  There Bob Z demonstrated many aspects of the new IDE and some very cool features of Clarion.NET in that IDE. Clearly many parts of the new Clarion system were demonstrated to great effect.  Full details are on Clarion Magazine's coverage of the two presentations Bob Z did there.

Each of these events were covered by Clarion Magazine if you wish to read more details.  In between Cambridge and the Aussie Devcon, C7 was released to a core alpha team as the first of 4 planned phases.

But here is where the step back or overview happens.  In each successive event, you can see steady progress being made.  Blow by blow details are certainly missing on this timeline.  Whether or not one thinks there should have in this blog is up to the individual reader.

Bob Z is one of those types that says something when there is something to say. Today, there are two blogs on the SV site.  Very topical as each is exactly the subject that those that have yet to see C7 are going to need to know.  One is the various designers posted by Bob Z.  The later one is the new solution oriented project system, posted by Scott Ferret, aka Surf.

Both blogs have either example code or screen shots and a short movie showing the new alignment feature in the designer.

SV's dissemination may not be regular, but it is increasing in regularity, something one sees when you take a few steps back.  For me, it is not the irregular intervals that matter, it is what is said when something surfaces. I think it worth pointing out that that they are increasing in frequency as well.

For those that attended the Aussie Devcon, not much new in those SV blogs.  But for the rest of the Clarion community that did not attend, these two blogs should be welcome news as there is some nice details and visuals there.

Does it seem to you that the content of public comment by SV seem to be getting more detailed?  More information is appearing?  If you see such trends, would it seem to you to mean that things are starting to come together?

Which leads me to see the big picture.  I think there is enough evidence in that suggests that Z wants a very solid Clarion in all aspects and is willing to take the time to produce it.  Features either work or they don't.  If they don't you pound the living daylights out of them until they do. 

Solid.  Stable.  Working.  That seems to be the goal.  If that is what Clarion 7 and the hot on its heels Clarion.NET are about, then it will be worth the wait instead of the past behavior of dragging the community through this growth period (which would have slowed these projects down).

If anyone else was guiding Clarion down this path of evolution, it would have been done differently, no question.  The only question is, would it have been better overall?

I did some coverage of Bob Zaunere's presentations of Clarion 7 and Clarion.NET sessions.  These presentations were well received by all those that attended.  The feedback I got was that the future is bright, its nice to see what Softvelocity has been working on all this time, Z is a nice guy after all, etc.

After the enthusiasm settles (especially still fighting a little jet lag since my return to the US), I got to thinking how would one use all that stuff that was shown?  The presentations were complete enough one should have got a picture of the future.

On the Clarion 7 side of things, well, we get a modern IDE to finally catch up with our modern language and sensible approach to rapidly building applications.  During my presentation of how to code ABC compliant wrappers, I used C7 in part of my presentation.  Clearly the Intellisense should boost our productivity.  I also showed off a bit of the project system, but had to resist temptation to show off the other nice features in order for me to stay on topic.  But it did make coding a hand coded test project easier than in C6.

I'm getting really enthused about Clarion.NET. I think this will become Softvelocity's new flagship product.  Gone are the headaches interfacing to non-Clarion languages, badly written OCX controls and COM interfaces (especially events).  Tool vendors that have the Clarion developers as their market will have a vastly bigger market since the Framework does not care what language you use (you do have to follow some easy to implement standards).  On the flip side of that, those that buy 3rd party tools for their applications now have a wide list of vendors to choose from, they no longer have to be Clarion vendors.

What about us regular super heroes that have yet to wear our undies on the outside? (thanks to Stu Andrews, I can never forget such a concept!)  A past complaint with Clarion is that dropping an OCX or ActiveX control in our applications is not trivial.  It does appear that such complaints are going to remain there -- in the past.  A few Clarion developers can code the wrappers needed to make them work, but it takes work, similar to what C++ developers must suffer through.  And that does not describe today's Clarion developer. Even those of us who can do this, don't want to!

Windows Mobile has been almost out of reach.  Not anymore.  The new IDE supports the mobile device emulators which are available from Microsoft, I think for free.  Use these puppies if you don't have the device (or funds) you are coding for.

ASP.NET is also now in reach.  Templates that generate C# code has got to be something that excites the true Clarion.NET developer.

The only thing I can think of that has yet to be addressed is the template language.  It needs some serious love, despite its current abilities.  Clarion 8 anyone?