On 2/5/2010 11:54 PM, David Mertens wrote: > > The first idea - changing the current working directory for the syntax > checker - is low-hanging fruit for anybody who knows the code, so > perhaps I could post that idea somewhere more... fruitful. I was going > to put it in as a request on the tracker but I couldn't find a way to > sign-up or sign-in.
The preferred method is to use the padre irc to talk to the developers. Someone there can help set up an account. At least, that was what worked for me. I think it is a good idea to enter this as a request in the tracker. That way there is a record of it even if you do not have time to contribute in the solution. > My second idea - interfacing with Inline - probably warrants a fair bit > of discussion among the developers. The more I think about it, the more > I feel that the best solution would be to add an option to Inline to > make it pretend it's working with a different file name. This is a > general solution that would minimize the code changes necessary on the > Padre end of things. What do you think? Should I send an email to the > Inline maintainer(s)? I haven't looked at the Inline code recently but this seems like something you might like to try a "hack" implementation to see if it works. It is much easier for the developers to look at a concrete code example rather than a paragraph of description. I suggest joining the inline mailing list and posting there for further discussion or, even better, feedback on your code implementing the feature. As a final note, I can appreciate how it can be frustrating to have a good idea and suggest it but then hear nothing back. The reality of open source software is that people do what they can and want to do when they have the time to do it. What that translates to is that small, actionable proposals are much more likely to be acted upon or responded to. In fact, often the choice is between working on code and replying so sometimes the code is worked on rather than email typed and sent. Cheers, Chris _______________________________________________ Padre-dev mailing list [email protected] http://mail.perlide.org/mailman/listinfo/padre-dev
