Automatic menu builder of directory structure

Does anyone have recommendations of how to create menus/links
of a directory structure that shows current folders and files
whenever the user opens the website page? The directories and files
exist on the same server that CFMX7 is installed on.
Thanks...

Better support for file based development is being working on for our 1.1 release.
-kris

Similar Messages

Feature Request: Build Favourites Menu based on Directory Structure

Hi
SQL developer is really a very nice tool and even for DBAs. I would like to request a feature in this tool which would a good value to this tool and usability. Most of us have our own scripts which we keep on using to perform day to day activities, Can we have a feature which builds a menu based on the directory structure like one of the popular tools Benthic Software's "Golden" does? It would really be a very good feature to have.
I love sql developer tool already..
regards

Better support for file based development is being working on for our 1.1 release.
-kris

Export images to a directory structure based on a collection tree?

A question:
Will lightroom have the capability to export images to a directory structure which mirrors a collections logical structure?
The reason I ask this is that when I create websites using third party tools (eg, Jalbum) I typically generate a flash or HTML based site with an menu structure for navigating the images.
So, the image interface is not simply a "flat-file" display as per the templates in Lightroom beta.
To do this, with previous image management tools (eg, iMatch) I create a hierarchy of images based on the categories (or collections) that the images are assigned to, export the images in a folder tree reflecting their categories (or collection), then use, say, Jalbum, to generate the website with the menu tree reflecting the folders/images.
This is extremely useful for more complicated image websites with categories and a large no of images.
If this function was built into Lightroom I guess it would be in the export function such that the "write to folder" box could take an argument {collection name} which would create a folder tree reflecting the collections logical tree which is being exported.
Apologies if this topic has been raised previously. But this function is extremely useful if you are using third party html tools or simply building websites by hand.
Regards
Alistair

I started simmilar thread in Lightroom Feature Requests few months ago, but can't find it anymore since new forum version...
What I can suggest as a new feature is export to directory structure from collections or second option from keywords. Probably more usable and easier to implement would be from collections.
What I need it to export many photos to different directories pretty often, and this would be great help since I could arrange them in collections and collection sets. Then select collection set and export it in a manner that collection set would be main export directory, and each collection within the set would be exported to its own folder within main collection set export folder.
This would be much appreciated feature in near future
Thank you for great product by the way

Change Directory Structure Created in MPZIP file

I'm trying to standardize my Multisim projects for inclusion in our documentation control system. As I build my project, I have a directory structure that I'm using. When I include the files in the project, the directory structure is remembered in the MPZIP file. However, the default is to unpack all files into the External(Project Name) folder. Following the help,
Extracted Path—The location to which the files will be extracted. The default is <project name>External\filename, for example project1External\amplifier.ms12. Use the drop-down lists in the Extracted Path column to select other locations as desired.
I can go in and change the directory path of each file using pull-down boxes. This makes a manual process and if I include datasheets, specifications, and dxf files, is quite time intensive. Is there a way to default to having the project to unpack to the old directory structure? Is there some other way to automate the unpacking? I can manually zip the old project structure, but other than the form of the directories, the MPZIP is so convenient.
Solved!
Go to Solution.

Hi Doug,
When you unpack the project, the default is to create a new folder and put everything together since it is unlikely that the new computer will have the same file structure as the computer where this project came from. If you want Multisim to create the same file structure as the original, you can click in the cell under "extracted path" and select the old path, if the folder doesn't exist, Multisim will create one. Unfortunately, you will have to do this for each item on the table.
Tien P.
National Instruments
Attachments:
unpack.png ‏17 KB

Organize iTunes file list by Directory Structure instead of artist/album?

Hello, I have searched for different audio players for os x which might have this feature but so far have had no luck. What I'm looking for is a feature similar to that of foobar2000 for win32 where I can organize my music by directory structure without the iTunes automatic organization by artist/album. Is there a way I can accomplish this in iTunes with some sort of xml config or hidden options? Thanks.

You don't have to have iTunes move music around on your hard drive (Preferences>Advanced>General, uncheck Keep iTunes Music folder organized and Copy files to iTunes Music folder when adding to library) but I suspect that's not what you're asking. You can't automatically view music from within iTunes by directory structure. iTunes organizes by ID3 tags ("mp3 tags"). You could, I suppose, spend a lot of time replicating your directory structure by using folders and playlists within iTunes but you'd probably have to do it all by hand.
You could check out Doug's Scripts to see if there are some scripts that might help.
http://dougscripts.com/itunes/index.php

Problems with "Open other project" in menu builder

Hi everyone,
I have a series of projects that I want to link together
using the menu builder of the "Skin Editor" dialog.
I create my menu items, and for each item choose "Open other
project" in the "On click" dropdown. I then choose the project that
I want the menu item to open. For this example, lets say I chose a
project named "Viewing_Patients"
However, when I publish the project, run it, and then use the
menu to open the next project, it just opens up a browser window
trying to access the URL "
http://Viewing_Patients.htm/
Why is that?
To check my sanity, I created a Click Box in one of the
project's slide where I chose the exact same configuration - "Open
other project" for the "On success" dropdown, and the
"Viewing_Patients" project as the project to open when the box is
clicked.
And this works fine (it opens the "Viewing_Patients" project)
Why is my menu failing but not my click box?
Thanks very much in advance for any help!
- eriiki - tubbs -

Hello Slothrop206,
Try the following steps:
1) Change your Action to be "Open URL or file"
2) Key in the relative URL to the movie you are attempting to
link. If it is in the same directory, simply key in the file name
of the .swf you are attempting to load.
3) Publish and test.
Let us know if this works for you.

Directory structure for a J2SE+J2EE project: suggestions are very welcome

Hi, I have to start coding and organizing the CVS tree of an already mature project which is J2SE. This J2SE project can be described as a "core engine" for something else, and is a quite large project, and up to now has only a command line User Interface. I organized the dir structure as this:
/build.xml
/src/
/src/java/<package>/...../*.java
/src/demo/<package/...../*.java
/src/test/<package>/....../*.java
when I ant compile, all the .classes will be done in the "build" directory (reflecting the structure in the "src" dir):
/build/
/build/java/<package>/....../*.class
/build/demo/<package/...../*.class
/build/test/<package>/..../*.class
I am happy with this, but now comes the issue: a web interface to use this core engine (it will have the same package namespace) is in developing progess, so I have to put somewhere the *.jsp, the WEB-INF dir with web.xml and servlet sources: how would you do this? And where would you let Ant put the compiled servlet classes?
I can modify the previous directory structure to accomodate the J2EE part, this is really not a problem!
Thanks to who can suggest me a clean solution
Alessio

Create a web-inf folder at the same level of src and
jsp folder inside src
i mean
/build.xml
/src/
/src/java/<package>/...../*.java
/src/demo/<package/...../*.java
/src/test/<package>/....../*.java
/src/jsp
/web-infSo, would you put in /src/jsp only the *.jsp?
And what in /WEB-INF ? What woud you put there? Would you do something like:
/WEB-INF/web.xml
/WEB-INF/src/<package>/..../<my_servlets_and_j2ee_stuff>.java
/WEB-INF/classes/<package>/..../<my_servlets_and_j2ee_stuff>.java
In this manner sources and classes are in the same tree, it does not seem very clean to me, expecially if you consider that probably I must have a "test" directory to unit test some j2ee stuff (as for the j2se stuff in "src"): how would you do that?
Is this directory structure anyway what you meant or not?
alessio

Directory Structure

I just created a network installer for Q4 Release. We have Developers, Full, and Debug licenses. The DVDs were copied to the VLM computer's harddrive. When I created the Debug configuration, the Network Installer reported the the DVDs did not have to be modified and would copy them directly. When the network installed was done, it did not create the directory structure similiar to what the help file below shows.
LabVIEW 8.0
\_SourceFiles
\Fourth Floor Engineering
\Client
vlmclient.exe
other files
setup.exe
\Applications Group
\Client
vlmclient.exe
other files
setup.exe
Figure 1. Network Installer Directory Structure
I would have expected
LabView 8.6
    \Source Files
    \Debug
        \Client
           vlmclient.exe
         setup.exe
Only the \DISK1, \DISK2, \DISK3, \DISK4 were created. The vlmclient.exe was not created.
Paul
Solved!
Go to Solution.

When you were creating the VLI, did you get a popup message that said the source did not need modification? If you saw that popup, that means VLM was not pointed to a valid source file location, which will cause a direct copy of the files with no additions.
If you select a valid source location, you should not see that message and the Product Name field should automatically populate. If you are using the Dev Suite or Platform DVDs, you will need to follow the steps in the KnowledgeBase article I refered to in my previous post.
Here is an example of what copying the installer directory could look like if you just copy the LabVIEW 8.6 Platform DVD 1:
LabVIEW 8.6 Platform DVD 1\_SourceFiles
                                                        \(the _SourceFiles directory will contain a copy of DVD 1)
                                                \LV PDS (License Set name)
                                                        \setup.exe
                                                        \Client
                                                                 \vlmclient.exe (as well as some other vlm files)
On the client machine, you would want to run "setup.exe" to begin the installation.

Directory structure mirroring

I have my mp3:s neatly organized in a directory structure on
my disk. There's where I'd like to add and remove albums,
and would like the itunes music library to automatically
update when I make changes.
I.e. if I add albums on my disk, I'd like them to appear in itunes (and on the ipod when syncing).
And if I remove albums from my disk I'd like them to
automatically disappear form itunes and the ipod.
Can I make Itunes work like this? I dont like to make all
changes twice, i.e. deleting both from the disk and then in
itunes. This gets especially irritating when moving many
albums.
Ideas? Cheers / Tom
Dell XPS PC Windows XP Pro

You need to create a form and assign it to the reconciliation process. In the form, you need waveset.organization set to where you want the user objects placed. By default, waveset.organization is set to just "Top". You can get the DN, parse it into a list and write the xml code to use the list to place each in a different virtual organization.
Start off simple, say create a container called Top:newusers. Take a copy of Empty Form and save it as orgEmpty Form or something. Define a field waveset.organization and just set its value to "Top:newusers". Then in the resource, set the reconciliation form to your new form.
Try this, once you see new ids show up in Top:newusers, you then can enhance the logic to be more sophisticated in placing objects. That is, parse the DN into a list and walk the list for a IDM waveset.organization value.
BTW, a good question to ask prospective IDM so called experts. Of 8 or so, I only met one that new how to do this efficiently.

Directory structure for the new Data Services Project

1) I do as prescribed in the manual "Building and deploying
Flex 2 Applications", page 325
"To create a web application make a copy of the /flex
directory and its contents. Rename the copy and store it in the
same location under /servers/default directory."
("flex" is an empty Flex Data Services application that
serves as a template for creating your custom application)
2) I create a corresponding project from Flex Builder 2 :
Project type: Flex Data Services
Root folder: C:\fds2\jrun4\servers\default\MyDS
Root URL:
http://localhost:8700/default/MyDS
Project name: MyDS
Project contents: C:\fds2\jrun4\servers\default\MyDS
2) I build the project
Immediately after "build project" the directory structure at
C:\fds2\jrun4\servers\default\MyDS becomes the following:
.settings
bin
----------------META-INF
----------------WEB-INF
---------------- --------------- classes
---------------- ---------------flex
--------------------------------jsp
--------------------------------lib
-------------------------------sessions
html-template
META-INF
WEB-INF
----------------classes
----------------flex
----------------jsp
----------------lib
----------------sessions
Notice that bin directory now contains another pair of
META-INF and WEB-INF in addition to those already existing in the
template project "flex".
Can anybody comment on this directory structure?
Which META-INF and WEB-INF are supposed to be used for
configuration?
What is the purpose of having two pairs of META-INF and
WEB-INF in the same web app?

Hello -
first, those folders are necessary in deployment - You need
only the contents of the bin folder for deployment, not the
sources. Since you're compiling the application locally in FB2 it
places all of the supporting and necessary files into one location
namely the "bin" folder. You'd deploy the "bin" folder's contents
to the FDS server, perhaps another FDS server that is not your
"development" server -- like a production server. The data and
configuration information that your app needs for FDS services are
stored in the WEB-INF and META-INF folders so these need to travel
with the final product. On the production server you'd just cop the
"bin" folder and it's contents to the /servers/default folder -
where you could then rename your bin folder to "MyDS"
HTH, Bill

An intelligent way to import already existing directory structure to Aperture

Hello,
is there an intelligent way to import already existing big directory structure of photographs (over 2TB) archive into Aperture?
I have my catalogue on a disk created in a way:
date - short shot description (i.e. “2011-02-14 Name Surname (portrait)”)
          Originals
          Converted
          PSD
          Final
I would like, when importing “date - short description”, it to become an Aperture Project with the same name and subfolders Originals, Converted, PSD and Final to become Aperture Albums or Folders in that Project.
The only way I found is to create a Project and Albums in that project manually and then import all the pictures from the corresponding folders, one-by-one, to Aperture’s Albums. I use references only to preserve the current archive structure on a disk as well.
thank you for your time.

You can try and experiment with the various options in File->Import Folders as Projects, specifically the option Import Folders as to see if you get what you are looking for but I doubt you will get exactly what you are looking for.
One way to achieve your goal would be to import the projects and then once that is done create the other entities (either folders or Albums) once and then paste them into each project.
The only way to truly automate this would be to write an Applescript and unless this is an ongoing requirement by the time you developed the script you could have just created the structure and pasted into the projects.

Package and Directory Structure

Hello --
I work in a group that supports 3 web sites. (b2b, b2c, b2e)
We're just beginning to develop Java in-house and
currently using Solaris and JDK 1.2.x.
I need to propose a package and directory structure strategy.
The "reverse the domain name" guideline makes sense to me.
My first thoughts are: ("classes" dir could be created anywhere)
classes/com/ppco/b2X/ <--- for .java and .class files (development)
lib/ <--- for b2X JAR files (ready for test or production)
util/ <--- for our utility classes like DBAccessor
lib/ <--- for our JAR files
sun/ <--- for classes like com.sun.mail pkg
lib/ <--- for JAR files like mail.jar
org/ <--- for classes in org.omg.CORBA pkg
lib/ <--- for JAR files
We need to handle 3rd party classes.
Development would be done in the b2X tree and JAR files would
be installed the lib/ dir for testing and release to production.
Does anyone have recommendations or experiences to share ?
Are there some things to avoid ?
Thanks !
Al

Hello Al,
you are on the right track. A typical convention I follow is:
<project>
bin - for startup scripts, etc. to run your application
build - for build scripts (not necessary if you build using your IDE. See below.)
classes - for my compiled classes
lib - for my 3rd party libraries
src - for my source code
test - for my test code (see http://junit.org/ )
That's the project hierarchy. The src (i.e. the package heirarchy) structure is another story.
As you say, you start with the reverse domain name. This is to give your packages a unique namespace. After that, your best guide is practice. Packages can be larger or smaller, depending on your coding practices. Usually you would have these (exact names may differ), plus others:
com/ppco/client
com/ppco/server
com/ppco/common
com/ppco/db
I think your break down of sun, org, etc. is a bit too much. If you would like to do so, however, I recommend you do the separation under /lib. This way, the top level project directory is not polluted by the different types of libraries in use.
Regards,
Manuel Amago.
From build above: I would suggest you always build your release distribution directly with the JDK, not using any IDE compiler. This is because Sun's JDK is the reference implementation, thus, any compatibility issues are not yours.
An easy way to achieve this is by using ANT (see http://jakarta.apache.ort/ant/ ).

Enable AppXRay on a legacy project with unconventional directory structure

I've got a legacy project. My first need is to do remote debugging of JSPs (application will be deployed on an app. server on a remote server).
I imported the existing project into Eclipse/Workshop Studio. When I try to enable AppXRay it popups a Folder Mappings dialog and asks for a folder in the project that corresponds to the '/' URI.
Here's what my directory structure looks like:
project/
--conf/
----web.xml
--htdocs/
----index.jsp
There is no WEB-INF/web.xml in the directory structure. The .war gets built by the Ant war command and just includes the web.xml from the conf/ dir.
If I choose the conf/ dir or the htdocs/ dir I get a warning that information related to web.xml will be missing fron AppXRay.
How do I get Workshop Studio to work in this situation?
As part of the Ant build I can add directories to the existing structure that mimic the structure of the .war that gets deployed if that will make Workshop Studio happy, but I cannot modify the existing directory structure significantly.
Thanks.
Dean

The WFM feature was implemented to support the project structure similar to yours.
Try the following steps to configure the project in Studio:
- The folder mapping for your project would be
project/htdocs => "/"
project/conf => "/WEB-INF"The "/" mapping will be your WebAppFolder (the folder containing web artifacts, like jsps, html...) and "/WEB-INF" would be the web configuration (containing web.xml and/or struts/jsf ... configuration filer).

Question re: Blaze DS Directory Structure Following Turnkey Installation

Hello. I've been building client-side apps with flex for a while and have started getting into backend development.
I have read up a fair bit on blaze ds and have downloaded the turnkey installation and successfully ran a few of the samples...but i have a couple of questions re: the directory structure if someone could help...i unzipped the turnkey into Blaze_ds folder on the desktop...
a) .........\Blaze_ds\tomcat\webapps\blazeds\WEB-INF - could u please explain the concept of the WEB-INF directory and the folders inside it (flex, src, classes, lib, etc.)
b) ......... \Blaze_ds\tomcat\webapps\samples - there are all the samples in here (eg. testdrive-chat, testdrive-101, dashboard, etc.)...and there is also a WEB-INF and META-INF folders...just wondering why there isn't WEB-INF/META-INF inside each sample folder
Finally, can someone also let me know the concept of localhost and the port number 8400 and are there any good books on blaze ds?
thx!

There's really not much difference. In some cases, you might already have a web application you are using so you could just copy the contents of the blazeds web app into your existing web application.
Application servers can host more than one web application and a Flex application that uses BlazeDS can be deployed on a different web app than the one where BlazeDS is running or a different server entirely so it really just depends how you want to set things up.
Hope I'm not just making things more confusing for you. . .
-Alex

How to install an entire directory structure and files with the LabVIEW installer

I think I may be missing something on how to do this - preserve a file directory structure in the LabVIEW build process.
Is there an easy way to distribute an entire directory structure (multiple directory levels/text files) and have the LabVIEW build process properly preserve and install them? I included a directory in my build specification but it completely flattened the file structure and then so when the installer builds it, the resulting structure in the /data directory is flattened as well. I'd prefer not to go through each file (~100) and setup a specific target location. Is there an easy way to preserve the file structure in the build process/installer process that I am missing (maybe a check box that I didn't see or an option setting somewhere)?
-DC

Hi DC
Sorry for the delay in responding to your question.
You should be able to do this using a 'Source Distribution' as described below:
- Right click on 'Build Specifications' and select 'New' - 'Source Distribution'
- Provide a name
- Add your files to 'Always included' under 'Source Files'
- Under 'Destinations' select 'Preserve disk hierarchy' and ensure that 'Directory' is selected as the 'Destination type'
When building an installer your can then choose to include your source distribution and it will be installed to a location of your choosing.
Hope this helps.
Kind Regards
Chris | Applications Engineer NIUK

Automatic menu builder of directory structure

Similar Messages

Maybe you are looking for