MESSAGE
| DATE | 2009-01-30 |
| FROM | Ronny Abraham
|
| SUBJECT | Re: [NYLXS - HANGOUT] NYLXS Projects
|
Ruben, I don't understand why you seem to be taking such an aggressive
tone. My statement was made in a kind manner.
I would have given the specifics, but it seemed arrogant to do so if
there is no interest.
In any case, I am happy to provide some ideas.
1. We can either use QT or GTK.
2(a) . If we use QT, we should probably stick with C++, as this is the
standard language that is used with the toolkit
2(b). If we use GTK, we should similarly use C#
3(a). My gut says it's probably better to go with QT, as that lends
itself more to platform independence. While GTK is also available on
windows and mac, it's a bit more of a hassle to set up.
3(b). Some might question the value of focusing on platform
independence. After all, this is New York LINUX society.
Nevertheless, I believe that this would open up such a project to
developers who are not necessarily linux users. What's more, I am
hoping this will be of greater benefit to more people.
3(c). Furthermore, it's easier to showcase this project off to an
employer or colleague if it can work on anything. Altruism is good,
but I'd like for myself and anyone working on this to also gain
respect from peers for it.
3(d). QT is a valuable commercial skill. Knowing how to use this
library with C++ can give helpful experience. On the other hand,
while I don't know too many people that rely on GTK, I do know PLENTY
of people that use C#. So I can hear the GTK route. It's also
probably easier to maintain for a windows environment. And as I
pointed out above, I think that's important.
4. I suspect this will be a learning experience both for myself and
anyone who works with me on this, as I am familiar with neither QT or
C++, or GTK and C#.
5. Ultimately my goal is to produce something that looks similar to
Omnioutliner. Not at the same level of functionality, but good enough
that it can be worth using for someone who needs a quick and handy
outliner program.
6. I'd expect about 3-4 hours a week of work. Which will have to be
divided up into the following tasks
6a. Developing
6b. Maintaining the code base
6c. Maintaining the docs
6d. Creating and maintaining a site describing the project
6e. Coming up with nifty ideas.
Well, that's all I can come up with as a first step.
Tameek, my email is ronny.coder-at-gmail.com, I'd be more than happy to
continue discussing this with you if you like.
-ron
On Thu, Jan 29, 2009 at 10:48 PM, Ruben Safir wrote:
>
> No the ball is in YOUR court. What specifically would you propose to do and
> who do you want to help you.
>
> Ruben
>
|
|
