Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
[1] http://www.dokuwiki.org/mediamanager
Cheers, Matthew Brush
Am 25.05.2011 23:54, schrieb Matthew Brush:
Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
You could do it by using the edit page function and there is a button -> screenshot.
Cheers, Frank
On 05/25/11 23:52, Frank Lanitz wrote:
Am 25.05.2011 23:54, schrieb Matthew Brush:
Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
You could do it by using the edit page function and there is a button -> screenshot.
Have you tried it?
I'm using that button which opens the media manager where you're supposed to be able to upload images but I see no options for this. See screenshot.
Cheers, Matthew Brush
Am 26.05.2011 08:53, schrieb Matthew Brush:
On 05/25/11 23:52, Frank Lanitz wrote:
Am 25.05.2011 23:54, schrieb Matthew Brush:
Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
You could do it by using the edit page function and there is a button -> screenshot.
Have you tried it?
Yepp. See http://wiki.geany.org/start ;)
I'm using that button which opens the media manager where you're supposed to be able to upload images but I see no options for this. See screenshot.
Not sure what's not working there. Did you turn off some JS or something? I was trying it on Firefox 4 at Win7 but I'm sure it should be working also on other browsers/plattforms.
Cheers, Frank
On 05/26/11 00:10, Frank Lanitz wrote:
Am 26.05.2011 08:53, schrieb Matthew Brush:
On 05/25/11 23:52, Frank Lanitz wrote:
Am 25.05.2011 23:54, schrieb Matthew Brush:
Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
You could do it by using the edit page function and there is a button -> screenshot.
Have you tried it?
Yepp. See http://wiki.geany.org/start ;)
I'm using that button which opens the media manager where you're supposed to be able to upload images but I see no options for this. See screenshot.
Not sure what's not working there. Did you turn off some JS or something? I was trying it on Firefox 4 at Win7 but I'm sure it should be working also on other browsers/plattforms.
Firefox prefs say JS is enabled and doesn't work in stock Epiphany either ... weird. Is it just a standard HTML upload form or some type of Java/Flash Applet? I don't know if I have Java installed but I know Flash is.
Cheers, Matthew Brush
Am 26.05.2011 10:22, schrieb Matthew Brush:
On 05/26/11 00:10, Frank Lanitz wrote:
Am 26.05.2011 08:53, schrieb Matthew Brush:
On 05/25/11 23:52, Frank Lanitz wrote:
Am 25.05.2011 23:54, schrieb Matthew Brush:
Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
You could do it by using the edit page function and there is a button -> screenshot.
Have you tried it?
Yepp. See http://wiki.geany.org/start ;)
I'm using that button which opens the media manager where you're supposed to be able to upload images but I see no options for this. See screenshot.
Not sure what's not working there. Did you turn off some JS or something? I was trying it on Firefox 4 at Win7 but I'm sure it should be working also on other browsers/plattforms.
Firefox prefs say JS is enabled and doesn't work in stock Epiphany either ... weird. Is it just a standard HTML upload form or some type of Java/Flash Applet? I don't know if I have Java installed but I know Flash is.
I don't see any rocket science inside this page. Weird.
Cheers, Frank
On Thu, 26 May 2011 10:40:51 +0200, Frank wrote:
Am 26.05.2011 10:22, schrieb Matthew Brush:
On 05/26/11 00:10, Frank Lanitz wrote:
Am 26.05.2011 08:53, schrieb Matthew Brush:
On 05/25/11 23:52, Frank Lanitz wrote:
Am 25.05.2011 23:54, schrieb Matthew Brush:
Hi,
I can't seem to find the "upload form" that the Docuwiki documentation talks about[1]. I would like to insert an image (screenshot) into a page I just created.
I guess maybe the Wiki isn't configured properly to allow this? Or am I missing something?
You could do it by using the edit page function and there is a button -> screenshot.
Have you tried it?
Yepp. See http://wiki.geany.org/start ;)
I'm using that button which opens the media manager where you're supposed to be able to upload images but I see no options for this. See screenshot.
Not sure what's not working there. Did you turn off some JS or something? I was trying it on Firefox 4 at Win7 but I'm sure it should be working also on other browsers/plattforms.
Firefox prefs say JS is enabled and doesn't work in stock Epiphany either ... weird. Is it just a standard HTML upload form or some type of Java/Flash Applet? I don't know if I have Java installed but I know Flash is.
I don't see any rocket science inside this page. Weird.
/me is at fault. Frank was in the group "manager" who can do edit, create, upload and delete. The others (beside me :D) were "just" in the group "user". And this group only could edit and create. Not sure what I thought when setting up the groups, I changed it so that also user members can everything, including upload and delete.
So, Matthew could you please try again?
And please note my apologies.
Regards, Enrico
On 05/26/11 13:41, Enrico Tröger wrote:
Not sure what I thought when setting up the groups, I changed it so that also user members can everything, including upload and delete.
So, Matthew could you please try again?
Yep, it works[1]! Thank you.
And please note my apologies.
No worries.
Cheers, Matthew Brush
Le 27/05/2011 01:54, Matthew Brush a écrit :
On 05/26/11 13:41, Enrico Tröger wrote:
Not sure what I thought when setting up the groups, I changed it so that also user members can everything, including upload and delete.
So, Matthew could you please try again?
Yep, it works[1]! Thank you.
Just for 5 minutes of Python fun, the guard generation would be better with something like this:
'H_' + ''.join([c if c in 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789' else '_' for c in '{filename}'.upper().rstrip('.H')])
advantages: * handles any character in the filename (most importantly dashes) * use H_ as a prefix rather than a suffix, to avoid possible name clashes with error codes (theoretically all uppercase names starting with E[A-Z] are reserved for them)
Cheers, Colomban
PS: I'm not sure that this kind of wiki pages are the best, a more generic stuff would perhaps be better if we end up with many snippets examples, suggestions and stuff. I mean, a page that gives general explanation, and an hostile snippets list, maybe with some notes. I think it may save some reading time to the user wanting more than one.
PPS: maybe we should add some possibilities to support this with file templates, maybe providing {NORMALIZED_FILENAME} to allow guards generation?
Just for 5 minutes of Python fun, the guard generation would be better with something like this:
'H_' + ''.join([c if c in 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789' else '_' for c in '{filename}'.upper().rstrip('.H')])
advantages:
- handles any character in the filename (most importantly dashes)
- use H_ as a prefix rather than a suffix, to avoid possible name
clashes with error codes (theoretically all uppercase names starting with E[A-Z] are reserved for them)
There is also a long standing convention to use uppercase filename with non-alphanumeric characters as _ so moving the H_ to the front would make Geany guards non-standard. I think despite the (very low) possibility of clashes with error codes it would be better to leave it the right way round as the default. The user can always hand edit if there is a clash.
PPS: maybe we should add some possibilities to support this with file templates, maybe providing {NORMALIZED_FILENAME} to allow guards generation?
There is a suggestion (lost?) somewhere in the system to add {FILENAME} for this but no one has had the time or inclination to do it.
Cheers Lex
On 05/26/11 18:42, Colomban Wendling wrote:
Just for 5 minutes of Python fun, the guard generation would be better with something like this:
'H_' + ''.join([c if c in 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789' else '_' for c in '{filename}'.upper().rstrip('.H')])
advantages:
- handles any character in the filename (most importantly dashes)
- use H_ as a prefix rather than a suffix, to avoid possible name
clashes with error codes (theoretically all uppercase names starting with E[A-Z] are reserved for them)
Meh. A filename choice of 'esrc.h', 'enetunreac.h', 'ehostunreac.h', etc may provide an entertaining debugging session for the coder unfortunate enough to use those filenames :)
If you feel strongly against what's on the wiki though, there's always an 'Edit This Page' button, where you can change it :)
PS: I'm not sure that this kind of wiki pages are the best, a more generic stuff would perhaps be better if we end up with many snippets examples, suggestions and stuff. I mean, a page that gives general explanation, and an hostile snippets list, maybe with some notes. I think it may save some reading time to the user wanting more than one.
The only reason I made a separate page for 'Library Headers' was because it was a 20-ish line snippet condensed onto one line and I thought it needed more explanation and a screenshot.
That being said, as above, use the 'Edit this Page' button if you want to shuffle stuff around and/or remove superfluous text or whatever.
PPS: maybe we should add some possibilities to support this with file templates, maybe providing {NORMALIZED_FILENAME} to allow guards generation?
I'm not sure how that would work with file templates, since the 'real' filename is unknown at the time it's created, unless I misunderstand. Maybe better would be to make a litte Add-on plugin: 'Insert Header' or similar.
Cheers, Matthew Brush
On 27 May 2011 17:17, Matthew Brush mbrush@codebrainz.ca wrote:
On 05/26/11 18:42, Colomban Wendling wrote:
Just for 5 minutes of Python fun, the guard generation would be better with something like this:
'H_' + ''.join([c if c in 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789' else '_' for c in '{filename}'.upper().rstrip('.H')])
advantages:
- handles any character in the filename (most importantly dashes)
- use H_ as a prefix rather than a suffix, to avoid possible name
clashes with error codes (theoretically all uppercase names starting with E[A-Z] are reserved for them)
Meh. A filename choice of 'esrc.h', 'enetunreac.h', 'ehostunreac.h', etc may provide an entertaining debugging session for the coder unfortunate enough to use those filenames :)
If you feel strongly against what's on the wiki though, there's always an 'Edit This Page' button, where you can change it :)
PS: I'm not sure that this kind of wiki pages are the best, a more generic stuff would perhaps be better if we end up with many snippets examples, suggestions and stuff. I mean, a page that gives general explanation, and an hostile snippets list, maybe with some notes. I think it may save some reading time to the user wanting more than one.
The only reason I made a separate page for 'Library Headers' was because it was a 20-ish line snippet condensed onto one line and I thought it needed more explanation and a screenshot.
That being said, as above, use the 'Edit this Page' button if you want to shuffle stuff around and/or remove superfluous text or whatever.
PPS: maybe we should add some possibilities to support this with file templates, maybe providing {NORMALIZED_FILENAME} to allow guards generation?
I'm not sure how that would work with file templates, since the 'real' filename is unknown at the time it's created, unless I misunderstand. Maybe better would be to make a litte Add-on plugin: 'Insert Header' or similar.
IIRC the proposal was to substitute {filename} or {FILENAME} on saveas
Cheers Lex
Cheers, Matthew Brush _______________________________________________ Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Am 27.05.2011 09:54, schrieb Lex Trotman:
I'm not sure how that would work with file templates, since the 'real'
filename is unknown at the time it's created, unless I misunderstand. Maybe better would be to make a litte Add-on plugin: 'Insert Header' or similar.
IIRC the proposal was to substitute {filename} or {FILENAME} on saveas
Well, I guess ths should be discussed on geany-dev.
Cheers, Frank
