Feature requests

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

Stéphane Ducasse
andres

what can I say?
Write PEPs take a couple of them that you think are really important, write them get people involved
and we see in 6 or 12 months from now.
If it succeeds I will be more than happy. Believe me.

> If you had actually considered what has been written in this thread, then you'll realize that throwing a bunch of items in an e-mail has nothing to do with feature requests.

yes this is about building synergy about an idea.
(you see I'm not mean I could have say around an idea that nobody has the financial impact to get real)

> I find quite contradictory that one of your main arguments is about not having enough contributors and yet take that attitude instead of getting something positive out of the initiative.

But I'm positive: I show you all the features we dream about. Take 3 and build a PEP and succeed building them
and we will all be happy.

> But I guess I must be wrong, that surely works, It's just me that doesn't understand how.

>
> Andrés
>
>
> Stéphane Ducasse escribió:
>> so here is my whislist in no order.
>> - multiwindowing system
>> - native mashup of native elements by os for building widgets
>> - new ui framework (with decent coordinate system) a cool sexy widget set (MVP behind).
>> - vm callable as dll - bootstrappable
>> - distributions + build servers + validated packages
>> - better code browsers and tools
>> - pretty print as you type
>> - cairo backend or opensvg like rendering
>> - faster/cleaner monticello
>> - new filesystem
>> - module system
>> - new mop
>> - UIbuilder and interpreter
>> - good RMI - better JIT
>> - cleaner VM code
>> - faster system
>> - good connection with C libraries
>> - clean and extensible event system
>> - remote debugger
>> - better compiler
>> - cross compilation
>> - better documentation with example
>> - 100% test coverage
>> - better library for connection to database
>> https
>> XML handling
>> web services gluing and extracting info
>> https support
>> network
>> - widget for seaside
>> - scaffolding for CRUD in Seaside
>> - persistency solutions
>> - OODMs
>> - ERP in Smalltalk
>> - ...
>> So ok add yours.
>


Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

Geert Claes
Administrator
In reply to this post by James Ashley
James Ashley wrote
...
As a complete smalltalk n00b, I just don't have a dog in this "fight."  Here's the summary of what I've seen in this thread...

Looking in from the outside, I can see that both of you are correct.  This is open source's biggest strength and its greatest weakness.
This is not a fight, it's just a very passionate discussion ... mind you, English is not the first language for a lot people here and even though things may get slightly misconstrued and discussions do sometimes appear to be intense, I bet they'll still gladly have a beer together :)

To summarize:
- The current list of "ideas to implement" lives here: http://code.google.com/p/pharo/wiki/IdeasToImplement
- Does the list of ideas have a voting system?  No.  Why?  There is no way to ensure ideas will be implemented according to the votes.
- How do we know which ideas are popular?  Ideas are discussed on the mailing list.
- Can anyone suggest new ideas?  Abso-freakin-lutely!

So I guess the only thing that may need to be elaborated a bit further is how an idea that has been discussed on the mailing list (e.g. native windows) will make its way to the list of "ideas to implement" and everyone can happily look forward to start the weekend with a beer in hand and smile on their face :)
Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

Marcin Tustin-2
It might be nice to keep track of who says they are interested in having a feature, so whoever wants to take the lead on implementation knows who to ask to pitch in.

On Fri, Dec 10, 2010 at 8:52 AM, Geert Claes <[hidden email]> wrote:


James Ashley wrote:
>
> ...
> As a complete smalltalk n00b, I just don't have a dog in this "fight."
> Here's the summary of what I've seen in this thread...
>
> Looking in from the outside, I can see that both of you are correct.  This
> is open source's biggest strength and its greatest weakness.
>

This is not a fight, it's just a very passionate discussion ... mind you,
English is not the first language for a lot people here and even though
things may get slightly misconstrued and discussions do sometimes appear to
be intense, I bet they'll still gladly have a beer together :)

To summarize:
- The current list of "ideas to implement" lives here:
http://code.google.com/p/pharo/wiki/IdeasToImplement
- Does the list of ideas have a voting system?  No.  Why?  There is no way
to ensure ideas will be implemented according to the votes.
- How do we know which ideas are popular?  Ideas are discussed on the
mailing list.
- Can anyone suggest new ideas?  Abso-freakin-lutely!

So I guess the only thing that may need to be elaborated a bit further is
how an idea that has been discussed on the mailing list (e.g. native
windows) will make its way to the list of "ideas to implement" and everyone
can happily look forward to start the weekend with a beer in hand and smile
on their face :)
--
View this message in context: http://forum.world.st/Feature-requests-tp3077333p3081581.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.




--
Marcin Tustin
Mobile: 07773787105
Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

Alan Rodas
I'm relatively new to Pharo, maybe this has been tried before, but what about a forum where the ideas are published.

Each idea could be a thread in the forum, and the people that would like to contribute may comment there. What it may be interesting is that the whole discussion about an idea could live in the thread, and you can keep track of old discussions and the state of a feature.

If you keep your ideas for yourself, and you cannot implement something by your own, that idea will die there. If you allow people to comment on ideas, maybe two or more people have the same, and they can start working on it together. A forum allows for contacting people, and sharing, and, in that way, maybe the community will grow (Some developers feel they can do something because they don't have the time to do it by their own, or they don't have the skills, but they can help to a dev team that share the same goals.)


Is just a thought.
If you did it before and didn't work, my apologies.


Cheers
--
Alan Rodas Bonjour
Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

solar_sea
There is such a forum and it's mirrored / synced to these mailing
lists. See http://forum.world.st/

Stanislav Paskalev



On Fri, Dec 10, 2010 at 2:06 PM, Alan Rodas <[hidden email]> wrote:

> I'm relatively new to Pharo, maybe this has been tried before, but what
> about a forum where the ideas are published.
> Each idea could be a thread in the forum, and the people that would like to
> contribute may comment there. What it may be interesting is that the whole
> discussion about an idea could live in the thread, and you can keep track of
> old discussions and the state of a feature.
> If you keep your ideas for yourself, and you cannot implement something by
> your own, that idea will die there. If you allow people to comment on ideas,
> maybe two or more people have the same, and they can start working on
> it together. A forum allows for contacting people, and sharing, and, in that
> way, maybe the community will grow (Some developers feel they can do
> something because they don't have the time to do it by their own, or they
> don't have the skills, but they can help to a dev team that share the same
> goals.)
>
>
> Is just a thought.
> If you did it before and didn't work, my apologies.
>
>
> Cheers
> --
> Alan Rodas Bonjour

Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

drush66
In reply to this post by Alan Rodas
On Fri, Dec 10, 2010 at 1:06 PM, Alan Rodas <[hidden email]> wrote:

> I'm relatively new to Pharo, maybe this has been tried before, but what
> about a forum where the ideas are published.
> Each idea could be a thread in the forum, and the people that would like to
> contribute may comment there. What it may be interesting is that the whole
> discussion about an idea could live in the thread, and you can keep track of
> old discussions and the state of a feature.
> If you keep your ideas for yourself, and you cannot implement something by
> your own, that idea will die there. If you allow people to comment on ideas,
> maybe two or more people have the same, and they can start working on
> it together. A forum allows for contacting people, and sharing, and, in that
> way, maybe the community will grow (Some developers feel they can do
> something because they don't have the time to do it by their own, or they
> don't have the skills, but they can help to a dev team that share the same
> goals.)
>
>
> Is just a thought.
> If you did it before and didn't work, my apologies.

Well, those are all nice thoughts. I am also relatively new to Pharo
though, I am with Smalltalk for quite a long time. In my humble
opinion, while both are always nice to have, at this stage Pharo, much
needs more hands willing to do the work, than hands filling the wish
lists and voting about them.

The Pharo team did marvelous job, I assume with a lot of investment of
their personal time and energy. They also did quite good job at
setting their targets since they already managed at transforming huge
but sometimes hectic Squeak core into consistent development product.

The way things currently work nicely reflect this, you can freely
float your ideas on the mailing list, but do not expect that someone
else should do it just because of that. But the better the idea is,
and the larger your contribution to Pharo is, chances of it being
implemented will rise. Otherwise, roll up your sleeves, and do it for
yourself. If that is too complicated, consider doing something else
simpler but usefull.

rush
http://www.cloud208.com/

Reply | Threaded
Open this post in threaded view
|

Re: Feature requests

Igor Stasenko
On 10 December 2010 13:32, Davorin Rusevljan
<[hidden email]> wrote:

> On Fri, Dec 10, 2010 at 1:06 PM, Alan Rodas <[hidden email]> wrote:
>> I'm relatively new to Pharo, maybe this has been tried before, but what
>> about a forum where the ideas are published.
>> Each idea could be a thread in the forum, and the people that would like to
>> contribute may comment there. What it may be interesting is that the whole
>> discussion about an idea could live in the thread, and you can keep track of
>> old discussions and the state of a feature.
>> If you keep your ideas for yourself, and you cannot implement something by
>> your own, that idea will die there. If you allow people to comment on ideas,
>> maybe two or more people have the same, and they can start working on
>> it together. A forum allows for contacting people, and sharing, and, in that
>> way, maybe the community will grow (Some developers feel they can do
>> something because they don't have the time to do it by their own, or they
>> don't have the skills, but they can help to a dev team that share the same
>> goals.)
>>
>>
>> Is just a thought.
>> If you did it before and didn't work, my apologies.
>
> Well, those are all nice thoughts. I am also relatively new to Pharo
> though, I am with Smalltalk for quite a long time. In my humble
> opinion, while both are always nice to have, at this stage Pharo, much
> needs more hands willing to do the work, than hands filling the wish
> lists and voting about them.

Abso-freakin-lutely! :)

>
> The Pharo team did marvelous job, I assume with a lot of investment of
> their personal time and energy. They also did quite good job at
> setting their targets since they already managed at transforming huge
> but sometimes hectic Squeak core into consistent development product.
>
> The way things currently work nicely reflect this, you can freely
> float your ideas on the mailing list, but do not expect that someone
> else should do it just because of that. But the better the idea is,
> and the larger your contribution to Pharo is, chances of it being
> implemented will rise. Otherwise, roll up your sleeves, and do it for
> yourself. If that is too complicated, consider doing something else
> simpler but usefull.
>

I am always discussing ideas before going to implement them.
And for things i do, if i not sure if i doing the best way, or there
are multiple 'nice'
ways to solve the problem, i asking people, what they prefer.
In that way people staying in course of what i do, and sometimes could
give an advice or help by
other means.
But i don't expecting much, because we all busy with own agendas.

> rush
> http://www.cloud208.com/


--
Best regards,
Igor Stasenko AKA sig.

12