coapp-developers team mailing list archive

["Trevor Dennis" <trevor@xxxxxxxxxxxxx>]

That's strange.  It's much easier and quicker to read a person's reply right
at the top of the message instead of scrolling all the way down through the
15 pages of conversation to get the new piece.  Especially when you get on a
mobile phone.  It's only bad when you're new to an old conversation that's
been going on for a while. I'm flexible though.

 

I agree it should be chronological on a forum though.  I see too many web
sites that post comments backwards as newest first so you have to get to the
last page and read backwards. Maybe distribution lists fall into this
category.

 

I think the package-version is just normal because that's what you always
get when you untar the package file.

 

For libraries, should we have a "Program Files\Shared" type of directory?
Similar to the /usr/share on UNIX? Or Libraries?

 

Trev.

 

 

From: coapp-developers-bounces+trevor=dennis-it.com@xxxxxxxxxxxxxxxxxxx
[mailto:coapp-developers-bounces+trevor=dennis-it.com@xxxxxxxxxxxxxxxxxxx]
On Behalf Of Elizabeth M Smith
Sent: Tuesday, April 06, 2010 1:13 PM
To: Garrett Serack
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Another kind of package.

 

On 4/6/2010 2:23 PM, Garrett Serack wrote: 

Bottom Poster!???!! Arg!  I preferred bottom-posting, but in my world, it's
just not done. 

Heh - in the open source world you get your head taken off for it (sigh)



 
>> $base_web_location/<vendor>/<package>/<version>
 
...\applications\<vendor>\<package-version> or ... \applications
\<vendor>\<package>\<version>?
 
Package-version as the dir name is a bit more traditional, I think.


Don't really think it matters - but personally it IS nice to have all your
versions in one directory ;) just a nicer way to look at them in my mind




 
>>  To further complicate things there is the idea of things in the PHP that
script libraries like PEAR and Zend Framework:
 
Ah. Yes.Hmmm.
 
How about ...\libraries\<vendor>\<package-version> for shared 'web
libraries' like PEAR.
This makes the tree (and increases the necessity for \sites , \applications
and \libraries)
 
inetpub 
+---applications
│   +---CoApp
│   │   +---Gallery-2.0.7
│   │   L---phpBB-3.0.2
│   L---WordPress
│       +---WordPress-4.3.6
│       L---WordPress-4.3.7
+---libraries
│   +---Adodb
│   │   L---AdoDB-2.5.6
│   L---Zend
│       L---ZendFrameworks-2.4.1
L---sites
    +---bar.com
    +---baz.org
    L---foo.com
  


Except then you run into things that AREN'T web apps being written in a web
language using a library.
PHP-GTK and PyGTK scripts, pyrus/pear packaging code, phpunit test suites
 - they all want to use libraries that aren't necessarily confined to web
space.

All these dynamic languages make traditional organization pretty hard ;)

Thanks,
Elizabeth M Smith