Thread: [Mysql-cocoa-users] New version out : 3.0.0 (MySQL 4.1 support and more...)
Brought to you by:
sergecohen
|
From: Serge C. <ser...@us...> - 2006-01-31 12:02:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List; It's been more than a year I was writing about it (not frequently thought)... And I finally managed to roll it out yesterday. This is the version 3.0 of the framework. It's been renamed MCPKit and contains a pseudo object/relational layer (which to answer a recent question on the list is able to generate KVC/KVO classes). Most importantly it supports MySQL 4.1 authentication out of the DMG. There is also an application (MCPModeler) to deal with object/rel. models and generate the required class description. At some point I'd like to make it easy to use directly Xcode models for CoreData as a way to describe classes (and indeed that was one thing I was hoping to do before release, but I realised I'd never have time enough...). Documentation and website are lagging behind, again lack of time. If anyone want to provide some help on this front, you're very welcome !!! Nice coding and happy new year (it was about time ;-) Serge. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD31Gg5EPeG5y7WPsRAqRRAJ4nDDBHzqPYAQx4N7ebQgwKuJhqywCg2Q4g bwbTsuSOnUldurOnpL/rs0s= =odkd -----END PGP SIGNATURE----- |
|
From: Aaron J. <aj...@ed...> - 2006-01-31 15:57:12
Attachments:
PGP.sig
|
Serge, This sounds pretty cool, especially the out-of-box support for MySQL 4.1 authentication. I have a question, though, since you say there is little documentation. Is the framework backwards compatible, or is it required that we use the relational layer? Aaron Jacobs On Jan 31, 2006, at 6:01 AM, Serge Cohen wrote: > It's been more than a year I was writing about it (not frequently > thought)... And I finally managed to roll it out yesterday. > This is the version 3.0 of the framework. It's been renamed MCPKit > and contains a pseudo object/relational layer (which to answer a > recent question on the list is able to generate KVC/KVO classes). |
|
From: Serge C. <ser...@us...> - 2006-01-31 16:17:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi; This is absolutely backward compatible, except for the name of the =20 header files and framework. The classes themselves have retained there names, so it should be a =20 very small amount of modification if you were using the previous =20 version. Serge. Le 31 janv. 06 =E0 16:57, Aaron Jacobs a =E9crit : > Serge, > > This sounds pretty cool, especially the out-of-box support for =20 > MySQL 4.1 authentication. I have a question, though, since you say =20= > there is little documentation. Is the framework backwards =20 > compatible, or is it required that we use the relational layer? > > Aaron Jacobs > > > On Jan 31, 2006, at 6:01 AM, Serge Cohen wrote: > >> It's been more than a year I was writing about it (not frequently =20 >> thought)... And I finally managed to roll it out yesterday. >> This is the version 3.0 of the framework. It's been renamed MCPKit =20= >> and contains a pseudo object/relational layer (which to answer a =20 >> recent question on the list is able to generate KVC/KVO classes). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD342X5EPeG5y7WPsRAme0AJ9s5E8B3wBWBN+AU+kaJxcdD779dACfeRQN CgmlR3sBy8Iez4yjeQDeVzw=3D =3DFGaV -----END PGP SIGNATURE----- |
|
From: Camille GOUREAU-S. <ca...@lu...> - 2006-01-31 16:05:21
|
Thanks a lot for the work. Congratulations. |
|
From: Aaron J. <aj...@ed...> - 2006-01-31 16:05:56
Attachments:
PGP.sig
|
Also, both of the source releases (.dmg and .tgz) on SourceForge are missing a ton of files. I need the source release so I can make universal binaries, and so I can comply with the license. :) Aaron |
|
From: Serge C. <ser...@us...> - 2006-01-31 16:18:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Aaron; Have to check that and update them then... Thanks for pointing me to =20 that problem. Unfortunately for the Universal binary, I don't have a intel based =20 Mac, so I've now (fairly) easy way to get the libmysqlclient.a in =20 universal, hence (unless you can make this one yourself), you'll have =20= hard time with this one. Serge. Le 31 janv. 06 =E0 17:05, Aaron Jacobs a =E9crit : > Also, both of the source releases (.dmg and .tgz) on SourceForge =20 > are missing a ton of files. I need the source release so I can =20 > make universal binaries, and so I can comply with the license. :) > > Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD343e5EPeG5y7WPsRAvacAKDwPgBlZjuWZuCWHc7X0D1jdGCcwQCfbAhU I8MkcfgJErY+Wty8OyIVcbo=3D =3DD3Bm -----END PGP SIGNATURE----- |
|
From: Aaron J. <aj...@ed...> - 2006-01-31 16:22:29
Attachments:
PGP.sig
|
I've got a shiny new Intel iMac, so I'm going to give it a shot. If I figure it out, I'll share it with you. Aaron On Jan 31, 2006, at 10:18 AM, Serge Cohen wrote: > Unfortunately for the Universal binary, I don't have a intel based > Mac, so I've now (fairly) easy way to get the libmysqlclient.a in > universal, hence (unless you can make this one yourself), you'll > have hard time with this one. |
|
From: Serge C. <ser...@us...> - 2006-01-31 16:50:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just updated the file packages on sourceforge.... Can you try it know, and tell me if there is still a problem (well, =20 indeed I'd be also interested to hear if there is NO problem ;-). Thanks in advance. Serge. Le 31 janv. 06 =E0 17:22, Aaron Jacobs a =E9crit : > I've got a shiny new Intel iMac, so I'm going to give it a shot. =20 > If I figure it out, I'll share it with you. > > Aaron > > > On Jan 31, 2006, at 10:18 AM, Serge Cohen wrote: > >> Unfortunately for the Universal binary, I don't have a intel based =20= >> Mac, so I've now (fairly) easy way to get the libmysqlclient.a in =20 >> universal, hence (unless you can make this one yourself), you'll =20 >> have hard time with this one. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD35Uv5EPeG5y7WPsRAjSaAKCd8P4D07QXWUzvzO8jbPmy34dQ0ACfYmaI RVFLUHDl/jVhfxp3iXRtMeE=3D =3D0iDg -----END PGP SIGNATURE----- |