homecomponents-devel Mailing List for HomeComponents
Status: Inactive
Brought to you by:
schapht
Menu
▾
▴
homecomponents-devel — Developers' list for HomeComponents
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(15) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <ben...@id...> - 2004-05-25 08:29:58
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Mat S. <sc...@ve...> - 2004-05-14 20:00:01
|
YAT! This has been an interesting afternoon. -Mat |
|
From: Mat S. <sc...@ve...> - 2004-05-14 19:10:09
|
having some email trouble. Excuse me. |
|
From: Mathew S. <mt...@dr...> - 2004-05-13 19:11:17
|
Just thought I'd see if there's any activity out there. I've been at work alot lately, so not alot of progress on my end. Mostly just some SQL modifications. I think I'm getting close to a workable Blog though. Anything going on on your end, bryan? -mat |
|
From: Mat S. <sc...@ve...> - 2004-05-06 00:53:38
|
Ok, I just moved my code into the sourceforge CVS server. The "HomeComponents" module is for code, "HomeComponents-design" is for design documents. Once we get to it, user docs and license information will probably go in the HomeComponents module, so that way we can just tar it up for releases. Maybe some sort of release build process is in order though. We'll cross that bridge when we get to it. I'm just about to change the Db class to HC_Db, so make sure to update your code before you start if the class is still "Db". Any design ideas for the Shoutbox so far? Feel free to post even rough design work (Word docs are fine too) to the CVS server. I'd like to see what you're doing, and others might be too (via anonymous CVS). If you need a CVS tool for loose files, try http://www.wincvs.org. I haven't used it myself, but the CVS development team seems to recommend it. I'm just about to try MacCVS. I've been using LinCVS compiled on Mac so far; it's not bad, but leaves something to be desired. -Mat |
|
From: Mat S. <sc...@ve...> - 2004-05-05 19:44:09
|
This page should have everything you'll need: http://smarty.php.net/crashcourse.php Does Dreamweaver have CVS integration? I've been curious to play with it, but I haven't done much aside from poking at it once in awhile. I like Word for short documents, but I've found pagination can get tricky on documents > 30 pages or so. As for diagraming, you should really try Dia. Especially the UML stuff and especially the class diagraming. It's pretty sweet. It's not the prettiest thing in the world though, but it's very development-friendly. Check out the windows version here: http://dia-installer.sourceforge.net/ -Mat On May 5, 2004, at 3:16 PM, b r y a n c h e n wrote: > I do all my work on my Windows XP Professional Edition, using > Microsoft Word > for both documents and diagrams. For PHP coding, I use Macromedia > Dreamweaver MX 2004. > > I'm not very familiar with Smarty, so I'll spend a few days reading > its API. > > > -----Original Message----- > From: hom...@li... > [mailto:hom...@li...] On Behalf Of > Mat > Schaffer > Sent: Thursday, May 06, 2004 3:03 AM > To: hom...@li... > Subject: Re: [Homecomponents-devel] Design Specification > > By all means :) > I'm not familiar with the term exactally. But I'm guessing it would be > something that people could post little notes into but not as formal as > a guestbook. I think this would be a great addition, and it seems like > a good "starter project" so we can get used to working together (with > regards to the HC_Common.php provisions, anyway). > > My recommendations would be: > - use a ShoutBox class to encapsulat the whole thing so a user can just > say: > $shoutbox =& new ShoutBox("box1"); > $shoutbox->getLatest(); > > something like that. getLatest would return the HTML to be printed as > a shoutbox. This HTML should be generated by use of a template (in the > HomeComponents/templates/shoutbox) directory, or something of the sort. > Use getSmarty() to retrieve a Smarty instance. > > the "box1" will specify which shoutbox to retrieve, or create it if > it's not found. > make sure to use HC_PREFIX on any tables you create. > Also, copy down all your SQL stuff into a .sql file. Later, I'd like > to create and installation script that puts the module in place, and > loads the database from provided .sql files. > > There's definitely some other stuff that I need to add to the spec that > I'm noticing. Things like: > - all HTML should be taken from templates, even the simplest pieces. > This will allow the user to make changes to the internal formatting of > the components if they want, without having to modify the code. > - all components should return strings to the user. The use of "echo" > should be only done to print error messages. This will allow the user > to easily place components into their existing page layout. > - make any attempts possible to avoid unnecesary memory usage ($obj =& > new Obj(), instead of $obj = new Obj()). > > I'll poke at in the coming week, and get those in there. > > Tonight, I'll load the current HomeComponents stuff into the > sourceforge CVS tree. So you can grab that and start working on the > Shoutbox as soon as you're ready. Let me know if you have any > questions. > > Good working with you, > Mat > > PS., what OS are you working on? What tools do you use? We might be > able to make recommendations to each other. > I'm on Mac OS X myself, I use Eclipse2 w/ php-eclipse for coding PHP. > Lyx for documentation. Dia for diagraming. > > On May 5, 2004, at 12:17 PM, b r y a n c h e n wrote: > >> I'd really like to work on a Shoutbox/Tagboard-type of module. Any >> suggestions? >> >> >> -----Original Message----- >> From: hom...@li... >> [mailto:hom...@li...] On Behalf Of >> Mathew Schaffer >> Sent: Wednesday, May 05, 2004 10:25 PM >> To: hom...@li... >> Subject: [Homecomponents-devel] Design Specification >> >> Here's the specification for the design so far. Section 1 covers all >> the coding practices I've been doing so far. Section 2 covers what >> the >> main system provides for the modules right now. >> None of this is ever to be set in stone, but as more modules develop, >> changes to the specifications will require more work. So, if you have >> any recommendations, it's better to discus them now. >> >> I've been working on the blog module so far. Is there a particular >> module you'd like to work on? >> >> Oh, there's one thing that's not in this document that just occured to >> me. I'll add it later which is: >> HC_DB_INCLUDE references a class called Db. This is a wrapper class >> for the database, not Pear's Db class. I felt that Pear's Db class was >> too confining, so I built my own simple wrapper. >> One of the next things I want to do is rename my "Db" class to "HC_Db" >> so that it could eventually enclose Pear's Db class if desired. I'll >> update the document and send a notice out once that's done. >> >> Also, I'm storing design docs in the HomeComponents-Design module in >> the CVS tree. I'll send this one via email, but in the future I'll >> probably just send an email out and you can sync your copy. I'd >> encourage you to make changes to these documents as you see fit as >> well. I'm using lyx as a designer. If you're more comfortable with >> another format, we could keep two seperate files, but we'll need to >> make sure we notify each other when we make changes so we can update >> the other file. >> Lyx is available on most popular platforms, and I highly recommend it >> as an alternative to writing documents in straight LaTeX. It can >> export to LaTeX, PDF, or DVI which are all highly portable document >> formats. >> >> Anyway, here's the PDF. >> -Mat >> >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by Sleepycat Software >> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to >> deliver higher performing products faster, at low TCO. >> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 >> _______________________________________________ >> Homecomponents-devel mailing list >> Hom...@li... >> https://lists.sourceforge.net/lists/listinfo/homecomponents-devel >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Homecomponents-devel mailing list > Hom...@li... > https://lists.sourceforge.net/lists/listinfo/homecomponents-devel > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Homecomponents-devel mailing list > Hom...@li... > https://lists.sourceforge.net/lists/listinfo/homecomponents-devel > |
|
From: Mat S. <sc...@ve...> - 2004-05-05 19:37:16
|
How neat would it be to have a Shoutbox::setCensorshipLevel() function that would make the program censor out curse words or something. Just incase someone gets particularly profane, it doesn't have to end up on someone's page. Perhaps it would just replace profanity with [***] when outputting the data. -Mat |
|
From: Mat S. <sc...@ve...> - 2004-05-05 19:36:18
|
I haven't made alot of decisions regarding the CMS portion of the project yet. I was thinking that the master class (Blog, ShoutBox, etc) should have all the necesary functions to make additions/modifications/deletions to the database, then build a page around it. That way if people wanted to make their own forms, or default certain values it wouldn't be too difficult. I was thinking the "HomeComponents/cms" directory would provide a simple authentication system, then link to a set of forms to interact with the module (blog_cms.php, shoutbox_cms.php, etc). What do you think? -Mat |
|
From: b r y a n c h e n <me...@br...> - 2004-05-05 19:17:15
|
I do all my work on my Windows XP Professional Edition, using Microsoft =
Word
for both documents and diagrams. For PHP coding, I use Macromedia
Dreamweaver MX 2004.
I'm not very familiar with Smarty, so I'll spend a few days reading its =
API.
-----Original Message-----
From: hom...@li...
[mailto:hom...@li...] On Behalf Of =
Mat
Schaffer
Sent: Thursday, May 06, 2004 3:03 AM
To: hom...@li...
Subject: Re: [Homecomponents-devel] Design Specification
By all means :)
I'm not familiar with the term exactally. But I'm guessing it would be=20
something that people could post little notes into but not as formal as=20
a guestbook. I think this would be a great addition, and it seems like=20
a good "starter project" so we can get used to working together (with=20
regards to the HC_Common.php provisions, anyway).
My recommendations would be:
- use a ShoutBox class to encapsulat the whole thing so a user can just=20
say:
$shoutbox =3D& new ShoutBox("box1");
$shoutbox->getLatest();
something like that. getLatest would return the HTML to be printed as=20
a shoutbox. This HTML should be generated by use of a template (in the=20
HomeComponents/templates/shoutbox) directory, or something of the sort.=20
Use getSmarty() to retrieve a Smarty instance.
the "box1" will specify which shoutbox to retrieve, or create it if=20
it's not found.
make sure to use HC_PREFIX on any tables you create.
Also, copy down all your SQL stuff into a .sql file. Later, I'd like=20
to create and installation script that puts the module in place, and=20
loads the database from provided .sql files.
There's definitely some other stuff that I need to add to the spec that=20
I'm noticing. Things like:
- all HTML should be taken from templates, even the simplest pieces. =20
This will allow the user to make changes to the internal formatting of=20
the components if they want, without having to modify the code.
- all components should return strings to the user. The use of "echo"=20
should be only done to print error messages. This will allow the user=20
to easily place components into their existing page layout.
- make any attempts possible to avoid unnecesary memory usage ($obj =3D& =
new Obj(), instead of $obj =3D new Obj()).
I'll poke at in the coming week, and get those in there.
Tonight, I'll load the current HomeComponents stuff into the=20
sourceforge CVS tree. So you can grab that and start working on the=20
Shoutbox as soon as you're ready. Let me know if you have any=20
questions.
Good working with you,
Mat
PS., what OS are you working on? What tools do you use? We might be=20
able to make recommendations to each other.
I'm on Mac OS X myself, I use Eclipse2 w/ php-eclipse for coding PHP. =20
Lyx for documentation. Dia for diagraming.
On May 5, 2004, at 12:17 PM, b r y a n c h e n wrote:
> I'd really like to work on a Shoutbox/Tagboard-type of module. Any
> suggestions?
>
>
> -----Original Message-----
> From: hom...@li...
> [mailto:hom...@li...] On Behalf Of
> Mathew Schaffer
> Sent: Wednesday, May 05, 2004 10:25 PM
> To: hom...@li...
> Subject: [Homecomponents-devel] Design Specification
>
> Here's the specification for the design so far. Section 1 covers all
> the coding practices I've been doing so far. Section 2 covers what =
the
> main system provides for the modules right now.
> None of this is ever to be set in stone, but as more modules develop,
> changes to the specifications will require more work. So, if you have
> any recommendations, it's better to discus them now.
>
> I've been working on the blog module so far. Is there a particular
> module you'd like to work on?
>
> Oh, there's one thing that's not in this document that just occured to
> me. I'll add it later which is:
> HC_DB_INCLUDE references a class called Db. This is a wrapper class
> for the database, not Pear's Db class. I felt that Pear's Db class was
> too confining, so I built my own simple wrapper.
> One of the next things I want to do is rename my "Db" class to "HC_Db"
> so that it could eventually enclose Pear's Db class if desired. I'll
> update the document and send a notice out once that's done.
>
> Also, I'm storing design docs in the HomeComponents-Design module in
> the CVS tree. I'll send this one via email, but in the future I'll
> probably just send an email out and you can sync your copy. I'd
> encourage you to make changes to these documents as you see fit as
> well. I'm using lyx as a designer. If you're more comfortable with
> another format, we could keep two seperate files, but we'll need to
> make sure we notify each other when we make changes so we can update
> the other file.
> Lyx is available on most popular platforms, and I highly recommend it
> as an alternative to writing documents in straight LaTeX. It can
> export to LaTeX, PDF, or DVI which are all highly portable document
> formats.
>
> Anyway, here's the PDF.
> -Mat
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
> _______________________________________________
> Homecomponents-devel mailing list
> Hom...@li...
> https://lists.sourceforge.net/lists/listinfo/homecomponents-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to=20
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
_______________________________________________
Homecomponents-devel mailing list
Hom...@li...
https://lists.sourceforge.net/lists/listinfo/homecomponents-devel
|
|
From: Mat S. <sc...@ve...> - 2004-05-05 19:02:52
|
By all means :)
I'm not familiar with the term exactally. But I'm guessing it would be
something that people could post little notes into but not as formal as
a guestbook. I think this would be a great addition, and it seems like
a good "starter project" so we can get used to working together (with
regards to the HC_Common.php provisions, anyway).
My recommendations would be:
- use a ShoutBox class to encapsulat the whole thing so a user can just
say:
$shoutbox =& new ShoutBox("box1");
$shoutbox->getLatest();
something like that. getLatest would return the HTML to be printed as
a shoutbox. This HTML should be generated by use of a template (in the
HomeComponents/templates/shoutbox) directory, or something of the sort.
Use getSmarty() to retrieve a Smarty instance.
the "box1" will specify which shoutbox to retrieve, or create it if
it's not found.
make sure to use HC_PREFIX on any tables you create.
Also, copy down all your SQL stuff into a .sql file. Later, I'd like
to create and installation script that puts the module in place, and
loads the database from provided .sql files.
There's definitely some other stuff that I need to add to the spec that
I'm noticing. Things like:
- all HTML should be taken from templates, even the simplest pieces.
This will allow the user to make changes to the internal formatting of
the components if they want, without having to modify the code.
- all components should return strings to the user. The use of "echo"
should be only done to print error messages. This will allow the user
to easily place components into their existing page layout.
- make any attempts possible to avoid unnecesary memory usage ($obj =&
new Obj(), instead of $obj = new Obj()).
I'll poke at in the coming week, and get those in there.
Tonight, I'll load the current HomeComponents stuff into the
sourceforge CVS tree. So you can grab that and start working on the
Shoutbox as soon as you're ready. Let me know if you have any
questions.
Good working with you,
Mat
PS., what OS are you working on? What tools do you use? We might be
able to make recommendations to each other.
I'm on Mac OS X myself, I use Eclipse2 w/ php-eclipse for coding PHP.
Lyx for documentation. Dia for diagraming.
On May 5, 2004, at 12:17 PM, b r y a n c h e n wrote:
> I'd really like to work on a Shoutbox/Tagboard-type of module. Any
> suggestions?
>
>
> -----Original Message-----
> From: hom...@li...
> [mailto:hom...@li...] On Behalf Of
> Mathew Schaffer
> Sent: Wednesday, May 05, 2004 10:25 PM
> To: hom...@li...
> Subject: [Homecomponents-devel] Design Specification
>
> Here's the specification for the design so far. Section 1 covers all
> the coding practices I've been doing so far. Section 2 covers what the
> main system provides for the modules right now.
> None of this is ever to be set in stone, but as more modules develop,
> changes to the specifications will require more work. So, if you have
> any recommendations, it's better to discus them now.
>
> I've been working on the blog module so far. Is there a particular
> module you'd like to work on?
>
> Oh, there's one thing that's not in this document that just occured to
> me. I'll add it later which is:
> HC_DB_INCLUDE references a class called Db. This is a wrapper class
> for the database, not Pear's Db class. I felt that Pear's Db class was
> too confining, so I built my own simple wrapper.
> One of the next things I want to do is rename my "Db" class to "HC_Db"
> so that it could eventually enclose Pear's Db class if desired. I'll
> update the document and send a notice out once that's done.
>
> Also, I'm storing design docs in the HomeComponents-Design module in
> the CVS tree. I'll send this one via email, but in the future I'll
> probably just send an email out and you can sync your copy. I'd
> encourage you to make changes to these documents as you see fit as
> well. I'm using lyx as a designer. If you're more comfortable with
> another format, we could keep two seperate files, but we'll need to
> make sure we notify each other when we make changes so we can update
> the other file.
> Lyx is available on most popular platforms, and I highly recommend it
> as an alternative to writing documents in straight LaTeX. It can
> export to LaTeX, PDF, or DVI which are all highly portable document
> formats.
>
> Anyway, here's the PDF.
> -Mat
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Homecomponents-devel mailing list
> Hom...@li...
> https://lists.sourceforge.net/lists/listinfo/homecomponents-devel
>
|
|
From: b r y a n c h e n <me...@br...> - 2004-05-05 16:17:29
|
I'd really like to work on a Shoutbox/Tagboard-type of module. Any suggestions? -----Original Message----- From: hom...@li... [mailto:hom...@li...] On Behalf Of Mathew Schaffer Sent: Wednesday, May 05, 2004 10:25 PM To: hom...@li... Subject: [Homecomponents-devel] Design Specification Here's the specification for the design so far. Section 1 covers all the coding practices I've been doing so far. Section 2 covers what the main system provides for the modules right now. None of this is ever to be set in stone, but as more modules develop, changes to the specifications will require more work. So, if you have any recommendations, it's better to discus them now. I've been working on the blog module so far. Is there a particular module you'd like to work on? Oh, there's one thing that's not in this document that just occured to me. I'll add it later which is: HC_DB_INCLUDE references a class called Db. This is a wrapper class for the database, not Pear's Db class. I felt that Pear's Db class was too confining, so I built my own simple wrapper. One of the next things I want to do is rename my "Db" class to "HC_Db" so that it could eventually enclose Pear's Db class if desired. I'll update the document and send a notice out once that's done. Also, I'm storing design docs in the HomeComponents-Design module in the CVS tree. I'll send this one via email, but in the future I'll probably just send an email out and you can sync your copy. I'd encourage you to make changes to these documents as you see fit as well. I'm using lyx as a designer. If you're more comfortable with another format, we could keep two seperate files, but we'll need to make sure we notify each other when we make changes so we can update the other file. Lyx is available on most popular platforms, and I highly recommend it as an alternative to writing documents in straight LaTeX. It can export to LaTeX, PDF, or DVI which are all highly portable document formats. Anyway, here's the PDF. -Mat |
|
From: Mathew S. <mt...@dr...> - 2004-05-05 14:24:52
|
Here's the specification for the design so far. Section 1 covers all the coding practices I've been doing so far. Section 2 covers what the main system provides for the modules right now. None of this is ever to be set in stone, but as more modules develop, changes to the specifications will require more work. So, if you have any recommendations, it's better to discus them now. I've been working on the blog module so far. Is there a particular module you'd like to work on? Oh, there's one thing that's not in this document that just occured to me. I'll add it later which is: HC_DB_INCLUDE references a class called Db. This is a wrapper class for the database, not Pear's Db class. I felt that Pear's Db class was too confining, so I built my own simple wrapper. One of the next things I want to do is rename my "Db" class to "HC_Db" so that it could eventually enclose Pear's Db class if desired. I'll update the document and send a notice out once that's done. Also, I'm storing design docs in the HomeComponents-Design module in the CVS tree. I'll send this one via email, but in the future I'll probably just send an email out and you can sync your copy. I'd encourage you to make changes to these documents as you see fit as well. I'm using lyx as a designer. If you're more comfortable with another format, we could keep two seperate files, but we'll need to make sure we notify each other when we make changes so we can update the other file. Lyx is available on most popular platforms, and I highly recommend it as an alternative to writing documents in straight LaTeX. It can export to LaTeX, PDF, or DVI which are all highly portable document formats. Anyway, here's the PDF. -Mat |
|
From: b r y a n c h e n <me...@br...> - 2004-05-04 02:40:49
|
Got it. -----Original Message----- From: hom...@li... [mailto:hom...@li...] On Behalf Of Mat Schaffer Sent: Tuesday, May 04, 2004 10:36 AM To: hom...@li... Subject: [Homecomponents-devel] test2 let me know if you get this. -Mat ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Homecomponents-devel mailing list Hom...@li... https://lists.sourceforge.net/lists/listinfo/homecomponents-devel |
|
From: Mat S. <sc...@ve...> - 2004-05-04 02:35:41
|
let me know if you get this. -Mat |
|
From: Mat S. <sc...@ve...> - 2004-05-03 15:51:59
|
Is this working for you, Bryan? -Mat |
