Propose your solution
Attachments
No attachments.
Duplicates
Comments
|
|
|
I propose emacs, does anyone propose vi? ;)
|
|
|
|
I agree, a lot more needs to be done to give burgeoning developers a clear, slick and easy path into development for the platform.
|
|
|
The problem is that many projects use different ide...some projects may not even use an ide for development...
a thread in the ubuntu forum can be used for this purpose... the existing developers can guide the new developers or even recruit for their own project...This will be like a resource pool.... This can be standardized by making new developers to submit their resume(i dont know the correct word - information about what the person knows and what he is interested to do)
|
|
|
When a project starts the developer should submit information on setting the system to start development (like installing apps,editors etc..),which will be available at the developer home page..
Almost every developer puts these kind of information... but that needs to be standardized
+1
|
|
|
The problem arises when people try and force their style into IDE's.
i think that the IDE should be full, but basic GUI (nothing fancy) that is similar to Emacs with far less key pressing
you should have a standard way of handling projects that is invisible to the user (they don't see how you handle the files) yet for every language their is a language specific interface (different for each language) that is completely customizable.
There should also be a project export that packages the project if the language appropriate manner.
I the development there should be a standard (syntax highlighting, file management, etc.) for handling languages that could be voted on.
|
|
foxdude
wrote on the 1 Aug 08 at 15:55
|
|
|
so far I like geany...
I know little about the environments here because I use devstudio (and am spoiled)
All the linux dev environments suck compared to MS dev studio unfortunatly. However if there was an effort to make something similar for linux, I would love to be part of that development process.
|
|
boteeka
wrote on the 18 Sep 08 at 17:44
|
|
|
As much as I want to keep myself out of MS' environment, I have to admit that Visual Studio - despite its many-many flaws - is a very powerful tool for developers. It achieves its powers through its high level of integration. I mean, if you start up VS, you can get your feet wet with programming: you have integrated help (which is not so high quality as open source counterparts, but is highly integrated), you have integrated debugging tools (you don't have to configure anything to use it, just create some breakpoints and go), your projects build with a single click (don't have to hunt down and install a ton of dependencies), it uses a portable (between instances of VS) project management system (a folder transferred to another computer containing the project is easily opened on it and your done - you can start building).
In contrast, the open source community has a few different build systems (autotools, scons, cmake, waf, etc.), no IDE which could load a project based on makefiles (and co) correctly, no project description files, etc.
I wanted multiple times to start tweaking on different projects (at least for my own pleasure at learning experience, but even for writing patches), but almost every time when I get the source code for the project, I find myself in front of error messages when trying to build it.
For example, the Banshee project, I followed the instructions on the webpage, got the source code, but when trying to load the solution file in Monodevelop, I got an error, telling me that something is not loadable.
Maybe I just have no luck, but at least 70% of the times when I try something like that (not necessarily with a mono based project, but Python and C projects too) something goes wrong. I'd rather start tweaking the code than start to hunt down the build and other problems, but unfortunately most of the times this is not the case.
|
Post your comment
|
