Menu
▾
▴
phpsqliteadmin-devel
|
From: Firman W. <fi...@gm...> - 2005-07-06 05:40:47
|
Hi again guys, 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? Also I has designed the good looking project homepage for phpsla. I will commit it later. Comments? Regards, --=20 :: Never Dreamt Before :: http://php.hm/~firman/ firman(@)php.net | firmanw(@)gmail.com |
|
From: Yves G. <yg...@mi...> - 2005-07-06 07:05:49
|
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? :-) > Also I has designed the good looking project homepage for phpsla. I > will commit it later. Any chance we could see it before :-) > Comments? Thanks for your engagement man, Yves > Regards, |
|
From: Firman W. <fi...@gm...> - 2005-07-06 08:25:08
|
On 7/6/05, Yves Glodt <yg...@mi...> wrote: > Firman Wandayandi wrote: > > Hi again guys, >=20 > Hi, >=20 > > 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? >=20 > 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? :-) >=20 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. > > Also I has designed the good looking project homepage for phpsla. I > > will commit it later. >=20 > Any chance we could see it before :-) >=20 I meant commit to this mailing list, if everyone like it, so release it. :-= D > > Comments? >=20 > Thanks for your engagement man, Nope, happy to help. > Yves >=20 > > Regards, >=20 --=20 :: Never Dreamt Before :: http://php.hm/~firman/ firman(@)php.net | firmanw(@)gmail.com |
|
From: Yves G. <yg...@mi...> - 2005-07-06 08:43:34
|
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. 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. >>>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 Ok cool, I'm just waiting for it :-) >>>Comments? >> >>Thanks for your engagement man, > > > Nope, happy to help. > > >>Yves >> >> >>>Regards, >> > |
|
From: Firman W. <fi...@gm...> - 2005-07-06 09:54:56
|
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 |
|
From: Firman W. <fi...@gm...> - 2005-07-07 09:30:36
|
Ah yes, I'm forgot one thing. How if we use Smarty as template engine? So the UI should be change into templating system. On 7/6/05, Firman Wandayandi <fi...@gm...> wrote: > 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 real= ly > > >>>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 proble= m. > > >>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 al= l > > > of codes. > > > > 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. >=20 > > >>>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 > > > > Ok cool, I'm just waiting for it :-) > > > > >>>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 |
|
From: Felipe L. <ff...@gm...> - 2005-07-07 13:26:46
|
Hi there folks! I myself don't like the idea of using Smarty....I just feel it is not necessary... What you guys think? Felipe Lopes On 7/7/05, Firman Wandayandi <fi...@gm...> wrote: > Ah yes, I'm forgot one thing. How if we use Smarty as template engine? > So the UI should be change into templating system. >=20 > On 7/6/05, Firman Wandayandi <fi...@gm...> wrote: > > 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 re= ally > > > >>>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 prob= lem. > > > >>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. > > > > > > 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. > > > > > > > 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 releas= e it. :-D > > > > > > Ok cool, I'm just waiting for it :-) > > > > > > >>>Comments? > > > >> > > > >>Thanks for your engagement man, > > > > > > > > > > > > Nope, happy to help. > > > > > > > > > > > >>Yves > > > >> > > > >> > > > >>>Regards, > > > >> > > > > > > > > > >=20 > -- > :: Never Dreamt Before :: > http://php.hm/~firman/ > firman(@)php.net | firmanw(@)gmail.com >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick > _______________________________________________ > Phpsqliteadmin-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel > |
|
From: Firman W. <fi...@gm...> - 2005-07-08 04:02:41
|
Hi Felipe! On 7/7/05, Felipe Lopes <ff...@gm...> wrote: > Hi there folks! >=20 > I myself don't like the idea of using Smarty....I just feel it is not > necessary... >=20 > What you guys think? >=20 I think we can be more easy to maintaining the UI or design of the interface if we use templating system method. Also switching from one theme to another, other peoples may able to create a theme and submit it to be use widely. > Felipe Lopes >=20 > On 7/7/05, Firman Wandayandi <fi...@gm...> wrote: > > Ah yes, I'm forgot one thing. How if we use Smarty as template engine? > > So the UI should be change into templating system. > > > > On 7/6/05, Firman Wandayandi <fi...@gm...> wrote: > > > 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 cv= s > > > > >>>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 pr= oblem. > > > > >>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 profesion= al > > > > > than before. I think this will be good for the lifecycle in futur= e > > > > > use. > > > > > Yes, maybe re-dev it. The new API has different logic and mechani= sm. I > > > > > think the new API will come with the brand new freshes codes mayb= e all > > > > > of codes. > > > > > > > > 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. > > > > > > > > > > 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 rele= ase it. :-D > > > > > > > > Ok cool, I'm just waiting for it :-) > > > > > > > > >>>Comments? > > > > >> > > > > >>Thanks for your engagement man, > > > > > > > > > > > > > > > Nope, happy to help. > > > > > > > > > > > > > > >>Yves > > > > >> > > > > >> > > > > >>>Regards, > > > > >> > > > > > > > > > > > > > > --=20 :: Never Dreamt Before :: http://php.hm/~firman/ firman(@)php.net | firmanw(@)gmail.com |
|
From: Yves G. <yg...@mi...> - 2005-07-07 17:48:04
|
On Thursday 07 July 2005 11:30, Firman Wandayandi wrote: > Ah yes, I'm forgot one thing. How if we use Smarty as template > engine? So the UI should be change into templating system. I think that (and the planned move to another class) would almost mean a complete rewrite. I have no experience at all with smarty, so I can not comment on it, but I have a question however: Would it help i18n'in phpsla? I would suggest, if you want to do it, that we create a new module in cvs, and leave phpsla as it is now untouched, and start development of phpsla-ng in a new branch. Comments? regards, Yves -- Linux 2.6.12 #1 Sun Jun 26 22:45:52 CEST 2005 i686 19:45:04 up 15 min, 0 users, load average: 1.10, 0.73, 0.45 |
|
From: Firman W. <fi...@gm...> - 2005-07-08 04:43:04
|
On 7/8/05, Yves Glodt <yg...@mi...> wrote: > On Thursday 07 July 2005 11:30, Firman Wandayandi wrote: > > Ah yes, I'm forgot one thing. How if we use Smarty as template > > engine? So the UI should be change into templating system. >=20 > I think that (and the planned move to another class) would almost mean a > complete rewrite. > I have no experience at all with smarty, so I can not comment on it, but > I have a question however: Would it help i18n'in phpsla? >=20 Yes, I has the method to handle it, with it phpsla will be support i18n. Actually I has the pattern of it, which is using Smarty and one plugin I named it "getLang" that provide string language management. getLang use one phpsla core class I named it "phpSLA_Language" , phpSLA_Language is the backend for the language file, so if u choose "en" it's should be english, "id" should be indonesian, "br" should be brazillian portuguese and so on. > I would suggest, if you want to do it, that we create a new module in > cvs, and leave phpsla as it is now untouched, and start development of > phpsla-ng in a new branch. Comments? >=20 I agree for that. But what is "phpsla-ng" exactly meant? > regards, > Yves >=20 --=20 :: Never Dreamt Before :: http://php.hm/~firman/ firman(@)php.net | firmanw(@)gmail.com |
|
From: Yves G. <yg...@mi...> - 2005-07-08 05:45:11
|
On Friday 08 July 2005 06:15, Firman Wandayandi wrote: > On 7/8/05, Yves Glodt <yg...@mi...> wrote: > > On Thursday 07 July 2005 11:30, Firman Wandayandi wrote: > > > Ah yes, I'm forgot one thing. How if we use Smarty as template > > > engine? So the UI should be change into templating system. > > > > I think that (and the planned move to another class) would almost > > mean a complete rewrite. > > I have no experience at all with smarty, so I can not comment on > > it, but I have a question however: Would it help i18n'in phpsla? > > Yes, I has the method to handle it, with it phpsla will be support > i18n. Actually I has the pattern of it, which is using Smarty and one > plugin I named it "getLang" that provide string language management. > getLang use one phpsla core class I named it "phpSLA_Language" , > phpSLA_Language is the backend for the language file, so if u choose > "en" it's should be english, "id" should be indonesian, "br" should > be brazillian portuguese and so on. Ok what I will do then is I will try to create a new branch called phpsqliteadmin-tng (or phpsqliteadmin2) the weekend or later todaty and then you can start playing with that. > > I would suggest, if you want to do it, that we create a new module > > in cvs, and leave phpsla as it is now untouched, and start > > development of phpsla-ng in a new branch. Comments? > > I agree for that. But what is "phpsla-ng" exactly meant? I actually meant to write phpsla-tng which stands for "The next generation" ;-) > > regards, > > Yves -- Linux 2.6.12 #1 Sun Jun 26 22:45:52 CEST 2005 i686 07:42:02 up 12:12, 0 users, load average: 0.28, 0.15, 0.18 |
|
From: Felipe L. <ff...@gm...> - 2005-07-08 06:22:23
|
I agree....Create a new module and lets check how this new generation comes= out! Cheers Felipe Lopes On 7/8/05, Yves Glodt <yg...@mi...> wrote: > On Friday 08 July 2005 06:15, Firman Wandayandi wrote: > > On 7/8/05, Yves Glodt <yg...@mi...> wrote: > > > On Thursday 07 July 2005 11:30, Firman Wandayandi wrote: > > > > Ah yes, I'm forgot one thing. How if we use Smarty as template > > > > engine? So the UI should be change into templating system. > > > > > > I think that (and the planned move to another class) would almost > > > mean a complete rewrite. > > > I have no experience at all with smarty, so I can not comment on > > > it, but I have a question however: Would it help i18n'in phpsla? > > > > Yes, I has the method to handle it, with it phpsla will be support > > i18n. Actually I has the pattern of it, which is using Smarty and one > > plugin I named it "getLang" that provide string language management. > > getLang use one phpsla core class I named it "phpSLA_Language" , > > phpSLA_Language is the backend for the language file, so if u choose > > "en" it's should be english, "id" should be indonesian, "br" should > > be brazillian portuguese and so on. >=20 > Ok what I will do then is I will try to create a new branch called > phpsqliteadmin-tng (or phpsqliteadmin2) the weekend or later todaty and > then you can start playing with that. >=20 > > > I would suggest, if you want to do it, that we create a new module > > > in cvs, and leave phpsla as it is now untouched, and start > > > development of phpsla-ng in a new branch. Comments? > > > > I agree for that. But what is "phpsla-ng" exactly meant? >=20 > I actually meant to write phpsla-tng which stands for "The next > generation" ;-) >=20 > > > regards, > > > Yves >=20 > -- > Linux 2.6.12 #1 Sun Jun 26 22:45:52 CEST 2005 i686 > 07:42:02 up 12:12, 0 users, load average: 0.28, 0.15, 0.18 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happen= ing > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by H= P, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Phpsqliteadmin-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel > |
|
From: Firman W. <fi...@gm...> - 2005-07-08 06:43:49
|
On 7/8/05, Felipe Lopes <ff...@gm...> wrote: > I agree....Create a new module and lets check how this new generation com= es out! >=20 > Cheers >=20 > Felipe Lopes >=20 > On 7/8/05, Yves Glodt <yg...@mi...> wrote: > > On Friday 08 July 2005 06:15, Firman Wandayandi wrote: > > > On 7/8/05, Yves Glodt <yg...@mi...> wrote: > > > > On Thursday 07 July 2005 11:30, Firman Wandayandi wrote: > > > > > Ah yes, I'm forgot one thing. How if we use Smarty as template > > > > > engine? So the UI should be change into templating system. > > > > > > > > I think that (and the planned move to another class) would almost > > > > mean a complete rewrite. > > > > I have no experience at all with smarty, so I can not comment on > > > > it, but I have a question however: Would it help i18n'in phpsla? > > > > > > Yes, I has the method to handle it, with it phpsla will be support > > > i18n. Actually I has the pattern of it, which is using Smarty and one > > > plugin I named it "getLang" that provide string language management. > > > getLang use one phpsla core class I named it "phpSLA_Language" , > > > phpSLA_Language is the backend for the language file, so if u choose > > > "en" it's should be english, "id" should be indonesian, "br" should > > > be brazillian portuguese and so on. > > > > Ok what I will do then is I will try to create a new branch called > > phpsqliteadmin-tng (or phpsqliteadmin2) the weekend or later todaty and > > then you can start playing with that. > > > > > > I would suggest, if you want to do it, that we create a new module > > > > in cvs, and leave phpsla as it is now untouched, and start > > > > development of phpsla-ng in a new branch. Comments? > > > > > > I agree for that. But what is "phpsla-ng" exactly meant? > > > > I actually meant to write phpsla-tng which stands for "The next > > generation" ;-) > > Yeah, let's begin! --=20 :: Never Dreamt Before :: http://php.hm/~firman/ firman(@)php.net | firmanw(@)gmail.com |
|
From: Yves G. <yg...@mi...> - 2005-07-08 11:07:49
|
Firman Wandayandi wrote: >>>Ok what I will do then is I will try to create a new branch called >>>phpsqliteadmin-tng (or phpsqliteadmin2) the weekend or later todaty and >>>then you can start playing with that. >>> >>> >>>>>I would suggest, if you want to do it, that we create a new module >>>>>in cvs, and leave phpsla as it is now untouched, and start >>>>>development of phpsla-ng in a new branch. Comments? >>>> >>>>I agree for that. But what is "phpsla-ng" exactly meant? >>> >>>I actually meant to write phpsla-tng which stands for "The next >>>generation" ;-) >>> > > > Yeah, let's begin! Ok, I will create a new cvs module asap, maybe later 2night or tomorrow. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X