basilisk-devel

[B2-devel] Test clipboard SheepShaver in Mac OS X

[Ronald P. R. <ron...@xs...>]

I tested SheepShaver clipboard integration in OSX 10.7.4 (Lion) with a two SheepShaver builds from yesterday's (June 23) source, downloaded from GitHub.

One UB build was made by me using the Xcode project with XCode 3.2.6 in OSX 10.6.8.
The other x86_64 only build was made by Howard Spoelstra in OSX 10.6.8 using the command line.

The x86_64 only build and the UB build in 64-bit mode behaved identically.


Findings:
 
In 32-bit mode:

Plain text:
Works in both directions, also for accented characters.

Formatted text:
Sort of a gamble. It may work with some applications, but not consistently.

Images from MacOS to OSX:
Works, but seems to work consistently only if the MacOS application from which the image is copied uses QuickTime for displaying images, like PictureViewer and Tex-Edit Plus do.

Images from OSX to MacOS:
Works from all tested applications.


In 64-bit mode:

Plain text from OSX to MacOS:
Works, also for accented characters.

Plain text from MacOS to OSX:
Works partially: Accented characters do not arrive correctly on the OSX clipboard.

Formatted text:
Not tested.

Images from MacOS to OSX:
Works from all tested applications.

Images from OSX to MacOS:
Works only from a few applications. It works when copied from Tex-Edit Plus (OSX version), but not when copied from Preview or GraphicConverter.

Copying images form OSX to MacOS does not work at all when the MacOS clipboard is empty (after a fresh restart) or contains text. The copied image does not appear on the MacOS clipboard, text on the clipboard is not replaced. Only when the MacOS clipboard already contains an image, another image that is copied in OSX will appear on the MacOS clipboard.


Ronald P. Regensburg.

Re: [B2-devel] Test clipboard SheepShaver in Mac OS X

[Alexei S. <ale...@gm...>]

Can you file issues on our GitHub issue tracker about these problems?

https://github.com/cebix/macemu/issues

Please file one issue per specific problem and include as much info as you
can (e.g. which specific apps and OS versions you tested with), so that a
developer can easily reproduce the problem.

Thanks!

-Alexei

On Sun, Jun 24, 2012 at 7:52 AM, Ronald P. Regensburg <ron...@xs...>wrote:

>
> I tested SheepShaver clipboard integration in OSX 10.7.4 (Lion) with a two
> SheepShaver builds from yesterday's (June 23) source, downloaded from
> GitHub.
>
> One UB build was made by me using the Xcode project with XCode 3.2.6 in
> OSX 10.6.8.
> The other x86_64 only build was made by Howard Spoelstra in OSX 10.6.8
> using the command line.
>
> The x86_64 only build and the UB build in 64-bit mode behaved identically.
>
>
> Findings:
>
> In 32-bit mode:
>
> Plain text:
> Works in both directions, also for accented characters.
>
> Formatted text:
> Sort of a gamble. It may work with some applications, but not consistently.
>
> Images from MacOS to OSX:
> Works, but seems to work consistently only if the MacOS application from
> which the image is copied uses QuickTime for displaying images, like
> PictureViewer and Tex-Edit Plus do.
>
> Images from OSX to MacOS:
> Works from all tested applications.
>
>
> In 64-bit mode:
>
> Plain text from OSX to MacOS:
> Works, also for accented characters.
>
> Plain text from MacOS to OSX:
> Works partially: Accented characters do not arrive correctly on the OSX
> clipboard.
>
> Formatted text:
> Not tested.
>
> Images from MacOS to OSX:
> Works from all tested applications.
>
> Images from OSX to MacOS:
> Works only from a few applications. It works when copied from Tex-Edit
> Plus (OSX version), but not when copied from Preview or GraphicConverter.
>
> Copying images form OSX to MacOS does not work at all when the MacOS
> clipboard is empty (after a fresh restart) or contains text. The copied
> image does not appear on the MacOS clipboard, text on the clipboard is not
> replaced. Only when the MacOS clipboard already contains an image, another
> image that is copied in OSX will appear on the MacOS clipboard.
>
>
> Ronald P. Regensburg.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>

[B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

I started to file issues with SheepShaver OSX here:

https://github.com/cebix/macemu/issues

I hope someone will look into these issues. More will follow.

An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?

Ronald.

Re: [B2-devel] Various issues SheepShaver OSX

[Giulio P. <giu...@gm...>]

On 28/06/2012 19:13, Ronald P. Regensburg wrote:
> 
> I started to file issues with SheepShaver OSX here:
> 
> https://github.com/cebix/macemu/issues
> 
> I hope someone will look into these issues. More will follow.
> 
> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?

1) When you clone a repository (e.g., git clone
https://github.com/cebix/macemu.git) you have the whole history in the
.git directory in your working directory.

You can get a specific revision with the checkout command (e.g.: git
checkout <hash_tag_of_the_revision>). This will change the content of
your working directory with those of the desired revision.

You can get the revisions history (with hash tags) with the log command.
You can see which files have been changed with "git log --raw".

You can also compare directly two revisions with the diff command.

You can also have a look at the bisect command.

Remember that you also can do "git help command" to get help.

2) If you want to change something and not just find the revision that
introduced the bug, I suggest to use the fork button on github and clone
your repository instead of the main one. This will simplify merging your
changes in the main repository later.

Bests,
	Giulio.

Re: [B2-devel] Various issues SheepShaver OSX

[Alexander v. G. <kal...@un...>]

On 28.06.2012 12:13, Ronald P. Regensburg wrote:
> I started to file issues with SheepShaver OSX here:
>
> https://github.com/cebix/macemu/issues
>
> I hope someone will look into these issues. More will follow.
>
> An important issue is that SheepShaver OSX appears to have lost the 
> ability to mount CD-ROMs sometime in the past few
> months. I have no experience with GitHub and I do not know how to narrow 
> the issue down to a specific patch. With CVS
> I used to download the source from different dates to see where a specific 
> issue appeared. Can that be done here as
> well? How?


git has a great feature for finding regressions called bisect

http://webchick.net/node/99
http://alblue.bandlem.com/2011/07/git-tip-of-week-git-bisect.html

you provide a known "good" revision, and a known "bad" revision. (you don't 
*have to provide the good revision...
however it definitely narrows down the pool of all commits to tree since the 
beginning of time)

Git then will start cutting the commits in half to narrow down where the 
problem started.

  -- Alex

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Thanks for your answer. But see my answer to Giulio Paci.

Your tips would probably be useful to developers. It does not help me with what I asked for.

Best,  Ronald.


Op 28 jun. 2012, om 20:56 heeft Alexander von Gluck het volgende geschreven:

> On 28.06.2012 12:13, Ronald P. Regensburg wrote:
>> I started to file issues with SheepShaver OSX here:
>> 
>> https://github.com/cebix/macemu/issues
>> 
>> I hope someone will look into these issues. More will follow.
>> 
>> An important issue is that SheepShaver OSX appears to have lost the 
>> ability to mount CD-ROMs sometime in the past few
>> months. I have no experience with GitHub and I do not know how to narrow 
>> the issue down to a specific patch. With CVS
>> I used to download the source from different dates to see where a specific 
>> issue appeared. Can that be done here as
>> well? How?
> 
> 
> git has a great feature for finding regressions called bisect
> 
> http://webchick.net/node/99
> http://alblue.bandlem.com/2011/07/git-tip-of-week-git-bisect.html
> 
> you provide a known "good" revision, and a known "bad" revision. (you don't 
> *have to provide the good revision...
> however it definitely narrows down the pool of all commits to tree since the 
> beginning of time)
> 
> Git then will start cutting the commits in half to narrow down where the 
> problem started.
> 
>  -- Alex
> 

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Thanks for your answer. But remember that I am only a (experienced) user of SheepShaver and BasiliskII, not a developer. I filed issues I encountered as a user with builds created with recent source. I do not intend to change anything myself, I would not know how to, I hope others will solve the problems.

"Clone repository"? "Working directory"? What is my working directory? Do I have one?

I only want to be able to download the source of certain dates, to build the application from it, so I can see and report when a problem starts. That could provide information about where to look for the code that is responsible.

With CVS I knew the commands needed to do that, and I did so on several occasions. But I do not know how to do that with GitHub. Your instructions presuppose knowledge I do not have and possibly need software on my Mac I do not have installed. So far, I only accessed cebix/macemu with a web-browser and there I see only one link to download the latest revision as zip archive. I don't think I want or need the whole repository and history.

Best,  Ronald.


Op 28 jun. 2012, om 20:09 heeft Giulio Paci het volgende geschreven:

> On 28/06/2012 19:13, Ronald P. Regensburg wrote:
>> 
>> I started to file issues with SheepShaver OSX here:
>> 
>> https://github.com/cebix/macemu/issues
>> 
>> I hope someone will look into these issues. More will follow.
>> 
>> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?
> 
> 1) When you clone a repository (e.g., git clone
> https://github.com/cebix/macemu.git) you have the whole history in the
> .git directory in your working directory.
> 
> You can get a specific revision with the checkout command (e.g.: git
> checkout <hash_tag_of_the_revision>). This will change the content of
> your working directory with those of the desired revision.
> 
> You can get the revisions history (with hash tags) with the log command.
> You can see which files have been changed with "git log --raw".
> 
> You can also compare directly two revisions with the diff command.
> 
> You can also have a look at the bisect command.
> 
> Remember that you also can do "git help command" to get help.
> 
> 2) If you want to change something and not just find the revision that
> introduced the bug, I suggest to use the fork button on github and clone
> your repository instead of the main one. This will simplify merging your
> changes in the main repository later.
> 
> Bests,
> 	Giulio.

Re: [B2-devel] Various issues SheepShaver OSX

[Giulio P. <giu...@gm...>]

Il 28/06/2012 21:47, Ronald P. Regensburg ha scritto:
> 
> Thanks for your answer. But remember that I am only a (experienced) user of SheepShaver and BasiliskII, not a developer.
> I filed issues I encountered as a user with builds created with recent source.
> I do not intend to change anything myself, I would not know how to, I
hope others will solve the problems.

I see.

> "Clone repository"? "Working directory"? What is my working directory? Do I have one?

A "working directory" is the copy of the content of a specific revision
that you have on your computer.

"Clone repository" is how you get your copy starting from a git repository.

> I only want to be able to download the source of certain dates, to build the application from it, so I can see and report when a problem starts.
> That could provide information about where to look for the code that
is responsible.

> With CVS I knew the commands needed to do that, and I did so on several occasions. But I do not know how to do that with GitHub.
> Your instructions presuppose knowledge I do not have and possibly need software on my Mac I do not have installed.

The instructions I gave were about the command line tool.

Given what you said, maybe you want to try the "github for mac": you can
get it at http://mac.github.com/.

Unfortunately I never used it, so I cannot help, but I think that it
should be easy to use.

Remember that "clone" retrieve the whole repository from the net, while
"checkout" allows to move inside the repository to get a specific revision.

> I don't think I want or need the whole repository and history.

To do what you want to do, you want the whole repository (this is how
you get a specific revision with git).

Bests,
	Giulio.


> Op 28 jun. 2012, om 20:09 heeft Giulio Paci het volgende geschreven:
> 
>> On 28/06/2012 19:13, Ronald P. Regensburg wrote:
>>>
>>> I started to file issues with SheepShaver OSX here:
>>>
>>> https://github.com/cebix/macemu/issues
>>>
>>> I hope someone will look into these issues. More will follow.
>>>
>>> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?
>>
>> 1) When you clone a repository (e.g., git clone
>> https://github.com/cebix/macemu.git) you have the whole history in the
>> .git directory in your working directory.
>>
>> You can get a specific revision with the checkout command (e.g.: git
>> checkout <hash_tag_of_the_revision>). This will change the content of
>> your working directory with those of the desired revision.
>>
>> You can get the revisions history (with hash tags) with the log command.
>> You can see which files have been changed with "git log --raw".
>>
>> You can also compare directly two revisions with the diff command.
>>
>> You can also have a look at the bisect command.
>>
>> Remember that you also can do "git help command" to get help.
>>
>> 2) If you want to change something and not just find the revision that
>> introduced the bug, I suggest to use the fork button on github and clone
>> your repository instead of the main one. This will simplify merging your
>> changes in the main repository later.
>>
>> Bests,
>> 	Giulio.
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel