And hence presumably boring. In retrospect that has to be a pretty useless journal entry. I'm definitely wishing for hometime too, especially given Caroline is coughing away behind me. Hopefully I won't catch it.
Ah but I'd be intending to install it at home rather than on chiark :-)
I'll wait until it's stopped feeping for preference.
If you can get the input and the graph to be in stone and lbs not kg though I'll be tempted. Turning off the black lines around the right and top edges of the graph would be good too. And can LJ::Simple post to say, the slimmingworld community rather than to my own journal?
I should be able to make the input in stone rather than in kg, although I'd probably have to make the value in the input file just stones, ie 10.5 for 10½ stone. I'm not sure how useful this would be...
<ponder> actually I should be able to support lb and a "st lb" format. It'll just take a little bit of thinking.... :)
I'll look into turning off the black lines on the right and top edges - that is more if gnuplot can do it.
LJ::Simple can indeed post to the slimmingworld community rather than your own journal. I've already coded that bit up :)
See the main LJ::Simple page (http://www.bpfh.net/computing/software/LJ%3a%3aSimple/) and the LJ::Simple manual page (http://www.bpfh.net/computing/software/LJ%3a%3aSimple/Simple.pm.htm) for that LJ::Simple can do.
Is "For preference I will wait until it has stopped feeping" clearer?
All it needs to do is take 3 sets of input rather than two. I've got a staroffice spreadsheet doing similar at home :-)
I don't know why perl modules all see the need to be so OOPy. But I might look at it in more detail if I decide I actually plan to use it. For now I'm happy enough with the web interface really.
I worked out the "feeping" reference about 2 minutes after I posted my comment when my brain woke up :)
I'm guessing that your spreadsheet has three columns for date, stone and lb ?
For day-to-day usage I'll carry on using the web interface. However for automated stuff like the "weekly weigh in" it made sense to automate the LJ posting :)
As for perl modules being OOPy.... it does make some sense as it means that you don't have to type lots of LJ::Simple::NewEntry(\%Event) or you don't have to worry about namespace pollution if you make NewEntry a part of the main namespace of your program.
The OOP system gets around part of this as whilst you have to do things like $lj = new LJ::Simple(...) you only have to refer to LJ::Simple once. After that it is just $lj->method() to call stuff within the object.
If I'm writing modules for inclusion in my own code which will not be used outside of that code I'll normally make them export their namespace so that I can use their functions directly.
However if I'm releasing the module it makes sense to avoid namespace collisions by using OOP stuff. Especially for things like this where you have a login which occurs once and then stuff done to that login value.
I've just been playing with gnuplot and it appears that it will not let you remove just the black lines around the right and top edges of the graph. All of the black lines (except for the tic marks), yes.
*giggle*. Actually I tried to just post a mood on its own, but it complained about missing mandatory items, without of course saying which were mandatory but it seemed a pretty good guess ;-)
You have to have an event in a journal entry... you see the LJ protocol is a little broken around deleting a journal entry. To delete a journal entry you set the event to be an empty string when you use the editevent mode.
Personally I'd say that they were ant footsteps :)
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2002-08-20 07:52 am (UTC)no subject
Date: 2002-08-20 07:59 am (UTC)Although its suffering from a case of feeping creaturism right now as otherwise I'd be going out of my here at work :)
no subject
Date: 2002-08-20 08:21 am (UTC)I'll wait until it's stopped feeping for preference.
If you can get the input and the graph to be in stone and lbs not kg though I'll be tempted. Turning off the black lines around the right and top edges of the graph would be good too. And can LJ::Simple post to say, the slimmingworld community rather than to my own journal?
no subject
Date: 2002-08-20 08:32 am (UTC)I should be able to make the input in stone rather than in kg, although I'd probably have to make the value in the input file just stones, ie 10.5 for 10½ stone. I'm not sure how useful this would be...
<ponder> actually I should be able to support lb and a "st lb" format. It'll just take a little bit of thinking.... :)
I'll look into turning off the black lines on the right and top edges - that is more if gnuplot can do it.
LJ::Simple can indeed post to the slimmingworld community rather than your own journal. I've already coded that bit up :)
See the main LJ::Simple page (http://www.bpfh.net/computing/software/LJ%3a%3aSimple/) and the LJ::Simple manual page (http://www.bpfh.net/computing/software/LJ%3a%3aSimple/Simple.pm.htm) for that LJ::Simple can do.
no subject
Date: 2002-08-20 08:42 am (UTC)All it needs to do is take 3 sets of input rather than two. I've got a staroffice spreadsheet doing similar at home :-)
I don't know why perl modules all see the need to be so OOPy. But I might look at it in more detail if I decide I actually plan to use it. For now I'm happy enough with the web interface really.
no subject
Date: 2002-08-20 08:52 am (UTC)I'm guessing that your spreadsheet has three columns for date, stone and lb ?
For day-to-day usage I'll carry on using the web interface. However for automated stuff like the "weekly weigh in" it made sense to automate the LJ posting :)
As for perl modules being OOPy.... it does make some sense as it means that you don't have to type lots of LJ::Simple::NewEntry(\%Event) or you don't have to worry about namespace pollution if you make NewEntry a part of the main namespace of your program.
The OOP system gets around part of this as whilst you have to do things like $lj = new LJ::Simple(...) you only have to refer to LJ::Simple once. After that it is just $lj->method() to call stuff within the object.
If I'm writing modules for inclusion in my own code which will not be used outside of that code I'll normally make them export their namespace so that I can use their functions directly.
However if I'm releasing the module it makes sense to avoid namespace collisions by using OOP stuff. Especially for things like this where you have a login which occurs once and then stuff done to that login value.
no subject
Date: 2002-08-20 09:19 am (UTC)Not what I'd call very useful *sigh*
no subject
Date: 2002-08-20 08:03 am (UTC)no subject
Date: 2002-08-20 08:23 am (UTC)Anyone else want a go at caption competition?
no subject
Date: 2002-08-20 08:34 am (UTC)You have to have an event in a journal entry... you see the LJ protocol is a little broken around deleting a journal entry. To delete a journal entry you set the event to be an empty string when you use the editevent mode.
Personally I'd say that they were ant footsteps :)