On Donnerstag, 9. November 2017 15:32:46 CET Friedrich W. H. Kossebau wrote:
> Am Dienstag, 7. November 2017, 20:08:59 CET schrieb Martin Koller:
> > On Dienstag, 7. November 2017 16:42:40 CET Martin Flöser wrote:
> > > Am 2017-11-03 21:30, schrieb Martin Koller:
> > > I don't mind what you develop
Am Dienstag, 7. November 2017, 20:08:59 CET schrieb Martin Koller:
> On Dienstag, 7. November 2017 16:42:40 CET Martin Flöser wrote:
> > Am 2017-11-03 21:30, schrieb Martin Koller:
> > I don't mind what you develop in your spare time. Not at all. What I
> > mind is if a product is added to KDE as a
Am Dienstag, 7. November 2017, 19:27:31 CET schrieb Martin Koller:
> On Dienstag, 7. November 2017 15:32:23 CET Friedrich W. H. Kossebau wrote:
> > BTW, would you like assistance to have liquidshell covered on
> > build.kde.org? Seems it is not there yet.
>
> Wow - didn't know that this exists.
>
Michail Vourlakos ha scritto:
>
>
> BTW: for every e-mail I send I need moderator approval is that a standard
> procedure or I can register somewhere to avoid this?
kde-core-devel is moderated even for registered users, but usually after few
posts the moderators put people in the whitelist.
Cia
On Thursday, 9 November 2017 09:58:26 CET Tomaz Canabrava wrote:
> On Sun, Nov 5, 2017 at 4:12 PM, Michail Vourlakos
>
> > during the review phase in Latte we removed the following code in case it
> > would conflict in some cases:
> >
> > #if __GLIBCXX__ <= 20150623
> > namespace std {
> > templ
On 05/11/17 16:12, Michail Vourlakos wrote:
> Do you know any better way to handle this?
You can let cmake do the check:
https://cmake.org/cmake/help/v3.0/module/CheckSymbolExists.html
Not sure if this is the best option, though.
Greetings,
Sven
signature.asc
Description: OpenPGP digital sig
On Sun, Nov 5, 2017 at 4:12 PM, Michail Vourlakos
wrote:
> Hello everyone,
>
> during the review phase in Latte we removed the following code in case it
> would conflict in some cases:
>
> #if __GLIBCXX__ <= 20150623
> namespace std {
> template
> unique_ptr make_unique(Args &&... args)
> {
>
Awesome,
On Thu, Nov 2, 2017 at 8:39 PM, Michail Vourlakos
wrote:
> Just to update...
>
> Latte from now on can be found at extragear after succeeding at its review
> phase...
> as mentioned also at: https://phabricator.kde.org/T7115
>
Downloading and installing to test.
<3
> regards,
> [mich
Hello everyone,
during the review phase in Latte we removed the following code in case it
would conflict in some cases:
#if __GLIBCXX__ <= 20150623
namespace std {
template
unique_ptr make_unique(Args &&... args)
{
return std::unique_ptr(new T(std::forward(args)...));
}
}
#endif
this was ne
Hi Shaheed, Chris,
Shaheed Haque schrieb am Sa., 4. Nov. 2017 um
18:35 Uhr:
> FWIW, I already tried that (types.ModuleType is itself a perfectly
> subclassable class!) […]
>
> Now, none of that may be a limiting factor in the plan you seem to be
> discussing, but it was part of what made me thin
Hi,
On Friday 2017-11-03 12:52, Philipp A. wrote:
Am I missing something? Namespaces should be Python modules, not classes.
If we can do represent them this way, the problem is solveable:
https://packaging.python.org/guides/packaging-namespace-packages/
there are two different things that shou
Hi Shaheed,
Thank you so much for all your work!
a framework-by-framework integration of the binding generation logic (as
> previously pioneered by Steve) probably cannot work in general because
> there are cases where multiple frameworks contribute to to the same C++
> namespace […]
>
> The prob
Hi Shaheed,
Shaheed Haque schrieb am Fr., 3. Nov. 2017 um
14:16 Uhr:
> Philipp,
>
> - my overall understanding of this technique is that it may end up
> being fragile, especially given the difference between P2 and P3.
>
Python 2? I’m sure we shouldn’t include into our decision making an
obsole
> On Nov 4, 2017, at 4:46 AM, Philipp A. wrote:
>
> Entirely new bindings lead to new applications being written using those
> bindings. Writing applications in Python 2 is an immediate maintenance burden
> and people only do it because of stubborn ideology or a complete lack of
> awareness
Hi Shaheed,
Thank you for the clarifications!
My observation is that *nobody* is likely to help with that problem: the
> framework owners did
> nothing obvious to either keep PyKDE4 going (out of tree) or to help
> Steve with my earlier SIP based efforts (in tree).
>
It's a bit sad, but not too
Hi Wim!
So now I have a (C++) namespace 'A' that bears no relationship to anything
> to do with the file system or any type of Python packaging: it exists only
> in memory for the duration of the python session.
>
Yeah, cool, so we just use a path hook and are ready to go right?
https://www.pyth
Just to update...
Latte from now on can be found at extragear after succeeding at its review
phase...
as mentioned also at: https://phabricator.kde.org/T7115
regards,
[michail]
Hello,
Just by curiosity, I've tried your shell.
It is quite similar to my plasmashell configuration. It works for me
except that I get tons of messages like:
"0 instead of 3 arguments to message {Memory Used: %1 MB (...} supplied
before conversion."
"0 instead of 2 arguments to message {Mem
18 matches
Mail list logo
