Were you the one whose code had Dimiants?
P.S. seen Dimiants in code posted recently, canât remember where âŠ
Were you the one whose code had Dimiants?
P.S. seen Dimiants in code posted recently, canât remember where âŠ
This is SOP for anyone thatâs worked in the âreal worldâ, which is probably why you donât find it mentioned on Xojo: Why use the Xojo programming language
What are Dimiants? Is that some sort of pun (Dims in it?) that I am missing?
-Karen
Its what happens to Variants when you search and replace Var for Dim
People should use my reformat code script, it takes care of all that without you thinking about it
I always search for "var " and/or for whole word when I do that search and replace to avoid such issues.
-Karen
Link might be helpful âŠ
Exactly. But it doesnât mean that Xojo Inc. has not already entered into such contracts. Really, it says more about the mickey mouse âcustomersâ who donât know how to negotiate, than the product theyâre considering.
New Xojo product suggestion: Xojo Platinum.
For an annual fee of $500,000 (give or take), you become a member of the Xojo source code escrow pool. Xojo Inc. could use the cash flow for all sorts of things: new features, bug fixes, etc. If youâre a big company, you wouldnât even blink at a half million/year.
Hi Markus,
If you click on Julianâs profile, there is a link there.
I never use Xojo without this script. It is the bomb
Have fun!
I was the one who posted that
Guessing youâre not old enoughâŠ
It was just a test, I use mainly El Capitan, so no API2 Xojo version⊠*
I have an external HDD with High Sierra, but 3 minutes of boot time is boring⊠It also needs an USB port; the second one is for DVT and thatâs all. If I want to scan / print / another external HD, I need to remove the DVTâŠ
I could search and replace with an ending space tooâŠ
Talking about API2. My main concern was the all at once change. Changing few instructions in each release would be - for me - far better. All at once was a huge step that I could not do. (yet ?)
To be a âXojo consultantâ is not tecnically a licence violation?
âYou wonât build apps from the projects of others so that they can avoid purchasing a Xojo License Key(s).â
Maybe that is one of the licence risk the tdd-contractor told about to the OP
That would apply to just compiling an App someone else wrote, not an app you write for someone else.
My favorite search/replace fiasco was when I was helping produce a childrenâs Christmas play for church. I was working the cast through one particular scene when we encountered a line that was simply incomprehensible. It actually took me 2 days to figure out what had happened. Turns out we had more girls in the cast than boys, so they had changed a part from Mark to Jessica. The original line was âThatâs remarkable!â To this day, I can still pronounce âThatâs rejessicaable!â (wasted brain space)
True.
Iâm not that old âŠ
Mentioning C as the father of all, I was referring to the current languages.
What would be an interesting counter to some of the technical debt issues would be to hear if Xojo had an option for source code access through an NDA which large companies like Microsoft do for partners and enterprise customers (see Microsoft | Shared Source Initiative). But as that option didnât make it on Xojo: Why use the Xojo programming language then I assume this isnât an option.
I guess this is another reason for backing technology from a large company and destroys most arguments about small/agile vs large/slow, you might not be able to speak to Satya but at least you can fix the bugs that matter to you, Iâd have a bit of that action if Xojo offered it.
To me, the new Xojo web page seems to have been created in reaction to Kimâs post and the responses that followed.
I was also drawn to this paragraph at the end:
Choosing Xojo means choosing to work with a team that is accessible. If you have a big project and an important problem to solve, you can reach the people you need to reach all the way up the Founder and CEO, if necessary. Thatâs hardly the case with the mainstream languages provided by large companies.
If you need to contact the CEO directly then something has really went wrong. It also gives you the impression that contacting the CEO will make a difference (which in my case resulted in nothing happening).
Ooof, I noticed your comments from a year ago on one of my three year old bug reports, damn that sucks.
The âSmallCompaniesAreBetterThanBigOnesâ is annoying as f.
They are not.
I donât want to talk to the CEO. I want that the CEO does its CEO-Things, while there a is a development team containing leaders and a reasonable number of developers. If I want to talk to someone, I want to talk to them.
Typescript for example has a huge ecosystem, its made by MS and I donât have to talk to Satya Nadella, I simply go to Github and open a case. I can even contribute to it.
Java, MySQL, NPM, Github, Xamarin, all former more or less smaller companies which grow under the roof of a big company.
I mean, it is okay to be or to stay small. You can also have outstanding products for sure. But imagine what your product can become if you have more man power? Imagine what Xojo could become with a development team bigger than 6 heads.
So please stop to tell us, that it is an advantage to be little. It is not. It has never been.