Leaderboard

You do know that you don't speak for everyone, right?

But if you want to make your forum really popular the "free beer" idea might be worth a try......

Hey, we work with computers and software. What could possibly go wron2c0+23423\09csxsz\+09r2123...

Lars, thank you for your post. It is indeed sad that Markus died. I want to correct one thing in your post. I founded Sisulizer with my brother, Markus and Renate. I wrote the application with my brother (in Delphi, of course). Markus and Renate handled the sales. We shared the support. About a ten years ago I left Sisulizer. I wanted to create a new and better localization tool that would be better suited for IT world heading to the cloud. I did not want to make a cloud only solution like MemSource and Crowdin. Instead wanted to make a hybrid solution that combines the best part of desktop tool and a cloud tool. So I wrote Soluling. The desktop part of that works like Sisulizer. It means you select a file, Soluling scans it, you translate or you let somebody else to translate, and finally Soluling build the localized files. Compared to Sisulizer, Soluling has the following improvements: The app itself is also provided as 64-bit Modern Office style ribbon UI The visual editors use real components. In Sisulizer they were emulated. This means that the translator will see the forms just as they appear in Delphi IDE. In .NET they use the real .NET components. Interactive translation memory with fuzzy matching and an interactive termbase. Sisulizer was loved by developers but not that much liked by translators because TM and TB were missing Support for 6 machine translation engines: Google, Microsoft. Amazon, IBM, DeepL and ModernMT More that 100 supported file formats including Delphi 11 Alexandria, .NET 6.0, Angular, React, Vue, DITA, Android, iOS and databases Command line version, SoluMake.exe , that can be used in build servers and even cloud based DevOps build processes Automatic conversion from Sisulizer's .slp to Soluling's .ntp. It generally takes a less than a day to switch from Sisulizer to Soluling. Soluling comes with open source I18N library that brings a nice grammatical number (plural) and grammatical gender (male/female) support for Delphi and .NET. Sisulizer customers get a discount. Soluling's desktop and command line apps are written in Delphi. Next year we start rolling out the cloud parts that let you push your projects to the cloud where the translators can get them and use either Soluling's desktop app or a browser app.

Based on historical experience this seems wildly optimistic!

It's really for you to decide. You have to test your app. We can't know what issues you will face. The big question to ask your self is what are the benefits and do they out weight the downsides which are primarily risk of new defects.

Well - that mistake was clearly not a highlight. *sigh* It was never the intention to approve the accounts manually, so I never expected to find a queue of accounts in that area of the admin-panel of this software. Something like this shouldn't happen - I'm honestly contrite. Maybe a free beer to everyone? 😉

There's a list of minimum requirements for Big Sur here: https://support.apple.com/en-au/HT211238. Note that includes late 2014 Mac Mini. There are legal virtual solutions available online, such as MacInCloud: https://www.macincloud.com/ and MacStadium: https://www.macstadium.com

If I was starting a new application targeting multiple platforms, I would develop for all platforms simultaneously while building the app. The reason is that different platforms will have slightly different ways of doing things and if you build the app to work well on one platform then address needs of others, it may affect some screen design decisions you would've made differently earlier. For example, iPhones and iPads don't have a back button but Android devices usually do so if you write the app with the assumption of an Android device first and assume everyone will have a back button, your screen may be too cluttered to add a back button later when you add the iOS platform. That's just one simple example and of course you should be aware of platform differences up front (and never make assumptions, etc.). There are many other considerations such as screen size and orientation, which style will you apply for the different platforms and how do all the different edit controls look and feel. All these things have subtle influences on your screen design. It's much easier to make those decisions in the early stages than to then try to morph a feature-complete app for another platform.

While mobile platforms are changing every year Delphi Community version is not a viable product. Every version of the mobile platforms requires changes in the development tools and community edition don't cover that. Even with paid versions of Delphi sometimes you have to wait a longer period of time for a solution (fix for the platform change).

Long term availability of a free community version depends on the long term availability of rich commercial customers who buy the expensive commercial versions.

The TMouseEvent is not handled currently by P4D. To see which events can be handled search the source code for "RegisterHandler". You could write some code to handle such events. Please see WrapDelphiEventHandlerTest under the Tests directory for how to do that and if you want submit a PR to add this to P4D.

Is 10.0 the first Delphi version that you use ? The risk you are exposed to is that if you don't update your code with each new release, the more difficult it will be. Between two consecutive releases, porting is quite easy. If you skip many releases, it will become more and more complex. Not only for Delphi itself, but also for 3rd party components you use.

I am just thinking about ways to realize such a remote free beer solution. Perhaps I should make an appointment with our local brewery for a brainstorming.

RADServer is a lot of promises, once using the product you find out you'd better choose another solution as a base for rest services. (we are still using it, but from week to week, less and less is used from the radserver itself), it's about the same as Delphi lot of commercial shit and shouting, but not really a usable product.

We've been waiting until Update 1 for every release for the last decade. Call me pessimist, but when things don't get better within a decade - will they ever?

Bad news: It appears that Markus Kreisel, who wrote Sisulizer, has died. https://web.archive.org/web/20210121010025/https://www.sisulizer.net/forum7/4079.html Posted Thu Dec 24th, 2020 11:54 pm by Harald Krause The link leads to an obituary written by Renate Reinartz, his wife and co-owner of Sisulizer. I can't find any activity online from her since then. Not on her LinkedIn account either.