Closed nightscape closed 8 years ago
The distinction was just made, because travis uses some ancient Ubuntu with an older GTK version. I like the look of the SearchEntry more then a plain Entry field. But i would be fine without SearchEntry. Glade powered UI is far nice then that!
As you can see, the build failed, because it can't find SearchEntry on the Ubuntu that travis is using..
Ok, just restored the feature-scoped functions and amended to the commit.
That's frustrating. It looks like travis has gtk 3.4? But Builder::new_from_string is from 3.10.
There is also a new way to use travis with containers, but i haven't got it to work wither (i think some libraries were missing the last time i tried)...
Apart from that.. any ideas?
The travis ticket for an Ubuntu update has not seen updates sind 2014.. https://github.com/travis-ci/travis-ci/issues/2046
As i said, not sure if we can get rrun to use travis + containers (which is the recommended and "new" way to run travis): https://docs.travis-ci.com/user/workers/container-based-infrastructure/
If you rebase this on the new master it will hopefully pass tests
Unfortunately, the container-based builds are also based on Ubuntu 12.04 Precise with the same hopelessly outdated GTK. I'm just trying the Trusty beta which is unfortunately not available for containers...
Wow, this was annoying. I wouldn't have expected Travis to be based on such an old version of Ubuntu.
So, back to sudo: required
and slow builds :-1: but at least we can use newer GTK versions now :+1:
Good to merge from my side.
Can we also get rid of the Entry then and just use SearchEntry? :)
This should make implementing #12 much easier :) No changes to the UI yet. Is the
search_entry
feature distinction important? If so, I can change the Glade file not to include theEntry
/SearchEntry
widget and add it from the code (as it was before).