Some ideas on Planning
Rodrigo Magalhães dos Santos
Thank you for the invitation. I transcribe here the message i've
posted on github issues page:
---------------------
As we have talked some days ago, I would like to give some suggestions
in order to define one or more "filosofical" paths for the project and
to organize the efforts of the whole team around one or more common
objectives.
My proposals are conceptually simple and I would like to know what you
think about them:
1. Define one or more paths for the Clever Language to follow. We
would need to answer questions like "What is the Clever Language
intended for?"; "Is it gonna be a scripting language embeddable on
some other languages, like Lua?"; "Is it gonna be a language like
PHP?"; "Is it gonna look like another existing language?". Such
answers would help we to plan new features in a more consistent way.
For instance: if Clever is going to be an embedable language, we would
think about features like Lua's; if Clever is going to look like PHP,
we would think of libraries for html output and related features and
bindings for running it on Apache and IIS (i have made some research
on the later recently);
2. Document all the intended features on the Issues list of Github,
and support all the developers interested in develop these features (i
think that is already being made);
3. Present all the progress and planned steps of the Clever Language
on the next C/C++ User Group meeting (did anybody go to the last
meeting, on setember?). I've sent an e-mail to Rodrigo Strauss asking
him about whether there would already be a date for the 2012 meeting,
but he just knew about the date of that meeting on Microsoft
(Janurary, 28th, too close and too microsoft-related);
So, what do you guys think about it?
Ricardo Gomes da Silva
First of all: welcome Rodrigo! We're glad to have you here :)
Now, about your message:
1. I agree. This should have been done a long time ago. I don't have a very well defined opinion about which way should clever go: web, desktop, embedded, etc. I think they're all good, but they're very different platforms. For web languages, I think you should consider the fact that you're working with it since the first line of code. For desktop I think we're ok. Embedding is a little bit tricky I guess, but it can also be done.
2. We're doing this, but I think not quite well yet.
3. I didn't even know there was a group, so I never knew about any meetings at all :) I haven't thought about that yet.
Best regards,
Ricardo
Rodrigo Magalhães
(...)
3. I didn't even know there was a group, so I never knew about any meetings at all :) I haven't thought about that yet.
(...)
Murilo Adriano Vasconcelos
Yes, http://www.ccppbrasil.org/wiki/index.php/Main, there is a mailing list on google groups too (https://groups.google.com/group/ccppbrasil). I went to the last meeting, on 2011, and they said that talkings about open-source projects using C++ would be appreciated.
Murilo Adriano Vasconcelos
http://murilo.wordpress.com
Ricardo Gomes da Silva
Felipe Pena
Em 17 de janeiro de 2012 10:34, Rodrigo Magalhães dos Santos
<rmagal...@gmail.com> escreveu:
> Hello Guys,
>
> Thank you for the invitation. I transcribe here the message i've
> posted on github issues page:
>
> ---------------------
>
> As we have talked some days ago, I would like to give some suggestions
> in order to define one or more "filosofical" paths for the project and
> to organize the efforts of the whole team around one or more common
> objectives.
>
> My proposals are conceptually simple and I would like to know what you
> think about them:
>
> 1. Define one or more paths for the Clever Language to follow. We
> would need to answer questions like "What is the Clever Language
> intended for?"; "Is it gonna be a scripting language embeddable on
> some other languages, like Lua?"; "Is it gonna be a language like
> PHP?"; "Is it gonna look like another existing language?". Such
> answers would help we to plan new features in a more consistent way.
> For instance: if Clever is going to be an embedable language, we would
> think about features like Lua's; if Clever is going to look like PHP,
> we would think of libraries for html output and related features and
> bindings for running it on Apache and IIS (i have made some research
> on the later recently);
>
I guess it is going to look like Python in matter of application usage. And
We must explain better our goal in the website.
> 2. Document all the intended features on the Issues list of Github,
> and support all the developers interested in develop these features (i
> think that is already being made);
>
I've prepared the website to make some documentation using the markdown syntax:
See an start at http://clever-lang.github.com/getting-started/
The files are in the clever-lang/clever-lang.github.com repository.
--
Regards,
Felipe Pena