Re: [Groupsuite-list] CVS Import

[TeamHost L. <of...@te...>]

Hello all, Hello Daniel!

I=B4m going to answer your qeustions between the lines.

> But, I still miss a design document (program flow, base
> functionality/library) and a basic framework (API) for the groupsuite
> application.
##
Have not made that yet :-(

I rather have ideas than the programming background.
So I guess it would be best to discuss the program design in the forum or
mail-list...

> And thus many questions arise, here are just a few to show
> some examples:
> How should modules communicate?
##
Basicly each part needs to put some own code to connect with the others.
(That is why i prefered not to make completly loose modules.)
e.g. If you see a list of last documents for a contact in adress book
there must be a code which is only used here...

> E.g. how can the mail client (when it gets written) read entries from
> the address book?
##
Certainly

> How should modules store their data?
##
Database?

I guess that is not quite what you meant...
Could you please tell me what the *real* question ist?

> How/where will modules be called?
##
Contacts (=3DAdress Book)
communication (=3DMail, Forum, Tickets)
calendar
....
settings (=3DAdministration)

short code for each module (navigation, language database and else) are
the first 3 letters

(Although i did not do that in the database for the contacts itself... it
has contacts as a prefix...)

> How will authentication be performed?
##
Directly in the index.php - there is a check with the database.
Information (=3DUsername, language) is then stored in Session.

> E.g. how will the calendar read user info? (e.g. to display a list of
> other users' calendars)
###
You mean the current user?
Just by putting $u_id in the query which is fetched from Session and save=
d
to $u_id in /inc_main/variables.inc


> I feel we can't just start by implementing a module (calendar, for
> example). We need the framework/API. The base on which to build it all.
###
Thats=B4s true.
Some frames are already avaiable...
We need to discuss on them and go ahead then by collecting ideas for
developement (e.g. calendar) and then design a database for this part.
Next step will be the code to be included in:
inc_cal
The programmer of the module is free to name parts of "subnavigation" -
the way to open the content for this part sotred in $_GET['vp'] ->
$view_page
Parts will be selected in inc_main/select.inc

Startpage is inc_cal/index.inc
Everything else is up to the programmer

We then need to have developers talk about implementing further steps to
combine parts:
- what information is needed to fetch information from database / provide
code for that
- which information must be included in $_GET in order to jump directly t=
o
a special content.

> Alex: The email containing the import by Ryan may have been held by the
> mailing list manager. Can you check groupsuite-cvsinfo and see if any
> posts are held for approval?
##
There is no mail yet.
I guess that is because the CVS still isn=B4t updated...

Bye,
Alexander