Development

On Thu, May 7, 2015 at 4:42 PM, Brian Hague alphaseinor@xxxxxxxxx wrote: now scalable? Hm? I never had a rebuild of the Deskbar, ever... Maybe that was John Scipione you are thinking of? -Augustin ...

Whatever happened to waddlesplash's rebuild of the deskbar? are the icons now scalable? I was going to work on it for a bit then I had a fire, and my life got thrown to the sharks... not worth repeating but there were some excelent ideas for an updated deskbar way back in 06,07,08 that kept the functionality without taking up a lot of space. alphaseinor ...

264 MB

fixed:

Patches welcome as long as they get Haiku running on a MIPS platform.

On Thu, May 07, 2015 at 09:43:04PM +0200, Humdinger wrote: This means we could even remove the setting to disable the expander. +1 to both of that. If I understand Adrien correctly, he is just suggesting that the 'expand' buttons on deskbar items should always be available (no ability to disable that ...

On 7 May 2015 at 21:20, Adrien Destugues pulkomandy@xxxxxxxxxxxxx wrote: This means we could even remove the setting to disable the expander. +1 to both of that. As we're talking about Deskbar default settings, I'd also propose to have the default icon size at 32px and increase the Deskbar window width by 16px. Todays resolutions are high enough that we could spend a few pixels on some eye candy. ...

Hello, We have a DeskBar setting to enable expando mode where applications can be expanded to show a list of window. There is a small button to show the window list inside the deskbar, instead of a separate menu. Should we make this the default? It makes it much easier to reach the windows, avoiding the menu, which needs 2 clicks to reach a window. The expand mode only works with DeskBar in vertical mode. ...

Hi Andrew, Yes, HDS is designed to be used both by user browsing and rating as well I assumed that it was only for the latter purposes and that the browsing of ...

Hello; A couple of clarifications on this discussion which should probably move to the HDS mailing list... my proposal was an application catalogue with information pulled (I never said anything about syncing, logging in or editing of package metadata) ...

MemoryView: - Add hooks and supporting status tracking members to enable edit mode. When editing is requested, we allocate a duplicate copy of the current block's data to perform edits in. Currently, editing is only supported from within the hex view, and when edit mode is enabled, the view is locked to 8-bit hex mode in order to avoid any possible confusion with regards to source vs target endian orientation. - Extend Draw() to determine whether to write data from the edit data store or the actual memory block. Also implement highlighting the current edit position caret when in edit mode, as well as highlighting bytes that have been changed compared to the block's original data. MemoryView: - Add hooks and supporting status tracking members to enable edit mode. When editing is requested, we allocate a duplicate copy of the current block's data to perform edits in. Currently, editing is only supported from within the hex view, and when edit mode is enabled, the view is locked to 8-bit hex mode in order to avoid any possible confusion with regards to source vs target endian orientation. - Extend Draw() to determine whether to write data from the edit data store or the actual memory block. Also implement highlighting the current edit position caret when in edit mode, as well as highlighting bytes that have been changed compared to the block's original data.

2 mai 2015 23:25 kallisti5 kallisti5@xxxxxxxxxxx a écrit: So when you have an issue at boot, there is no guarantee that syslog will be written to disk. (99.99% of the time it isn't) This means you have to pull out the ol' serial cable to get kernel ...

2 mai 2015 22:19 Jim Saxton black.belt.jimmy@xxxxxxxxx a écrit: requirements on recipes: Bad recipes will result in bad packages which in turn will result in inconsistent package repositories and bad user experiences. Since the dependency resolution process has to work repository-wide and library installations are system-wide, a broken package can easily have effects beyond the respective software not working correctly. ...

I own a Gumstix Overo Fire card with a TI OMAP processor - two cores, one an ARM Cortex A8, the other a TI c6xxx DSP. It has an I/O daughtercard with lots of ports, including 1024x768 video, USB and serial. I'd love to help with an ARM port. My sister and her husband lent me their Android phones after they bought new ones; I'm not real sure they'd ever want them back. It would be quiet cool to get Haiku to run on what would otherwise be ...

how about syslogging into a dedicated partition? You'd need to set the partition up ahead of time, then identify it in the boot parameters. A userspace tool to dump it out after a successful boot would be straightforward. If you had a second partition with a known-good OS, you'd boot, crash, boot into that good OS then examine the partition syslog. Michael David Crawford, Consulting Software Engineer mdcrawford@xxxxxxxxx ...

On 2015-05-02 16:27, kallisti5 wrote: On 2015-05-02 11:35, Ingo Weinhold wrote: On 02.05.2015 17:12, kallisti5 wrote: No clue why I never thought of this. So when you have an issue at boot, there is no guarantee ...

On 2015-05-02 11:35, Ingo Weinhold wrote: On 02.05.2015 17:12, kallisti5 wrote: No clue why I never thought of this. So when you have an issue at boot, there is no guarantee that syslog will be written to disk. (99.99% of the time it isn't) ...

On Sat, May 2, 2015 at 4:21 PM, Jim Saxton black.belt.jimmy@xxxxxxxxx wrote: not build or build and do not run or do not call out their dependencied properly, in haikuports are the onse produced by these same people who nit-pick line breaks etc. just my observaqtion and experiance. ...

* This version actually works. * This version actually works.

On 5/2/15, Ingo Weinhold ingo_weinhold@xxxxxx wrote: requirements on recipes: Bad recipes will result in bad packages which in turn will result in inconsistent package repositories and bad user experiences. Since the dependency resolution process has to work repository-wide and library installations are system-wide, a broken package can easily have effects beyond the respective software not working correctly. ...

* Update libvorbis x86_64 package. * Update libvorbis x86_64 package.