Increasing usage for C++ new operators based on data model indexes?

kshegunov · 26 Oct 2018, 18:18

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

I got another software development idea which I find useful.

Good. Make a proof of concept for it as well. We can discuss it after that.

I have described it in a few variants for this feature request already.

You have not written anything tangible for us to discuss. You can describe it all night long, but at the end of the day we have to have something to base the discussion on. Some kind of proposed code that is to replace the current approach and then we can compare and argue.

Another approach

Finish one of the approaches before jumping into the next one.

elfring · 26 Oct 2018, 18:26

You have not written anything tangible for us to discuss.

Can you discuss the programming interface design for a single function in terms of concepts (without referring to source code examples)?

kshegunov · 26 Oct 2018, 18:40

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

Can you discuss the programming interface design for a single function in terms of concepts (without referring to source code examples)?

No. There's no interface design for single functions, plus if it's only one function, just write it down for us and we can take a stab at the issue.

elfring · 26 Oct 2018, 18:56

There's no interface design for single functions,

I find this view questionable.

plus if it's only one function, just write it down for us and we can take a stab at the issue.

template<typename model_item, typename model_index> model_item * get_item_pointer(model_index mx);

Can you discuss such a function template declaration better?

kshegunov · 26 Oct 2018, 19:10

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

I find this view questionable.

That's your right. I will not spend any time arguing it either way.

Can you discuss such a function template declaration better?

That's a declaration, moreover it's a template, so this declaration doesn't mean anything to me. I have no idea what it is to be doing. Neither can I know how this model_item is to be handled inside the model, nor what model_index is, since it's a generic template type. Additionally there's no clarity of how this function is to be integrated into the QObject derived models, because there are limitations of what moc can parse.

Give us some solutions to these problems and I'd be happy to pitch in with ideas, critiques and even work. But only if you take the time to actually prepare something that can reasonably be discussed.

Vague notes about theoretical constructs are not acceptable.

elfring · 26 Oct 2018, 19:12

I have no idea what it is to be doing.

Your understanding of this programming interface (and my API proposal) might be still incomplete at the moment.
But I am confident that you know already what such a function should be doing: You get a pointer for an object based on the provided input data.

…, since it's a generic template type.

Can you become used to work with templates for software development and involved concepts?

kshegunov · 26 Oct 2018, 19:17

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

Your understanding of this programming interface (and my API proposal) might be still incomplete at the moment.

That is for sure, as you have not proposed an API.

But I am confident that you know already what such a function should be doing: You get a pointer for an object based on the provided input data.

Humor me.

Can you become used to work with templates for software development and involved concepts?

I already am.

elfring · 26 Oct 2018, 19:18

…, as you have not proposed an API.

A function template declaration can be a succinct description for an application programming interface, can't it?

kshegunov · 26 Oct 2018, 19:21

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

A function template declaration can be a succinct description for an application programming interface, can't it?

No, it can't. Not even by a long shot.

elfring · 26 Oct 2018, 19:23

No, it can't. Not even by a long shot.

How can your view fit to the C++ standard template library?

kshegunov · 26 Oct 2018, 19:36

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

How can your view fit to the C++ standard template library?

It fits perfectly. The STL is comprised by many, many, many functions and classes. They even have bodies too, unlike the one declaration you wrote.

elfring · 26 Oct 2018, 19:42

The STL is comprised by many, many, many functions and classes.

My proposal can eventually grow into another template library, can't it?

They even have bodies too, unlike the one declaration you wrote.

The desired implementation can evolve further if the required concepts will be generally accepted.

kshegunov · 26 Oct 2018, 19:47

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

My proposal can eventually grow into another template library, can't it?

Only if you write the library, or at least the core of it.

The desired implementation can evolve further if the required concepts will be generally accepted.

The only thing that's going to be generally accepted is written code, i.e. an implementation. Since you have written none, none is going to evolve.

elfring · 26 Oct 2018, 22:02

The only thing that's going to be generally accepted is written code, i.e. an implementation.

Some software designers expect the development of specific concepts before concrete programming.
Template programming can help to achieve a safer coding style.

JKSH · 27 Oct 2018, 08:24

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

Some software designers expect the development of specific concepts before concrete programming.

@elfring, discussing "specific concepts" with you is difficult because your posts are unclear. If you write code, then your ideas will be clearer and easier to understand.

elfring · 27 Oct 2018, 09:50

discussing "specific concepts" with you is difficult because your posts are unclear.

I hope that the involved communication difficulties can be resolved after a bit more time.

If you write code, then your ideas will be clearer and easier to understand.

Can your desire for “source code” distract from the really relevant functional design?
Can other information presentation variants and communication tools help more to achieve also a better common understanding?

kshegunov · 27 Oct 2018, 17:22

I'll take the liberty to answer instead of @JKSH.

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

I hope that the involved communication difficulties can be resolved after a bit more time.

Your hopes are falling short. If you don't make an effort to provide what is required for a conversation, then the conversation is nonexistent. You don't. You don't answer questions, you don't in any way try to give back what was asked for, and you randomly pick up parts of the sentences to try and extend this thread.

Can your desire for “source code” distract from the really relevant functional design?

It can't. Source code is the product of thought in this community. Arguing excessively and arguing against providing source code is not going to work. We want to see you're serious enough about your claim that you're willing to put an effort in defending it. Empty platitudes and (semi)random links to documentation(s) are not going to be entertained.

Can other information presentation variants and communication tools help more to achieve also a better common understanding?

Common understanding is a two-way street. If you're not willing to meet us halfway I see no reason any of us to want to waste our time.

elfring · 27 Oct 2018, 17:33

You don't answer questions,

I find this information inappropriate.

you don't in any way try to give back what was asked for, …

I chose to respond in different ways.

Arguing excessively and arguing against providing source code is not going to work.

Are there any developers around who can clarify design extensions without thinking only in source code?
Can the original development idea become more interesting?

Common understanding is a two-way street.

Can the clarification of design aspects from a function template declaration help here?

kshegunov · 27 Oct 2018, 17:44

@elfring said in Increasing usage for C++ new operators based on data model indexes?:

I find this information inappropriate.

Yeah, me too.

I chose to respond in different ways.

Yeah, me too.

Are there any developers around who can clarify design extensions without thinking only in source code?

We don't think only in source code, but we find it as a useful way to clarify what we mean. Are you able to clarify your design extensions through source code?

Can the original development idea become more interesting?

Not unless you make it more interesting by including some source that we can discuss.

Can the clarification of design aspects from a function template declaration help here?

Nope, but a class with its function bodies would help.

elfring · 27 Oct 2018, 17:55

Are you able to clarify your design extensions through source code?

My published software development activities demonstrate that such contributions can happen.

Not unless you make it more interesting by including some source that we can discuss.

How will your interests evolve for application programming interfaces expressed in the format of function template declarations?

Nope, but a class with its function bodies would help.

Can it occasionally be more helpful to clarify software design properties before attempting a specific implementation?