You can subscribe to this list here.
2003 |
Jan
|
Feb
(193) |
Mar
(55) |
Apr
(32) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Sven W. <sve...@in...> - 2003-02-04 15:02:27
|
Hi @all, now we're all on the list (i put Fabrice their, because he seems to be buzy at the moment). So from now on all discussion on this way :-) gogogo Sven -- Sven Walther, sve...@in... Infopark AG Kitzingstr. 15, D-12277 Berlin, Germany Tel +49 30 747993-0, Fax +49 30 747993-93 http://www.infopark.de/ |
From: Sven W. <sve...@in...> - 2003-02-04 14:39:49
|
> >>I started a new mailing list "phpeselgui-developer" at sourceforge, i >>think this will be the way of such discussions in the future ;-) It's available now: The web page for users of your mailing list is: https://lists.sourceforge.net/lists/listinfo/phpeselgui-developer You can even customize these web pages from the list configuration page. However, you do need to know HTML to be able to do this. There is also an email-based interface for users (not administrators) of your list; you can get info about using it by sending a message with just the word `help' as subject or in the body, to: php...@li... ...i've subscribed already ;-) -- Sven Walther, sve...@in... Infopark AG Kitzingstr. 15, D-12277 Berlin, Germany Tel +49 30 747993-0, Fax +49 30 747993-93 http://www.infopark.de/ |
From: Sven W. <sve...@in...> - 2003-02-04 14:30:16
|
(...) > > First of all, we shouldn't mail to all of us any longer. Could you all please subscribe to the php...@li...-Mailing-List? > I think we should continue this discussion also there and sent a cc of this message to this list the list has been started by me, but sourceforge takes a long time (up to 24 hours) to activate it, have a look at our project page... (...) > >>Something i forgot to mention in the list: >>Any good ideas for a installation-script...? > > Yes: Let's use normal Linux-Packages: rpm, deb, and for those without a popular distribution: .tar.gz OK, but im not realy addicted to them (i always compile the sourcecode myself :), so i'm currently unable to built them. BTW: Which operating systems do we have on our computers? My Webserver is on a SuSE 7.0 (but, as mentioned before, self-compiled with "--prefix=/xxx") And many of the users us the webserver from their hoster and are unable to rpm there... (...) > > A propos config... can't we move it to /etc/phpeselgui? Since it can be viewed with a browser, this is a security-hole, isn't it? This is a security hole, we could built a new folder "config" and store there a very restrictiv .htaccess. /etc/xxx is a problem on the sides being hosted at big providers (you won't have write access at /etc there...) (...) > > The best thing would be docbook-xml. We could convert it in most popular formats (html, xhtml, pdf, ps, txt, etc.), but when i tried to use it yesterday, i run into _BIG_ trouble cause docbook-xml is relatively new and i wasn't able to find good documentation for it. If you can explain us the basics how to use them, why not? (...) >>P.S. Something i forgot to mention: >>we'll need some newer screenshots at phpeselgui.sourceforge.net... > > > Done > > Sven, please have a look at it, if it comforts you, please erase the old-directory (this is where your old screenshots had been) Thanks, looks cool, we'll make it bigger later on (when 0.6 final is out i think). > > > regards > Roman > > -- Sven Walther, sve...@in... Infopark AG Kitzingstr. 15, D-12277 Berlin, Germany Tel +49 30 747993-0, Fax +49 30 747993-93 http://www.infopark.de/ |
From: Roman K. <rom...@ep...> - 2003-02-04 14:05:08
|
> I added both of you to the project just a few seconds ago. For the > starting-point your are all admins, we'll make this a little more > precise later on. Thanks, Sven > Yes, let's use all of the features of sourceforge (i didn't need them as > long as i had my "one-man-show"), as told above: you are now admins, so > go and switch them on (and maybe explain the others, how it works / how > it's configured...) Ok, here we go... First of all, we shouldn't mail to all of us any longer. Could you all please subscribe to the php...@li...-Mailing-List? I think we should continue this discussion also there and sent a cc of this message to this list > I know, frames are always the more easy way, but i'm not a friend of > them (they have so many problems in the day-by-day-use...). I think, we > can work without them by using "templates" in PHP. I also think so > Here i want to ask the others: do you know how to work object > orientated? If so, we'll convert, i personally tried to keep my > sourcecode simple (and functions are for the none technicals much more > easy readable). In theory i know what object orientated programming means. But not practically _yet_. > >>e.g.: If i download "test1-powered-by-eselfilme.de.bin" and > >>"test1-powered-by-eselfilme.de.cue", the .cue-files points to the > >>filename of the .bin-file. So if we rename the .bin the user won't be > >>able to burn this image with cdrdao. (OK, a clever has a look at the > >>.cue and renames the .bin, but some users aren't clever enough) > > you're right, so the default entries should be quite simple (like the > %20 to space and the %7c to |). Some comment lines in front of the > config entry and then the user can start... > > Just an idea: Building a parser for the cues and changing the content at > commit-time...? OK, but i think this is a "minor priority"-task > Something i forgot to mention in the list: > Any good ideas for a installation-script...? Yes: Let's use normal Linux-Packages: rpm, deb, and for those without a popular distribution: .tar.gz > > It would be cool if the gui can rename the file in the detailed file > > view to one of the others in the list or to a name in an input field. > > Yes, but how? This is a feature i would be happy to find in details... I heard rumors, that some functions are not available via the telnet-protocol, but via the GUI-Protocol. Maybe we can use this protocol? It might be faster than telnet. > changing in config sounds better; this means we would have to develop > some things nearly twice (if they changed singificantly) A propos config... can't we move it to /etc/phpeselgui? Since it can be viewed with a browser, this is a security-hole, isn't it? > >>>- a documentation about security (password, SSL, .htaccess) > >>I think i can take this part. > >>I would prefer the documentation in the html-format, so the users can > >>read it in their browser. We could also place a Button in the Gui to > >>access the docu. > >>Of course the Install-documentation should remain as unformatted Text. > hm, maybe all in plain text, but building a php-file, which list them > all and shows them in a themes-design (using fopen)? I'm not a fan of > html doku (i hate starting lynx or so just to have a short look on > something via SSH...) The best thing would be docbook-xml. We could convert it in most popular formats (html, xhtml, pdf, ps, txt, etc.), but when i tried to use it yesterday, i run into _BIG_ trouble cause docbook-xml is relatively new and i wasn't able to find good documentation for it. > I started a new mailing list "phpeselgui-developer" at sourceforge, i > think this will be the way of such discussions in the future ;-) Oh... you already mentioned it... well, this is my last mail which is directly to all of you, my next mails go to this list > P.S. Something i forgot to mention: > we'll need some newer screenshots at phpeselgui.sourceforge.net... Done Sven, please have a look at it, if it comforts you, please erase the old-directory (this is where your old screenshots had been) regards Roman |