Its market forces, half the problem is listening to the naysayers, I look back at some of the app’s I’ve done in the past and I should not have shelved them after listening to the naysayers but I think some people have different agenda’s, like customers not wanting to be abandoned or perceived lowered level of service ie not getting Dev Support if other products got successful. I think some of them could have been quite lucrative with hindsight.
One thing I’ve learnt there are plenty of external factors to contend with like Search Engines, social media and these are beyond out control, but I know from experience there have been some who have been planning ahead and there is always more than one way to skin a cat.
Perhaps all true. Nevertheless, we are not addressing templates/classes for the few.
Most of ABC is over 25 years old (CW 2.0 released June 1996). Dct based templates, tps files, and the desktop are all faded in the rear view mirror. The Clarion potential, however, is being taken to the SV deathbed, even with all the fantastic assisted living the community at large has provided in these twilight years.
And look at how the Internet has taken off and exposed people to much more knowledge.
Yet programming hasnt changed that much from what I have seen over the last 30 odd years, I remember when that NoSql started to appear, it got its fanbase but now some of that fanbase is falling out of love with it.
In short, most of what has transpired in the NoSQL movement is simply a forgetting of the reasons that we switched to relational databases to begin with.
If History doesnt repeat, it certainly rhymes and I think Clarion has a place at producing code efficiently, better than most of the stuff I’ve seen and tried, but learning the templates is a jump which everyone should make imo, certainly with hindsight, but who can predict that lightbulb moment?
I wonder how long it will be before CoPilot gives us buggy code, seems its not all that its cracked up to be and a more diverse template market could probably give CoPilot a run for its money in some arena’s. GitHub Copilot · Your AI pair programmer
The same risk CoPilot exposes users to also exists in any code that is essentially cut and pasted, but at least with the Clarion Templates, its tried and tested in an “open source” like way, ie everyone can see the source and comment on it, but it costs money to enter the game unlike FOSS where any good hacker could con their hack into a repo. php.internals: Changes to Git commit workflow
Just lamenting that there isn’t a standard, well-known to the community, public repository for this sort of info - whether it’s Wikipedia or ClarionHub, or something else. Sorry - that really didnt add anything to the discussion:/
I understand the concept, but I find the actual crown jewels to be worthless. Maybe they have some historical value, but otherwise - who cares? I realize that’s a distinctly non-Brit perspective:)
I find the “keys to the kingdom” comparison equally meaningless.
To me, the WHY is what’s important. Why is this feature or that feature considered the “crown jewels” or the “keys to the kingdom”? Does that mean that (like the crown jewels) these features are worthless except for their historical value? I doubt that was the intention
Not trying to be difficult here. I see comparisons to terms that dont convey a reasonably specific value or meaning, rather than some specifics that indicate why a particular feature is hugely valuable. This would seem important, particularly when trying to sell the idea to someone who isnt a Clarion insider.
It is a fairly universal concept though, which I think plenty of people will understand, however I couldnt use something like “Templates are like the Fort Knox of the Toolset” because a) there isnt any gold left in Fort Knox and b) most people dont know what Fort Knox is, ergo, Fort Knox hasnt conveyed the concept of value or importance.
I cant use Religions because that causes too many disagreements, so what else would you suggest I use to convey the concept of importance and value?
The other problem I didnt want to get too buried in is detail, Templates, a word many are familiar with will generate an idea or concept in the mind without getting into the details of what is a template. It could be briefly described as a cookie cutter but in the programming sense most people will assume there is more to it. Its got to be enough to whet the appetite but not too detailed to bore the pants of the reader, it is after all the opening paragraph.
There isnt really anything else I could use, I cant use a comparison to a rival product, thats shooting oneself in the foot, and pretty much anything else is going to be branded in some way which then causes all sorts of legal issues with copyright and things like that.
I know you like your Cadbury’s Milk Chocolate, but other’s prefer Hershey’s, so you see I couldnt really use anything else.
One thought I had was to put the Templates into a GitHub repository and have an open source type effort to improve them.
I see this mainly for the Legacy Templates in which I have a lot of code. I also see Legacy as changed less, simpler and self contained. To do this for ABC would often require joint modificatons of the ABC classes which complicates things. Now that AnyScreen is in the picture this seems less likely as AS does require some template mods.
Examples:
The way Legacy generates code for Browse Column Colors is verbose and poor. I would change the code to “Calculate the Color” and store it in a variable, then do one assignment. An embed between those 2 would allow overriding the template color logic. Many times it would be easier to enter the logic as code in the Embed rather than via Template data entry.
Often run into small bugs that are easy to fix: The View Form template did not handle TEXT CHECK OPTION or SPIN. The Process and Report templates should look at the Driver of the Primary file and decide if it supports Records() else use Bytes() for the Progress bar.
Standardising the controls so things like all buttons are 12 or 14px high instead of a mish mash would be a start, some have icon’s some dont, justification is another.
I dont know what SV would say about having the templates in a Github repo, would these be on public display or something, I’ve not used Github so dont know how it work?
Might be helpful for Legacy, but does little for Clarion looking forward.
Most relevant to the thread topic is for templates to enable easy implementation of classes.
However, a rethinking of the critical base classes first seems necessary to allow and easily take advantage of what is current. SV has been riding the intellect of the Topspeed Chapman/DAB era for a LONG time. I wonder what those folks might come up if given the task today? On the other hand, I have to believe there are like minded, younger folks around too. Unfortunately, there is little evidence to suggest that SV will be leading the search to find them, let alone providing outcome guidance.
This is very straight-forward to do today using the freely available cape01.tpw and cape02.tpw.
I’ve used them a few times in webinars now - enough to see how to use them - which isn’t hard. Documentation for use is inside cape01.tpw, and the Reflection Class product (free) makes a good example of using them.
