Xojo Conferences

« FileMaker DevCon to s… | Home | MBS Booth ready for F… »

The big cleanup for our Xojo plugins

There is something I’d like to talk about. Fewer people are using Real Studio and as we approach the end of live for 32-bit on all operation systems, the days of Real Studio are counted. Everyone should move this year to Xojo in order to support 64-bit later this year.

For my Xojo and Real Studio plugins, I do consider dropping Real Studio versions. Old plugins stay of course available for a long time, but download rates on current plugins in the Real Studio format are far down (<3%). Would someone miss newer plugins not being available in Real Studio format?

Second I may do a big cleanup and remove old stuff like everything related to QuickTime, FSSpec, GWorld pictures and maybe a few more like the older overlay window class. We could even consider dropping Carbon for Mac. Wait, I think this is still used for console projects, so we may need to keep it around.

On the plugin itself, we may merge some to reduce the number of plugins we deliver and make it easier to manage them. Or otherwise split them more into individual ones, so you can easier sort out the parts you don’t need. Not sure yet.

Otherwise I could really cleanup more aggressive and remove some parts. For example the ImageMagick plugin is not well maintained by me as I favorite the GraphicsMagick one for my own projects. Same for the PHP plugin which is not the best thing in the world as the php code misses usually extensions and the apache environment. Next to drop could be LCMS Plugin for the older 1.x version of the library. Everyone should have moved to 2.x already.

In general unless a lot of people relay on something, the cleanup could make my life easier, the build processes and deployment faster and finally with less plugins to load actually give faster Xojo startup times.

What do you think?
24 07 17 - 15:38
nine comments

I think it’s a good idea. Of course you won’t find out what people rely until you remove it. But then if people are still using Real Studio I doubt they’re updating very often and they can always go back to an older version. I say go for it.
Bob Keeney (URL) - 24 07 17 - 15:47

Same as Bob said. I vote for fewer plugins and not for more individual plugin configurations.
Sascha (URL) - 24 07 17 - 17:11

Absolutely go for it. Anyone who needs older stuff still has the older versions. You’ve overlapped a long span already. Fewer plugin files are also fine. Years ago you already had it so only the portions of each plugin are compiled into the builds so there should be no downside on build sizes of apps.
Jay Lichtenauer - 24 07 17 - 21:26

Not sure if ‘the older window overlay class’ is OverlayWindowMBS. If it is I still use this. Happy to loose Real Studio plugs and everything else you mention. Would prefer less plugin files than more. You can specify functions that are deprecated though can’t you? Maybe this would be a good way to see what people require for the questionable functions.
Mark Franken - 25 07 17 - 10:27

do it! it’s an excellent idea
nkne - 25 07 17 - 14:54

You are aware some Carbon API do not have a Cocoa alternative? For example the Status Items/menu are used a lot and as far as I know, there is no Cocoa version available.
Jan - 26 07 17 - 09:29

Excellent. Go for it. Just mention some where the depreciated functions.
Sunil Abraham - 26 07 17 - 15:21

Moin, Real Studio Plugins können gerne eingefroren werden. Sollte ein Big Bug noch in den RS-Plugins sein, so müsste man diesen aber noch beheben. Beim Trennen/Zusammenführen von Plugins wäre es mir wichtig, dass man diese am Namen erkennen kann. Mac…. oder Win…. oder Lin…, damit man die Plugins weglassen kann, die man nie benötigt (bin Windows-Programmierer). Alle übergreifenden Plugins können Ihre schreibweise behalten.
Frank Jürgensen (URL) - 01 08 17 - 10:56

Carbon should definitely be dropped, the next macOS release will most certainly drop it.
halamri - 08 08 17 - 15:57

Remember personal info?

Emoticons / Textile

Hide email:

Small print: All html tags except <b> and <i> will be removed from your comment. You can make links by just typing the url or mail-address.