I'm working on a README.md file in a GitHub Enterprise repository.
It's funny, I'm using the same code snippet I use in my public repositories, i.e.
Unfortunately, this kind of command doesn't work on the enterprise project.
I see one big difference in the raw version of a picture. Specifically, in the enterprise repository I have a the URL of the raw picture file with a query parameter, e.g.
?token=AAABGqiVI6Qk6Mi4ZM0ZBeHrXexkUBmNks5W_AyCwA%3D%3D
Does someone know how to embed a picture in a markdown in GutHub enterprise?
Have you tried working with using relative links to your images? So trying to do something like ? The reason why I recommend this is because if they are working with your repo, they should have these images regardless and if they are accessing this online, GitHub will handle the rendering properly. This is assuming that you want this information to be facing towards others to be able to see it.
It is actually recommended by GitHub to not use absolute links such as [Absolute README link](https://github.com/username/repo/blob/branch/docs/more_words.md) Source
Edit: I also found this question/answer on SO that might be useful to refer to about how to solve it. It also mentions with the relative linking:
GitHub recommend that you use relative links with the ?raw=true parameter to ensure forked repos point correctly.
It also talks about how you can have a separate branch that can contain all of your screenshots and you can reference them as:
Hope this helps!
Related
In this video (https://www.youtube.com/watch?v=qPHKWsZK2Jc&list=PLvv0ScY6vfd-p1gSnbQhY7vMe2rng0IL0&index=10) from about a year ago, there is example code on the SDL_CreateWindow function documentation page. I have seen other posts talking about the SDL examples.
If you look at the documentation now it is the same minus the example code
https://wiki.libsdl.org/SDL2/SDL_CreateWindow
Am I blind or is there no longer any example code on the SDL2 wiki?
If not, does anybody know what the reasons for removing it are?
I expect that
There are some official examples somewhere
If they were removed from the official wiki they would at least be placed in a 'legacy' repo or something like that.
A Google (DuckDuckGo) search gives only third party examples and, aside from a few forum posts, no mention of there ever being any examples on the wiki.
In 2022, the Wiki migrated from MoinMoin to ghwikipp. With that came a host of breaks and bugs. Your issue specifically is covered under issue #233.
The images were also broken, but that issue shows a workaround for viewing the Wiki in working form: use archive.org on wiki.libsdl.org, not wiki.libsdl.org/SDL2 where it is currently hosted. This gives you your examples back.
e.g. like this
If you have some sort of MediaWiki viewer program, you can also just pull an old revision from the Repo and read it offline. Even Github's MarkDown viewer isn't terrible. Caveat that new changes won't be reflected.
They promise us that it will be fixed at some point, and they do seem to be working hard on it. The only hardfix is either to (a) wait, or (b) help them finish their migration.
I have been playing around with FHIR for a few weeks and Extensions have been causing me some confusion. I have a resource derived from Basic that contains two extensions (one based off of ImagingStudy and the other off of Device). However, when I build the IG, I don't see the Referenced type properties available for inspection. Am I doing something incorrectly with my defintions?
I have also read that when creating extensions, I need to publish them so that they can be referenced (maybe this is part of the original problem?). Is there a good reference or tutorial that describes the publishing process? I would like to push to my local system.
Any other resources that folks could recommend to a beginner would be greatly appreciated!
Thank you very much!
oh that shouldn't happen. can you report a bug here https://github.com/HL7/fhir-ig-publisher/issues wihth a link to a github repo branch or a zip that reproduces it?
Where can I find the full API documentation of EquipmentManager? the official/unofficial docs and books keep pointing to the javadoc packages (JP170001,J1700001,J1700002) which I couldn't find.
P.S I'm looking for an online documentation (without downloading the whole software to get its documentation).
I know this answer is 3 months old, but you can find a good deal of information on Equipment Management in this Oracle Doc:
https://docs.oracle.com/cd/E16582_01/doc.91/e15144/managing_equipment.htm#EOASM00153
This doc will mention that P1702 is the Fast Path app ID to get to the application. From the application within JDE, you can run the Data Browser to view some of the underlying table information:
V1201R [F1201/1217 Equipment Master]
This app will use the view 1201R that utilizes tables F1201 and F1217.
It doesn't sound like you have the application installed, but this website will have plenty of table information for these two tables:
http://jderef.com/?schema=910&system=&table=F1217
If you find yourself struggling with the underlying tables, JDERef.com should be a good starting point.
I also found this online reference that directly mentions those Javadoc's in regards to this API. It's from version 9.0 but seems to have a good deal of information, including the tables mentioned above, and the packages you mentioned:
https://docs.oracle.com/cd/E15156_01/e1apps90pbr0/eng/psbooks/1afi/chapter.htm?File=1afi/htm/1afi09.htm
However, it seems to point mostly to where to find the Javadoc through the Enterprise One install directory (example): C:\B9\STAGINGA\java\javadoc
If you still need this exact javadoc, I can get it for you this evening. I'll just install JDE and pull it from the install directory.
UPDATE: As promised, here's the Javadocs you requested.
Link to Javadocs
UPDATE #2: This also just dawned on me, but you can go to Oracle's eDelivery website, and search for the JD Edwards Standalone software. You can scroll through the list until you see the "REL:JD Edwards EnterpriseOne Standalone 9.2.0.0". Download the 4 files and unpack them. One of the files will have a single folder inside that says DEMO. The javadocs are located in DEMO\Java\Javadocs folder. On a standard release in the real world, the DEMO folder would be the folder with the proper instance name. Good luck to you!
I am currently trying to analyse Bugzilla in order to find the ratio of number of bugs : lines of code for each Firefox component. However, I have never worked with Bugzilla before and have no knowledge of Firefox's codebase.
How would I go about finding lines of code per Firefox component (as they appear on Bugzilla under Comp header)? I have made an attempt at looking through mozilla central, but have no idea which source files relate to which components.
EDIT: Dexter pointed out that there is a directive BUG_COMPONENT in the mozilla-central tree, but this directive seems extremely incomplete and is not helpful. Any other advice, or pointers as to where I could get such advice would be much appreciated.
Great question! We recently added the BUG_COMPONENT directive (see the meta bug) to the Firefox code: it's in the moz.build file contained in each directory in the source. This directive allows linking each file in the repository to the related Bugzilla component.
For example, the following directive found here, tells that all the files in test/browser containing the Telemetry word belong to the Toolkit::Telemetry component on Bugzilla.
with Files("test/browser/*Telemetry*"):
BUG_COMPONENT = ("Toolkit", "Telemetry")
You can use either DXR or searchfox to quickly search the Firefox repository.
Updated the answer to account for the questions in the comments.
As noted in the comments, some components are tracked on Bugzilla (e.g. Activity Stream) but do not have a direct mapping to source files within the mozilla-central repository (the one Firefox is built from). That's because some newer components do not ride "the trains" (~6 weeks development cycle), but are rather updated more frequently and deployed as addons.
The code for these components usually lives under the Mozilla github account, along with other project. Since there are quite a number of projects, one way to identify the ones you might be interested in is to restrict them to JavaScript ones. If you follow this last link, you'll see the repository for both the test-pilot and Activity Stream (plus other addons).
I'm afraid the only way to match GitHub projects to Bugzilla components is to look at the name of the repository on GitHub and find the matching component in Bugzilla: you can type the name here to get some component suggestions. If you want to get fancy, you might also leverage the Bugzilla REST API:
Get a list of the JS GitHub project.
Extract the name of the project.
Use the REST API to get the component suggestion.
I would personally just consider the mozilla-central repository as a starting point, as it is mostly annotated: scrape the BUG_COMPONENT from the source files, map them to the paths then use the REST API to get the list of bugs.
Sidenote: the Download Panel seems to be correctly annotated in the main repo.
I am currently working on a Jekyll blog on Linux. However I'd like to add contributors to this blog who are using Windows and who haven't any skills in programming or using tools like Git etc.
I was wondering what could be the best process/pratice to enable them to post on the blog?
Installing them the entire environment and writing a script maybe?
Could it cause any issues due to the OS?
Any suggestions or advices are welcome :)
I don't think installing git, and pushing content to your repo is hard task for any non-tech guy.
1: Little tough way
Use team viewer and help your partner to setup git.
Allowed access to your repository.
Teach them, about frontmatter, and some jekyll commands.
2: Simple and smooth way.
Just get doc files dirctly from partner, which contain only content, nothing else, and convert yourself into markdown with manual frontmatter.
3: Create your own dashboard.
You can create your own dashoard like WordPress, where your partner can add categories, tags, title, meta description etc things, that can convert into frontmatter automatically. For that, you need to build yourself. (I find out that kind of generator here, but look's like he deleted, you can find it, by visiting him, old deleted commits).
I had the same problem so I ended up using Wordpress as the interface to it and creating a plugin to marry the systems up.
I figured I'd share it so feel free to have a look:
https://wordpress.org/plugins/wp2jekyll/