theaterlinux-devel Mailing List for Theater
Status: Planning
Brought to you by:
ahlt
Menu
▾
▴
theaterlinux-devel — List for developers, testers and other contributors
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(1) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andrew L. <ly...@ya...> - 2006-02-25 15:45:50
|
Hi TheaterLinux developers, I have been monitoring TheaterLinux for a while and am also working on a similar project called AMICUS. While the two projects have quite different approaches, I have now seen the benefit of making a Linux mini-distribution to support HTPCs due to some of the install problems users have had with AMICUS. I am not proposing to write one from scratch but rather to literally reuse the Debian Netinst Testing with additions for MythTV. So to make AMICUS install better for new users, I am now pursuing making a "base install CD ISO" approach so that the new user can burn the CD from the ISO, boot their blank PC, and quickly install a base system for which the AMICUS script can run in without all the internet downloading. Obviously, my new approach is more similar to the TheaterLinux proposal and since there appears to be a lull in the TheaterLinux development at present I was wondering if any of the TheaterLinux development group would like to join up with AMICUS. Please consider, I certainly could use some help. Maybe this could help generate some more interest in your project as well. http://amicus.sourceforge.net/ Thank you. Andrew Lynch PS, There are two mailing lists to help in the discussion: https://lists.sourceforge.net/mailman/listinfo/amicus-users (For A.M.I.C.U.S. users) https://lists.sourceforge.net/mailman/listinfo/amicus-devel (For A.M.I.C.U.S. developers) |
|
From: Jason P. <pri...@gm...> - 2006-01-26 21:24:28
|
confirm 415624 |
|
From: Are H. <ah...@th...> - 2006-01-05 14:46:55
|
I've now published some screenshots from the configuration wizard. You can view them at TheaterBlog: http://theatermag.org/blog/node/27 Note that these pictures are of a newer version than that one currently located at our CVS server. |
|
From: Are H. <ah...@th...> - 2005-12-05 19:43:25
|
My Python skills improves each day I read about it, and once in a while I find some new functions that I can use with the configuration wizard. Some days ago I read some interesting documentation about boxes. The currently issue about the missing wizard widget can actually easily be solved using normal gtk boxes: For each time the forward button is pressed, hide the current stage box and show the next one. Those boxes are already loaded in the same window, but are automatically hided at the startup.=20 This solution is much more practically than showing each stage in different windows. So I've did a complete rewrite of the wizard, and the new files can again be located at the cvs depot. I hope to upload some screenshots of the application before Christmas Eve. But it's still some time before it will be of any use. It's far from functionally. |
|
From: Are H. <ah...@th...> - 2005-11-21 19:17:27
|
After some search on the web I found some interesting information. It seems to me (if I got it right though) that there is no Gtk widget for h= andling wizards alike applications. There is one called GtkAssistant, but i= t is not stable yet.=20 So what to do now? We could use GnomeDruid, but... nah. Due to this issue there will not be released any build of the wizard yet. W= e gotta think over some other way to create the wizard. Of-course just temp= orarily, while the GtkAssistant widget is being further developed. As for now, I've made it so that each stage as showed within a own window. = And you can also call up a specific stage with the command main.py stage-nu= mber. More on this is described in the README file. The current files of the config-wizard can be located at TheaterLinux's CVS= depot. |
|
From: Are H. <ah...@th...> - 2005-10-31 11:59:14
|
As mention in the "The Default Theater System?" thread on this list, I've been lately playing with the idea of a configuration wizard that helps you chose which front end to use etc.=20 The wizard should be executed after the very first startup on a fresh installed system. I've also mentioned the wizard idea over at htpcnews.com (link1) and the respond has been interesting. So I decided to go on with my idea. And now I want to start to develop this configuration wizard. I will use PyGTK to accomplish that. Personally I do not know Python/PyGTK well, but I hope to learn more with this project. I've also asked for help over at the job section here at sf.net. Hopefully someone more experienced Python developer will join me. When I've managed to made a build of the wizard I will upload it to our CVS. So far I've done nothing regarding this wizard, so please be patient. Link 1: http://htpcnews.com/forums/index.php?showtopic=3D17212 |
|
From: Are H. <ah...@th...> - 2005-10-22 21:11:21
|
After some speculating about this subject I thought perhaps the front end selection could be made after the system installation, instead of during it. With that I mean a configuration wizard that is executed after the very first startup. The configuration wizard could include the opportunity to chose which front end to use and the installation of other optional application. The the Tasksel package could only include the selection of what WM to use. The configuration wizard can easily be developed using PyGTK. So what do you think about that idea? I personally think it would be better to take the front end selection within a nice GTK GUI, instead of within the Tasksel package. |
|
From: Are H. <ah...@th...> - 2005-10-12 11:44:34
|
Simplifying the process: Setting up a HTPC box using Linux is a process that requires more than average skill and time to accomplish. It should be possible to simplifying this process, so regular people should be able to set up an Linux/GNU HTPC box in no time. How to make that happen is not yet clear to me.=20 I also think that it would be great if the control panel for Theater was available as a web interface. Then people would be able to administrate the system from a remote system. What you think? |
|
From: Are H. <ah...@th...> - 2005-10-09 17:12:09
|
The main purpose for this project is to create a Linux/GNU distribution for use with HTPC's. Currently the project do not have any releases yet, this because the projects development status is set to planning. And it is therefor I've posted this thread. I think we all should do some brainstorming here, and share every idea we can come up with related to this project. What can we do and how can it be done? |
|
From: Are H. <ah...@th...> - 2005-10-02 20:08:50
|
Under a Debian installation you got the opportunity to chose between tasks that provides you with different system installations. Example Desktop, Web server, DNS server etc. This is done by using the package Tasksel. Since Theater is based on Debian Sarge I thought maybe Theater also should have that opportunity. But am not sure what tasks that should be available. Perhaps you people have some ideas? But even if the user have some alternatives, there is always a default task. And that lead me to the question: what should the default Theater task include? Personally I thought of Fluxbox as WM. This because of it's speed and flexibility. And maybe MythTV as front end. As of other packages am really not sure. You see I posted this thread so we all could have some brainstorming here... I've currently not tested Freevo, do anyone have some experience to share? --=20 Are Hjelt <ah...@th...> TheaterLinux.org |
1 message has been excluded from this view by a project administrator.
