Talk:The OS/2 API Project: Difference between revisions
No edit summary |
mNo edit summary |
||
(8 intermediate revisions by 2 users not shown) | |||
Line 8: | Line 8: | ||
Too bad Andreas that you are not able to communicate in an educated matter. You are free to spin off your own page. This page will be protected for the moment. [[User:Martini|Martini]] ([[User talk:Martini|talk]]) 14:05, 4 December 2017 (CET) | Too bad Andreas that you are not able to communicate in an educated matter. You are free to spin off your own page. This page will be protected for the moment. [[User:Martini|Martini]] ([[User talk:Martini|talk]]) 14:05, 4 December 2017 (CET) | ||
I cannot realise your "educated matter". What does your communication mean - answering after nine months? What does a German oak care about?--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 18:33, 4 December 2017 (CET) | |||
See Andreas,you are doing it again. Why instead of complaining about the nine months don't you just list what needs to be fixed? You enjoy too much correcting people and getting into nonsense discussion with your "over the shoulder" and/or sarcastic arguments, that is just so wrong. Please Andreas try to cool off. 20:21, 4 December 2017 (CET) | |||
Unfortunately I already mentioned the parts which need a major rework or at least some kind of clarification. Perhaps the first step would be to narrow the scope to "OS/2 API". It should not stand for "abbreviated potpourri inside". Everything that makes use of a libraries (that interface with the OS/2 API itself) should be branched out - because it's creating to much bloat here and leads to confusion. It's not an enjoyment to write all the time about almost the same simple principles. My main objective is an improvement of range and vigour. As the adminstration of this side keeps all statistical data secret I can only use available public services for optimisation tasks. It's uninteresting for potential readers to see in every second page the same copy-pasted stuff that proves almost everytime wrong after closer investigation. Search engines use similar models for the ranking mechanism. Can you still follow?--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 00:40, 5 December 2017 (CET) | |||
I think you should try your own idea fork of this page: | |||
* I'm trying to document all OS/2 related APIs that are available. Not only the "IBM Brand OS/2 API", and I have it separated in three se4ctions on the page. I don't think that what is it not IBM's should be branched out. | |||
* I don't think that the page is bloated nor creates confusion. I notice that you don't like tables on wiki pages, I have a different opinion. | |||
* Can you put an example of the "same copy-pasted stuff that proves almost every time wrong after closer investigation" ? | |||
* I don't understand what secret information do you require? I don't think that you need to optimize every nanosecond of loading page time if the user will not notice any difference. | |||
[[User:Martini|Martini]] ([[User talk:Martini|talk]]) 01:02, 5 December 2017 (CET) | |||
So why not make a separate "OS/2 related APIs" because it's completely different from the "OS/2 API". I didn't talk about IBM but just tried to conform with the matching ABI for practical purposes. All cross-platform stuff that's not directly related has to perish. OS/2 API is complex enough with over 1000 calls to manage it. Putting 10000 more calls to a list is no improvement at all. I don't want to walk through all so-called "Examples" of non-working C code etc. Some copy-paste errors date back to times when IBM created the documentation. But the largest chunk of copy-paste errors came from wrong code page translation. I can understand that this pages are no longer for a programming audience and it's not important for you to have working code snippets. So I politely ask for a ''SyntaxHighlight'' and ''Cite'' extension to enable on this server? That would at least help my coding servants. | |||
Regarding tables: My workers and me are following the usual wiki rules, to avoid tables where not appropriate. I don't know on what your allegation is based. I cannot count the number of tables we created or reformatted. But we are in 2017 (not 1997) and the use of table for meagre layout purposes should be avoided. | |||
But bandwidth is quite limited for this server. If it seems fast for you (because everything cames from your local cache) it's fine. But that's not the real visitor's experience. At least the bandwidth waste by large graphics could be cut further down. Nothing too "secret" only the MRT after the referrer if possible.--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 03:20, 5 December 2017 (CET) | |||
About your comments: | |||
1) Let me check the extensions required with Adrian. I guess you mean: | |||
* https://www.mediawiki.org/wiki/Extension:SyntaxHighlight | |||
and | |||
* https://www.mediawiki.org/wiki/Extension:Cite | |||
2) I can not fix the mistakes on the IBM documentation because of my lack of skills on this area. But it can be a good time for you to fix it since you have more programming skills, of if there is other place that already fixed the IBM mistakes on the documentation let me know. | |||
3) Please post a reference about "the usual wiki rules, to avoid tables where not appropriate." | |||
[[User:Martini|Martini]] ([[User talk:Martini|talk]]) 14:15, 5 December 2017 (CET) | |||
#I have no view of the wiki configuration. But the second one should be already available with the outdated version used here. | |||
#I would opt for addition of different file types. Now there are only pictures ...not useful for programming at all. In my opinion it would be a better approach to have all types of source code (with the right codepage) and related stuff in their own files. Plain text MIME type should be sufficient. I don't know how the current configuration will handle text/x-asm, text/x-c or application/postscript. | |||
#As references don't work until now I can only post the link to MediaWiki's official documentation [https://www.mediawiki.org/wiki/Help:Tables] (the first sentence).--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 16:24, 5 December 2017 (CET) | |||
==OS/2 Ported APIs== | |||
"These are APIs ported from other platforms to OS/2-eCS-ArcaOS. The functions documentation of the APIs are only linked to their respective sites." | |||
I don't realise, how such wrong claims can be made seriously. Please show at least one example, before telling fairytales here. There's no reason to port portable libraries that are not APIs. They can be simply build for a specific target platform.--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 19:33, 14 December 2017 (CET) |
Latest revision as of 20:33, 14 December 2017
Martini (talk) 13:52, 21 February 2017 (CET) Andreas, where did you move all the "OS/2 Ported APIs" table?
Martini (talk) 13:55, 21 February 2017 (CET) I found this KLIBC Ports it is very sad that you deleted my table for this page. I'm switching it back. Let me know if you don't like it so I will protect this page.
Martini (talk) 04:45, 1 March 2017 (CET) Andreas, I don't like what you did to this page. I will be reverting the changes and protecting this page since you don't seems to understand that this page is a quick view of the APIs that are available for the OS/2 platform. When you separate the pages you are making it harder for developers to know which APIs can be used on OS/2. You also created categorized pages to separate this page which I think it is not right.
Unfortunately this page makes wrong claims. First there is written "This are the APIs included on the IBM's OS/2 Warp product." And then follows a table that contains also stuff that is definitely NOT included. Again I destroyed nothing, You removed my corrective edits without discussion. I concentrated first on the content to be right, the next step to create a template for better formatting is now no longer possible for me. It's sad that you also removed my fixes of wrong spelling. You are making it harder by inventing APIs that are simply not existing or introducing programming language specific stuff to this area. And much worse compiler specific and library specific things like this kLIBC halfbaked ports. The categories should help to maintain everything in a more effective way and preventing name space problems (that were introduced by your clueless usage of ":"). --ak120 (talk) 12:08, 1 March 2017 (CET)
Too bad Andreas that you are not able to communicate in an educated matter. You are free to spin off your own page. This page will be protected for the moment. Martini (talk) 14:05, 4 December 2017 (CET)
I cannot realise your "educated matter". What does your communication mean - answering after nine months? What does a German oak care about?--ak120 (talk) 18:33, 4 December 2017 (CET)
See Andreas,you are doing it again. Why instead of complaining about the nine months don't you just list what needs to be fixed? You enjoy too much correcting people and getting into nonsense discussion with your "over the shoulder" and/or sarcastic arguments, that is just so wrong. Please Andreas try to cool off. 20:21, 4 December 2017 (CET)
Unfortunately I already mentioned the parts which need a major rework or at least some kind of clarification. Perhaps the first step would be to narrow the scope to "OS/2 API". It should not stand for "abbreviated potpourri inside". Everything that makes use of a libraries (that interface with the OS/2 API itself) should be branched out - because it's creating to much bloat here and leads to confusion. It's not an enjoyment to write all the time about almost the same simple principles. My main objective is an improvement of range and vigour. As the adminstration of this side keeps all statistical data secret I can only use available public services for optimisation tasks. It's uninteresting for potential readers to see in every second page the same copy-pasted stuff that proves almost everytime wrong after closer investigation. Search engines use similar models for the ranking mechanism. Can you still follow?--ak120 (talk) 00:40, 5 December 2017 (CET)
I think you should try your own idea fork of this page:
- I'm trying to document all OS/2 related APIs that are available. Not only the "IBM Brand OS/2 API", and I have it separated in three se4ctions on the page. I don't think that what is it not IBM's should be branched out.
- I don't think that the page is bloated nor creates confusion. I notice that you don't like tables on wiki pages, I have a different opinion.
- Can you put an example of the "same copy-pasted stuff that proves almost every time wrong after closer investigation" ?
- I don't understand what secret information do you require? I don't think that you need to optimize every nanosecond of loading page time if the user will not notice any difference.
Martini (talk) 01:02, 5 December 2017 (CET)
So why not make a separate "OS/2 related APIs" because it's completely different from the "OS/2 API". I didn't talk about IBM but just tried to conform with the matching ABI for practical purposes. All cross-platform stuff that's not directly related has to perish. OS/2 API is complex enough with over 1000 calls to manage it. Putting 10000 more calls to a list is no improvement at all. I don't want to walk through all so-called "Examples" of non-working C code etc. Some copy-paste errors date back to times when IBM created the documentation. But the largest chunk of copy-paste errors came from wrong code page translation. I can understand that this pages are no longer for a programming audience and it's not important for you to have working code snippets. So I politely ask for a SyntaxHighlight and Cite extension to enable on this server? That would at least help my coding servants. Regarding tables: My workers and me are following the usual wiki rules, to avoid tables where not appropriate. I don't know on what your allegation is based. I cannot count the number of tables we created or reformatted. But we are in 2017 (not 1997) and the use of table for meagre layout purposes should be avoided. But bandwidth is quite limited for this server. If it seems fast for you (because everything cames from your local cache) it's fine. But that's not the real visitor's experience. At least the bandwidth waste by large graphics could be cut further down. Nothing too "secret" only the MRT after the referrer if possible.--ak120 (talk) 03:20, 5 December 2017 (CET)
About your comments: 1) Let me check the extensions required with Adrian. I guess you mean:
and
2) I can not fix the mistakes on the IBM documentation because of my lack of skills on this area. But it can be a good time for you to fix it since you have more programming skills, of if there is other place that already fixed the IBM mistakes on the documentation let me know.
3) Please post a reference about "the usual wiki rules, to avoid tables where not appropriate." Martini (talk) 14:15, 5 December 2017 (CET)
- I have no view of the wiki configuration. But the second one should be already available with the outdated version used here.
- I would opt for addition of different file types. Now there are only pictures ...not useful for programming at all. In my opinion it would be a better approach to have all types of source code (with the right codepage) and related stuff in their own files. Plain text MIME type should be sufficient. I don't know how the current configuration will handle text/x-asm, text/x-c or application/postscript.
- As references don't work until now I can only post the link to MediaWiki's official documentation [1] (the first sentence).--ak120 (talk) 16:24, 5 December 2017 (CET)
OS/2 Ported APIs
"These are APIs ported from other platforms to OS/2-eCS-ArcaOS. The functions documentation of the APIs are only linked to their respective sites."
I don't realise, how such wrong claims can be made seriously. Please show at least one example, before telling fairytales here. There's no reason to port portable libraries that are not APIs. They can be simply build for a specific target platform.--ak120 (talk) 19:33, 14 December 2017 (CET)