Lazarus
Programming => Packages and Libraries => Ported from Delphi/Kylix => Topic started by: ahmetnurideniz on June 18, 2007, 07:58:09 am
-
Hi
I write a ERP program with Delphi .i need Jedi and FIB+ components. Becouse i use them in my program befeore. Anyone thing port this components in 3 years?
I see Fıb+ for Lazarus in sourceforge but i can't see Jedi. Jedi is very important and usefull tool for us. I want to port it but i never port comp. befor.
Thank for all.
-
I guess 3 years is time enough.
-
Jedi are a very useful component packages that it would be really nice if there were available in lazarus
-
I converted TJvXPBar and I'm in the middle of TJvNavigationPane but suddenly I get shot of spare time then the conversion is getting just 4-5 hours a week.
You can get what I did from:
http://
https://lazarus-ccr.svn.sourceforge.net/svnroot/lazarus-ccr/components/jvcllaz
My policy:
1. Convert components which have no substitute.
2. Convert components which I like most.
3. Convert those code as needed.
Regards.
-
Hi
I see Fıb+ for Lazarus in sourceforge but i can't see Jedi. Jedi is very important and usefull tool for us. I want to port it but i never port comp. befor.
The most mature DB access layer in lazarus is Zeoslib and still in (slow) active development.
May be you should change your app from FIB to Zeos.
Regards.
-
is anyone work about this subject.
for Port JCL,JVCL, Jedi Components to Lazarus.
I think now lazarus and free pascal has enough capasity for port this components.
I think when jedi port lazarus, lazarus will be better than Delphi
write that in this page : Jvcl work windows, linux, mac
http://sourceforge.net/projects/jvcl/
is it true ?
-
is anyone work about this subject.
for Port JCL,JVCL, Jedi Components to Lazarus.
I think now lazarus and free pascal has enough capasity for port this components.
I think when jedi port lazarus, lazarus will be better than Delphi
Nobody works on the port and most likely nobody will do it in future either.
The simple reason is that Jedi libraries are put together in a stupid way. There are many useless dependencies and useless glue code. Tons of DEFINEs must be set. Everything depends on Windows even when it makes no sense.
I have extracted and ported 2 components from Jedi libs. See:
http://wiki.lazarus.freepascal.org/bzip2lib
http://wiki.lazarus.freepascal.org/StringHashMap
For example the hash map depended on Windows, and it depended on the rest of JCL! I had to remove all the dependencies and other useless code.
Please look at the JCL and JVCL code yourself, or try to port it yourself and you see what I mean.
The good news is that most Jedi components can be replaced with some other existing Lazarus component.
If there is a useful component which doesn't have a replacement, it can be ported separately, removing the dependencies.
Juha
-
Some JVCL components have been partly ported by CodeTyphoon team:
http://www.pilotlogic.com/sitejoom/index.php/forum/advsearch?q=jvcl&exactname=1&childforums=1
-
Some JVCL components have been partly ported by CodeTyphoon team:
http://www.pilotlogic.com/sitejoom/index.php/forum/advsearch?q=jvcl&exactname=1&childforums=1
That is cool, especially the jvDesignSurface and jvDesignPanel components. I didn't know of them.
I bet they also required lots of code removal and refactoring.
Juha
-
Note that porting will just make them available for win32. Large parts are intrinsically unportable, because they use every trick available.
But it could be useful to check Jedi SVN (or whatever they use) and see if they are cleaning up their large amounts of assembler hacks in the light of XE2 supporting 64-bit.