On Sun, Aug 12, 2012 at 5:13 PM, Enrico Tröger <[email protected]> wrote: > First, Geany is just an IDE or text editor or something between. > Its job is to help users writing code, not to provide everything to get > it compiling/running, especially because Geany supports not only C but > also many many more languages. > Setting up an environment capable of compiling/running/debugging code > was, is and will be the responsibility of the user because only he knows > what she needs and wishes. That's definitely true. It's amazing to know that Geany is quite general-purpose.
> You are speaking multiple times of "noobs". I think less advanced users > need a tutorial how to setup a dev environment. They don't need a huge > installer with everything in. That would maybe ease installation but > won't help understanding what's going on. And then, from my experience, > users who want to learn a programming language, especially a language > like C, are not that noobish anymore. They should know how to install a > program or how to unpack an archive into a specific path. I'm writing a Wiki page. https://wiki.geany.org/tag/win32/getting-started Actually myself want a bundled, PATH independent version, too. Since it would be hard to setup PATH in low privilege Windoze environment like that found in my department. > Then, if we would include Mingw for C development, then Python users > will arrive and request inclusion of a Python runtime, then the Perl > guys, PHP, Ruby, ... > The installer would end up in a 3 GB file with everything included. Anyway, what I proposed an addition rather than a replacement. It's just like there is a GTK bundled version. > Another reason is that it might raise licensing questions when bundling > different runtime environments of various languages into one installer, > even if they are all Free Software. True. But GCC should be OK, anyway. > To sum it up: > the Geany installer won't get a bundled Mingw or whatever environment > built into. > However, as others said before, if anyone wants to do that as a > contribution, that is welcome. Yes, I'd like to do it unofficially. > P.S.: Generally it helps to use the correct names of software components > in the public, even if you don't like them (which is also true for me > and probably many others) but still using something like "Windoze" might > create a wrong impression of how serious you are about the whole topic. I'm grateful that Windows users seems not offended by "Windoze". Windows is a trademark of a giant firm, anyway. So I'd keep the spelling in this thread. _______________________________________________ Geany mailing list [email protected] https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
