1. Lazarus GUI. Make a GUI that works equally well on all compiler target platforms and gives a unique look and feel to all applications.
2. A slick, anti-aliased and zoomable OpenGL application GUI. Especially the text. That is easy to port, runs everywhere and looks much better than the current, pixelated ones.
3. Platform-agnostic, message-driven multitasking and multi-threading. Or, in other words: distributed processing.
And yes, I will help.
1. Lazarus GUI. Make a GUI that works equally well on all compiler target platforms and gives a unique look and feel to all applications. That would be the Apple way. Chance of success: low, without a strong and visible lead.Why is this in this list, and on the first place? The main bottleneck is a unified compilation platform. No specific syntax, like with Objective Pascal or the JVM target. And coming from that, the incompatible event and widget models. And it would make the most difference in establishing Free Pascal / Lazarus as one of the main development platforms.
1 and 2 are not Lazarus points, and the other toolkits do all kinds of owner drawn work, so that is their turf.
You don't think that having (1) as an option in LCL would help wider acceptance of Lazarus and FPC?
Quote from: Zoran on March 17, 2016, 10:56:43 amYou don't think that having (1) as an option in LCL would help wider acceptance of Lazarus and FPC?That depends on how you interpret (1). Polish Apple a bit within the current lazarus constraints: go ahead, but that is no real change from current policies, so I didn't take it that way.Make something universal as I read it: that will break the lazarus contraints too much or be very unwieldy, so I think there is no realistic outcome of such effort. Not if we can't even get a simple working cocoa backend in 5+ years. Nativeness on all targets is hard. Even Java GUIs with billions pored into them still feel non-native.
But fully working FPC-drawn LCL-widgetset, maybe will not feel native, but it will give you an option to have same look and feel everywhere. It must be nothing more but an option, the "native" widgetsets have to stay.
I believe that there are people who prefer this to "nativeness" and I believe that having it in LCL will be more helpful for wide-spreading FPC and Lazarus than telling people to go to one-man projects like MSE or fpGUI.
Not because these projects are not good, but new user will certainly more likely decide to stay with FPC if we can offer it in one place with "native" widgetsets, that is inside Lazarus. Inside the IDE with community of developers and users, not one-man project IDE-s. Plus Lazarus would offer easy switch from "OS-native" to "Pascal-native" controls and the other way.
Well, Delphi is as good as dead. And, to be honest: good riddance. As the developments of the last ten years were nothing to write home about.
Delphi is dead