Changing default editor font on Os X
|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
 |
Changing default editor font on Os X
by Batuhan Bozkurt
::
Rate this Message:
Hi list,
I've done a nabble search but could not find something very similar. I want to change the default monospace font SC uses on OS X(monaco that is) with something else. What should I do? I want that font to be used when I "Paste without formatting" also. Any suggestions? BB. _______________________________________________ sc-users mailing list sc-users@... archive: http://www.listarc.bham.ac.uk/lists/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by Stephen Lumenta
::
Rate this Message:
You could edit your startup.rtf file (~/Application Support/SuperCollider/startup.rtf) . Mine looks like this: // m-audio Server.default.options.device = "FireWire 410 Multichannel"; // post win font Document.listener.font_(Font("Andale Mono", 10)); Document.listener.background_(Color.new255(190,190,190)); // use the default font on the help files Document.initAction_({ |doc| if(doc.path.notNil, {if("html".matchRegexp(doc.path), {}, {doc.font_(Font("Andale Mono", 12))} )}, {doc.font_(Font("Andale Mono", 12))} ); }); Stephen Am 23.06.2008 um 06:44 schrieb Batuhan Bozkurt:
|
|
|
Re: Changing default editor font on Os X
by Batuhan Bozkurt
::
Rate this Message:
Thanks, that works very fine.
BB Stephen Lumenta wrote: > You could edit your startup.rtf file (~/Application > Support/SuperCollider/startup.rtf) . > > Mine looks like this: > > // m-audio > Server.default.options.device = "FireWire 410 Multichannel"; > > // post win font > Document.listener.font_(Font("Andale Mono", 10)); > Document.listener.background_(Color.new255(190,190,190)); > > // use the default font on the help files > Document.initAction_({ > |doc| > if(doc.path.notNil, > {if("html".matchRegexp(doc.path), > {}, > {doc.font_(Font("Andale Mono", 12))} > )}, > {doc.font_(Font("Andale Mono", 12))} > ); > }); > > > Stephen > > Am 23.06.2008 um 06:44 schrieb Batuhan Bozkurt: > >> Hi list, >> >> I've done a nabble search but could not find something very similar. >> >> I want to change the default monospace font SC uses on OS X(monaco >> that is) with something else. What should I do? I want that font to >> be used when I "Paste without formatting" also. Any suggestions? >> >> BB. >> >> _______________________________________________ >> sc-users mailing list >> >> sc-users@... <mailto:sc-users@...> >> archive: http://www.listarc.bham.ac.uk/lists/sc-users/ >> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ > _______________________________________________ sc-users mailing list sc-users@... archive: http://www.listarc.bham.ac.uk/lists/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by Valentin Haller
::
Rate this Message:
where can I change the fontsize for the Insert-shortcuts (Format-Menu). When I have something to insert it works fine, but when theres nothing the font is changed. Any hints? Valentin Am 23.06.2008 um 10:06 schrieb Stephen Lumenta:
|
|
|
Re: Changing default editor font on Os X
by Patrick Dohman
::
Rate this Message:
On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote:
First I want to say thanks for the tip. Stephen's startup file does a good job of changing the font of the post window and any new windows I create but it does not effect my help files. If I execute the code directly it completes without errors but it does not apply changes to any of the help files which would be great. I tried searching the archives and google with no results and I also tried using the code on two different OS X systems. Any suggestions? Peace Patrick |
|
|
Re: Changing default editor font on Os X
by Jan Trutzschler-2
::
Rate this Message:
Hi,
help files are *.html files and they are explicitly excluded within your initAction. Remove the check for html files and it will change all files: Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; J On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: > > On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: > >> You could edit your startup.rtf file (~/Application Support/ >> SuperCollider/startup.rtf) . > >> // post win font >> Document.listener.font_(Font("Andale Mono", 10)); >> Document.listener.background_(Color.new255(190,190,190)); >> >> // use the default font on the help files >> Document.initAction_({ >> |doc| >> if(doc.path.notNil, >> {if("html".matchRegexp(doc.path), >> {}, >> {doc.font_(Font("Andale Mono", 12))} >> )}, >> {doc.font_(Font("Andale Mono", 12))} >> ); >> }); >> >> >> Stephen > > First I want to say thanks for the tip. Stephen's startup file does > a good job of changing the font of the post window and any new > windows I create but it does not effect my help files. If I execute > the code directly it completes without errors but it does not apply > changes to any of the help files which would be great. I tried > searching the archives and google with no results and I also tried > using the code on two different OS X systems. Any suggestions? > Peace > Patrick > _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by James Harkins-2
::
Rate this Message:
On Wed, Jul 2, 2008 at 6:08 PM, Jan Trutzschler <sc3@...> wrote:
> Hi, > help files are *.html files and they are explicitly excluded within your > initAction. Remove the check for html files and it will change all files: > > Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; Doing this will obliterate all formatting and make the help files harder to read. I'm not crazy about that idea -- I prefer a non-default font myself but losing the HTML formatting is too much of a sacrifice for me. hjh -- James Harkins /// dewdrop world jamshark70@... http://www.dewdrop-world.net "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by Patrick Dohman
::
Rate this Message:
Hi,
That makes sense now... I suppose what I really need is the ability to increase the font size without effecting the formating of the help files. Something akin to pressing Cmd + two or three times. Thanks! Patrick On Jul 2, 2008, at 5:08 PM, Jan Trutzschler wrote: > Hi, > help files are *.html files and they are explicitly excluded within > your initAction. Remove the check for html files and it will change > all files: > > Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; > > J > > On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: > >> >> On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: >> >>> You could edit your startup.rtf file (~/Application Support/ >>> SuperCollider/startup.rtf) . >> >>> // post win font >>> Document.listener.font_(Font("Andale Mono", 10)); >>> Document.listener.background_(Color.new255(190,190,190)); >>> >>> // use the default font on the help files >>> Document.initAction_({ >>> |doc| >>> if(doc.path.notNil, >>> {if("html".matchRegexp(doc.path), >>> {}, >>> {doc.font_(Font("Andale Mono", 12))} >>> )}, >>> {doc.font_(Font("Andale Mono", 12))} >>> ); >>> }); >>> >>> >>> Stephen >> >> First I want to say thanks for the tip. Stephen's startup file >> does a good job of changing the font of the post window and any >> new windows I create but it does not effect my help files. If I >> execute the code directly it completes without errors but it does >> not apply changes to any of the help files which would be great. I >> tried searching the archives and google with no results and I also >> tried using the code on two different OS X systems. Any suggestions? >> Peace >> Patrick >> > > > _______________________________________________ > sc-users mailing list > > > info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/ > MusicTechnology/880 > archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ > search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by Batuhan Bozkurt
::
Rate this Message:
It would be nice if we could separate the content from the designs of
the help files(i.e. like it is done with cascading style sheets). Since the help files have a visual standard(I'm not sure if it is reflected in code though) maybe this can be automated. It is not a must have feature but would be nice and writing new help files would become easier I think. I will look into the possibilities and report back. BB Patrick Dohman wrote: > Hi, > > That makes sense now... I suppose what I really need is the ability to > increase the font size without effecting the formating of the help > files. Something akin to pressing Cmd + two or three times. > Thanks! > Patrick > > On Jul 2, 2008, at 5:08 PM, Jan Trutzschler wrote: > >> Hi, >> help files are *.html files and they are explicitly excluded within >> your initAction. Remove the check for html files and it will change >> all files: >> >> Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; >> >> J >> >> On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: >> >>> >>> On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: >>> >>>> You could edit your startup.rtf file (~/Application >>>> Support/SuperCollider/startup.rtf) . >>> >>>> // post win font >>>> Document.listener.font_(Font("Andale Mono", 10)); >>>> Document.listener.background_(Color.new255(190,190,190)); >>>> >>>> // use the default font on the help files >>>> Document.initAction_({ >>>> |doc| >>>> if(doc.path.notNil, >>>> {if("html".matchRegexp(doc.path), >>>> {}, >>>> {doc.font_(Font("Andale Mono", 12))} >>>> )}, >>>> {doc.font_(Font("Andale Mono", 12))} >>>> ); >>>> }); >>>> >>>> >>>> Stephen >>> >>> First I want to say thanks for the tip. Stephen's startup file does >>> a good job of changing the font of the post window and any new >>> windows I create but it does not effect my help files. If I execute >>> the code directly it completes without errors but it does not apply >>> changes to any of the help files which would be great. I tried >>> searching the archives and google with no results and I also tried >>> using the code on two different OS X systems. Any suggestions? >>> Peace >>> Patrick >>> >> >> >> _______________________________________________ >> sc-users mailing list >> >> >> info (subscribe and unsubscribe): >> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ > > > _______________________________________________ > sc-users mailing list > > > info (subscribe and unsubscribe): > http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 > archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ > search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ > _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by andrea valle-3
::
Rate this Message:
The question has been discussed many times.
- content is not separated from visualization - the html is messy, and it's not at all standard But - the actual implementation is mainly mac-centric. - works pretty well on mac (it is integrated in the mac app), and still SC users tends to be on mac - all the help files, in case of a new format, should be converted. No, they are not consistent (I've parsed them all once) I would say that there's not a tech solution, there could be many different political solutions . I'm getting conviced of what Thor once said. It would be really important to have, like in PD, a standard GUI manager, completely portable, providing Document and GUI facilities for all platform, and thus integrating help files. But of course in a do-cracy like SC one should start doing something before complaining, and I'm not able to do that sort of things... Best -a- Ps: in any case on a mac the Helper classes works fine. They worked better before I tried to make them more linux-friendly. But this has been discussed too On 3 Jul 2008, at 00:39, Batuhan Bozkurt wrote:
-------------------------------------------------- Andrea Valle -------------------------------------------------- CIRMA - DAMS Università degli Studi di Torino --> andrea.valle@... -------------------------------------------------- " Think of it as seasoning . noise [salt] is boring . F(blah) [food without salt] can be boring . F(noise, blah) can be really tasty " (Ken Perlin on noise) |
|
|
Re: Changing default editor font on Os X
by Patrick Dohman
::
Rate this Message:
I am confused by the documentation for font_ in the Document class.
What can be accomplished with rangestart and rangesize? Is it possible to increase only the size of the fonts in the helpfiles? Would that effect the formating? On Jul 2, 2008, at 5:39 PM, Batuhan Bozkurt wrote: > It would be nice if we could separate the content from the designs > of the help files(i.e. like it is done with cascading style > sheets). Since the help files have a visual standard(I'm not sure > if it is reflected in code though) maybe this can be automated. It > is not a must have feature but would be nice and writing new help > files would become easier I think. I will look into the > possibilities and report back. > > BB > Patrick Dohman wrote: >> Hi, >> >> That makes sense now... I suppose what I really need is the >> ability to increase the font size without effecting the formating >> of the help files. Something akin to pressing Cmd + two or three >> times. >> Thanks! >> Patrick >> >> On Jul 2, 2008, at 5:08 PM, Jan Trutzschler wrote: >> >>> Hi, >>> help files are *.html files and they are explicitly excluded >>> within your initAction. Remove the check for html files and it >>> will change all files: >>> >>> Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; >>> >>> J >>> >>> On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: >>> >>>> >>>> On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: >>>> >>>>> You could edit your startup.rtf file (~/Application Support/ >>>>> SuperCollider/startup.rtf) . >>>> >>>>> // post win font >>>>> Document.listener.font_(Font("Andale Mono", 10)); >>>>> Document.listener.background_(Color.new255(190,190,190)); >>>>> >>>>> // use the default font on the help files >>>>> Document.initAction_({ >>>>> |doc| >>>>> if(doc.path.notNil, {if("html".matchRegexp >>>>> (doc.path), >>>>> {}, >>>>> {doc.font_(Font("Andale Mono", 12))} >>>>> )}, >>>>> {doc.font_(Font("Andale Mono", 12))} >>>>> ); >>>>> }); >>>>> >>>>> >>>>> Stephen >>>> >>>> First I want to say thanks for the tip. Stephen's startup file >>>> does a good job of changing the font of the post window and any >>>> new windows I create but it does not effect my help files. If I >>>> execute the code directly it completes without errors but it >>>> does not apply changes to any of the help files which would be >>>> great. I tried searching the archives and google with no results >>>> and I also tried using the code on two different OS X systems. >>>> Any suggestions? >>>> Peace >>>> Patrick >>>> >>> >>> >>> _______________________________________________ >>> sc-users mailing list >>> >>> >>> info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de: >>> 8888/MusicTechnology/880 >>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >>> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ >> >> >> _______________________________________________ >> sc-users mailing list >> >> >> info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de: >> 8888/MusicTechnology/880 >> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ >> > > > _______________________________________________ > sc-users mailing list > > > info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/ > MusicTechnology/880 > archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ > search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by Batuhan Bozkurt
::
Rate this Message:
Andrea Valle wrote:
> The question has been discussed many times. Yeah, I thought so, so I'll check the archives. > - content is not separated from visualization > - the html is messy, and it's not at all standard Actually upon little inspection, I figured its not at all that bad. There is some kind of styling at the beginnings of each help file so this is a good thing. But styles are not consistent across different help files. In my opinion, the best thing to do would be to craft a central styling for all help files to use, if I'm not missing something about the current help system. > But > - the actual implementation is mainly mac-centric. But the help files are mainly html files, which should be platform independent. Is there something I should be aware of, in terms of consistency or functionality of these files across different platforms? > - works pretty well on mac (it is integrated in the mac app), and > still SC users tends to be on mac Yeah they work well on a mac but as in this case, it is hard to have a consistent look between the editor and help files i.e. by changing the styling of the help files from a central location or with a single command. For example monaco 10px might be the default on a mac but I really dislike it and always try to change it. But in the case of help files, I feel stuck. It is also bad for accessibility I guess. > - all the help files, in case of a new format, should be converted. > No, they are not consistent (I've parsed them all once) Yeah this is the main problem, but a multi-pass batch solution might work. First pass: Since styling across help files is not consistent, maybe one could parse and collect all the styling statements in all files at a central location. Work to be done by hand: There would be many duplicate stylings listed with different class names(p1, p2, p3), then many "slight" duplicates and then maybe completely different ones. At this stage, one would need to reduce the number of different stylings probably by hand picking, eliminate the redundant ones and link/direct each old styling to a new central styling scheme(a header, a smaller header, maybe an alternative header, paragraph, code, etc. What really is needed could probably be extracted from the current help files, what is needed so far should give an idea) Second pass: This would be the actual batch rewriting of the help files. Since each styling statement is now linked to a new central styling scheme, the process would rewrite the help files to make them use the new styling by changing the tag classes etc. in respect to the work done by hand at step 2. > > I would say that there's not a tech solution, there could be many > different political solutions . > > I'm getting conviced of what Thor once said. > It would be really important to have, like in PD, a standard GUI > manager, completely portable, providing Document and > GUI facilities for all platform, and thus integrating help files. This may or may not be the way to go, I can't know by myself. As in everything that needs a change in accordance to standardization, there needs to be compromises but something will be gained by the whole process for sure. The debate of balancing things in this sense takes long, and its hard. We probably won't see this change happening soon, but if it is the way to go, I believe we are going to get there eventually. But even then, at some stage, in order not to rewrite the help files by hand, we will need to make them consistent enough to render them computer parsable anyways. Html is right for this, I think. It will continue to work now, and they will be ready when the door knocks. My 10 bits. BB > But of course in a do-cracy like SC one should start doing something > before complaining, and I'm not able to do that sort of things... > > Best > > -a- > > > Ps: in any case on a mac the Helper classes works fine. They worked > better before I tried to make them more linux-friendly. But this has > been discussed too > > On 3 Jul 2008, at 00:39, Batuhan Bozkurt wrote: > >> It would be nice if we could separate the content from the designs of >> the help files(i.e. like it is done with cascading style sheets). >> Since the help files have a visual standard(I'm not sure if it is >> reflected in code though) maybe this can be automated. It is not a >> must have feature but would be nice and writing new help files would >> become easier I think. I will look into the possibilities and report >> back. >> >> BB >> Patrick Dohman wrote: >>> Hi, >>> >>> That makes sense now... I suppose what I really need is the ability >>> to increase the font size without effecting the formating of the >>> help files. Something akin to pressing Cmd + two or three times. >>> Thanks! >>> Patrick >>> >>> On Jul 2, 2008, at 5:08 PM, Jan Trutzschler wrote: >>> >>>> Hi, >>>> help files are *.html files and they are explicitly excluded within >>>> your initAction. Remove the check for html files and it will change >>>> all files: >>>> >>>> Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; >>>> >>>> J >>>> >>>> On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: >>>> >>>>> >>>>> On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: >>>>> >>>>>> You could edit your startup.rtf file (~/Application >>>>>> Support/SuperCollider/startup.rtf) . >>>>> >>>>>> // post win font >>>>>> Document.listener.font_(Font("Andale Mono", 10)); >>>>>> Document.listener.background_(Color.new255(190,190,190)); >>>>>> >>>>>> // use the default font on the help files >>>>>> Document.initAction_({ >>>>>> |doc| >>>>>> if(doc.path.notNil, >>>>>> {if("html".matchRegexp(doc.path), >>>>>> {}, >>>>>> {doc.font_(Font("Andale Mono", 12))} >>>>>> )}, >>>>>> {doc.font_(Font("Andale Mono", 12))} >>>>>> ); >>>>>> }); >>>>>> >>>>>> >>>>>> Stephen >>>>> >>>>> First I want to say thanks for the tip. Stephen's startup file >>>>> does a good job of changing the font of the post window and any >>>>> new windows I create but it does not effect my help files. If I >>>>> execute the code directly it completes without errors but it does >>>>> not apply changes to any of the help files which would be great. I >>>>> tried searching the archives and google with no results and I also >>>>> tried using the code on two different OS X systems. Any suggestions? >>>>> Peace >>>>> Patrick >>>>> >>>> >>>> >>>> _______________________________________________ >>>> sc-users mailing list >>>> >>>> >>>> info (subscribe and unsubscribe): >>>> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >>>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >>>> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ >>> >>> >>> _______________________________________________ >>> sc-users mailing list >>> >>> >>> info (subscribe and unsubscribe): >>> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >>> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ >>> >> >> >> _______________________________________________ >> sc-users mailing list >> >> >> info (subscribe and unsubscribe): >> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ > > -------------------------------------------------- > Andrea Valle > -------------------------------------------------- > CIRMA - DAMS > Università degli Studi di Torino > --> http://www.cirma.unito.it/andrea/ > --> http://www.myspace.com/andreavalle > --> andrea.valle@... <mailto:andrea.valle@...> > -------------------------------------------------- > > > / > " > Think of it as seasoning > . noise [salt] is boring > . F(blah) [food without salt] can be boring > . F(noise, blah) can be really tasty > " > (Ken Perlin on noise) > / > > > > > _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by Dan Stowell
::
Rate this Message:
2008/7/3, Batuhan Bozkurt <batuhan@...>:
> Andrea Valle wrote: > > > The question has been discussed many times. > > > Yeah, I thought so, so I'll check the archives. > > > - content is not separated from visualization > > - the html is messy, and it's not at all standard > > > Actually upon little inspection, I figured its not at all that bad. There > is some kind of styling at the beginnings of each help file so this is a > good thing. But styles are not consistent across different help files. In my > opinion, the best thing to do would be to craft a central styling for all > help files to use, if I'm not missing something about the current help > system. > > > > But > > - the actual implementation is mainly mac-centric. > > > But the help files are mainly html files, which should be platform > independent. Is there something I should be aware of, in terms of > consistency or functionality of these files across different platforms? As already noted, there's been a lot of discussion on this before so I don't want to rehash it all, have a look at the archives. But the mac-centric "something you should be aware of" is that most helpfile editing happens on Mac, and the extreme simplicity of editing helpfile text just like any other document is important to encourage the gradual improvement of helpfile content. This is provided for by the Mac's WebKit, which is the reason that the helpfiles are auto-generated HTML without semantic markup or centralised CSS. The lack of semantic markup and centralised CSS is a drawback, but IMHO it's minor when weighed against the contributions from editors. If you come up with some great new way to do it, then I'm all ears... but do read the old conversations first because we've talked about all the usual candidates! You can guess the topics: wiki/markdown, cross-platform html editor kits, javadoc syntax, etc. > > - works pretty well on mac (it is integrated in the mac app), and still SC > users tends to be on mac > > > Yeah they work well on a mac but as in this case, it is hard to have a > consistent look between the editor and help files i.e. by changing the > styling of the help files from a central location or with a single command. > For example monaco 10px might be the default on a mac but I really dislike > it and always try to change it. But in the case of help files, I feel stuck. > It is also bad for accessibility I guess. > > > - all the help files, in case of a new format, should be converted. No, > they are not consistent (I've parsed them all once) > > > Yeah this is the main problem, but a multi-pass batch solution might work. > First pass: > Since styling across help files is not consistent, maybe one could parse > and collect all the styling statements in all files at a central location. > > Work to be done by hand: > There would be many duplicate stylings listed with different class > names(p1, p2, p3), then many "slight" duplicates and then maybe completely > different ones. At this stage, one would need to reduce the number of > different stylings probably by hand picking, eliminate the redundant ones > and link/direct each old styling to a new central styling scheme(a header, a > smaller header, maybe an alternative header, paragraph, code, etc. What > really is needed could probably be extracted from the current help files, > what is needed so far should give an idea) > > Second pass: > This would be the actual batch rewriting of the help files. Since each > styling statement is now linked to a new central styling scheme, the process > would rewrite the help files to make them use the new styling by changing > the tag classes etc. in respect to the work done by hand at step 2. > > > > > > I would say that there's not a tech solution, there could be many > different political solutions . > > > > I'm getting conviced of what Thor once said. It would be really important > to have, like in PD, a standard GUI manager, completely portable, providing > Document and GUI facilities for all platform, and thus integrating help > files. > > > This may or may not be the way to go, I can't know by myself. As in > everything that needs a change in accordance to standardization, there needs > to be compromises but something will be gained by the whole process for > sure. The debate of balancing things in this sense takes long, and its hard. > We probably won't see this change happening soon, but if it is the way to > go, I believe we are going to get there eventually. But even then, at some > stage, in order not to rewrite the help files by hand, we will need to make > them consistent enough to render them computer parsable anyways. Html is > right for this, I think. It will continue to work now, and they will be > ready when the door knocks. > > My 10 bits. > > BB > > > > > But of course in a do-cracy like SC one should start doing something > before complaining, and I'm not able to do that sort of things... > > > > Best > > > > -a- > > > > > > Ps: in any case on a mac the Helper classes works fine. They worked better > before I tried to make them more linux-friendly. But this has been discussed > too > > > > On 3 Jul 2008, at 00:39, Batuhan Bozkurt wrote: > > > > > > > It would be nice if we could separate the content from the designs of > the help files(i.e. like it is done with cascading style sheets). Since the > help files have a visual standard(I'm not sure if it is reflected in code > though) maybe this can be automated. It is not a must have feature but > would be nice and writing new help files would become easier I think. I will > look into the possibilities and report back. > > > > > > BB > > > Patrick Dohman wrote: > > > > > > > Hi, > > > > > > > > That makes sense now... I suppose what I really need is the ability to > increase the font size without effecting the formating of the help files. > Something akin to pressing Cmd + two or three times. > > > > Thanks! > > > > Patrick > > > > > > > > On Jul 2, 2008, at 5:08 PM, Jan Trutzschler wrote: > > > > > > > > > > > > > Hi, > > > > > help files are *.html files and they are explicitly excluded within > your initAction. Remove the check for html files and it will change all > files: > > > > > > > > > > Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; > > > > > > > > > > J > > > > > > > > > > On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: > > > > > > > > > > > > > > > > > > > > > > On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: > > > > > > > > > > > > > > > > > > > You could edit your startup.rtf file (~/Application > Support/SuperCollider/startup.rtf) . > > > > > > > > > > > > > > > > > > > > > > > > > > // post win font > > > > > > > Document.listener.font_(Font("Andale Mono", > 10)); > > > > > > > > Document.listener.background_(Color.new255(190,190,190)); > > > > > > > > > > > > > > // use the default font on the help files > > > > > > > Document.initAction_({ > > > > > > > |doc| > > > > > > > if(doc.path.notNil, > {if("html".matchRegexp(doc.path), > > > > > > > {}, > > > > > > > {doc.font_(Font("Andale Mono", 12))} > > > > > > > )}, > > > > > > > {doc.font_(Font("Andale Mono", 12))} > > > > > > > ); > > > > > > > }); > > > > > > > > > > > > > > > > > > > > > Stephen > > > > > > > > > > > > > > > > > > > First I want to say thanks for the tip. Stephen's startup file > does a good job of changing the font of the post window and any new windows > I create but it does not effect my help files. If I execute the code > directly it completes without errors but it does not apply changes to any of > the help files which would be great. I tried searching the archives and > google with no results and I also tried using the code on two different OS X > systems. Any suggestions? > > > > > > Peace > > > > > > Patrick > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > sc-users mailing list > > > > > > > > > > > > > > > info (subscribe and unsubscribe): > http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 > > > > > archive: > http://www.listarc.bham.ac.uk/marchives/sc-users/ > > > > > search: > http://www.listarc.bham.ac.uk/lists/sc-users/search/ > > > > > > > > > > > > > > > > > _______________________________________________ > > > > sc-users mailing list > > > > > > > > > > > > info (subscribe and unsubscribe): > http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 > > > > archive: > http://www.listarc.bham.ac.uk/marchives/sc-users/ > > > > search: > http://www.listarc.bham.ac.uk/lists/sc-users/search/ > > > > > > > > > > > > > > > > > _______________________________________________ > > > sc-users mailing list > > > > > > > > > info (subscribe and unsubscribe): > http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 > > > archive: > http://www.listarc.bham.ac.uk/marchives/sc-users/ > > > search: > http://www.listarc.bham.ac.uk/lists/sc-users/search/ > > > > > > > -------------------------------------------------- > > Andrea Valle > > -------------------------------------------------- > > CIRMA - DAMS > > Università degli Studi di Torino > > --> http://www.cirma.unito.it/andrea/ > > --> http://www.myspace.com/andreavalle > > --> andrea.valle@... <mailto:andrea.valle@...> > > -------------------------------------------------- > > > > > > / > > " > > Think of it as seasoning > > . noise [salt] is boring > > . F(blah) [food without salt] can be boring > > . F(noise, blah) can be really tasty > > " > > (Ken Perlin on noise) > > / > > > > > > > > > > > > > > > _______________________________________________ > sc-users mailing list > > > info (subscribe and unsubscribe): > http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 > archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ > search: > http://www.listarc.bham.ac.uk/lists/sc-users/search/ > -- http://www.mcld.co.uk _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by andrea valle-3
::
Rate this Message:
I agree with Dan's comment, and, me too, I don't want to rehash it too. But it's useful to point out that the main problem is exactly that Linuxers are having not a real good time for editing, and thus improving, help files. Best -a-
-------------------------------------------------- Andrea Valle -------------------------------------------------- CIRMA - DAMS Università degli Studi di Torino --> andrea.valle@... -------------------------------------------------- " Think of it as seasoning . noise [salt] is boring . F(blah) [food without salt] can be boring . F(noise, blah) can be really tasty " (Ken Perlin on noise) |
|
|
Re: Changing default editor font on Os X
by Batuhan Bozkurt
::
Rate this Message:
Thanks for all the input. I'll check the archives and see if I can come
up with something. Best BB Andrea Valle wrote: >> IMHO >> it's minor when weighed against the contributions from editors. > > I agree with Dan's comment, and, me too, I don't want to rehash it too. > But it's useful to point out that the main problem is exactly that > Linuxers are having not a real good time for editing, and thus > improving, help files. > > Best > > -a- > > >> >> If you come up with some great new way to do it, then I'm all ears... >> but do read the old conversations first because we've talked about all >> the usual candidates! You can guess the topics: wiki/markdown, >> cross-platform html editor kits, javadoc syntax, etc. >> >> >>>> - works pretty well on mac (it is integrated in the mac app), and >>>> still SC >>> users tends to be on mac >>>> >>> Yeah they work well on a mac but as in this case, it is hard to have a >>> consistent look between the editor and help files i.e. by changing the >>> styling of the help files from a central location or with a single >>> command. >>> For example monaco 10px might be the default on a mac but I really >>> dislike >>> it and always try to change it. But in the case of help files, I >>> feel stuck. >>> It is also bad for accessibility I guess. >>> >>>> - all the help files, in case of a new format, should be converted. No, >>> they are not consistent (I've parsed them all once) >>>> >>> Yeah this is the main problem, but a multi-pass batch solution >>> might work. >>> First pass: >>> Since styling across help files is not consistent, maybe one could >>> parse >>> and collect all the styling statements in all files at a central >>> location. >>> >>> Work to be done by hand: >>> There would be many duplicate stylings listed with different class >>> names(p1, p2, p3), then many "slight" duplicates and then maybe >>> completely >>> different ones. At this stage, one would need to reduce the number of >>> different stylings probably by hand picking, eliminate the redundant >>> ones >>> and link/direct each old styling to a new central styling scheme(a >>> header, a >>> smaller header, maybe an alternative header, paragraph, code, etc. What >>> really is needed could probably be extracted from the current help >>> files, >>> what is needed so far should give an idea) >>> >>> Second pass: >>> This would be the actual batch rewriting of the help files. Since each >>> styling statement is now linked to a new central styling scheme, the >>> process >>> would rewrite the help files to make them use the new styling by >>> changing >>> the tag classes etc. in respect to the work done by hand at step 2. >>> >>> >>>> >>>> I would say that there's not a tech solution, there could be many >>> different political solutions . >>>> >>>> I'm getting conviced of what Thor once said. It would be really >>>> important >>> to have, like in PD, a standard GUI manager, completely portable, >>> providing >>> Document and GUI facilities for all platform, and thus integrating help >>> files. >>>> >>> This may or may not be the way to go, I can't know by myself. As in >>> everything that needs a change in accordance to standardization, >>> there needs >>> to be compromises but something will be gained by the whole process for >>> sure. The debate of balancing things in this sense takes long, and >>> its hard. >>> We probably won't see this change happening soon, but if it is the >>> way to >>> go, I believe we are going to get there eventually. But even then, >>> at some >>> stage, in order not to rewrite the help files by hand, we will need >>> to make >>> them consistent enough to render them computer parsable anyways. Html is >>> right for this, I think. It will continue to work now, and they will be >>> ready when the door knocks. >>> >>> My 10 bits. >>> >>> BB >>> >>>> >>>> But of course in a do-cracy like SC one should start doing something >>> before complaining, and I'm not able to do that sort of things... >>>> >>>> Best >>>> >>>> -a- >>>> >>>> >>>> Ps: in any case on a mac the Helper classes works fine. They worked >>>> better >>> before I tried to make them more linux-friendly. But this has been >>> discussed >>> too >>>> >>>> On 3 Jul 2008, at 00:39, Batuhan Bozkurt wrote: >>>> >>>> >>>>> It would be nice if we could separate the content from the designs of >>> the help files(i.e. like it is done with cascading style sheets). >>> Since the >>> help files have a visual standard(I'm not sure if it is reflected in >>> code >>> though) maybe this can be automated. It is not a must have feature but >>> would be nice and writing new help files would become easier I >>> think. I will >>> look into the possibilities and report back. >>>>> >>>>> BB >>>>> Patrick Dohman wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> That makes sense now... I suppose what I really need is the >>>>>> ability to >>> increase the font size without effecting the formating of the help >>> files. >>> Something akin to pressing Cmd + two or three times. >>>>>> Thanks! >>>>>> Patrick >>>>>> >>>>>> On Jul 2, 2008, at 5:08 PM, Jan Trutzschler wrote: >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> help files are *.html files and they are explicitly excluded within >>> your initAction. Remove the check for html files and it will change all >>> files: >>>>>>> >>>>>>> Document.initAction_{|doc| doc.font_(Font("Andale Mono", 12))}; >>>>>>> >>>>>>> J >>>>>>> >>>>>>> On Jul 2, 2008, at 11:27 PM, Patrick Dohman wrote: >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> On Jun 23, 2008, at 3:06 AM, Stephen Lumenta wrote: >>>>>>>> >>>>>>>> >>>>>>>>> You could edit your startup.rtf file (~/Application >>> Support/SuperCollider/startup.rtf) . >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> // post win font >>>>>>>>> Document.listener.font_(Font("Andale Mono", >>> 10)); >>>>>>>>> >>> Document.listener.background_(Color.new255(190,190,190)); >>>>>>>>> >>>>>>>>> // use the default font on the help files >>>>>>>>> Document.initAction_({ >>>>>>>>> |doc| >>>>>>>>> if(doc.path.notNil, >>> {if("html".matchRegexp(doc.path), >>>>>>>>> {}, >>>>>>>>> {doc.font_(Font("Andale Mono", 12))} >>>>>>>>> )}, >>>>>>>>> {doc.font_(Font("Andale Mono", 12))} >>>>>>>>> ); >>>>>>>>> }); >>>>>>>>> >>>>>>>>> >>>>>>>>> Stephen >>>>>>>>> >>>>>>>> >>>>>>>> First I want to say thanks for the tip. Stephen's startup file >>> does a good job of changing the font of the post window and any new >>> windows >>> I create but it does not effect my help files. If I execute the code >>> directly it completes without errors but it does not apply changes >>> to any of >>> the help files which would be great. I tried searching the archives and >>> google with no results and I also tried using the code on two >>> different OS X >>> systems. Any suggestions? >>>>>>>> Peace >>>>>>>> Patrick >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> sc-users mailing list >>>>>>> >>>>>>> >>>>>>> info (subscribe and unsubscribe): >>> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >>>>>>> archive: >>> http://www.listarc.bham.ac.uk/marchives/sc-users/ >>>>>>> search: >>> http://www.listarc.bham.ac.uk/lists/sc-users/search/ >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> sc-users mailing list >>>>>> >>>>>> >>>>>> info (subscribe and unsubscribe): >>> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >>>>>> archive: >>> http://www.listarc.bham.ac.uk/marchives/sc-users/ >>>>>> search: >>> http://www.listarc.bham.ac.uk/lists/sc-users/search/ >>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> sc-users mailing list >>>>> >>>>> >>>>> info (subscribe and unsubscribe): >>> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >>>>> archive: >>> http://www.listarc.bham.ac.uk/marchives/sc-users/ >>>>> search: >>> http://www.listarc.bham.ac.uk/lists/sc-users/search/ >>>>> >>>> >>>> -------------------------------------------------- >>>> Andrea Valle >>>> -------------------------------------------------- >>>> CIRMA - DAMS >>>> Università degli Studi di Torino >>>> --> http://www.cirma.unito.it/andrea/ >>>> --> http://www.myspace.com/andreavalle >>>> --> andrea.valle@... <mailto:andrea.valle@...> >>>> -------------------------------------------------- >>>> >>>> >>>> / >>>> " >>>> Think of it as seasoning >>>> . noise [salt] is boring >>>> . F(blah) [food without salt] can be boring >>>> . F(noise, blah) can be really tasty >>>> " >>>> (Ken Perlin on noise) >>>> / >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> sc-users mailing list >>> >>> >>> info (subscribe and unsubscribe): >>> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >>> search: >>> http://www.listarc.bham.ac.uk/lists/sc-users/search/ >>> >> >> >> -- >> http://www.mcld.co.uk >> >> _______________________________________________ >> sc-users mailing list >> >> >> info (subscribe and unsubscribe): >> http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 >> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ >> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ > > -------------------------------------------------- > Andrea Valle > -------------------------------------------------- > CIRMA - DAMS > Università degli Studi di Torino > --> http://www.cirma.unito.it/andrea/ > --> http://www.myspace.com/andreavalle > --> andrea.valle@... <mailto:andrea.valle@...> > -------------------------------------------------- > > > / > " > Think of it as seasoning > . noise [salt] is boring > . F(blah) [food without salt] can be boring > . F(noise, blah) can be really tasty > " > (Ken Perlin on noise) > / > > > > > _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
|
|
Re: Changing default editor font on Os X
by andrea valle-3
::
Rate this Message:
An easy way, not mac centric, for input, is to have a GUI with predetermined text fields, which mirrors the Helper/Template structure.
Then, the code (e.g. Helper in the background) generates the html. Being GUI --> HTML, this (even if it forces linuxers to use SwingOSC) should work fine. For editing an existing file, one would need a HTML --> GUI conversion. This is clearly not possible for older files, but could be easy to do with files created with the previously mentioned mechanism. This will discourage future "hand" editing. Then, progressively we could convert all the help files. But, re-articulating it further: The mechanism could be GUI --> internal format --> HTML and back for editing. This will allow to map the internal format when desired to other outputs. -a- On 3 Jul 2008, at 12:35, Batuhan Bozkurt wrote:
-------------------------------------------------- Andrea Valle -------------------------------------------------- CIRMA - DAMS Università degli Studi di Torino --> andrea.valle@... -------------------------------------------------- " Think of it as seasoning . noise [salt] is boring . F(blah) [food without salt] can be boring . F(noise, blah) can be really tasty " (Ken Perlin on noise) |
|
|
Re: Changing default editor font on Os X
by andrea valle-3
::
Rate this Message:
ok
This is pretty boring! :-)
It is already defined by the Style Guide (and implemented in Helper classes) Best -a- -------------------------------------------------- Andrea Valle -------------------------------------------------- CIRMA - DAMS Università degli Studi di Torino --> andrea.valle@... -------------------------------------------------- " Think of it as seasoning . noise [salt] is boring . F(blah) [food without salt] can be boring . F(noise, blah) can be really tasty " (Ken Perlin on noise) |
|
|
Re: Changing default editor font on Os X
by nescivi
::
Rate this Message:
On Thursday 03 July 2008 06:14:04 Andrea Valle wrote:
> > IMHO > > it's minor when weighed against the contributions from editors. > > I agree with Dan's comment, and, me too, I don't want to rehash it too. > But it's useful to point out that the main problem is exactly that > Linuxers are having not a real good time for editing, and thus > improving, help files. To clarify: I basically don't bother, because it is such a hassle and it is not encouraging to hear if I do, that they don't look right on mac. sincerely, Marije _______________________________________________ sc-users mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/ |
| Free embeddable forum powered by Nabble | Forum Help |
