PHP Developer's Kit
This is a discussion on PHP Developer's Kit within the alt.comp.lang.php forums, part of the PHP Programming Forums category; I hope you do not consider this spam, considering it is entirely specific to this subject-matter and does not ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
12-30-2006
|
|||
|
|||
PHP Developer's Kit
I hope you do not consider this spam, considering it is entirely
specific to this subject-matter and does not qualify as evil, fire-hosing spam. Thanks! The PHP Developer's Kit is available to web-site developers. It greatly streamlines and speeds development by taking care of all the mundane details while you focus on the design. For instance, here is all that is needed to create an entire, working web page that supports asynchronous construction, compression, extensibility, CSS and a wealth of other time-saving features... // create a page object and open $page = new page( "Title Here" ) ; $page->open() ; // create one of the dozens of css objects, like this // predefined one for links that uses hover, etc, and // output it into the page's <style> area... $css = new css_link( $page , OUTPUT_NOW ) ; // create one of the dozen HTML objects derived from // class_attributes, like this link class $kitlink = new link( "View Kit Demo" , "http://www.fotocar.com.mx/kit" ) ; // link it to the css object above and output $kitlink->link2css( $css ) ; $kitlink->output() ; // collect all the pieces, compress and send to the browser $page->close() ; Please visit the demo at http://www.fotocar.com.mx/kit. Meanwhile, here are some of the features. I guarantee you will find the kit helpful and a very real time-saver. Object Oriented -- The PHP Developer's Kit is entirely object oriented (OO) using over 100 classes and not quite 1,000 methods. The Kit is programmer-oriented in that all the tedious programming has been implemented inside the classes. The programmer has only to decide what to do and then create the objects to do most of the work. Rapid Protyping -- The Kit uses extensive defaults and constants to define standard, simple-to-use default behaviors and color schemes. This simplifies and speeds prototyping. It is a simple matter to change the colors and behavior with a few additional method calls. Extensible -- Object Oriented programming languages, like PHP, were designed to make them fundamentally extensible. The Kit is extensible not only to the developer but within itself, using extensibility to build increasingly concrete, derived functionality on top of abstract parent classes. You may extend the Kit as your specific development requirements are defined and as the W3 adds new definitions. Asynchronous construction -- The entire page may be built entirely asynchronously. You may add Javascripts, Cascading Style Sheets, <head> and <body> material at any time prior to sending the finished page with a simple call to close(). This is particulary useful when a page is being built in real-time from data in a database. Cascading Style Sheets -- The Kit supports CSS Levels 1 and 2 and generates clean, formatted styles directly into the web page. Both external and internal style sheets and inline styles are supported. Using CSS has never been easier with 39 CSS-related classes doing most of the work for you. Compression -- The page object queries the user's web browser and, if supported, compresses the entire page before sending it. Typical ratios range from 20:1 to 30:1, dramatically improving perceived bandwidth, especially with larger pages. Error Logging and Notification -- The page object will log errors and even email you if problems arise. Source Code Included -- The Kit includes over 14,000 lines of tested, stable and extensible code. Keyword support -- Search websites, like Google and Yahoo, regularly send search bots out to look for keywords embedded inside pages. The PHP Kit page class provides a keywords() method so you may add your own search words. MySQL -- Interface with MySQL databases and tables with lots of predefined methods taking care of the details. Sample Project -- The Kit includes an entire sample project with its own development menu. The project demonstrates all of the major pieces of the Kit including database maintenance using add, modify and delete, email, displaying the contents of a database using a table and Cascading Style Sheets and lots of examples to kick-start your own project. Please email me if you have any questions. Thanks! 
|
|
12-30-2006
|
|||
|
|||
|
Re: PHP Developer's Kit
phpdevkit schrieb:
> I hope you do not consider this spam, considering it is entirely > specific to this subject-matter and does not qualify as evil, > fire-hosing spam. Thanks! > > The PHP Developer's Kit is available to web-site developers. It > greatly streamlines and speeds development by taking care of all the > mundane details while you focus on the design. For instance, here is > all that is needed to create an entire, working web page that supports > asynchronous construction, compression, extensibility, CSS and a wealth > of other time-saving features... > > // create a page object and open > $page = new page( "Title Here" ) ; > $page->open() ; > > // create one of the dozens of css objects, like this > // predefined one for links that uses hover, etc, and > // output it into the page's <style> area... > $css = new css_link( $page , OUTPUT_NOW ) ; > > // create one of the dozen HTML objects derived from > // class_attributes, like this link class > $kitlink = new link( "View Kit Demo" , "http://www.fotocar.com.mx/kit" > ) ; > > // link it to the css object above and output > $kitlink->link2css( $css ) ; If I'd use a kit like this one, I would prefer an overloaded function for link(), that accepts $css as parameter, if given it sets the class="" if not don't set it > $kitlink->output() ; why an extra output for a simple element, I would understand it, for tables where you add rows like: $kittable->header(); $kittable->addrow(); $kittable->addrow(); $kittable->output(); > > // collect all the pieces, compress and send to the browser > $page->close() ; > > Please visit the demo at http://www.fotocar.com.mx/kit. Meanwhile, > here are some of the features. I guarantee you will find the kit > helpful and a very real time-saver. > This may be true for simple sites, but may work against you in case of complex sites with a complex design, an html template system is usually better for that. > Object Oriented -- The PHP Developer's Kit is entirely object oriented > (OO) using over 100 classes and not quite 1,000 methods. The Kit is > programmer-oriented in that all the tedious programming has been > implemented inside the classes. The programmer has only to decide what > to do and then create the objects to do most of the work. > > Rapid Protyping -- The Kit uses extensive defaults and constants to > define standard, simple-to-use default behaviors and color schemes. > This simplifies and speeds prototyping. It is a simple matter to > change the colors and behavior with a few additional method calls. > > Extensible -- Object Oriented programming languages, like PHP, were > designed to make them fundamentally extensible. The Kit is extensible > not only to the developer but within itself, using extensibility to > build increasingly concrete, derived functionality on top of abstract > parent classes. You may extend the Kit as your specific development > requirements are defined and as the W3 adds new definitions. > > Asynchronous construction -- The entire page may be built entirely > asynchronously. You may add Javascripts, Cascading Style Sheets, > <head> and <body> material at any time prior to sending the finished > page with a simple call to close(). This is particulary useful when a > page is being built in real-time from data in a database. Asynchronous construction I don't think the word asynchronous is suitable in this context > > Cascading Style Sheets -- The Kit supports CSS Levels 1 and 2 and > generates clean, formatted styles directly into the web page. Both That is a performance problem, if you use a specific file for css or js the browser will be able to cache it and load it only once. If you put the css code inside the page, the browser has to load it everytime. > external and internal style sheets and inline styles are supported. > Using CSS has never been easier with 39 CSS-related classes doing most > of the work for you. > > Compression -- The page object queries the user's web browser and, if > supported, compresses the entire page before sending it. Typical > ratios range from 20:1 to 30:1, dramatically improving perceived > bandwidth, especially with larger pages. Usually this is automatically done by the webserver, if properly configured:-) > > Error Logging and Notification -- The page object will log errors and > even email you if problems arise. > > Source Code Included -- The Kit includes over 14,000 lines of tested, > stable and extensible code. That has to be proven > Keyword support -- Search websites, like Google and Yahoo, regularly > send search bots out to look for keywords embedded inside pages. The > PHP Kit page class provides a keywords() method so you may add your own > search words. > > MySQL -- Interface with MySQL databases and tables with lots of > predefined methods taking care of the details. > > Sample Project -- The Kit includes an entire sample project with its > own development menu. The project demonstrates all of the major pieces > of the Kit including database maintenance using add, modify and delete, > email, displaying the contents of a database using a table and > Cascading Style Sheets and lots of examples to kick-start your own > project. > > Please email me if you have any questions. Thanks! >
|
|
12-31-2006
|
|||
|
|||
|
Re: PHP Developer's Kit
Hi Ric, thanks for the excellent comments, see below...
Ric wrote: > If I'd use a kit like this one, I would prefer an overloaded function for link(), that accepts $css as parameter, if given it sets the class="" if not don't set it Good idea, and certainly doable. I wanted to keep the HTML objects (the content) separate from the presentation and also standardize the way all content is linked to $css objects via the link2css() method. (If you know how to do it with one HTML object you know how to do it for all of them.) The link object is, first of all, a link. It's presentation can be optionally altered by linking it to a $css object. Also, I could not figure out how to standardize constructor signatures since all the HTML objects require different initial values depending on their purpose. The link, for example, can optionally take a label and an href, a button a label, a. I also wanted to minimized the number of parameters. The list_definition class can take an optional 1 or 2 css objects, each one controlling a different aspect (i.e., one for the term, another for the description). // create one of the dozen HTML objects derived from // class_attributes, like this link class $kitlink = new link( "View Kit Demo" , "http://www.fotocar.com.mx/kit" ) ; // link it to the css object above and output $kitlink->link2css( $css ) ; $kitlink->output() ; >> why an extra output for a simple element, I would understand it, for >> tables where you add rows like: It has an OUTPUT_NOW optional parameter for the constructor and as long as you have given it the minimum information needed to actually be a link (the label and href) then you may create a link with one statement. But, just in case you need to set additional parameters like the target or name or id before outputing, you would wait and use the output() method when ready. The Kit's link object can take about 30 different attributes. I didn't want the constructor to look like this... new link( $name , $id, $label , $href, $target, $onblur, $onfocus, $class, $outputnow=false ......) > Asynchronous construction > > I don't think the word asynchronous is suitable in this context It solved one of my personal nuisances when building a page by letting me output tweaked/customized CSS settings only when the page was ready and by collecting all the pieces (html, title, script, style, head, body) in the right order. > Please visit the demo at http://www.fotocar.com.mx/kit. Meanwhile, > here are some of the features. I guarantee you will find the kit > helpful and a very real time-saver. >> This may be true for simple sites, but may work against you in case of >> complex sites with a complex design, an html template system is usually >> better for that. It is, of course, a personal preference. I find the very advantages OO was designed to provide (code re-use/sharing, reduced complexity, extensibility, overriding, additional/modified behavior) my preference. > > > > > Cascading Style Sheets -- The Kit supports CSS Levels 1 and 2 and > > generates clean, formatted styles directly into the web page. Both > > That is a performance problem, if you use a specific file for css or js > the browser will be able to cache it and load it only once. If you put > the css code inside the page, the browser has to load it everytime. I worried about that too but 1) I found no problems with performance, in fact, I have been surprised at how transparent it all seems. Maybe I am running on a super fast Apache server but some informal testing showed the kit pages loading no slower than a equally sized html page already built (and I am often on a less-than-speedy connection and computer). 2) If anything, you can tweak a css object then save it into a permanent external css page and reference it using the page object's setcssfilename() method. > > external and internal style sheets and inline styles are supported. > > Using CSS has never been easier with 39 CSS-related classes doing most > > of the work for you. > > > > Compression -- The page object queries the user's web browser and, if > > supported, compresses the entire page before sending it. Typical > > ratios range from 20:1 to 30:1, dramatically improving perceived > > bandwidth, especially with larger pages. > > Usually this is automatically done by the webserver, if properly > configured:-) > > > > > > > Source Code Included -- The Kit includes over 14,000 lines of tested, > > stable and extensible code. > > That has to be proven Absolutely true for any software. I had two peers contribute and test things. I fixed any problems they found. I am happy to make my kit available for review to a couple more volunteers. Ric, thanks for the remarks. I enjoy the academic exercise. I know there are always better ways of doing things. Thanks.
|
|
12-31-2006
|
|||
|
|||
|
Re: PHP Developer's Kit
My apologies. The PHP group seemed like a good place to make people
aware of a PHP-related tool. Michael Vilain wrote: > In article <457be$45972894$8259c69c$24000@news2.tudelft.nl> , > "Rik" <luiheidsgoeroe@hotmail.com> wrote: > > > phpdevkit wrote: > > > I hope you do not consider this spam, > > > > I do. Now what? > > You report them to their ISP and the domain registrar of any URLs they > use in their posts. I do this regularly--it's called a LART (luser > attitude readjustment tool). > > Some ISPs will actually close accounts based on complaints. > > -- > DeeDee, don't press that button! DeeDee! NO! Dee...
|
|
12-31-2006
|
|||
|
|||
|
Re: PHP Developer's Kit
phpdevkit schrieb:
> Hi Ric, thanks for the excellent comments, see below... > > Ric wrote: >> If I'd use a kit like this one, I would prefer an overloaded function > for link(), that accepts $css as parameter, if given it sets the > class="" if not don't set it > > Good idea, and certainly doable. I wanted to keep the HTML objects > (the content) separate from the presentation and also standardize the > way all content is linked to $css objects via the link2css() method. > (If you know how to do it with one HTML object you know how to do it > for all of them.) > > The link object is, first of all, a link. It's presentation can be > optionally altered by linking it to a $css object. Also, I could not > figure out how to standardize constructor signatures since all the HTML > objects require different initial values depending on their purpose. > The link, for example, can optionally take a label and an href, a > button a label, a. I also wanted to minimized the number of > parameters. The list_definition class can take an optional 1 or 2 css > objects, each one controlling a different aspect (i.e., one for the > term, another for the description). > > // create one of the dozen HTML objects derived from > // class_attributes, like this link class > $kitlink = new link( "View Kit Demo" , "http://www.fotocar.com.mx/kit" > ) ; > // link it to the css object above and output > $kitlink->link2css( $css ) ; > $kitlink->output() ; > >>> why an extra output for a simple element, I would understand it, for >>> tables where you add rows like: > > It has an OUTPUT_NOW optional parameter for the constructor and as long > as you have given it the minimum information needed to actually be a > link (the label and href) then you may create a link with one > statement. But, just in case you need to set additional parameters > like the target or name or id before outputing, you would wait and use > the output() method when ready. Still doesn't make sense to me, you only output to the browser as soon as your page is completely comprised, what you do internally doesn't matter. > > The Kit's link object can take about 30 different attributes. I didn't > want the constructor to look like this... new link( $name , $id, > $label , $href, $target, $onblur, $onfocus, $class, $outputnow=false > .....) > >> Asynchronous construction >> >> I don't think the word asynchronous is suitable in this context > > It solved one of my personal nuisances when building a page by letting > me output tweaked/customized CSS settings only when the page was ready > and by collecting all the pieces (html, title, script, style, head, > body) in the right order. > Asynchronus is describing a way of communication. It would mean your kit communicates with someone in an asynchronous way and that is not the case. What you mean is rather parallel vs serial, serial would mean you set each tag from the top. Anyway any object oriented design allows that means, you can always change an objects state at any time. >> Please visit the demo at http://www.fotocar.com.mx/kit. Meanwhile, >> here are some of the features. I guarantee you will find the kit >> helpful and a very real time-saver. > >>> This may be true for simple sites, but may work against you in case of >>> complex sites with a complex design, an html template system is usually >>> better for that. > > It is, of course, a personal preference. I find the very advantages OO > was designed to provide (code re-use/sharing, reduced complexity, > extensibility, overriding, additional/modified behavior) my preference. > >>> Cascading Style Sheets -- The Kit supports CSS Levels 1 and 2 and >>> generates clean, formatted styles directly into the web page. Both >> That is a performance problem, if you use a specific file for css or js >> the browser will be able to cache it and load it only once. If you put >> the css code inside the page, the browser has to load it everytime. > > I worried about that too but 1) I found no problems with performance, > in fact, I have been surprised at how transparent it all seems. Maybe > I am running on a super fast Apache server but some informal testing > showed the kit pages loading no slower than a equally sized html page No it is because you never ran into high loads:-) I have worked on pages that served 200M pages a day and depending on the size of your css definitions that approach can save you a couple of servers. One of my owns site has a 30KB css file, if I would put those definitions inside each page the performance impact would be huge. > already built (and I am often on a less-than-speedy connection and > computer). 2) If anything, you can tweak a css object then save it > into a permanent external css page and reference it using the page > object's setcssfilename() method. > >>> external and internal style sheets and inline styles are supported. >>> Using CSS has never been easier with 39 CSS-related classes doing most >>> of the work for you. >>> >>> Compression -- The page object queries the user's web browser and, if >>> supported, compresses the entire page before sending it. Typical >>> ratios range from 20:1 to 30:1, dramatically improving perceived >>> bandwidth, especially with larger pages. >> Usually this is automatically done by the webserver, if properly >> configured:-) >> >>> >>> Source Code Included -- The Kit includes over 14,000 lines of tested, >>> stable and extensible code. >> That has to be proven > > Absolutely true for any software. I had two peers contribute and test > things. I fixed any problems they found. I am happy to make my kit > available for review to a couple more volunteers. > > Ric, thanks for the remarks. I enjoy the academic exercise. I know > there are always better ways of doing things. Thanks. Sure no problem, it is definitely a good exercise.
|
Linear Mode
