First Thank you ta0kira you been kind. Just to let you know i have read How To Ask a Question
http://www.linuxquestions.org/linux/...Ask_a_Question
I take yours and this post in great detail and appreciate you putting in the time.
I was hope to bring-up a heated response on this form of what people like in an standardize api as well as if they wanted such a thing. My dream was to have kde and gnome use the same utility use this type of api.
The reason I would what to do this is I think it would prevents blot,reduce dependency etc which i put in my bullets. To me it looks like i done what was asked to heat such a discussion but it flopped.
Just to give you a run down on my thoughts of how i meat what you post.
Quote:
Originally Posted by ta0kira
Well, there is a certain implicit priority with public posting. The most important piece of info is the title, and if it doesn't contain a representative summary of the post's contents then people will go into it with an incorrect assumption.
|
I give much thought to my title, I think the one I give is good if you have a better please, let me know. I was think about try to post on other form as well such as wxwidgets (if i did not already do so i would have to check). I was think about try to post something on the Portland project, kde developer , gnome developer, mailing list etc.
Quote:
Second most-important are the topic sentences of your paragraphs and bullets. One should know what you're talking about in vague detail just by reading the first sentences of your paragraphs, with the latter paragraphs generally being less important, though normally one should get a good idea of what your post is about from the first and last paragraphs. One will get more detail by reading more sentences per-paragraph. While it isn't always "polite" to read things this way, it's generally how people read a long article or post if they have a lot to do or a lot else to read. If the strategically-read sentences spark an interest and reflect a new idea then people tend to re-read more closely to get a better idea of what you're talking about, otherwise they generally assume it's just a recombination of ideas they've pondered to death already.
|
Well I knew the above and tried to do that. My first sentence under My category
Who/What?
was
Quote:
I would like to create create a standardize api that would work on all platform.
|
which was the best way I thought of describing what i what to do in vague details.
How would you word it?
Quote:
Anyway, I do think it's interesting to standardize in the way you're talking about, but it's difficult to standardize GUIs and threads because different operating systems deal with that sort of thing in extremely different ways. Java already attempts to do this, but in a way that wouldn't work well with C++.
|
I think wxwidgets does this two which dose work well with c++ and keep a native look an feel( which is why I wanted to base my api off of it).
It keeps the code to make the program stander while keeping the code that implement the program specific to the os it run on.
I would say In my opinion wxwidgets dose what i want except for
1.)
I don't think it flexible enough to listen to the demands of all users
Which i want to do. I want it design to be based of the demand of the user who would be interested in this idea(of a standardize api).
i was hoping to get design idea in this thread. I think it flopped.
Just to give you an example wxwidget dose not support namespace because they want to be compatible with all compilers,some compilers don't work with it. I think good free ISO compilers are easier to find know days if I'm not mistaken I think borland,gcc and even Microsoft new c++ compiler all support the ISO c++ stander. Microsoft be late in the game. Well i think they support the ISO stander ,I could be mistaken. I find it hard to tell.
I have yet been able to find any books or web site explaining c++ and the stander in plain text as well as full details. The best source of info was on
www.cplusplus.com
2.)
I don't think is easy to port
In short i think it design can be improved so it can be easy ported to other gui beside gtk an X wich it has port for.
To give you an example of what i try to say.
I tried to make a port of wxwidgets to qt a little myself and quick became aggravated buy all the ifdef that did not work, I don't think it is a good idea to implement it this way. I think it is better to derive a basic class with virtual function with default implementation of a function that are missing when ever possible instead of useing ifdef to cut them out and remove the derived class when done.
Quote:
Basically what you're trying to do is make the JRE C++-friendly, and maybe go so far as to make a specification out of it for others to creatively implement. Maybe you should just find a way to make Java work well with C++ in an OS-portable way! If you could do that then I might actually willingly use Java.
ta0kira
|
I do not know a-lot about Java. I know of the basic of JRE and Java bite-code but not much more but, basically yes that what i try to do. I try to have a native feel thou to the gui there using and go father than c++ and expand to other languages like wxwidgets did.
I don't think people will be willing to settle for java because of a native api.
Note:
I looking for way to revive this dead thread. I think that this idea is very good and is very important to me, but I have a hard time explaining it and getting people attention. I think other would like it two, if I could get there attention. If They don't like it I could let my idea go since there no way of implementing it. Even thou i think this type of thing would be said, because to me I don't see how any one could not want this unless people would rather fight than try to be creative and solve there differences. I think that such an api would bring much order to in my opinion a messy OS. A lot of people reinvent the same program because of a lack of a standardize api even thou licenses are part of the problem. If thing get implement my way i think it will solves most of people problems. I think if we work together we can make an api flexible enough to meat the needs of almost all user.
I just can't help but wondering what do i do now?