1. Feature requests
- Posted by Tapani Talvitie <tapani.talvitie at gmail.com>
Jan 07, 2007
-
Last edited Jan 08, 2007
Hi!
A lot of fine new features have been suggested and disgusted here lately. I
added few to the Euphoria Sourceforge page. Please add there other ideas too and
comment existing ones!
Feature requests:
http://sourceforge.net/tracker/?func=browse&group_id=182827
Best regards,
--Tapani Talvitie
2. Re: Feature requests
Tapani Talvitie wrote:
>
> Hi!
>
> A lot of fine new features have been suggested and "disgusted" here lately.
> I added few to the Euphoria Sourceforge page. Please add there other ideas too
> and comment existing ones!
>
>
> Best regards,
> --Tapani Talvitie
They weren't that bad, were they?
3. Re: Feature requests
- Posted by Tapani Talvitie <tapani.talvitie at gmail.com>
Jan 08, 2007
-
Last edited Jan 09, 2007
Jeremy Peterson wrote:
>
> Tapani Talvitie wrote:
> >
> > Hi!
> >
> > A lot of fine new features have been suggested and "disgusted" here lately.
> > I added few to the Euphoria Sourceforge page. Please add there other ideas
> > too
> > and comment existing ones!
> >
> >
> > Best regards,
> > --Tapani Talvitie
>
> They weren't that bad, were they?
No they weren’t :D
Best regards,
--Tapani Talvitie
4. Re: Feature requests
Tapani Talvitie wrote:
>
> Feature requests:
> <a
> href="http://sourceforge.net/tracker/?func=browse&group_id=182827">http://sourceforge.net/tracker/?func=browse&group_id=182827</a>
Seems to me we are lacking proper design docs, or as I believe they
are called in unix-land, rfc's. I'd actually be quite happy to host and maintain
some of these on my own site, but obviously they definately would be better
living on sourceforge. Some method of "owning" these requests ought to be
formalised, I think much more importantly for the "design" phase than the actual
implementation.
As a test case, I think I'll pick Matt's 80-column request, if nothing else I
think I have some code to experiment with. But someone needs to allocate it to me
first and Matt has to agree/get me started with his thoughts.
I will still want Matt to do the final implementation, probably.
Regards,
Pete
5. Re: Feature requests
Pete Lomax wrote:
>
> Tapani Talvitie wrote:
> >
> > Feature requests:
> > <a
> > href="http://sourceforge.net/tracker/?func=browse&group_id=182827">http://sourceforge.net/tracker/?func=browse&group_id=182827</a>
>
> Seems to me we are lacking proper design docs, or as I believe they
> are called in unix-land, rfc's. I'd actually be quite happy to host and
> maintain
> some of these on my own site, but obviously they definately would be better
> living on sourceforge. Some method of "owning" these requests ought to be
> formalised,
> I think much more importantly for the "design" phase than the actual
> implementation.
>
> As a test case, I think I'll pick Matt's 80-column request, if nothing else
> I think I have some code to experiment with. But someone needs to allocate it
> to me first and Matt has to agree/get me started with his thoughts.
> I will still want Matt to do the final implementation, probably.
If you'd like to have developer permission,
get a SourceForge id, and I'll add you to the list.
I think you'll then be able to claim
a feature or bug for yourself, or at least add
your design ideas to a feature request or bug report.
Since I have full permissions, and I haven't used
SourceForge before, it's hard for me to know exactly what
other developers can and can't do, or what ordinary
non-developers can or can't do.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
