Tag Info

New answers tagged

0

In addition to the exhaustive answer already given: If you look for an platform independent approach, a framework like Apache Thrift or similar might be worth a look, as they are designed especially for that purpose of platform-agnostic and language-agnostic communication. It is even possible to combine such an framework with Message Queues or a Service ...


0

You are dealing with a problem of inter-process communication with the constraint that this needs to be platform independent and with the other constraint (that frees up more design options) that its on the same machine. There is nothing inherently wrong with this approach. I recall Mathematica uses this approach (the calculation engine ('kernel') and the ...


1

How about just putting your application logic into a library. Then you could build an exe for each GUI that calls into the library and links to it.


0

My 2ยข: Pick any EOL encoding you want, but make sure it plays well with your build system, compilers, interpreters, etc. Make sure that this is cleanly explained in your wiki page, readme files, etc, intended for contributors. On the same page explain how to git config core.eol properly, so that contributors have an easy time sending pull requests. ...


0

For interpreted languages: use one that is supported by an "execution platform" (e.g. an application server) OS. That's because you should probably use the same OS for development in a first place. Also you may find yourself in a situation when you need to read or change (not a good idea, but possibility) deployed sources. For compiled languages: I see no ...


6

I would vote for CRLF: Windows is still the most widely used OS for personal computing, therefore all other OSs have ways to deal with DOS line endings The opposite is not necessarily true, not all Windows apps can deal with Unix or Mac line endings CRLF is also the line ending for all Internet Standards and RFCs, e.g. HTTP, MIME, Usenet, Internet Mail, ...


2

Here's a mostly flawless setup for testing your websites : Cross-browser compatibility : A good resource prior to implementing your solution is to check Can I Use?, which has compatibility for all the HTML5/CSS3/JS/SVG, etc... Every time you implement a new feature, test your site in Chrome, Firefox, IE, Safari and Opera (in order of importance). They're ...


5

In Jenkins you can setup different build slaves (which could run on different physical or virtual machines). Your Jenkins master could then delegate different build jobs to the corresponding slave (also in parallel). So in your case you could setup some Jenkins slaves where every slave runs on a virtual machine with a different operating system. Your ...


1

firstly for multiple classes with the same name, I would suggest that you use namespaces to clear out what class in which namespace is supposed to handle it. most frameworks error handlers can be overwritten to achieve custom error handling , I'm using Yii and at least that is supporting it. and also you can use the old frameworks working parts and include ...



Top 50 recent answers are included