Hello everyone.
Since my last report, apart from working on the remaining changes, I have been more focused towards testing the tcp module against the already made changes. In the first week of the previous month I did try to port a testing tool to Haiku but did not succeed. So I have been writing a tool of my own to artifically inject packets into the stack and read the replies.
Hello World.
It’s been almost 3 weeks since my last update. The first evaluation was complete, I’d like
to thank Haiku for recognizing my work so far. And here’s an update on what I worked on for the past few weeks.
I replaced all IconView with BButton, since it has built in functions for label, icon handling.
I worked on categorizing all preflets based on their categories, and sorted them into
respective BBox.
TL;DR: Compiling Swift programs works, added C library interoperability and adding support for running the test-suite.
Hello Everyone,
This report covers my activities done since the first evaluation of GSoC. I spent the first week looking into the most critical aspects of the compiler and focused my attention on the TaskQueue class. Whenever a task is executed, the TaskQueue tries to read its data via a pipe and it was found that it read 0 bytes from it, despite poll() reporting that there is still data available for reading. Therefore, the compiler fails to output a executable and becomes stuck in a infinite loop; at least with the Unix implementation.
Hello Everyone!
It has been three weeks since my last blog post. In this post I would update
you with the current progress on the Calendar Application.
I have been working on the following since the past three weeks:
- Writing the Event and Category class.
- Working on UI of Event Manager.
- Working on UI of Category Manager and Category Edit Window.
- Working on a pop-up Calendar control to select event start and end date.
- Working on the Calendar View class to highlight the current system
date.
- Fixing bugs in the existing code and improvements.
- Working on Add/Modify/Delete events functionality.
- Exploring existing Haiku applications to look for widgets, trying to
implement new ones(For e.g DateTimeEdit - to select calendar start and end
date)
Add/Modify/Delete events
Basic Add/Modify/Delete events functionality is complete now. There has been
a little change from the initial mockups. Instead of switching views(I thought
of using the BCardLayout initially to switch been Day View and Add Event
section) and showing the Add Event section in the MainWindow, there will be a
separate Event Manager window for it. Event details such as Event's name, place,
description, start and end date/time can be filled. Also an event can be made
an all day event which will make it appear on the top of the Day View. Event
recurrence is not implemented currently and event category is not complete so
it's disabled for now. Because of not having a DateTimeEdit currently there's
just a text control that shows the date selected in Calendar View and a dummy
time. Also the calendar pop-up control is under work which would be a part of
DateTimeEdit. Currently, for storing purposes I am using BMessage and flat
files.
Hello again,
Sorry for late report, things are not going as I planned. In order to implement tree manipulation or copy-on-write function, I must first have a blocks/extents allocator that works well. Also, those things need to handle transactions as well.
In the previous weeks, I did some “edgy” works that are supported functions, add some on-disks structures, modify some parts of the source code, etc. Currently, I am implementing the extent allocator, it can now dump all the free extents and used extents for all roots, included backup roots. The goal is allocating continuous extents and preventing external fragmentation, but I’m stuck at it. My initial idea is using AVLTree that is existed in Haiku for tracking extents, and from that I can find a next necessary extent for allocating, but I’m not sure it is the right way. You can read all the works in my commit history[1].
Hey there, it's time for the monthly report again!
This report covers hrev51196-hrev51253.
Kernel
time_t now uses 64-bit on 64-bit systems. This fixes the year 2038 bug for
64-bit Haiku, so we can continue to run it after 2038.
This breaks the ABI, so all the 64bit packages were rebuilt.
Some bug fixes in packagefs, to avoid some annoying issues when updating the system
or repeatedly installing and uninstalling packages without rebooting.
Hello everyone. It's been substantial time since I started working on the project and here's the progress report.
On the reading end
Finally got over with reading the source code. What took it so long was that I first read most of the rfcs, including those I will be implementing even later on, before reading the current code. That kind of helped me not only to understand the code better but to also jot down the areas, where a change would have to be made, as and when encountering them. But then it consumed a lot of time as well.
Hello everyone! This report covers the span of the last two weeks of my porting efforts to get swift running on Haiku. I started debugging the runtime library ’libswiftCore’ on both Haiku and Linux and focused my attention specifically to the ImageInspection logic in order to fully understand how the runtime extracts ’type metadata’ from a swift generated shared object. My mentor korli, recommended me to use the get_next_image_info() function, which is the Haiku equivalent of iterating through the list of loaded libraries in a executable. Hence this, it was used to implement dl_iterate_phdr() in ImageInspection.cpp, taking some inspiration from the Cygwin port but parts were rewritten to be used on ELF based platforms.
Hi all,
This is my first post during the coding period of GSoC 2017. I have been working on a demo application which renders text using the harfbuzz library.The work on application started before the coding period. You can find the application here.
The work on application started before the coding period, but now the application is successfully running(Thanks to stippi!).
I pointed out few issues in one of my previous blog post. I have used the same words in Hindi for rendering in application. You will see that it is being rendered properly.
Hello World.
Now that we’re almost near to the first evaluation, and also it’s been 2 weeks since my last blog post. The last blog post had a plain vanilla GUI without any elements apart from the listview of the applications.
I worked on adding icons to the GUI, under respective categories. I’ve hardcoded the categorization part, after the first evaluation, I’ll work on categorizing the applications.
I used IconView.h along with some functions from LaunchBox. waddlesplash told me to go with BButton, so will be replacing the IconView with BButton soon as it provides easier handling of labels.
