I just ran a quick test against a recent Pd-extended nightly, I downloaded Gem 0.92.3 from gem.iem.at and put it into ~/Library/Pd and now that Gem gets loaded first before the embedded one.
The problem is that the manual and examples then don't show up in the new help browser since that stuff is now based on libdirs. So if the 'doc' folder was added to the 'Gem' folder as 'manual' and the 'examples' folder was moved to the 'Gem' folder, then the Gem standalone releases would be a pretty solid libdir.
.hc
----------------------------------------------------------------------------
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hans-Christoph Steiner wrote:
The problem is that the manual and examples then don't show up in the new help browser since that stuff is now based on libdirs. So if the 'doc' folder was added to the 'Gem' folder as 'manual' and the 'examples' folder was moved to the 'Gem' folder, then the Gem standalone releases would be a pretty solid libdir.
why does it has to be called "manual"? shouldn't this "manual" path be (manually) settable via the -meta file?
and what is offered by Pd if it was indeed called "manual"? i suggest to add all the libdirs to the docbrowser. (and introduce libdir versions...)
fmadft IOhannes
On May 7, 2010, at 4:20 AM, IOhannes m zmölnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hans-Christoph Steiner wrote:
The problem is that the manual and examples then don't show up in the new help browser since that stuff is now based on libdirs. So if the 'doc' folder was added to the 'Gem' folder as 'manual' and the 'examples' folder was moved to the 'Gem' folder, then the Gem standalone releases would be a pretty solid libdir.
why does it has to be called "manual"? shouldn't this "manual" path be (manually) settable via the -meta file?
"manual" is a pretty clear, widely used term for "long-form written documentation of a particular piece of project".. Why make it settable? That just adds complexity for no advantage that I can see.
and what is offered by Pd if it was indeed called "manual"? i suggest to add all the libdirs to the docbrowser. (and introduce libdir versions...)
I guess you haven't tried the Help Browser in recent Pd-extended builds, this is implemented, and will be folded into pd-gui-rewrite/0.43
.hc
fmadft IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvjzWgACgkQkX2Xpv6ydvT/BACfdXbSNuBMGmesJxbW5nbYvT2q QDoAoL3ox6xY74BiJ583GRza9RZPZrVL =QpIn -----END PGP SIGNATURE-----
----------------------------------------------------------------------------
I hate it when they say, "He gave his life for his country." Nobody gives their life for anything. We steal the lives of these kids. - Admiral Gene LeRocque
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hans-Christoph Steiner wrote:
why does it has to be called "manual"? shouldn't this "manual" path be (manually) settable via the -meta file?
"manual" is a pretty clear, widely used term for "long-form written documentation of a particular piece of project".. Why make it settable? That just adds complexity for no advantage that I can see.
whereas "doc" could mean anything from MD to word :-)
and what is offered by Pd if it was indeed called "manual"? i suggest to add all the libdirs to the docbrowser. (and introduce libdir versions...)
I guess you haven't tried the Help Browser in recent Pd-extended builds, this is implemented, and will be folded into pd-gui-rewrite/0.43
true i haven't tried it. that's why i'm asking. i'm currently travelling and would rather not have to download PdX.
so does it do anything special about the keyword "manual"? or will it directly show all the libdir-directories in the help-browser, so a package could ship with "docs" and "exemples" and even "beispiele" and still be browseable from within the help-browser?
this makes most sense to me, as it is surely most robust against the odd developer... (i'd prefer a system that allows for oddities and still provides a somewhat uniform user experience, rather than imposing/enforcing so called "standards")
fgamsrad IOhannes
IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
why does it has to be called "manual"? shouldn't this "manual" path be (manually) settable via the -meta file?
"manual" is a pretty clear, widely used term for "long-form written documentation of a particular piece of project".. Why make it settable? That just adds complexity for no advantage that I can see.
whereas "doc" could mean anything from MD to word :-)
and what is offered by Pd if it was indeed called "manual"? i suggest to add all the libdirs to the docbrowser. (and introduce libdir versions...)
I guess you haven't tried the Help Browser in recent Pd-extended builds, this is implemented, and will be folded into pd-gui-rewrite/0.43
true i haven't tried it. that's why i'm asking. i'm currently travelling and would rather not have to download PdX.
so does it do anything special about the keyword "manual"? or will it directly show all the libdir-directories in the help-browser, so a package could ship with "docs" and "exemples" and even "beispiele" and still be browseable from within the help-browser?
this makes most sense to me, as it is surely most robust against the odd developer... (i'd prefer a system that allows for oddities and still provides a somewhat uniform user experience, rather than imposing/enforcing so called "standards")
It just shows what's in the directory. But you highlight a good reason to have standardized names: internationalization. It would be pretty easy to have 'examples' and 'manual' translated in the Help Browser, even tho the folder is called 'examples' etc. on the file system. A lot of OS's are doing it like this these days for common folders like Desktop, Documents, etc.
.hc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hans-Christoph Steiner wrote:
It just shows what's in the directory.
ah cool next release, i will put everything but a README.txt into the subfolder Gem/
But you highlight a good reason to have standardized names: internationalization. It would be pretty easy to have 'examples' and 'manual' translated in the Help Browser, even tho the folder is called 'examples' etc. on the file system. A lot of OS's are doing it like this these days for common folders like Desktop, Documents, etc.
i don't have a "Desktop" nor a "Documents" folder. instead i organize my content by type, so i have a "Directories" and a "Files" folder.
mgfasr IOhannes
On Sat, 8 May 2010, IOhannes m zmölnig wrote:
i don't have a "Desktop" nor a "Documents" folder. instead i organize my content by type, so i have a "Directories" and a "Files" folder.
hmm, so, if all regular-files go in the "Files" directory, then, you don't have much use for any subfolder of the "Directories" directory, isn't it ?
find ~/Directories -type f -exec mv '{}' ~/Files ';'
then you can remove all the empty directories, because there's nothing in them.
(I'm not really kidding, I just have no idea how your system works)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
-
Hans-Christoph Steiner -
IOhannes m zmölnig -
Mathieu Bouchard