On 12/09/12 01:12, Richard Rose wrote:
> I'd keep the app in C55 if its not causing any problems other than
> needing some new functionality (and depends on what new functionality
> needs to be added) simply becuase if the program was not well written
> you will need to make sure all variables are thread safe in C6 including
> any Queues in use as one example and the C6 compiler enforces the code
> syntax more rigorously so code that didnt throw a compiler error in C55
> could throw a compiler error in C6. Migrating to C6 could be a can of
> worms. Lets just call them some of the undocumented features of C55.
> Some templates will need revisiting in C6 if used as they were modified
> so could mean reselecting a template option which will be time consuming.
>
> I've migrated a number of apps to later versions of Clarion and all have
> had their own problems when migrating to C6 or later. Programmers all
> have different styles and the vast majority dont program defensively ie
> not trapping and handling errors. Clarion also attracts alot of non
> programmers becuase any amateur with half a brain cell can knock out
> something resembling a program so thats also worth bearing in mind when
> taking on other peoples work to convert.
>
Thanks for the advice. Our aim is to keep it in C5.5 - if we decide to
migrate, we will probably re-write the program using totally different
tools. It was never a good match for Clarion in the first place, but
the programmer who did the job convinced us that he could make a great
application quickly using Clarion. Without any experience of Clarion
ourselves, we took his word for it. My own choice for a tool would be
Python with wxPython toolkit.
The program doesn't use MDI at the moment, and I don't see it coming in
the future for this particular application.
>
> I mention this becuase there is a rumour circulating the MDI has been
> deprecated but there is nothing official on their website and I have
> asked MS employees who would be in the know.
MS don't really know themselves where they are going at the moment. On
the one hand, they seem to want developers to target "Metro" because
they hope that if people learn to put up with a totally insane gui on
desktops, they will be less reluctant to buy telephones and pads with
the same gui. But on the other hand, they know that Metro is useless
for desktops and desktop applications, and want people to keep
developing "normal" windows applications so that users don't move to
Linux or Macs.
For the most part, I don't give a *beep* what MS think or say in this
regard. The application here is designed to run as the only program on
the machines in question, so we use XP on these systems. And if we do
end up re-writing it, it will be done with cross-platform tools so that
the dedicated systems can run Linux instead.
>
> In the C7/C8 runtime, sleep delays were added to the start of each new
> thread in a bid to help minimise the multiple MDI min/max/close buttons
> from appearing, users have reported C7 apps were slower than C6, and I
> believe in C8 MDI toolbar support was dropped as well to also help
> minimise the mdi button problem but the MDI API call hasnt been changed
> as at the latest build in C8 in July 2012, in favour of what MS recommends.
>
> Its also worth noting that when a MDI child window sometimes dissappears
> off screen and in the ini file its got the XY coords -
2147023728 this
> value is a fixed value passed by the runtime to the window api
> CreateMDIWindowA when its called. Ideally the RTL would look for any
> reg/ini window position before creating the window but it doesnt and
> thats not the only critisicm I have the RTL in its C8 version, but I
> dont run the company!
>
> C6 isnt as stable on Vista/W7 32 as C6 is on XP but its very solid on
> XP, although your biggest risk is having too many controls on a
> window/report or embed code which goes beyond the 16bit register limits.
>
It's not a very big program, so it should be no problems here. (I
remember having to deal with an over-grown Visual Basic 3 program that
had trouble with the 16-bit limits on controls - users had to be careful
not to open too many windows at a time. That got migrated to Python,
solving those problems.)
> If you run C6 in seperate memory and make the template registry readonly
> you can also run multiple instances of Clarion all at the same time.
>
That won't be a problem here.
> You could buy C8 and use the C55 compiler and runtime in the new IDE but
> people report variable IDE stability issues, if you dont change the IDE
> layouts and config too much you get less stability issues, but if you
> want to undock taskbars and make the IDE more of your own then things
> become alittle disconnected.
>
I am really hoping to be able to run a pure C55 installation. I still
haven't found a way to do so legally. I think I will be able to get a
copy of the installation CDs, but not the license, from the original
developer. If I buy a full C8 license can I install C55 instead?
> Just a few points which could affect you at this moment from someone who
> has used it since the dos CPD 2.1 days but is now also porting their
> apps to other languages to take advantage of what is missing from Clarion.
>
>
Out of curiosity, what are you using instead?
mvh.,
David