search

aaltowebapps / zouba

Github repository for the Team 14
3 stars 0 forks source link

set up directory structure in git #8

Closed davidmaxwaterman closed 12 years ago

davidmaxwaterman commented 12 years ago

docs tests html js css images

etc

vilen commented 12 years ago

For example if you init a RoR application then it creates automatically all those directions and test units.

Perhaps I can push an initial RoR application to our git, so everybody can see the structure? For Android app (wrapper for our website) there should be a separate folder, of course.

davidmaxwaterman commented 12 years ago

I think the RoR stuff should be kept separate, perhaps make a dedicated subdirectory for it.

I wonder if we can do something similar for each supported platform too. Personally, I'd like to keep the top level directory as a chrome app, which is pretty simple. Though, I suppose we could also have a subdirectory for chrome. Yeah, I suppose that makes sense.

vilen commented 12 years ago

Well, RoR can be in '/server', but it will also have all the Javascript, CSS and images in '/server/public/(javascripts | images | stylesheets)'. For the android wrapper we can have '/android'. Then the structure would be something like:

/android /iphone /server <- this is where the RoR server-code is /server/public/ <- this is where all the web-app UI stuff goes /server/public/javascripts/ <- JS files /server/public/images/ <- image files /server/public/stylesheets/ <- CSS files

Of course all the UI files (JS, IMG, CSS) can be somewhere else, but they have to be in the '/server' directory, otherwise RoR instance will not see them. If that makes sense, I will upload it right away.

davidmaxwaterman commented 12 years ago

well, the stuff in /server will be completely different to that in the client app, so I suggest something like :

/client /client/js/ /client/css/ /client/images/ /server /server/js/ /server/css/ /server/images/

RoR has nothing to do with HTML5, per se, and only applies to servers that support the actual application; or have I misunderstood something?

vilen commented 12 years ago

Yes, you're right, sorry for the confusion. I forgot that we are making a standalone HTML5 app, not a server with HTML5 frontend. Should we put the Android wrapper in separate folder or under '/client'? Perhaps it is not so important, as long as '/client' is linked when compiling the Android app.

davidmaxwaterman commented 12 years ago

Well, my instinct would be to put the code in target-independent directories, and then make links to them from each target directories. eg

/client/html /client/js /client/css /client/images /client/android/html->../html /client/android/js->../js /client/android/css->../css /client/chrome/html->../html /client/chrome/js->../js /client/chrome/css->../css /client/ios/html->../html /client/ios/js->../js /client/ios/css->../css /client/meego/html->../html /client/meego/js->../js /client/meego/css->../css /server/...as you had

or something like that. I would like to suggest we simply target chrome first, and then add different targets as we find time. I suppose some platforms/sdks/etc might dictate directory structure and we can follow these structures in the appropriate dedicated subdirectory. Anyway, it allows for more flexibility.

I think we should use symbolic links so that there is only a single copy of source files to maintain. Hopefully, if some targets require specific changes, we can split things so that the changes are isolated in the appropriate subdirectory, but still keeping the common code in the /client directory - hrm, perhaps we could have /client/common/{html,js,css,images,audio,etc}.

I only mention multiple platforms because I'm pretty sure we want to each have it run on our own devices. It'd be good to know what we each have. I know we can all put chrome on our desktop/laptops, so that's a good place to start. I have MeeGo, Maemo, S60 3rd, Android 2.1(something), and WP7.5. I guess we can get more WP7.5 phones, but I don't know how well IE on WP7.5 supports the features.

Thoughts?

vilen commented 12 years ago

'client/common' sounds good. Then we can add more platforms later. I have access to Symbian Belle and Android 4.0. Also, we can run iOS stuff in the emulator.

davidmaxwaterman commented 12 years ago

Ok, great. Can you do that? Thanks.

rioev commented 12 years ago

I have access to an iPod touch if we need iOS

davidmaxwaterman commented 12 years ago

lets make a wiki page with our devices - I started one :

https://github.com/aaltowebapps/zouba/wiki/Available-devices

vilen commented 12 years ago

I uploaded the initial folder structure plus initiated RoR app. Can we close this issue?

davidmaxwaterman commented 12 years ago

looks like a good start - closing