Re: [Phpsqliteadmin-devel] The API break

[Firman W. <fi...@gm...>]

On 7/6/05, Yves Glodt <yg...@mi...> wrote:
> Firman Wandayandi wrote:
> > On 7/6/05, Yves Glodt <yg...@mi...> wrote:
> >
> >>Firman Wandayandi wrote:
> >>
> >>>Hi again guys,
> >>
> >>Hi,
> >>
> >>
> >>>I'm currenty now working on phpsla core class, but the latest cvs
> >>>codes seem doesn't meet with the pattern that I'm working on. I really
> >>>really extreme break the API, that's ok for u guys?
> >>
> >>If it's worth it, and if phpsla will benefit from it, I see no problem.
> >>Are you going to fix phpsla to make it use the new api? :-)
> >>
> >
> >
> > The pattern I currently working is OO paradigm, to feet the
> > requirements and useability, I hope is more benefit and profesional
> > than before. I think this will be good for the lifecycle in future
> > use.
> > Yes, maybe re-dev it. The new API has different logic and mechanism. I
> > think the new API will come with the brand new freshes codes maybe all
> > of codes.
>=20
> Ok I see. My only concern is that cvs should stay in a good shape, I
> mean cvs should (apart of a more or less short period of time) stay
> usable. If you need help in particular things, let us know.
>=20

Ah ok, I think I just need write the core classes for replacing the
old class *forgot the name*, and then we can start to work on the
phpsla interface, features and stuffs.

> >>>Also I has designed the good looking project homepage for phpsla. I
> >>>will commit it later.
> >>
> >>Any chance we could see it before :-)
> >>
> >
> >
> > I meant commit to this mailing list, if everyone like it, so release it=
. :-D
>=20
> Ok cool, I'm just waiting for it :-)
>=20
> >>>Comments?
> >>
> >>Thanks for your engagement man,
> >
> >
> > Nope, happy to help.
> >
> >
> >>Yves
> >>
> >>
> >>>Regards,
> >>
> >
>=20

--=20
:: Never Dreamt Before ::
http://php.hm/~firman/
firman(@)php.net | firmanw(@)gmail.com