Reply to thread

Message

<blockquote data-quote="Klintus Fang" data-source="post: 421995" data-attributes="member: 3580">the manual configuration I'm talking about is the idea that the user might have to manually configure the other application.&nbsp;&nbsp; I realize its up to the designer of the other application.&nbsp; But you cited the manual interaction with the application as the reason that the libraries won't work.but back to the library issue:&nbsp; there's no reason you can't put pop-up windows and dialogs in your library if you want.&nbsp; so I still don't understand what the tcp-ip connection is buying you, other than maybe the ability to pass information between two computers.I still think libraries are better, and the reason I've been argueing it so hard is because I've thought about it a lot over the past 12 months.&nbsp; There are lots of great applications out there for doing this or that minor task.&nbsp; And my opinion is that they would all be&nbsp; alot more usefule if the developers would design them as two pieces.&nbsp; One piece is the core computation code that should compile easily on any OS whatsoever.&nbsp; The other piece is the gui that wraps around it and used the library.&nbsp; If they were designed that way (which is trivially easy to do) then it would only be a tiny step to publish the libraries api and let others leverage the work you've done directly.&nbsp; If people are really, really protective of the idea that their name has to be revealed to the user when the library is used then they can put pop-ups or dialogs in the library if they want.&nbsp; But by making that choice they make it so their library will no longer easily carry from one platform to another.Either way I'm still confused:&nbsp; what is wrong with shared libraries?I know that opening a tcp/ip port isn't that big of a deal but I still don't see what value it gives you other than adding an extra layer to the means by which developers can share their work.And I know that I am being stubborn, but I haven't seen any compelling reason for why tcp/ip is better than just compiling as a library and publishing the api?&nbsp; distributed computing is one thing that was mentioned but what rpg problem requires more than one computer in order for it to be solved quickly, i.e., what rpg problem needs to be distributed across a network?</blockquote>

[QUOTE="Klintus Fang, post: 421995, member: 3580"] the manual configuration I'm talking about is the idea that the user might have to manually configure the other application. I realize its up to the designer of the other application. But you cited the manual interaction with the application as the reason that the libraries won't work. but back to the library issue: there's no reason you can't put pop-up windows and dialogs in your library if you want. so I still don't understand what the tcp-ip connection is buying you, other than maybe the ability to pass information between two computers. I still think libraries are better, and the reason I've been argueing it so hard is because I've thought about it a lot over the past 12 months. There are lots of great applications out there for doing this or that minor task. And my opinion is that they would all be alot more usefule if the developers would design them as two pieces. One piece is the core computation code that should compile easily on any OS whatsoever. The other piece is the gui that wraps around it and used the library. If they were designed that way (which is trivially easy to do) then it would only be a tiny step to publish the libraries api and let others leverage the work you've done directly. If people are really, really protective of the idea that their name has to be revealed to the user when the library is used then they can put pop-ups or dialogs in the library if they want. But by making that choice they make it so their library will no longer easily carry from one platform to another. Either way I'm still confused: what is wrong with shared libraries? I know that opening a tcp/ip port isn't that big of a deal but I still don't see what value it gives you other than adding an extra layer to the means by which developers can share their work. And I know that I am being stubborn, but I haven't seen any compelling reason for why tcp/ip is better than just compiling as a library and publishing the api? distributed computing is one thing that was mentioned but what rpg problem requires more than one computer in order for it to be solved quickly, i.e., what rpg problem needs to be distributed across a network? [/QUOTE]

Verification