Page 1 of 1
Open source or build from scratch
Posted: Thu Oct 05, 2006 6:03 pm
by Jastoblasto
Just starting learning PHP (love it) and a friend and I are embarking on a web project incorporating some degree of social networking with photo galleries, and alot of user driven content. Was curious to those who have done alot of work, especially in this area, if I should try and find an open source package aimed at building such a site or build it all from scratch.
Posted: Thu Oct 05, 2006 6:18 pm
by bob_the _builder
Hi,
I would be building it from scratch, that way it will offer the functions you would like.
Use pen on paper and start building a structure to build off.
Have fun
Posted: Thu Oct 05, 2006 6:50 pm
by Ambush Commander
If you're learning PHP, have no qualms on embarking on such a project, but do remember that the end product will probably
not be usable and you'll end up trashing it eventually. Do it for the learning experience.

Posted: Thu Oct 05, 2006 6:52 pm
by Luke
yea.. I'd build from scratch to learn.
Posted: Thu Oct 05, 2006 8:02 pm
by daedalus__
scratch
Posted: Thu Oct 05, 2006 8:07 pm
by s.dot
Definately scratch. Good learning experience. Plus, if you use something some other site has.. (like a downloaded configurable package) some of your users may have think they've "seen it before".
Posted: Thu Oct 05, 2006 9:29 pm
by waradmin
Do it from scratch. I speak from experience as I have built and am building a social networking system.
I first built "MyOpenSpace" which was just a open-source semi-clone of myspace done in php. I got quite a bit done, but the system it was on crashed and I lost it all. (I also lost the blog system I coded, I still have version 1.0 (latest) but lost v.9 to .1

)
Currently with the unknown support of people here I have been getting help building my "Friendbook" Social Networking website, which is going to be an Open-Source Facebook-Style Social networking site. Now, I have quite a bit done on this, but its nowhere near done. Its a fun experience, and time consuming. I have invested over 30 hours into this already.
So is it worth it, yeah. But do it from scratch because then you can call it your own if it turns into anything. However, plan plan plan on paper, or you will be spending tons of extra time deciding what to do next. I didnt plan much of Friendbook and I am building as I go. That leaves me room to add stuff as I please, but takes longer.
If you build on someone else's stuff, you will spend just as much time figuring out their system as you would making your own.
Posted: Thu Oct 05, 2006 9:42 pm
by alex.barylski
My cat's name is scratch...so I second everyone else here, do it for scratch

Re: Open source or build from scratch
Posted: Fri Oct 06, 2006 8:12 am
by waradmin
Jastoblasto wrote:.... a friend and I are embarking on a web project
Also, make sure your friend is dedicated to doing it. I know I have started many projects with my friends but they always get sick of it, or dont have time for it, etc. So chances are this will happen, which is why I try to fly solo on projects.
Posted: Fri Oct 06, 2006 9:07 am
by ryuuka
i would say go from scratch
but keep open source code in handy for refference that's how i learned
most of my php skills (still not much though

) it's good learning to figure out how
other people put out their code.
and another advice: think logical and keep that code nice and tidy
it will be easier to figure out a mistake that way.
good luck on your project.
Posted: Fri Oct 06, 2006 12:01 pm
by waradmin
Also, be sure to program the layout first. Some say thats not the right way to do it (yes, ive been told that) but I find that once I design a layout I can better program the features. For example I designed my layout for the SN I am working on now based off of Facebook, with about a 700px width. That means that images cant be any wider, and subtract the menu bar on the side you got like 500px or so for pictures so knowing that you can figure out thumbnail size, how many per row, etc.
But if you program the core first, you will be stuck trying to make a global interface work for each part of code, vs having a set interface that you know the size of to fit your core to.