And here we go... again!

5 am! Best hour for our intellect to come by and say "Hey"

This might be one of the busiest weeks ever for us, we have been working very hard on the project. We've been working literally around the clock to be able to present our project today, we are actually very excited about this even tho its going to be though.

Now its only matter of time for us to finish we are doing the very last details of it, hopefully every one enjoys it!

Cheers
-Deco

And here we go.

We are a few hours of submitting the project to the jury. Still not completely ready to be evaluated but we are working on the mistakes of last time, always come when you least need them.

On the other hand you are ready our video. I never thought to edit videos so late but here it is. I leave the league so they can see directly into YouTube.

http://www.youtube.com/watch?v=DsfR6WWAN-c

Greetings

Belissa

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

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

Second iteration

Ok and here we're finishing the progress for the second iteration and we had several problems.
For my part I try to implement Subversion with Eclipse and as seen in Googlecode I could not even organize it, this little problem delayed us a bit more.

As for the code we are checking how to make a query, the database classes can help a lot but not find a way to give us a single fact in Django.

As mentioned there were several changes to the project and this occasion our unit tests would not go in this iteration.

We hope soon to give more as we progress with the project.

Belissa

Here... once again

Hello,

I've been wanting to post, but i've been really busy...

First of all, i want to tell you, that we've made some changes... what do i mean with changes? I mean... BIG CHANGES. Not in functionality but in the architecture... Ty client!!

So first of all... the biggest change: We wont have 2 types of users, since the client realized that expositors and organizers should be the same... both should be able to do both things...

This helped... a bit... even though we can't figure out if its a 0 bit or a 1 bit... here, let me explain... Before we had 2 types of users, so we had to model each user, model their permisions and stuff... now... since we only have one user, we can/are use/using python.contrig.auth.user, so its going to be easier to handle users, but we had to change basicly everything.

The other change, is since we deleted those 2 kinds of users, we had to make different applications, the apps schema changed, now we have only 3 types of apps:

-Index.- which will handle login, expo searches, and users profile (this user profile is public)
-Users.- This will handle the registration of the users, non-public profile page, change personal data and user-confirmation emails.
-Expos.- Which will handle everything bout making expos and registering to them. (EVERYTHING ABOUT EXPOS =P)

Oh by the way, Belissa told me to tell you that she's been working in the projects style and well helping me out as well (since she hasn't posted =P )

Ok, so there it is... my weekly-not-so-weekly post

Cheers.
Deco.

1rst Iteration

So here we are, today we've got the first check iteration of the project.

I personally don't think we've come far right now, but we are now finishing up the basics with django. We've been struggling with POST requests and even more while trying to send emails, it's actually getting rough.

Dunno what else to say, because actually the hardest part is yet to come.

Cheers.

Deco.