Page 14 of 27

Posted: Tue Sep 05, 2006 7:02 am
by feyd
Jenk wrote:feyd - everytime I see that dancing bannana I get the peanut butter jellytime track stuck in my head.[/offtopic]
Yeah, innit great? ("Yeah, isn't it great?" for those who don't understand the slang.)

Posted: Tue Sep 05, 2006 7:06 am
by sike
onion2k wrote:
sike wrote:to get things started we should really just start with a bunch of bullet lists where we group requirements (e.g article, cart...). at a later stage we can build some more refined things upon that.

chris
We've got that. The main page of the Wiki is a list of general features, which I'm in the process of linking to seperate pages that give a more detailed list of requirements for the individual items. It's slowly going to build into a complete list of requirements. Unfortunately work is getting in the way of my fun right now. :)
ok, i'll take a deeper look at the wiki and try to clean things up und help u a bit.
onion2k wrote:
sike wrote:what i am trying top say is that we should not think too much about how we write / organize requirements but rather get things rollin'. it will evolve by time (sort of requirements refactoring (; )
I don't really agree. Jumping into the code at this stage, prior to knowing what's really needed, will slow things down and lead to a similar sort of spaghetti mess OSCommerce is in at the moment. That's exactly what this project is trying to avoid. I realise it's not so glamorous and it's a bit boring for people who prefer to be coding than documenting, but experience has taught us that documentation first is very much the right way to go on a large project.
i wasn't talking about coding. i am on your side : we need solid requirements before getting our hands dirty. but the process of writing those requirements will evolve by time (that's why i said we should start with some bullet lists) but i get the feeling we are thinking a lot on how we "write" those requirements rather than just start (:

chris

Posted: Tue Sep 05, 2006 7:22 am
by ok
I think we should design and build something like this: http://zap.co.il/
For example:
http://zap.co.il/c-E-TV lists all TVs and on the top there is nevigation options:
Filter by: manufacturer->Toshiba, LG...
cost price->0-1000$, 1000-2000$...
technology->LCD, DLP...
screen size->34-42inch, 29-32inch...
Order by: popularity, cost price, product rank...

Posted: Tue Sep 05, 2006 8:03 am
by Jenk
Instead of 'borrowing' ideas from other sites, I'd rather we went the full hog and design the whole thing from scratch, almost as if the site was the first of it's kind.

I'll happily swing with what the majority decides, but for me this project is a learning process and thus the primary objective for me is to learn as much as possible about creating an application from the start, whilst the secondary objective is to develop a working e-commerce application.

In summary: No shortcuts please :)

Posted: Tue Sep 05, 2006 8:22 am
by onion2k
ok wrote:I think we should design and build something like this: http://zap.co.il/
For example:
http://zap.co.il/c-E-TV lists all TVs and on the top there is nevigation options:
Filter by: manufacturer->Toshiba, LG...
cost price->0-1000$, 1000-2000$...
technology->LCD, DLP...
screen size->34-42inch, 29-32inch...
Order by: popularity, cost price, product rank...
The store will be able to do all that. If you look at the catalogue page on the Wiki you'll see that I've defined meta data filters, price range filtering and various ordering options as requirements. The point is that we're attempting to develop a store application that will be able to be customised and configured to match any online shop you care to mention.

Whether we should write it to allow Hebrew language display though .. that's a whole new ballgame. It's possible.. but it'd be really, really difficult.

Posted: Tue Sep 05, 2006 8:22 am
by feyd
An integral part of the design process is judging and knowing your peers. It's a component in the "business case" document in your "standard" project management process.

Posted: Tue Sep 05, 2006 8:34 am
by Oren
zap.co.il is not a shopping cart, it's more like http://froogle.google.com

Posted: Tue Sep 05, 2006 10:25 am
by ok
I only think we should add zap's design to our themes list. :D

Posted: Tue Sep 05, 2006 10:26 am
by Luke
Sorry I haven't been around lately... been very busy. I will try and look through everything on the wiki tonight and see what I can do.

Posted: Tue Sep 05, 2006 11:07 am
by Jenk
The Ninja Space Goat wrote:Sorry I haven't been around lately... been very busy. I will try and look through everything on the wiki tonight and see what I can do.
Image

(revenge from labor day thread :P)

Posted: Tue Sep 05, 2006 12:29 pm
by onion2k
ok wrote:I only think we should add zap's design to our themes list. :D
This is the sort of thing that will needed to be decided: how will themes/skins work, and what will be included in a default install. A question for our HTML and CSS team no doubt.

Posted: Wed Sep 06, 2006 1:46 am
by ok
Invision Board templates are working with functions and I think that this method is the best...

Code: Select all

<?
function header($data)
{
 return <<<EOF
<html ...>
<head>
<title>{$data['title']}</title>
....
</head>
EOF;
}
?>
EDIT: If we use this, we won't need to use str_replace, preg_replace etc.

Posted: Wed Sep 06, 2006 3:34 am
by Jenk
Stop stealing ideas from other places!

Posted: Wed Sep 06, 2006 3:41 am
by onion2k
And if you do have an idea, put it on the Wiki. ;)

Posted: Wed Sep 06, 2006 5:13 am
by ok
We have a Project Homepage? a project name? deadlines?