Tuesday, November 23, 2010
And we continue.
Now we're a bit on the design and view our site. To do this I have helped in a very good tutorial I found online of how we do with CSS. " I leave the league for that visit:
http://www.w3schools.com/css/default.asp
It's hard to tell if it looks good to you and every day I make changes according loq ue me tell people they are shown the site, this in order to have a friendly user interaction.
As for the googlecode I had problems and I can not do updates and commits or not it is due. I tested on Linux and Windows, command line and an Eclipse plugin. If one more try I can not go I'll have to ask for help from my computer to be registered on the website of SeconStrike.
I think this is all for now.
Greetings.
Belissa
Thursday, November 11, 2010
Back-on-track
Ok
So after we did all that stuff about the users, we got to a new dilemma (thank you django!).
How are we going to store the stands in our database?
Our first choice was to create tables "on the fly" which we were going to use as matrix, so every position in our table would be a stand. Yes, that didn't work. So after more than a week investigating how to make that happen, we actually decided not to, its too difficult to implement it that way.
Current solution:
Now we are going to store all the stands in one table (yes, at large scale its going to be huge but we couldn't figure out any better way to do it).
Instead of giving you a big messy explanation I'm just going to paste what would be our design for the expo and the stand models:
=Exposiciones=
nombre -> String
creador -> Usuario
entrada -> norte, sur, este, oeste -> 0,1,2,3
salida -> norte, sur, este, oeste -> 0,1,2,3
columnas -> #
filas -> #
pasillos -> horizontal, vertical -> 0,1
=Stands=
exposicion -> Exposiciones
x -> columnas -> #
y -> filas -> #
usuario -> Usuario
Cheers
-Deco
So after we did all that stuff about the users, we got to a new dilemma (thank you django!).
How are we going to store the stands in our database?
Our first choice was to create tables "on the fly" which we were going to use as matrix, so every position in our table would be a stand. Yes, that didn't work. So after more than a week investigating how to make that happen, we actually decided not to, its too difficult to implement it that way.
Current solution:
Now we are going to store all the stands in one table (yes, at large scale its going to be huge but we couldn't figure out any better way to do it).
Instead of giving you a big messy explanation I'm just going to paste what would be our design for the expo and the stand models:
=Exposiciones=
nombre -> String
creador -> Usuario
entrada -> norte, sur, este, oeste -> 0,1,2,3
salida -> norte, sur, este, oeste -> 0,1,2,3
columnas -> #
filas -> #
pasillos -> horizontal, vertical -> 0,1
=Stands=
exposicion -> Exposiciones
x -> columnas -> #
y -> filas -> #
usuario -> Usuario
Cheers
-Deco
Subscribe to:
Posts (Atom)