Skip to main content

Planning

There are so much things that I want to write down but can't find out a time to do it. Lately my time management seem to be the worst ever. So I'll try to jot down first what in my head and hopefully I can write about it soon.

  • Understanding Django Content Type framework - I've been working on application that require me to use Django's Content Type framework (at least I decided to use contenttype to accomplish the task). Along the way I started to understand how Django implemented it. Content type concept not really unfamiliar to me since Drupal also using the concept for their Information Archictecture (IA). Django Content Type however seem much more flexible (compared to pre Drupal 7) and simpler to understand (compared to Drupal 7 similar concept).
  • Using Django's haystack app for search in your website/application - I decided to use haystack to provide search in another application I've developing and quite excited to see how simpler and fast I can get search working through haystack. I used whoosh for the search backend since the application not that big and will be used by just a number of users so performance not that important.
  • Look into buildbot or jenkins - I need to pick up a topic for our next company meetup in Pycon Sg next week. It can be any topic of my interest so long as it can still benefited the whole team in the presentation. I'm still not decided but topic on automated testing/continuous integration maybe what I'm heading up to.
  • Sqlalchemy - I used sqlalchemy in of my migration script and need to jot down how to get started quick plus some of the concept such as the Session that I started to understand. As everybody know, sqlalchemy is a very huge library and documentation span over few hundred pages I guess. Always lost in the documentation whenever I need to use it.

On another note, would be going to Pycon Sg next week. This would be my first experience with Pycon, hopefully can learn lot of things along the way.
Labels:

Comments

Post a Comment

Popular posts from this blog

PHP with docker

A friend asking about a PHP library and I decided to test whether that library is working. But I don't have PHP environment setup (we're Python shop btw). But thanks to docker, that's easy these days. docker run -it --tty --rm --volume $PWD:/app --user $(id -u):$(id -g) composer require google/apiclient:^2.0 Then we just need to create the script to run, still in the same directory:- include_once __DIR__ . '/vendor/autoload.php'; $GCSE_API_KEY = "nqwkoigrhe893utnih_gibberish_q2ihrgu9qjnr"; $GCSE_SEARCH_ENGINE_ID = "937592689593725455:msi299dkne4de"; $client = new Google_Client(); $client->setApplicationName("My_App"); $client->setDeveloperKey($GCSE_API_KEY); $service = new Google_Service_Customsearch($client); $optParams = array("cx"=>self::GCSE_SEARCH_ENGINE_ID); $results = $service->cse->listCse("lol cats", $optParams); And we can run that script again using docker:- docker run -it --...
1 comment
Read more

Ubuntu 22.04 Wayland share screen

 After switching to Dell XPS 13 which running Ubuntu 22.04, I noticed that trying to share screen through Google Meet, it shows this:-    This - Use operating system settings, I never saw it before. Usually here we will be presented the windows that we want to share.  It turned out that screen sharing in Ubuntu 22.04 indeed an issue, due to the use of Wayland instead of Xorg as its display server. Many suggested to disable wayland and back to use Xorg. I try to avoid that since Wayland seems to works fine so far. After some searching, the conclusion seems we can make this working by installing some packages. sudo apt install xdg-desktop-portal xdg-desktop-portal-gnome But it turned out that I have already installed the packages! So what were the problems?  Well, turn out it's more psychological than technical. Since the pop up is different than what I'm used to before, I never click the allow button. But clicking the allow button we will see this:-   Which...
Post a Comment
Read more

The rise of localhost

I noticed a pattern in dex world, where you build client backend to participate in the network, and then build a web app that simply connect to  localhost:someport  for the UI. To check my scuttlebutt updates, I opened up http://localhost:8027/. For those using Ethereum Parity wallet, they can open it at http://localhost:8180/. ZeroNet users are browsing at http://localhost:43110/. But Parity for example, try to make it seamless, they still provide a dns - web3.site which then redirected to home.web3.site which simply resolved to 127.0.0.1. But this I think bring up some problem, especially non-tech user which think that Parity is a website hosted by Parity Technologies. I seen this in a some articles about the latest bug .
1 comment
Read more