OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Main Development Beginning, Stage 1 Information
dz
post Sep 22 2004, 11:32 PM
Post #1


~


Group: Admin
Posts: 596
Joined: 2-February 04
From: Cape Canaveral, FL
Member No.: 1,667



Ok, so I thought I'd keep you guys informed of the progress. I've begun the main bulk of the site. What's done so far is a preliminary layout and the login/registration system. I've decided to keep the accounts db different than that of the one we use here at the ZUG. What I did though is add a field in the 'options' page for the accounts where you can enter your ZUG username. What I plan to do with that is if someone wants to message you from there, they can enter a message and you have the option of it being automatically inserted here in the ZUG messageboard messages or having it be emailed to you. As well, for the project subscriptions, if there's an update, it can do the same.

I'm going to start production on the main core of the ZSI2 now, which is the actual projects themselves. I'll explain the database structure and the features so if any of you can think of anything else, those will be added.

A project has the following fields: id, name, unixname, screenshot, currentVersion, resolution, rom, model, processor, description, dateAdded, views, license, homepage, owner, and updated.

name: Name of the project.
unixname: Name of the projects filename. This will have no spaces, commas, ~'s; things like that.
currentVersion: I plan to have the ability to put multiple versions on the site and to have multiple branches. Those of you familiar with Sourceforge understand how this works. You can have a development branch and a stable branch, and have multiple versions of the program in there. The currentVersion field is set to whatever you consider the latest version to be.
Resolution: Admin will be able to add/edit/remove different resolutions. If Sharp decides to make another Zaurus and it has a resolution of 800x600 or something, we'll be able to add it easily.
Rom,Processor,License: Same as resolution where admin has complete control.
Model: I put this in so that if we do decide to take this to more than just the Zaurus, we can simply add the other models using the Admin page. Initially though, this will be something like Zaurus c860, Zaurus 5500, et al.
owner: This will be linked to your account.
updated: The last time the project has been updated.

If this sounds at all complicated, give me a few days and you'll see how simple it really is. Some of the stuff can be dropdown boxes (For example licenses), and some can be checkboxes (Resolution for projects that can function on multiple resolutions for example).

That is what is going to be programmed next. After that, the main chunk of the programming is done and I can add the 'features'.

Ok well, time to go to work. Let me know if anyone thinks of any new ideas smile.gif

Roy
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
lardman
post Sep 30 2004, 09:23 AM
Post #2





Group: Members
Posts: 4,515
Joined: 25-October 03
From: Bath, UK
Member No.: 464



QUOTE
Well what will happen is we will need to talk to the people who release Cacko and ask them for the list of libraries in this rom and then simply enter it.


Yep, when a ROM is released get the authors to state their version of GCC and libc (which are the two main ROM dependant things I think).

QUOTE
lm: So what you are proposing, is when someone goes to download a project, they are first promped to enter what type of Rom they are using. Once they enter that, the site itself cross-references what libs that specific Rom is using and what libs the program uses, and then says whether or not they'd need to download additional libraries?


I wasn't thinking of cross-referencing all the libs (like the output from ldd), just the specific dependencies which are listed in the control file (though if you could implement it using the output from ldd would be pretty cool :-))

QUOTE
Hmm.. sounds very interesting. Indeed it would be much more work. By doing that, we now require the programmers to enter almost every lib their program uses. I'd imagine though if you are making a program, you know exactly what it's using.


See above, either the control file or ldd are quick and easy, not much for the programmer to do (other than state their version of libc - if you decide on the control file method - and their version of GCC).

QUOTE
As well, we need to get information on any available rom we choose to support. We need to figure out what lib they come with, and what version that lib is.


Again, it depends how far you want to go with it: One option is to just list the libc version (and possibly other must-haves such as libncurses); the other, is of course, to go the whole hog and have a db containing a list of every standard lib in the image and their versions (not sure how much work this would be, but probably not insurmountable, assuming new ROMs aren't released daily ;-)).

QUOTE
One question I have though is would we need the user to also enter their Zaurus model then? Things like screen-size, memory, and processor do make a difference I'd assume.


Yes. The ROM defines some of the constraints, but the model defines the others (instruction set and screen size), so both would be needed (and people would know both too).


Si

P.S. Perhaps I'm going too far here? I'm quite happy to read a list of the ROMs which people have tried, and to make my own mind up, but for those with less experience I think this system would be hassle-free (though possibly not for the maintainers). Feel free to shoot me down on any of this (especially if you think I'm going to far - I am a bit of a perfectionist)
Go to the top of the page
 
+Quote Post

Posts in this topic
dz   Main Development Beginning   Sep 22 2004, 11:32 PM
dz   Eee, almost forgot the categories field. That one...   Sep 22 2004, 11:34 PM
lardman   Will you have multiple categories, like killefiz d...   Sep 23 2004, 02:27 AM
dz   QUOTEWill you have multiple categories, like kille...   Sep 23 2004, 05:24 AM
offroadgeek   QUOTE(lardman @ Sep 23 2004, 03:27 AM)P.S. Wh...   Sep 23 2004, 08:38 AM
lardman   QUOTEactually, I think it was decided that we woul...   Sep 23 2004, 02:35 PM
r0bin   I think this would be a good idea: Dynamic feeds, ...   Sep 26 2004, 05:51 PM
dz   Question: When a user enters a project, should th...   Sep 29 2004, 04:10 AM
dhns   QUOTE(dz @ Sep 29 2004, 01:10 PM)Question: W...   Sep 29 2004, 04:29 AM
Hrw   Remember about paging - ZSI doesn't have it so...   Sep 29 2004, 04:56 AM
lardman   It would be nice to have the dependencies listed (...   Sep 29 2004, 05:01 AM
tumnus   QUOTE(Hrw @ Sep 29 2004, 12:56 PM)Field which...   Sep 29 2004, 06:42 AM
dz   QUOTE(tumnus @ Sep 29 2004, 09:42 AM)What mig...   Sep 29 2004, 07:05 AM
dhns   QUOTE(dz @ Sep 29 2004, 04:05 PM)Most of the ...   Sep 29 2004, 07:31 AM
lardman   I'd be tempted to get rid of the model name an...   Sep 29 2004, 07:46 AM
dhns   QUOTE(lardman @ Sep 29 2004, 04:46 PM)However...   Sep 29 2004, 08:12 AM
dz   QUOTE(lardman @ Sep 29 2004, 10:46 AM)I'd...   Sep 29 2004, 08:32 AM
dz   QUOTE(dhns @ Sep 29 2004, 11:12 AM)QUOTE(lard...   Sep 29 2004, 08:33 AM
dz   For the rom and processor choices, should they be ...   Sep 29 2004, 09:33 AM
bluedevils   I've seen instances where something does not w...   Sep 29 2004, 09:53 AM
dz   Before I go on, I'd like to see if we could co...   Sep 29 2004, 10:18 AM
swing   QUOTE(dz @ Sep 29 2004, 06:18 PM)Before I go ...   Sep 29 2004, 10:23 AM
_Psycho   QUOTE(bluedevils @ Sep 29 2004, 12:53 PM)I...   Sep 29 2004, 11:06 AM
lardman   That's going to get even more confusing I reck...   Sep 30 2004, 01:06 AM
dhns   I think we have two groups with different aspects ...   Sep 30 2004, 06:56 AM
lardman   Okay, I'll admit defeat ;-) Will the ROM list...   Sep 30 2004, 07:20 AM
dz   QUOTE(lardman @ Sep 30 2004, 10:20 AM)Will th...   Sep 30 2004, 07:49 AM
swing   QUOTE(dz @ Sep 30 2004, 03:49 PM)One question...   Sep 30 2004, 07:59 AM
dz   QUOTE(swing @ Sep 30 2004, 10:59 AM)Only conc...   Sep 30 2004, 08:10 AM
lardman   QUOTEWell what will happen is we will need to talk...   Sep 30 2004, 09:23 AM
_Psycho   It would not be possible to do a script that read ...   Sep 30 2004, 10:26 AM
lardman   ...and I'm sure someone who's better at sh...   Sep 30 2004, 10:41 AM
dz   Heh, no i don't regret it. This is a fun proj...   Sep 30 2004, 10:46 AM
lardman   QUOTEI'm not exactly positive of the structure...   Sep 30 2004, 01:04 PM
lardman   Addendum: libc etc. are of the format lib*-?.?.?....   Oct 1 2004, 01:15 AM
dhns   QUOTE(lardman @ Sep 30 2004, 06:23 PM)QUOTEYe...   Oct 1 2004, 02:00 AM
_Psycho   QUOTE(dz @ Sep 30 2004, 01:46 PM)As far as ma...   Oct 1 2004, 05:35 AM
dz   Ok, how about this. How about we formulate a list...   Oct 1 2004, 07:21 AM
_Psycho   Yes, thats actually sound a good way to do it Ma...   Oct 1 2004, 07:56 AM
lardman   I accept that you don't want the extra work, b...   Oct 1 2004, 08:02 AM
lardman   QUOTEThe project include the following libraries: ...   Oct 1 2004, 08:08 AM
dz   It's not really a matter of extra work, but mo...   Oct 1 2004, 08:20 AM
dz   Just wanted to let you all know that I haven't...   Oct 5 2004, 10:37 AM
lardman   Cool, keep up the good work. Si   Oct 5 2004, 01:28 PM
jamesm   Well done dz, I'm looking forward to seeing th...   Oct 6 2004, 01:53 AM


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 19th December 2014 - 02:49 AM