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!
Related
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 have to make a web application with Meanstack for a school project. I have downloaded and installed the newest version of the Mean.js boilerplate (http://meanjs.org/) and got the sample site working. But I have no idea how to continue. There are so many files in the project directory. Can somebody please tell me the files I can/need to change to start building my own app?
I'm very new to programming, so sorry if this is a stupid question. I'd really appreciate an answer.
This is what the project folder looks like.
The meanjs.org documentation (here) has plenty of great information about what each file does, and what you might need to research to get started. Besides that there are a lot of great tutorials out there, one I liked in particular was this youtube series.
Please note that in these examples I am using the mean stack from meanjs.org, not mean.io, and I am using version 0.3. If you are using a different MEAN stack, or version, I would still recommend first looking through the official documentation, and then various tutorials online.
I am trying to install LXR tp parse my working folder of linux. In some of the tutorials on the web to set it up, they are trying to use the initdb-mysql script to initialize LXR's database in mysql. Well, I can not find this script in v2.0.0 but I can see it in older versions. Is that one still valid for use with v2.0.0? If not, what script I can use to setup the db for LXR v2.0.0? or if this whole DB thing was dropped how can I proceed?
on a side note: why linux projects always lack the proper documentation?!!!! I can see they have procedure for installing LXR on their own webiste and I believe it is outdated...why not update it?
Thank you!
Don't know if you're still looking for an answer, but here is one for the record.
Creating the DB is part of LXR initialization and is considered an internal step (i.e. not end-user visible). As such, it is allowed to change along the configuration process. This is why it is crucial to follow the procedure adapted to the LXR version.
LXR 2.x is configured with a configuration wizard (scripts/configure-lxr.pl) which takes care of generating the DB structure based on a template (templates/initdb/initdb-*-template.sql). These templates are not directly usable; they must be customized by the wizard to produce an initialization script custom.d/initdb.sh which you must manually launch after the wizard has finished its job.
The whole procedure for a simple case is shown on the LXR site. From the home page, select the installation link for the version you use (note that the procedure for 1.x also applies to 2.x).
For complex cases, download and read the comprehensive user's manual from SourceForge. Once again, select the manual adapted to the LXR version.
These manuals are not outdated since the LXR project has a rule to withhold release until documentation is ready.
I'm new to CI. Anyone could help to the latest version of CI. most of the Tutorial is for last version and it didn't work for the latest version. please help.
You can still get started using what's availabe for 1.7, if you pay attention to how file structure changed between the two versions (ie the System and Application directories are now separate). To that, many of the tuts you'll find are applicable - bearing in mind that the paths may differ, and you'll want to verify that the functions are still supported in 2.0 by use of the User's Guide).
If you walked through the tut in your link, using the Models, Views, Controllers directories inside Application, you'd get a "Hello World" page.
The User's Guide is a great tool, as are the Community Forums.
Best of luck to you.
I recently migrated a site using CodeIgniter from 1.7 to 2.0. - I found the following link to be very useful:
http://philsturgeon.co.uk/news/2010/05/upgrading-to-codeigniter-2.0
I know some of the tutorials for creating Xcode project templates, for example this one here: http://robnapier.net/blog/project-templates-364
This is the best one I could find. All others basically repeat the same info, or are no longer up to date, or worse tell me that even they don't know what they're doing. Possibly useful tools that are linked to here and in other places are no longer available.
I keep running into roadblocks, and would like to gather as much information as possible on the process of creating Xcode project templates. Info that is most importantly up to date (at least it must be relevant for Xcode 3 or higher).
For example, what I'd like to see is:
a description of the
TemplateChooser.plist and similar
plist files and what these options do
(in my case, once I add a
TemplateChooser.plist, my project
disappears from the Xcode project
template list)
how to create a project template that references another .xcodeproj (when I do that, the other .xcodeproj appears in the project template list even though it doesn't use the special naming convention)
processes that can be applied, for example is it possible to run a script during the creating of a project from a template? This would be useful to unzip certain files into the newly created project.
If you have the answer or suggestions to any of the issues above, I'd appreciate that. Otherwise any link to good Xcode project template resources would be highly recommended. Especially if there is an official documentation from Apple - I haven't found one yet which seems to imply that project templates are undocumented.
Have you seen these:
http://www.sodeso.nl/?p=895
http://www.codeproject.com/KB/iPhone/CreatingXcodeProject.aspx
If you say you have searched, I'm pretty sure you've already seen the links but these are the best resources I could find with my 'googlabilities'
You might try contact this guy - http://linkedin.com/in/mottishneor he has some related messages around the web
The links suggested by FX are also not bad at all!
There is indeed little XCode template info out there. What I have found of interest are the following links (I documented myself on the topic, but haven't yet gone any further):
a Google Code search reveals a few examples, but not much
in particular, I found interesting to look at the code provided by Three20; they have some basic examples, like here
referencing another project worked for me, so maybe you could open a specific question about that giving more details?
there is information scattered on the Apple mailing-lists
there is no official documentation from Apple, as is evidenced by the lack of results to this query
I'm sorry if this is not a Enlighting, concise answer. As you said, it's not well documented, and sources are all over the place. I just hope I could highlight some places to find information that your own searches might not have reached :)
I don't have a Mac anymore, so this is as much as I can give you without testing this myself. As far as I can tell, Xcode templates are undocumented by Apple.
This guy has some guides for messing with Xcode templates but the info is pretty sparse. My suggestion for working with templateChooser.plist is to try to only edit that file in the interface builder.
This guide is a good example of how to add a reference to another .xcodeproj. For the reason you were having trouble adding a reference to your project we probably need more information.
If you scroll way down in this doc you can that each template already includes a script called myscript.sh. This script will show up in the scripts menu for projects built with that template. That isn't quite as convenient as running scripts automatically, but it's better than nothing.
In conclusion, Xcode template documentation is a nightmare. It looks like there are a lot of powerful features there, but they are obscured because of lack of user friendlyness and because documentation lags far behind Apples updates of Xcode. It just doesn't seem to be a priority for them. I hope this helps.
And yet another video link http://howtomakeiphoneapps.com/2010/10/how-to-make-custom-xcode-templates-with-video/