You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you plan to pack konstrukt into its own namespace instead of using k_ prefix in class names? If so, what should be the name of its global namespace?
And by the way, what version should it relate to?
The text was updated successfully, but these errors were encountered:
I have personally not been using Konstrukt for over 3 years now, so very little work is going into developing it further. I believe there are still some people using it, mainly for legacy apps, so there is the occasional fix now and then, but Konstrukt will probably never get ported to having full namespace support. If you're starting on new projects today, I would suggest that you base it on a framework with some more momentum.
Thanks for your response. I wanted (and probably still want) to use Konstrukt as a core of my project's second major version. Because this project has been written proceduraly by one of my collaborators for first time, it can be great new start using Konstrukt. Later I will completely rewrite it for our needs but I can keep a branch for improving the original Konstrukt. :-)
Do you plan to pack konstrukt into its own namespace instead of using
k_
prefix in class names? If so, what should be the name of its global namespace?And by the way, what version should it relate to?
The text was updated successfully, but these errors were encountered: