public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Cliff Free <anaranjado@bellsouth.net>
To: "Derek J. Belrose" <derek@omegabyte.com>
Cc: bdharring@wisc.edu, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GUI installer
Date: 13 Apr 2003 09:55:11 -0400	[thread overview]
Message-ID: <1050242111.23405.14.camel@Jester.poody.net> (raw)
In-Reply-To: <3E99324E.9090001@omegabyte.com>

That sounds good to me.  I'm no P.M. either, but I'd be willing to help
with some grunt-work.(this is becoming an itch I want to scratch. :-D )

On Sun, 2003-04-13 at 05:47, Derek J. Belrose wrote:
> I'm all for doing it this way if everyone agrees.  I think it would be a 
> decent start, definitely. 
> 
> I'm gonna head to sleep...it's almost 6am here.  But, I want to carry on 
> a discussion with you about the cli portage viewer/manager.  I have been 
> thinking about this one a lot, and want to hear other people's ideas on 
> it. 
> 
> I'm wondering if this will increase the threads on gentoo-dev enough to 
> warrant something like an IRC channel to do more of a realtime chat thing.
> 
> I'm pretty easy right now as i'm unemployed :)  If anyone wants to offer 
> suggestions on how to take this step by step, it would be pretty cool.  
> Project management isn't my forte. 
> 
> I like python...so I, myself would suggest a decent python/ncurses 
> layout for the cli viewer/manager.  I'll start documenting my thoughts 
> on this when the sun rises :) 
> 
> Alright,
> nite...
> 
> Brian Harring wrote:
> 
> >While I think an X based installer would be nice, I think we might benefit 
> >from first doing up a cli based installer first... at the very least, we 
> >would need a cli portage viewer/manager, which would be a nice package on 
> >it's own...
> >
> >Something also I thought about (and have been playing with), is having 
> >essentially a two stage process for the installer- basically everything prior 
> >to the chroot, and then everything after.  Why?  Well, it would be nice to 
> >have the first half of the installer handle all the fdisking, untarring, etc.  
> >From there, it chroots, emerge syncs and emerge portages, then pulls down the 
> >newest version of itself, and runs that.
> >
> >From there, if we wanted we could probably setup some simple equivalent of a 
> >quicky binary x server/svgalib for a x based installer.  Meanwhile, if we 
> >have at least a basic cli installer setup, that would be immediately useful 
> >for the cd's, and w/ an update capability, we could push a graphical 
> >installer down to the user once we have it ready...
> >Thoughts?
> >~harring
> >bdharring@wisc.edu
> >
> >On Sunday 13 April 2003 04:30 am, Derek J. Belrose wrote:
> >  
> >
> >>The only real way I can think of is to do some checks on if X is
> >>running, and if it is, use a graphical toolkit for X...if not, use a
> >>terminal based kit like ncurses.
> >>
> >>I like this idea.  I should download a liveCD to throw some code on and
> >>do tests.
> >>
> >>Is anyone against pyGTK or something like it?  pyQT?  wxPython?
> >>
> >>Is anyone against python? :)
> >>
> >>Cedric Veilleux wrote:
> >>    
> >>
> >>>Why not simply use gentoo's livecd?
> >>>
> >>>The livecd can boot the user into a fully loaded console or X workstation,
> >>>with all the tools needed.
> >>>
> >>>The installer could be an additional tool on the liveCD system.. Anybody
> >>>knows a GUI abstration toolkit that can generate either terminal based or
> >>>X based interface, depending on what's available at runtime?
> >>>
> >>>This way the same installer could be used if X is not working or can't be
> >>>used.
> >>>
> >>>In both environment (terminal / X), multitasking would be possible so
> >>>experienced users could perform manual tasks while the installer is
> >>>waiting for input..
> >>>
> >>>
> >>>Just my 2 cents,
> >>>
> >>>Cedric
> >>>      
> >>>
> >>--
> >>gentoo-dev@gentoo.org mailing list
> >>    
> >>
> >
> >
> >--
> >gentoo-dev@gentoo.org mailing list
> >
> >  
> >
> 
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
-- 
Cliff Free <anaranjado@bellsouth.net>


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-13 13:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 23:04 [gentoo-dev] GUI installer Jeff Rose
2003-04-11 23:25 ` Riyad Kalla
2003-04-12  0:05   ` Alec Berryman
2003-04-12  2:19 ` Brian Harring
2003-04-12  3:52 ` George Shapovalov
2003-04-13  5:05 ` Justin Whitney
2003-04-13  5:38   ` Derek J. Belrose
2003-04-13  6:50     ` Cliff Free
2003-04-13  7:08       ` Derek J. Belrose
2003-04-13  8:49         ` Jeff Rose
2003-04-13  9:14           ` Derek J. Belrose
2003-04-13  9:23           ` Cedric Veilleux
2003-04-13  9:30             ` Derek J. Belrose
2003-04-13  9:34               ` Brian Harring
2003-04-13  9:47                 ` Derek J. Belrose
2003-04-13 13:55                   ` Cliff Free [this message]
2003-04-18  9:35           ` Mark Bainter
2003-04-18 14:54             ` Jeff Rose
2003-04-19  3:45             ` Abhishek Amit
2003-04-20  2:50             ` Evan Powers
2003-04-20  3:05               ` C. Brewer
2003-04-13 16:33 ` Alain Penders
2003-04-13 20:04   ` Jeff Rose
2003-04-13 20:09     ` Graham Forest
2003-04-13 20:36     ` Derek J. Belrose
2003-04-13 22:26       ` Cliff Free
2003-04-13 22:33         ` Derek J. Belrose
2003-04-13 23:13           ` Alec Berryman
2003-04-15 14:26             ` DJ Cozatt
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 10:18 Stroller
2003-04-14 13:17 ` William Hubbs
2003-04-15  4:06   ` John Nilsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1050242111.23405.14.camel@Jester.poody.net \
    --to=anaranjado@bellsouth.net \
    --cc=bdharring@wisc.edu \
    --cc=brd@alumni.clemson.edu \
    --cc=derek@omegabyte.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox