> I have defined a new field called "Record Date" to accept the dates from a
> previous logging system. I am not too concerned with the timestamp
> associated with these old imported entries. But for new entries...
> There is no way I am able enter/edit the time into my new field. They all
> show as having a time of 12:00. What am I doing wrong? Here is a portion of
> my config

Date is "date", and not "date-time" unfortunately. There is no way right now to
enter a time. I plan however to add a new format "datetime", which allows that
option. So stay tuned.

- Stefan

> I would like to increase the spacing between 'MOptions' choices. I have
> created a new theme and have been playing with the CSS stylesheet. But can't
> find how to increase this spacing. Having lots of fun otherwise!

Intersting question (meaning: I don't have an answer... (;-) )

The class which applies there is "attribvalue". You can increase the padding for
that class, but that only increases the space between all options and the cell
border, but not between them. I could put each MOption in a separate cell of a
subtable. Then one could increase the padding between them, but the layout would
be fixed, meaning that they are always left-to-right. As you can see in this
forum, the MOptions nicely place below each other if the screen is too narrow.
This functionality would be lost.

Maybe someone else has a clever solution?

I would like to increase the spacing between 'MOptions' choices. I have
created a new theme and have been playing with the CSS stylesheet. But can't
find how to increase this spacing. Having lots of fun otherwise!

Tks,

mark

I have defined a new field called "Record Date" to accept the dates from a
previous logging system. I am not too concerned with the timestamp
associated with these old imported entries. But for new entries...
There is no way I am able enter/edit the time into my new field. They all
show as having a time of 12:00. What am I doing wrong? Here is a portion of
my config

-----------------------------------------------------------

Attributes =   Record Date, Spacecraft, Author, SubSystem, Title

Required Attributes = Record Date, Spacecraft, Author, SubSystem, Title

Type Record Date = date
Time format = %A, %d %B, %Y, %H:%M
Date format = %A, %d %B, %Y, %H:%M

Preset Record date = $date
List Display = Record date, Spacecraft, Author, SubSystem, Title
Start page = ?rsort=Record date

Entries per page = 100
Message Height = 15
Page Title = ELOG - $title
Reverse sort = 1
Quick filter = Date, Spacecraft, SubSystem, Author

message comment = "Please make your log entry in the box BELOW."
Attachment Comment = "Please upload your attachment in the box BELOW."

Menu commands = List, New, Edit, Delete, Reply, Find, Help, Download, Last
Day, Move to, Copy to


Subst Author = $long_name from $remote_host
Subst Email = $user_email

RSS Title = $Title, by $author on $Record Date

Guest menu commands = Find, Last 10, Login, Help
Guest Find Menu commands = Find, Last 10, Login, Help

> I'm looking for an option to attach a user to a log?
> 
> For example:
> 
> Rob is making the log, and whant's to dedicate the log to a stagaire,
> the stagiare recieves an E-mail so that he can do the job?
> 
> Bud we all want recieve the mail bud the stagiare see's that the job is for 
> him.

Maybe use an attribute for that?

Like

Attributes = Author, ..., stagaire
Options stagaire = Jim, Joe, ...

So Rob can select a stagaire from the list, and the email contains this name.

- Stefan

Hello,

I'm looking for an option to attach a user to a log?

For example:

Rob is making the log, and whant's to dedicate the log to a stagaire,
the stagiare recieves an E-mail so that he can do the job?

Bud we all want recieve the mail bud the stagiare see's that the job is for 
him.

Is there a solution for it?

Best regards Rob de Bruin

> > Was just wondering about the status of the multi-line attributes in Elog, are 
> > they implemented in elog yet? If not is that something you are planning to do 
> > in the future?
> 
> In order to have multi-line attributes, the whole format of the logbooks has to be
> changed. I plan to use XML for the logbook format in the future. We would not have
> any more one file per day, but one big file per logbook. I have already some XML
> functionality in elog, but this one requires a major rewrite of the whole code. On
> the other hand, searching etc. will become much faster afterwards. I plan to start
> this development soon, but it might take quite some time, so don't expect it
> before summer or fall.
> 
> Best regards,
> 
>   Stefan

Thanks for your help, thats useful to know.

Paul

> Was just wondering about the status of the multi-line attributes in Elog, are 
> they implemented in elog yet? If not is that something you are planning to do 
> in the future?

In order to have multi-line attributes, the whole format of the logbooks has to be
changed. I plan to use XML for the logbook format in the future. We would not have
any more one file per day, but one big file per logbook. I have already some XML
functionality in elog, but this one requires a major rewrite of the whole code. On
the other hand, searching etc. will become much faster afterwards. I plan to start
this development soon, but it might take quite some time, so don't expect it
before summer or fall.

Best regards,

  Stefan