Login  •  Register


The time is now: Mon Nov 18, 2019 1:22 pm

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 3 of 3 [ 68 posts ]    Go to page Previous  1, 2, 3
Print view Previous topic  |  Next topic

Basilisk II OS X native GUI with presets
Poll ended at Fri Nov 08, 2019 3:16 am
Thanks, yes please! 75%  75%  [ 6 ]
Thanks for your work but not interested 13%  13%  [ 1 ]
Undecided 13%  13%  [ 1 ]
Total votes : 8
Author Message
PostPosted: Thu Oct 24, 2019 8:37 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Uploaded new version...forgot to change the version number...

Think I've fixed all the current issues... haven't had time to extensively test it.

The last thing I "fixed" was as Ronald noticed the inability to keep an alias linked to the executable...

I had to completely re-write the method of creating the prefs file for this since it originally just deleted the prefs file and wrote a new one using an outdated method of file handling.

So for now it writes two prefs files... the original as it has been with the name unchanged and a new one for testing an alias with called ".basilisk_ii_prefs_debug". Both should have identical content.

But as I haven't had a chance to completely rewrite all references to the old file handling method this is for testing purposes.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Oct 24, 2019 9:14 am 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
munkymajic wrote:
Ronald P. Regensburg wrote:
Well, I did not get far. Your app crashes immediately on launch. It may be something in my prefs file.

Edit: Sorry, your app does not crash, see below.
Very sorry. I did not pay attention and got fooled by Gatekeeper.
Your app does not crash when reading my prefs file.
Could you please explain for others how you fixed this?
I did not fix anything. I was presented the message that the app was from an unknown developer and I clicked OK without reading the message. When I realised I was not paying attention, I used right-click and chose Open from the contextual message. (If the secondary mouse button is not enabled, a control-click will do the same.) After that is done once, the app can be launched normally bij double-clicking.

Quote:
EDIT: Also what's the terminal command to apply to the app so that it can access app relative paths? Some kind of sandbox thing I guess? Will need it later for launching basilisk.
I suppose you want to open BasiliskII from the GUI app. It used to work in the old GUI, but it seems it does not work anymore in recent macOS versions. I suppose new security features interfere.

As far as I know, terminal commands can only be used to open the executable inside the application package. So you will need something like:
Code:
open BasiliskII.app/Contents/MacOS/BasiliskII
If BasiliskII is launched that way, it will only be able to use the full paths in the prefs file.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Nov 12, 2019 12:50 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Hi Ronald,

Not sure if you noticed this update from the 24th of October?

I don't have enough time to test it myself, plus it's much better to have an objective 3rd party check it as I don't notice things as much...

Cheers!

P.S. Change alias link to executable to alias link to prefs file.

munkymajic wrote:
Uploaded new version...forgot to change the version number...

Think I've fixed all the current issues... haven't had time to extensively test it.

The last thing I "fixed" was as Ronald noticed the inability to keep an alias linked to the executable...

I had to completely re-write the method of creating the prefs file for this since it originally just deleted the prefs file and wrote a new one using an outdated method of file handling.

So for now it writes two prefs files... the original as it has been with the name unchanged and a new one for testing an alias with called ".basilisk_ii_prefs_debug". Both should have identical content.

But as I haven't had a chance to completely rewrite all references to the old file handling method this is for testing purposes.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Nov 12, 2019 10:37 am 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
munkymajic wrote:
Not sure if you noticed this update from the 24th of October?
I missed that post, sorry.

Your latest "build" does indeed now save two prefs files.
(It is confusing that that build does not only have the same 0.14c version number as the previous one, but also carries the same creation and modification date and time as the previous one.)

Did anything else change compared with the previous O.14c build? I tested that one extensively and discussed it here: viewtopic.php?p=64457#p64457

Note that I may not have explained clearly enough how and why I would like file names without path to be left alone. This resulted in you implementing the local path feature for disk image files which does not do what I would like to see.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 12:32 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Hi Ronald,

Thanks for all the time you've spent testing. I'd like to try to get a version of this finished that is safe to use with real prefs files by the end of the year.

Unfortunately it doesn't make a lot of sense for me to get into it unless there's a lot of work to be done, one minor bug can usually wait until the next update.

Ronald P. Regensburg wrote:
I missed that post, sorry.

Your latest "build" does indeed now save two prefs files.
(It is confusing that that build does not only have the same 0.14c version number as the previous one, but also carries the same creation and modification date and time as the previous one.)


I don't know why Xcode does that, it's beyond my control. Btw, I'm still working on High Sierra, not that it should make a difference.

Quote:
Did anything else change compared with the previous O.14c build? I tested that one extensively and discussed it here: viewtopic.php?p=64457#p64457


Ronald P. Regensburg wrote:
I tested 0.14c concentrating on adding and removing files.

Disk images:
- With one exception:
If the GUI encounters in the prefs file a 'disk' string that is not a full path, it should display it as such and again save it as such. Showing "No Path!" for the kind is helpful to remind the user that it may not work if the name is not correct or if the file is not in the same folder as the BasiliskII application.


Thought I fixed that?

Quote:
Note that I may not have explained clearly enough how and why I would like file names without path to be left alone. This resulted in you implementing the local path feature for disk image files which does not do what I would like to see.


Yes I know what you would like, the exact same behaviour as the X11 GUI.

Quote:
"Unix Root"
I can imagine one improvement: While browsing, don't allow files to be selected. Unix Root should be a folder.


Should be fixed.

Quote:
"ROM File"
Does not work correctly with regards to the message:


Should be fixed.

Quote:
"Raw Keycodes"
Does not read the prefs file, regardless whether keycodes is set to true or false. Ticking "Use" and entering (the path to) a file in the box is saved correctly, but when the GUI is launched again both boxes are empty and saving sets it back to false with no (path to a) file name.


Should be fixed.

Additional fixes:

You could test using an alias link to the _debug prefs file and see if it breaks the alias.

Most if not all other previously mentioned issues should be fixed.

EDIT: Just downloaded and tested the app on my Mojave laptop for the first time and it crashed straight away.

Couldn't decipher the crash log, but would hazard a guess that it is breaking some sandbox rules with trying to access the local prefs file. I guess I will have to move the project to my laptop after all.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 8:07 am 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
Downloaded again. Is this again a new build? (Again the same version number and the same creation and modification dates as before.)

Code:
Just downloaded and tested the app on my Mojave laptop for the first time and it crashed straight away.
It runs fine on my Mojave (10.14.6) iMac.

There will be a planned power outage here part of the day. I will test the app later, probably next weekend.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 10:41 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Ronald P. Regensburg wrote:
Downloaded again. Is this again a new build? (Again the same version number and the same creation and modification dates as before.)

Code:
Just downloaded and tested the app on my Mojave laptop for the first time and it crashed straight away.
It runs fine on my Mojave (10.14.6) iMac.

There will be a planned power outage here part of the day. I will test the app later, probably next weekend.


No it’s not a new version since I added the debug prefs file.

I think it crashes when there’s no prefs file now, not sure. Busy moving to Xcode on my laptop.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 2:31 pm 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
Maybe this is the same issue that I encountered when I thought the app crashed when I tried the app the first time. It is probably not signed/notarized properly yet. Just try to open it the first time using the Finder contextual menu (right-click or control-click the app icon).


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 2:38 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 1092
Under Mojave, I was able to open version 0.14c (1) by double-clicking on it and selecting Open. Maybe the crash on other systems had something to do with the prefs file?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 3:11 pm 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
Indeed, when I remove the .basilisk_ii_prefs_test file, the app crashes. Before it crashes it does, however, create an empty .basilisk_ii_prefs_test file. But with the empty .basilisk_ii_prefs_test file, the app still crashes.

Didn't earlier versions create a prefs file with default configuration?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Nov 14, 2019 11:27 pm 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Ronald P. Regensburg wrote:
Indeed, when I remove the .basilisk_ii_prefs_test file, the app crashes. Before it crashes it does, however, create an empty .basilisk_ii_prefs_test file. But with the empty .basilisk_ii_prefs_test file, the app still crashes.

Didn't earlier versions create a prefs file with default configuration?


Yeah earlier versions didn’t do this. Must be the new file handling method. Think I’ll onky use it for writing. Can you please check if alias links break with the _debug prefs file?

EDIT: Well I think I found the crash bug. But haven’t recompiled. Will wait for Ronald’s next list of ransom demands :lol:


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sat Nov 16, 2019 9:26 pm 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
1. The alias to the debug prefs file stayed connected all through the testing over two days. And the contents of the test prefs file and the debug prefs file were identical after each save.

2. All previously reported issues seem to have been solved except for one small thing with the rom setting:

The "message" is now displayed when the rom line is missing or when the rom line is only "rom"
The message is not displayed when the rom line is "rom " (rom and one space).

When the box is cleared in the interface, there will still be that one space, so it would be better if the message would also be displayed then.

In fact, that is how it works with the extfs setting.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Nov 17, 2019 1:36 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Ok thanks very much for testing Ronald!

With the rom, it is because of the prefs matching system I use isn’t exact. Will look into it. A search for a matching keyword “rom” returns two matches... rom and cdrom.

I’m using match contains to get the whole line for that setting not exact match as that wouldn’t return the setting value...


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Nov 17, 2019 7:25 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Version 0.14d uploaded...

Fixed crash with no prefs file...

Removed old file handling method

Writes one prefs file using new method

Hopefully squashed the rom bug

Added an icon


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Nov 17, 2019 1:07 pm 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
munkymajic wrote:
Fixed crash with no prefs file...
check
And again creates a new prefs file with default settings

Quote:
Removed old file handling method
Writes one prefs file using new method
check
And alias stays connected

Quote:
Hopefully squashed the rom bug
check

Quote:
Added an icon

Hm, yes. How about combining that icon with the BasiliskII icon:

Image

The corresponding icon file is here: http://ronaldpr.home.xs4all.nl/emaculation/BII-GUI.icns


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Nov 18, 2019 1:20 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Hi Ronald,

Thanks for testing!

I like your icon a lot too.

I’m not 100% sure how that’s going to look scaled down to a regular icon size though?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Nov 18, 2019 6:01 am 
Offline
Inquisitive Elf

Joined: Thu Nov 08, 2018 3:04 am
Posts: 32
Some other icon options...

Image

Top left is the current icon, pixelated version of Apple's current logo to match pixelation of control panel icon.

One down is Apple Menu icon from System 7, scaled to match pixelation of cp icon.

One down is Apple Logo from the official Basilisk II website: basilisk.cebix.net

Top right is from Mac OS 8 boot screen.

One down is grayscale version.

One down is a modification of Ronald's idea.

EDIT: Since Basilisk II can run Mac OS 8, I'm not sure I understand the relevance of 6 7... unless it's the author's birth year? And a bit ironic given that neither System 6 or 7 had that happy face icon in them?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Nov 18, 2019 1:01 pm 
Online
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5617
Location: Amsterdam, Netherlands
munkymajic wrote:
I’m not 100% sure how that’s going to look scaled down to a regular icon size though?

A proper icns icon file contains images in different sizes. Here are the smaller icon images, copied directly from my icon file. All still pretty recognizable, I think.

16x16
Image

32x32
Image

64x64
Image

128x128
Image

Quote:
Since Basilisk II can run Mac OS 8, I'm not sure I understand the relevance of 6 7... unless it's the author's birth year? And a bit ironic given that neither System 6 or 7 had that happy face icon in them?
Yes, this is mentioned by others before. But it has been the icon for BasiliskII for years now. Putting the same orange 67 in the BasiliskIIGUI icon would make a nice match with the BasiliskII icon.

I tried to introduce the picture of a basilisk as icon for BasiliskII a long time ago, but that icon survived only two builds in 2008 and 2009:

Image

Edit: I do not know who made the 67 icon. It was based on a 9 (MacOS9) icon, where the 9 was replaced by 67. I was told that early BasiliskII versions could also run System 6.0.8 or even earlier. Not anymore, at least not the OSX/macOS version.


Last edited by Ronald P. Regensburg on Mon Nov 18, 2019 1:19 pm, edited 1 time in total.
 


Top
 Profile  
Reply with quote Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 3 of 3 [ 68 posts ]    Go to page Previous  1, 2, 3


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group