Opened 9 years ago

Closed 6 years ago

#6040 closed enhancement (fixed)

Vision setup info is non-existent

Reported by: Meanwhile Owned by: anevilyak
Priority: normal Milestone: R1
Component: Documentation Version:
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


First time Vision users aren't given any info on how to set it up / make a connection.
The info on the Haiku website (Userguide section) points to the Vision website, which has no info on this.
(I only got things going with the help of, which tells how to set it up in Zeta...)

Change History (13)

comment:1 Changed 9 years ago by Meanwhile

Summary: Vision setup info is non-existantVision setup info is non-existent

comment:2 Changed 9 years ago by humdinger

Agreed. Maybe BeSly would like to contribute their article to the Vision dev to put up on their site. Vision being a bundled 3rd party app, I'm not sure this ticket is warrented. I do agree, however, to provide a default profile for Vision that makes joining the #haiku channel easy and can be used as a template to see what goes where... See #4783.

comment:3 Changed 9 years ago by Meanwhile

Yes, ticket #4783 is an important one IMHO. When that one is fixed/implemented, this ticket becomes less important, as it's easier to change settings from a working example. Still, instructions like in BeSly would be the best, especially for those who are totally new to IRC or for whatever reason clueless/intimidated/in a hurry etc.

comment:4 Changed 9 years ago by anevilyak

Owner: changed from nielx to anevilyak
Status: newin-progress

comment:5 Changed 9 years ago by anevilyak

Resolution: fixed
Status: in-progressclosed

Fixed in hrev36900.

comment:6 Changed 8 years ago by diver

Resolution: fixed
Status: closedreopened

It seems that recent Vision package misses settings file again. Reopening...

comment:7 Changed 8 years ago by stargatefan

It was not on the haiku ISO from last night either and I have also had trouble with vision files copying during install. It should be made into a optional package for te time being if the BOM etc is cuasing trouble with it.

my $0.02

comment:8 Changed 8 years ago by scottmc

Does this get included with Vision rev908? Is there a specific file I should check for in the zip file to know that we have fixed this issue?

comment:9 Changed 8 years ago by scottmc

Resolution: fixed
Status: reopenedclosed

The .bep file has now been adjusted so that the VisionSettings files is included into the package. Applied to Haiku in hrev42024.

comment:10 Changed 8 years ago by diver

It doesn't auto-connect to Freenode. IIRC previous settings file did it.

comment:11 Changed 7 years ago by mmadia

Resolution: fixed
Status: closedreopened

AFAICT, when Vision was updated in hrev43523 and subsequent revisions, the settings file was omitted from the package. We could move the settings file to a separate archive inside Vision's optional package if statement

# Vision
if [ IsOptionalHaikuImagePackageAdded Vision ] {
	if $(TARGET_ARCH) != x86 {
		Echo "No optional package Vision available for $(TARGET_ARCH)" ;
	} else {
		if $(HAIKU_GCC_VERSION[1]) >= 4 {
				: $(baseURL)/ ;
		} else {
				: $(baseURL)/ ;
		InstallOptionalHaikuImagePackage vision-default-settings-<date>.zip
			: $(baseURL)/vision-default-settings-<date>.zip ;
		AddSymlinkToHaikuImage home config settings deskbar Applications
			: /boot/apps/Vision/Vision ;

However, concern has been raised that the settings file would/could overwrite existing user settings. Thoughts?

comment:12 Changed 7 years ago by anevilyak

Personally I'd be in favor of making it two separate optional packages, and simply adding the settings package to the alpha profile. That way, those of us who have our own settings can simply omit that one in our personal builds and everything's fine. Alternatively, if InstallOptionalHaikuImagePackages had an optional argument that allowed one to tell unzip to only overwrite if the source is newer, that would resolve it as well.

comment:13 Changed 6 years ago by anevilyak

Resolution: fixed
Status: reopenedclosed

Should be fixed in the latest revisions.

Note: See TracTickets for help on using tickets.