Hi,
We would like to announce that Klorofil Platform Discussion Forum is ready to be used.
Do you have opinions, advices or comments related to Klorofil Collaboration Project? This is the forum for you.
In this forum, you can speak directly with the Klorofil Development Team.
Regards,
Klorofil Administrator
just curious about the main bussiness proccess of klorofil, do you have some kind a graphic or illustration about how it works?
for gambArt design, you could brows to klorofil home page, but if you still have any question, please submit here, we'll be hapy to answer your question.
May be you can wait for ver 0.2, we'll open all code for public, we expect many question and sugestion from klorofil user :D
I know that this comes in contradiction with the work you have done up to this point, but I am not sure about the benefits of using "custom-drawn" controls. I agree that GTK painfully slow, but native Win32 controls aren't. And not using them leads to very serious issues, like the reported (and not reported) quirks, theme unfriendly-ness and a strange overall user experience.
You might ask what benefit could Klorofil bring over WinBinder. It could be the coding style required. I think WinBinder is to "C-ish" for the users that are more experienced in PHP that in writing bare-bones Win32 applications (no MFC, no WTL, no .NET and so on). With an OOP-oriented design, Klorofil could become the first free real RAD solution for Windows (at least); cross-platform too. The other player would be Microsoft's C# Express; but, as many of us know, .NET is pretty sluggish (especially the user interface part, which is of great importance). (In fact, at a Microsoft conference, I brought to attention this particular point: sluggishness of the controls in C#, but without getting a good answer).
To end: you're doing a great job, but you have to take into consideration the points I expressed above.
i know this will always be an issue even from the beginning of this project. Native control will always faster than custom control coz it run on kernel space not in user space. And it a lot easier to code :D !
But we have a lot of consideration before we choose custom draw control. Mainly because we don't want to stuck with just already provided control. We need to create a lot custom control other than default native control. I know we can do that on c (extention) level, but it will make us too dependent to c language, not php. And i see custom draw performance good enough -- although i expect some other bugs :D
Well, denny, first of all the kernel does not "draw" the controls in linux. That's true for windows, but it's the only example I can think off right now. Now, about the custom draw controls: why reinvent the wheel? That doesn't make sense. Sure it may be lureing to make only one set of controls for all the platforms, but think of the draw-backs: _ugly_ bugs, extra work and of course slow code. On the other hand creating bindings fo GDI on windows, thus native controls, will spare you of lots of hard work. For linux/unix you can use the xlib routines you have already implemented.
Now about the C language: the language in which the bindings are implemented is not that important. What matters is that you can code desktop apps in php. The end user doesn't have to know what's "under the hood". All he know is that he can use php to create cross-platform desktop apps.
@GrayShade, yes we can do that, but we choose all control is custom draw because we want one source code for all platform. We choose to localize the different between one platform to other just in drawing layer (xlib/gdi/other). I know the drawback, we have to reimplement something that already done and hard tested. But after all, in linux we have to implement those control from scratch, because already provided solution is not suitable for us.
@blAckEnEd, custom draw does make sense, you could refer to java Swing and eclipse. They do just like use, use lightweight/custom draw control. But if you say those gui framework is slow, you could test our gambArt framework. I think it
I installed it not long ago (REALLY easy installation btw) and ran the samples (also really easy to execute). I must say, it's looking pretty damn good!
Poked around through some of the installation folders and it looks like there's even support for SQLite... which means you can create a desktop app with its own simple database storage... such possibilites... :)
If this thing (Klorofil) gets more and more mature, there could be a big wave of developers utilising its ease of use to create desktop apps.
Ideally it'd be great to be able to build a standalone .exe file that contains your application and the entire Klorofil framework so that distributing your application is a breeze.
Great work Klorofil developers!
Great work Klorofil developers!
Thanks for your support on Klorofil project. :-)
We will do our best to maintain the project.
I installed it not long ago (REALLY easy installation btw) and ran the samples (also really easy to execute). I must say, it's looking pretty damn good!
Easy installation is one of our main goals. We hope developers can install Klorofil Platform easily within minutes.
If this thing (Klorofil) gets more and more mature, there could be a big wave of developers utilising its ease of use to create desktop apps.
Yes, we hope many people will start to use Klorofil Platform to create GUI (desktop) apps using PHP.
Recent comments
6 days 18 hours ago
16 weeks 1 day ago
28 weeks 6 days ago
34 weeks 3 days ago
52 weeks 12 hours ago
1 year 5 weeks ago
1 year 8 weeks ago
1 year 10 weeks ago
1 year 13 weeks ago
1 year 13 weeks ago