> >> I'd say in this order of importance: > >> - reliable > >> - simple and consistant with what eclipse users are used too: > >> - http://e-p-i-c.sf.net/updates > >> - http://update.phpeclipse.net/update/nightly > >> - http://phpeclipse.sourceforge.net/update/releases > >> - simple URL that can be remembered > > I think the name of the plugin is less important than the functionality it > installs.
True. But that's not a reason for not taking care of the name. If you want the tool to be successful, it should be well identified. It has to have a name. > I think this because once you install it, you'll never refer > to it by that name, but by the fact that you create a pike > project/file or open the Pike perspective. I don't think so. I installed it twice, i made other people install it 3 times. I hope to have it installed even more in the company :) I'd like to work on it, to work with, to make some other people work with it, to make other people update their plugin. I'll have to refer to it, thus to name it. We now have some developpers thousands of kilometer from here. Chances are i'll ask them to handle some Pike code someday. I'll ask them to install the Pike eclipse plugin, say PDT. The problem is that they'll already have a PHP plugin. Guess the name? (Hint: PHP Development Tools). I don't feel the need to fuck up with an eclipse plugin name collision thousands of kilometers away. > > Any news about this? I think it would be nice to have a running update > > site by the conference. > > I can provide dns and possibly a caudium virtual server. The thing I'm a > little hesitant about is being able to share access properly with the > folks necessary. I think you probably already have access, Bertrand, so > that's probably less of an issue. > > perhaps > > http://eclipse.gotpike.org/updates ? -- Bertrand _______________________________________________ pdt-devel mailing list [email protected] http://lists.riverweb.com/mailman/listinfo/pdt-devel
