Menu
▾
▴
freevo-docs — Freevo Documentation Project
This list is closed, nobody may subscribe to it.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dirk M. <dm...@tz...> - 2004-08-09 12:44:00
|
Alexej Fink wrote:
> Hallo!
>
> @ starting freevo I get:
> ---------------------------------------------
> You are using version 5.09, changes since then:
> Version 5.11:
> Add IMAGEVIEWER_OSD to customize the osd and VIDEO_AUTOJOIN to
> auto join
> movies with more than one file
>
> Version 5.12:
> Added TV_RECORD_SERVER_UID to set the uid for the recordserver and
> TV_RECORDFILE_SUFFIX for the suffix. If your TV_RECORDFILE_MASK
> contains
> the suffix, please remove it here
>
> Version 5.13:
> Added TV_RECORD_SERVER_GID to set the gid for the recordserver. If you
> use TV_RECORD_SERVER_UID, the gui _must_ match one of the users gids
> ---------------------------------------------
>
> I grep'ed freevo py sources and freevo doc files for IMAGEVIEWER_OSD,
> but no usable information was found.
> Therefore I can't set these vars to a meaningfull value...
I guess the variable was removed or renamed after 5.11.
> So could U please add some good doc about all user-configurable vars
> and their valid values (better with some examples) ! ? (at least
> include the new one in local_conf.py in usual way)
Our main problem: we need people to write the docs.
> freevo: could not connect to socket
> freevo: Connection refused
> WARNING: Could not initialize PyLirc!
>
> - what's this? - I have lirc installed, but not configured now.
> - is lirc aplugin ?
> - can I disable it (until lirc & 2.6er will work together in debian) ?
You can ignore it or search the freevo_config.py how to disable lirc
support.
Dischi
--
panic ("No CPUs found. System halted.\n");
2.4.3 linux/arch/parisc/kernel/setup.c
|
|
From: Alexej F. <ale...@gm...> - 2004-08-07 08:19:44
|
Hallo!
@ starting freevo I get:
---------------------------------------------
You are using version 5.09, changes since then:
Version 5.11:
Add IMAGEVIEWER_OSD to customize the osd and VIDEO_AUTOJOIN to auto
join
movies with more than one file
Version 5.12:
Added TV_RECORD_SERVER_UID to set the uid for the recordserver and
TV_RECORDFILE_SUFFIX for the suffix. If your TV_RECORDFILE_MASK
contains
the suffix, please remove it here
Version 5.13:
Added TV_RECORD_SERVER_GID to set the gid for the recordserver. If you
use TV_RECORD_SERVER_UID, the gui _must_ match one of the users gids
---------------------------------------------
I grep'ed freevo py sources and freevo doc files for IMAGEVIEWER_OSD,
but no usable information was found.
Therefore I can't set these vars to a meaningfull value...
So could U please add some good doc about all user-configurable vars and
their valid values (better with some examples) ! ? (at least include
the new one in local_conf.py in usual way)
also bacause of lack of var docu I set MPLAYER_VO_DEV=fbdev in my
config, but I don't know is this a valid way...
[because @ display = xv (matrox framebuffer without X) => mplayer
didn't work util set to fbdev ]
====
====
second Q:
freevo: could not connect to socket
freevo: Connection refused
WARNING: Could not initialize PyLirc!
- what's this? - I have lirc installed, but not configured now.
- is lirc aplugin ?
- can I disable it (until lirc & 2.6er will work together in debian) ?
Thx for great work!
Alexej
|
|
From: <ben...@id...> - 2004-05-22 12:30:34
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Dirk M. <dm...@tz...> - 2004-01-07 16:31:14
|
"Kernel Jake" wrote: > Quick question: what program was used to create the freevo_hw.gif > diagram on http://freevo.sourceforge.net/about.html#About ? OpenOffice diagram drawing tool. More information from "Krister Lagerstrom" <kr...@km...> Dischi -- A real friend is a friend with chocolate. |
|
From: Kernel J. <ker...@ho...> - 2004-01-06 02:39:57
|
Quick question: what program was used to create the freevo_hw.gif diagram on http://freevo.sourceforge.net/about.html#About ? _________________________________________________________________ Enjoy a special introductory offer for dial-up Internet access limited time only! http://join.msn.com/?page=dept/dialup |
|
From: Daniel M. <thu...@ya...> - 2003-12-04 07:38:26
|
Sorry to bother you with a doc request but could you update your webpage. Specificaly the "Current status" information. Its dated May 29, 2003 and it has the old information about no dependencies. "Freevo can be installed on any Linux system, there are no dependencies on external libraries or applications if the full binary release is used." Thanks and awesome project. I bet your code is going to be in a lot of different products in a few years. Its been great to see all the features being added and the look being polished over the life of the program. Dan --------------------------------- Do you Yahoo!? Free Pop-Up Blocker - Get it now |
|
From: Dirk M. <dm...@tz...> - 2003-08-20 17:23:08
|
Travis Place wrote:
> Hey guys,
Hi, sorry for the later answer.
> 1) An event to detach the audio (so i can map it to a key on my remote)
Add plugin.activate('audio.detach') and press DISPLAY while playing
audio.
> I was also thinking about a system information plugin, like CPU/RAM usage..
in CVS.
Dischi
--
When all else failed, she tried being reasonable.
-- (Terry Pratchett, Johnny and the Bomb)
|
|
From: Travis P. <wi...@wi...> - 2003-08-05 23:24:51
|
Hey guys, Im a new member to the list, and have really enjoyed setting up and using freevo over the last week or so..I think it is a really great project, keep up the good work! I did have a few requests of things i think might be handy in freevo though.. 1) An event to detach the audio (so i can map it to a key on my remote) 2) An event to shutdown freevo (so i can press the POWER button on my remote to shut down freevo from the main menu) I was also thinking about a system information plugin, like CPU/RAM usage.. Thanks Travis. |
|
From: Eduardo R. <tr...@mu...> - 2003-07-17 22:34:52
|
On Thu, 2003-07-17 at 12:38, Dirk Meyer wrote: > "Tommy Killander" wrote: > > Hi guys, > > Hi from me, too > > > Also I have Zero knowledge in Wiki, DocBook and SGML/XML, so I need to spend > > some time with that before I'm up to speed. Around ten tags is all what you need to make a functional doc. > > I would prefer DocBook. I don't know the DTD, it's very complex. But > we only need a subset of it. Look at the installation howto in the > Freevo Docs dir, it looks very simple. > > > 1. Should we establish DocBook as the preferred standard for the > > documentation that is shipped with Freevo ? > > I vote for yes. Me too. > > 2. Should we maintain the Wiki also ? > > No, the new _real_ documentation should be our only doc. The WiKi may > be a way to submit new docs. What I was thinking is a system like the php or mysql documentation. Sometimes this is called 'annotated documentation'. A simple description is: documentation that at the bottom accepts pieces of text submitted by interested people. I can't find something like this already done and distributed as a package. I imagine that we need something that takes the xml of the docbook document and generates this page+script automatically. After some time elapsed we include the annotations in the real docbook document and regenerates the whole thing. I can't believe that nothing like that exits, can't found it, that is the problem. > > > 4. How do we communicate with the development team about implementation > > questions and upcoming features ? > > You should read the devel list and the developers should sent you a > small description about new features and how to use them. Very important point. > > > 5. How many are on the list right now ? > That's a good question. I count four addresses since my subscription. > > > Please send a small presentation with name and the usual stuff. Also throw > > in a couple lines about your area of knowledge and how you could contribute > > to the documentation effort. > > OK, my name is Dirk Meyer, but I'm called Dischi (don't ask why, long > story with too much Beer). I live in Germany and work at the > University of Bremen. I have a Diplom (similar to a Master) in > Computer Science and I'm working on my Phd right now. And I'm the > current maintainer of Freevo, but I guess you know that. > My turn. My name is Eduardo Roldan. I live in Uruguay and work in a Wireless ISP. I haven't any degrees at all :), but I have four years working in all sort of things around telco/unix. I like freevo and I use it on my house. I want to put a bit of my time making freevo better. Something like 99% of my programming work is done with python. I also do PHP, postgreSQL, MySQL, docbook(little), unix admin, networking. Currently my free time is taken by my baby project quica (sf.net/projects/quica), so I wan't to take an important role in the docs team. Almost forget this, my native tongue is Spanish. Well, nobody want to take the torch. We are screwed as a doc team? |
|
From: Dirk M. <dm...@tz...> - 2003-07-17 15:39:02
|
"Tommy Killander" wrote: > Hi guys, Hi from me, too > Also I have Zero knowledge in Wiki, DocBook and SGML/XML, so I need to spend > some time with that before I'm up to speed. I would prefer DocBook. I don't know the DTD, it's very complex. But we only need a subset of it. Look at the installation howto in the Freevo Docs dir, it looks very simple. > 1. Should we establish DocBook as the preferred standard for the > documentation that is shipped with Freevo ? I vote for yes. > 2. Should we maintain the Wiki also ? No, the new _real_ documentation should be our only doc. The WiKi may be a way to submit new docs. > 3. Should we use the CVS repository to store documentation in progress ? Someone could get CVS access for docs. > 4. How do we communicate with the development team about implementation > questions and upcoming features ? You should read the devel list and the developers should sent you a small description about new features and how to use them. > 5. How many are on the list right now ? That's a good question. > Please send a small presentation with name and the usual stuff. Also throw > in a couple lines about your area of knowledge and how you could contribute > to the documentation effort. OK, my name is Dirk Meyer, but I'm called Dischi (don't ask why, long story with too much Beer). I live in Germany and work at the University of Bremen. I have a Diplom (similar to a Master) in Computer Science and I'm working on my Phd right now. And I'm the current maintainer of Freevo, but I guess you know that. Dischi -- A mathematician is a machine for converting coffee into theorems. |
|
From: Tommy K. <th...@al...> - 2003-07-13 11:28:59
|
Hi guys, Sorry for the late response. I have been busy with getting the 1.3.2 rele= ase to work on my system and buying a house(!), so I hasn't been much time le= ft for thoughts about the documentation effort lately... I don't mind taking on the task to coordinate and finalize the documentation, but there might be other candidates that are better suited for this job - at times I will be "offline" for days/weeks since I will h= ave tons of work to do on the house. It's a wooden house built 1922 that need= s to be totally renovated; The foundation and frame is good but the rest ne= eds some work :-) Also I have Zero knowledge in Wiki, DocBook and SGML/XML, so I need to sp= end some time with that before I'm up to speed. Anyway, I think that it is a good thing to start discussing the outline o= f the documentation, tools and methods to use: 1. Should we establish DocBook as the preferred standard for the documentation that is shipped with Freevo ? 2. Should we maintain the Wiki also ? 3. Should we use the CVS repository to store documentation in progress ? 4. How do we communicate with the development team about implementation questions and upcoming features ? 5. How many are on the list right now ? Please send a small presentation with name and the usual stuff. Also thro= w in a couple lines about your area of knowledge and how you could contribu= te to the documentation effort. I'll start with myself: My name is Tommy Killander and I live in Sweden, with my fianc=E9 Malin a= nd my one year old son Vilhelm. I work at Teleca, a consultant company working with embedded systems design, as a manager for a team of System Architect= s and electronics engineers. I came across Freevo when a friend of mine showed me an Mini-ITX system running Linux. My first thought when I saw that where "Maybe I could buil= d a mediaplayer using that platform ?" and after one week of surfing the web = I found two things a) Freevo where perfectly suited for my application b) i= t was created by an old friend of mine - Krister Lagerstr=F6m. Part from the fact that I'm a little bit short on time to spend in the project I think that I can contribute with knowledge in the Linux platfor= m (PC hardware and the OS) and what good documentation should look like - I have been writing and reviewing that in projects for military, telecom, consumer electronics companies for more than a decade now - working as a project manager or as a design engineer. I'm eager to help but I can't guarantee that I can spend huge amounts of time in the project. But I can altleast contribute by reviewing the documentation and possibly maintain some of the topics too. Regards, Tommy Killander > -----Original Message----- > From: fre...@li... > [mailto:fre...@li...]On Behalf Of Eduardo > Roldan > Sent: den 1 juli 2003 23:45 > To: fre...@li... > Subject: [Freevo-docs] Status > > > I'am subscribed?, low traffic in the list. Somebody can tell me how is > doing the documentation effort? Is Tommy Killander an official doc > mantainer? > Come on guys. Let's talk. > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/0= 1 > _______________________________________________ > Freevo-docs mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freevo-docs > |
|
From: <cor...@in...> - 2003-07-08 22:09:21
|
Hi Guys, It seems as good a place as any to start - and would certainly make life a bit easier for everyone, can we start this project by putting together a complete listing of key / event mappings for the various plugins and main operations? I'm quite happy to collate it if everyone can send in the mappings for their plugins. Sweet, Corin |
|
From: Eduardo R. <tr...@mu...> - 2003-07-01 21:47:07
|
I'am subscribed?, low traffic in the list. Somebody can tell me how is doing the documentation effort? Is Tommy Killander an official doc mantainer? Come on guys. Let's talk. |